We were about to roll out fresh agent installation on azure side. We were testing couple of devices & every time it went partially successful though in installation log we observed not completed (strange thing is , whichever OS agent package we use for different flavored OS , we noticed one string in the installation log like "Installation NOT APPLICABLE “ManageSoft for Solaris (x86) Managed Devices[common](19.0.0)” , which we've never seen in the past at the time of agent 17 or 18 roll out. We had used the same package 4 months before & it went successful but not this time.
We were about to roll out fresh agent installation on azure side. We were testing couple of devices & every time it went partially successful though in installation log we observed not completed (strange thing is , whichever OS agent package we use for different flavored OS , we noticed one string in the installation log like "Installation NOT APPLICABLE “ManageSoft for Solaris (x86) Managed Devices[common](19.0.0)” ,RTasks which we've never seen in the past at the time of agent 17 or 18 roll out. We had used the same package 4 months before & it went successful but not this time.
Here are some of the suggestions that I found:
Check if the serial number of the device is already appearing on the compliance DB or UI. If yes, you may need to delete the duplicate device record or use a different serial number.
Rerun the mgspolicy.exe with the -t machine flag on the device. This will force a policy update and may help the device to check-in.
Ensure that the device can resolve the beacon server name and connect to the beacon server port. You can use NSLOOKUP and TELNET commands to test this.
Verify that the agent package you are using matches the OS type and architecture of the device. You can find the agent packages for different OS types in the following folder on your beacon server: C:\ProgramData\Flexera Software\Staging\Common\Packages\FlexeraAdoption <version> Rev1.0.
