Troubleshooting the xCmd utility

The xCmd utility communicates by using the Server Message Block (SMB) or Common Internet File System (CIFS). Therefore, if xCmd is used over a WAN, it works as expected as long as the Windows shares are working correctly. However, if WAN accelerator devices are used, they might cache the Windows share information, which can then conflict with xCmd.

Consider the following points:

• You must start the BMC Atrium Orchestrator Configuration Distribution Peer service with administrator credentials. For details, see To log on as a service on the target computer.
• Depending on the account credentials that you use to connect to the remote computer, they can override the account settings specified in the preceding bullet.
• The account credentials that you use to start the service on the remote computer are specified by providing the option to log on as a service.
• To run the xCmd utility in debug mode, set the value of the <debug-utility> element to true in the Windows Command adapter configuration. For details, see the Windows Command adapter configuration. When <debug-utility> is set to true:
  • On the client, xCmd writes to the grid log where xCmd is running on the remote computer.
  • On the host, the service on the target computer logs events to the Windows Application event log.

To log on as a service on the target computer

1. Navigate to Start > Control Panel > Administrative Tools > Local Security Policy.
2. Under Local Policies, double-click User Rights Assignment.
3. Double-click Log on as service.
4. In the Log on as service Properties dialog box, type the name of the user.
5. Click OK.
6. Click Start > Run.
7. Run the gpupdate command.
   
   You now have permission to log on as a service.