Information and troubleshooting the ZCM Registration Process - Registration Web Server.
Registration Web Service
The Registration Web Service (RWS) provides the registration mechanism for managed devices. Before a device can be managed, it must be represented within the ZCM data-store. The RWS is responsible for the creation of an appropriate object within ZCM data-store (containment), uniquely naming the object (naming), and adding the object to the desired groups (group membership).
The RWS functionality is exposed through a standard HTTP/SOAP request. When a device makes the request for registration, it will provide both required and optional attributes including an optional registration key. In addition to providing a key-based registration model, ZCM will also retain the ability for registration to take place based on a set of attribute-driven rules.
Registration of a managed device can occur in three ways:
- Migration -> Deployment -> Registration
- Discovery ->Deployment -> Registration
- Manual Installation -> Registration
- Manual Registration -> Manual Installation -> Reconciliation
During migration, the preexisting GUID is preserved so that preexisting assignments and policies can be maintained. The GUID is preserved by the migration utility and placed on the managed device so that when the managed device registers, it used the preexisting GUID.
After the Deployment task pushes the client to the managed device, the managed device will reboot and attempt to register with a Primary Server. If the registration is successful, the RWS will mark the Deployment as Complete.
If an administrator desires to incorporate a managed device into the management zone before the device has physically been connected, they do it through manual registration which requires only three pieces of information:
- Serial Number
- Registration Key Name
The managed device is now represented within the management zone, however no policies, or actions can be applied to the device until it is physically connected to the management zone. When the administrator deploys the client to the managed device, the serial number is used to reconcile the managed device to the existing managed device representation in the management zone.
The Registration Web Service provides two registration mechanisms:
- Key-based Registration (Preferred)
- Rule-based Registration
Both registration mechanisms are controlled by the configuration tab in ZCC where an administrator can define both registration rules and registration keys. In addition to defining rules and keys, the administrator can use ZCC to set global registration settings such as the Registration Naming Template, and Rule-based Registration settings.
Initial registration determines the device name based on the naming template associated with the location where the device is to be created, the device location, group membership, and device attributes like IP address, DNS name, Hostname, etc. Subsequent registrations associated with the device refresh will never update the device location.
ZCC allows the following registration related settings:
- Global Naming Template (This template can be overridden at different locations)
- Dynamic Rename (If any of the information used to name device changed, the name changes)
- Enable/Disable Rule-based registration.
- Enable/Disable Default Rule (Default Location, Default Name, No Groups)
If, for some reason, the managed device uses a new GUID to register, you may see a device name that looks like this:
The Registration Web Service writes its debug messages into the services-messages.log file located in the following directories:
This should display the Web Service menu for the Registration Web Service. Select the "Test Serviceâ link and then select the third "pingâ method. Then click the Invoke button and you should see the following message: