Once the client is installed on a workstation, the workstation sends inventory data to the CM Current Branch servers and can be managed via the console. 

CM Client Requirements

The only requirement besides installing the client is the GPO CIT-IDM-MachineCertificateAutoEnrollment needs to be applied to the OU that the clients are in.

This enrolls devices in the Client Authentication Certificate necessary to facilitate the PKI communication. PKI is the primary authentication method between the CM server and clients.

Install via Imaging

The primary way to install the CM client is to image the device. This will install the CM client and perform other tasks that allow the device to function within the Cornell IT environment as expected.

If you encounter a unique scenario and need to mass deploy the CM client to many devices without imaging them, please reach out for assistance at Endpoint Infrastructure and Engineering | IT@Cornell.

Manual Installation

1. On the client computer, navigate to \\files.cornell.edu\CIT\CMConsole\OITFS\CM_Client
2. "Run as Administrator" ccmsetup_rem.bat

Manual Un-Install

1. On the client computer, navigate to \\files.cornell.edu\CIT\CMConsole\OITFS\CM_Client
2. "Run as Administrator" ccm_uninst.bat

Imaging

See Operating System Deployment or Deploy a Task Sequence.

CM Client Tips

• We suggest that you copy the GPO listed on this page to your OU and apply them from there.
• Devices that are not imaged, and are instead manually configured, can run into many problems. A non-exhaustive list of example issues is below:
  • Configuration drift occurs when devices are not configured in a consistent way, resulting in unexpected behavior.
  • Unsupported vendor software installed by the OEM can sometimes cause issues on devices.