SmartDeploy supports two ways for clients to communicate with the SmartDeploy Console Service:
Local-first (default): the client tries the console over the local network first, then fails over to cloud.
Cloud-only: the client connects directly to the SmartDeploy Cloud Broker Service in Azure and does not attempt local console communication.
This architecture enables cloud-connected deployments without exposing your console host to the public internet.
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.)
You can identify which connection type a client is using by checking the Computer Management interface, where each client will display either "Local" or "Cloud" as its connection type. This visibility allows you to quickly verify that clients are connecting through your preferred method.
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.
Where the Config File is (on the Endpoint):
On Windows clients running the SmartDeploy Client Service, the file is in:
C:\Program Files\SmartDeploy\ClientService\ClientConfig.json
What to Change to Force a Cloud Connection:
- Open Services.msc and stop the SmartDeploy Client Service
- Edit ClientConfig.json as Administrator
- Set: "ConnectionType": 2 (forces Cloud)
- Save the file
- Start the SmartDeploy Client Service again
How to Change it from a Cloud Connection to a Local Connection:
If the workstation is connected to the same network as your SmartDeploy Console you would want to restart the service below on the workstation:
- SmartDeploy Client Service (SDClientService)
