1. Shane O’Neill Synergy Geekovation 2015

2. XenDesktop VM’s need to be registered in order for the user to be able to access them. Registration with the XenDesktop DDC can fail for a number of reasons. This can result in unnecessary user down time and increased calls to the organization’s helpdesk.

3. Taking advantage of the Monitor Service API on the DDC, I created an agent that resides on each VM which allows it to become “self-aware” of its registration status. At regular intervals, the agent can use a web service to query the DDC and check its status. If the VM discovers that it is not registered, it can take some corrective action to try and get itself registered.

4. A call to the Data endpoint gives read-only access to the XenDesktop SQL database and allows us to query a machine. Request Response

5. The flow of the process to attempt to register the VM…

6. By being able to fix itself and ensuring that it is available, any potential impact to the user is avoided. This in turn will reduce calls to the helpdesk. In the case of VM’s where the self-healing is not successful, proactive alerting to support can allow for the issue to be fixed before the user is impacted. This also presents a more positive experience of XenDesktop to the business. I think therefore I am… Registered!