Jump to content

Smart Deploy Agent

Recommended Posts

If you're talking about clients on the same local network as your console host, then it should be within about 3-5 minutes after the service starts. (It is on a delayed start, so give it extra time if the client has just booted.) If it's not connecting, then check that the service started successfully, and look for errors in the Application log in Event Viewer. 

If you're talking about off-site clients and connecting through the cloud, you want to make sure that you used the non-fqdn name of your console host, and not an IP. Additionally, you want to make sure that your console hostname isn't externally accessible from the internet. 

Lastly, you may need to block access to your console host via VPN if you want to use the remote/cloud deployments. (You can create a CNAME alias for you to use as an administrator if you need to RDP to the host yourself.) This is because the clients need to fail to reach the console host to switch to the cloud. If they can reach the host, it can get stuck in a semi-functional state, and fail to appear in the console. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...