BradAtkins

That works for me.




Thanks!

I think there are 2 different categories of customer here.
1st category uses a proxy. (Some have proxy installed on Linux, and some have proxy installed on Windows Server.) 2nd category doesn't use a proxy.  We have ESET Endpoint Security installed on Windows 10 endpoints.  You have to read between the lines in the posts above to tell which customer is in which category.
I'm in the 2nd category, we don't use a proxy, and yet we get the same error message.  (Please go back to my original post to see my screenshots.)  So, our problem is not caused by a proxy.
It seems to me, just based on experience, this seems like a problem with startup order.  When the Windows 10 endpoint boots up, maybe ESET client attempts to contact the management system before the OS has all the networking services up and running.  If this wild guess is correct, it could be solved by changing the startup order, or trying again later long after bootup is complete.
I solved the problem for myself by switching the License Interval Check from Limited to Automatic.  So, if my wild guess is correct, the Limited setting only checks once early in Windows bootup.  So, I switched the setting to Automatic, and the error went away with repeated connection attempts.
I'm well aware this is a wild- guess, I could be completely wrong about the reasons.  But the end result - problem solved by switching to Automatic.

I think there are 2 different categories of customer here.
1st category uses a proxy. (Some have proxy installed on Linux, and some have proxy installed on Windows Server.) 2nd category doesn't use a proxy.  We have ESET Endpoint Security installed on Windows 10 endpoints.  You have to read between the lines in the posts above to tell which customer is in which category.
I'm in the 2nd category, we don't use a proxy, and yet we get the same error message.  (Please go back to my original post to see my screenshots.)  So, our problem is not caused by a proxy.
It seems to me, just based on experience, this seems like a problem with startup order.  When the Windows 10 endpoint boots up, maybe ESET client attempts to contact the management system before the OS has all the networking services up and running.  If this wild guess is correct, it could be solved by changing the startup order, or trying again later long after bootup is complete.
I solved the problem for myself by switching the License Interval Check from Limited to Automatic.  So, if my wild guess is correct, the Limited setting only checks once early in Windows bootup.  So, I switched the setting to Automatic, and the error went away with repeated connection attempts.
I'm well aware this is a wild- guess, I could be completely wrong about the reasons.  But the end result - problem solved by switching to Automatic.

OK, that works!
I created a Live Installer package that only included the Management Agent.  And that installed on the Azure VM with no problems and checked into our Cloud Manager.
Then I ran the efsw_nt64.msi installer.
I was able to apply the license from the cloud.  
All is well, thanks!