This page describes the best practice for when you want to keep the CSMS service deactivated in the Horizon Cloud Connector. All tenants in the cloud plane are created to have the CMS initially enabled by default and remain that way unless you explicitly toggle it off. If the CSMS service is in a deactivated state within a pod's Horizon Cloud Connector and the tenant account has the Cloud Monitoring Service (CMS) setting toggled on, a
sync failed error is reported for that pod.
If you want to keep CSMS deactivated in the Horizon Cloud Connector, a best practice is to log in to the Horizon Universal Console and toggle off the CMS setting in your tenant account before you pair the pod with the Horizon Cloud Connector. The Cloud Monitoring Service (CMS) is one of the cloud-plane services provided to each tenant, while the CSMS service is a microservice that runs within the Horizon Cloud Connector to communicate with that CMS in the cloud plane. Some deployments of the Horizon Cloud Connector appliance will have the CSMS service deactivated by default, such as when you select use of the Basic Profile for version 1.9. In such deployments, you can optionally activate the CSMS service when you are ready to take advantage of the cloud-plane's Cloud Monitoring Service's features.
However, when the CSMS service is not running in the Horizon Cloud Connector at the same time when the CMS toggle is enabled for your tenant, a
sync failed error is reported for that pod. In this use case where you want to leave the CSMS microservice inactive, to prevent having this
sync failed message, you should toggle off the Cloud Monitoring Service in your tenant account before pairing the pod with the Horizon Cloud Connector.
To toggle off the Cloud Monitoring Service in your tenant account, log in to the Horizon Universal Console at cloud.horizon.vmware.com. If your tenant has no pods yet, the Getting Started page of the console should be visible to you right after you log in. The CMS toggle is located within the Cloud Monitoring Service row under the General Setup menu. Expand General Setup, click Edit within the Cloud Monitoring Service row, and toggle off the Cloud Monitoring Service. After it is toggled off, then you can proceed with pairing the pod with the CSMS microservice not running in the Horizon Cloud Connector and avoid the
sync failed message at the same time.