As far as I know, the communication is from beacon to app server, how did you test port?
Also when you configured the beacon you need to import the beacon configuration file, which contain an BeaconID which need to be identical with the BeaconID configured in your WebUI.
After beacon config file is imported, did you test from beacon interface the upload location?
Did you receive some errors?
Good evening/morning for everyone.
We do think that yes, we did those checkings.
We do use from the beacons the root url from all-in-one itam , on all 3 URL settings and we download with success. https://ITAM_FQDN/
Afterwards, we can do the IExplorer test on the ManagesoftRL/test . No certificates problems; althought being self-signed on the beacon part (on ITAM all-in.one they are validable with CRL certificates).
Thanks for your attention and effort. What else could prevent the Beacon to download their policy?
We have other environments, also on cloud, and on them is only necessary to have Local Admin or System account on the beaconengine service to succeed.