Hi Everyone, I just wanted to provide an update on this to perhaps assist others in the future who experience similar error messages. Turns out it was some stale data in the Beacon table/s that was being captured in the Beacon Policy that caused some additional packages to be downloaded. In my scenario it was downloading Beacon versions of 13, 16 and 17. My current version was 16 when the errors began, it was suggested to upgrade the Beacon version because 16 was no longer available. I went ahead and upgraded all of my 5 Beacons to 17 but the trouble still remained afterwards, however, version 16 was removed from the list of packages being downloaded. After looking at the packageretriever logs and the Beacon Policy we could see that version 13 was still being picked up and in turn causing the downloading errors. By checking the dates on the Downloaded packages which are kept locally on the Beacons we were able to clearly identify what package version/s were causing the trouble. Engineering became involved and identified that the Beacon Table had some old versions which we being included into the Beacon Policy which triggered the additional packages being downloaded and subsequently causing the authenticode errors.
To resolve this, a Hot Fix was deployed to our Cloud environment instance that cleared out the old versions and everything returned to normal after the next updated Beacon Policy was received by the Beacons. The two key areas to look at were the packageretriever log file along with the Beacon Policy which both identified the old versions. In addition, the downloaded package dates which are kept locally on the Beacon Servers were also very important in piecing togeather what was occurring since the dates on the files reflected that something had happened recently as the dates should always be current.
Hope that helps ...
Bruce
