When the SmartDeploy client service starts, it will attempt to reach the SmartDeploy console service on the host that is specified in the answer file or client installation package using an https request on the local network. If the client service cannot connect to the console service on the local network after 5 minutes, it automatically connects to the SmartDeploy cloud broker service in Azure.
Note: If the answer file or client installation package is configured as cloud only, it does not try to connect to the console service on the local network. Instead, it connects directly to the cloud broker service in Azure. (Version 3.0.1 or newer is required for cloud only.)
SmartDeploy client installations have a unique identifier for your account and use that to register as a cloud-connected client. The client service checks for new messages (deployments) from the console service host that it’s assigned to every 5 minutes.
The SmartDeploy console service is always connected to this same service and periodically checks for new clients registered as a cloud client assigned to its host name. New deployments to cloud-connected clients are sent to the cloud broker service as a message, and within 5 minutes the target client performs its check, receives the deployment message, and begins.
The SmartDeploy cloud broker service facilitates the communication between the console host and the clients assigned to it. This removes the need for exposing your SmartDeploy console host to the internet or otherwise forwarding ports form external addresses to your console host.
