1 of 1 people found this helpful
Frequency is exactly the same as it would internally. Components such as inventory try direct connection and then gateway.
Did the machines get assigned a certificate for the gateway? In the latests builds, remote control seems to work OK, but without a gateway certificate the others won't work.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
The One-Stop Shop for LANDesk Enhancements
Update - New Stand-Alone State Notifier Console for Service Desk Operators
Update - State Notifier now detects machine and user Idle states
Update - WoW & State Notifier now integrate for even more functionality
-Make sure you have run brokerconfg on the client to retrieve a certificate
--This can be done on network using brokerconfig.exe /r or running the brokerconfig.exe and pressing send
--Off network requires credentials that are a member of the management suite group, you can manually enter them or use doc 1888 to automate the process.
-Make sure you are using the core name not IP or a DNS Alias
Thanks guys, after running BrokerConfig I was able to run a Vulnerability scan and it now shows up in my console, thank you.
My next question is (and I'll try looking up this answer too) is there a way automate this process or preconfigure it somehow? We recently updated our agents to be able to "enable cloud services" which I thought took care of the BrokenConfig process.
I assume deploying updated agents isn't enough?