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 till the Windows shares are working correctly. However, if WAN accelerator devices are used, they might cache the Windows share information and can conflict with xCmd.
Note the following points:
- You must start the TrueSight Orchestration Configuration Distribution Peer service with administrator credentials. For details, see To log in as a service on the target computer.
- The account credentials that you use to connect to the remote computer: Depending on what account credentials you use, this setting can override the account settings specified in the earlier bullet.
- The account credentials that you use to start the service on the remote computer: This is specified by providing the option to login in as a service.
- Set the value of the <debug-utility> element to true in the Windows Command adapter configuration to run the xCmd utility in debug mode. For details, see the Windows Command adapter configuration. When <debug-utility>is set to true:
- On the client side, 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 in as a service on the target computer
- Navigate to Start > Control Panel > Administrative Tools > Local Security Policy.
- Under Local Policies, double-click User Rights Assignment.
- Double-click Log on as service.
- In the Log on as service Properties dialog box, type the name of the user.
- Click OK.
- Click Start > Run.
- Run the gpupdate command.
You now have permission to log on as a service.
xCmd utility on 64-bit target systems
To enable the utility to run on 64-bit systems, you must set the OSARCH parameter in the xCmd utility to 64-bit. A new element <service-launch-mode> is also added to the Windows Command and the PowerShell adapter to specify the service type image on the target host system. Sometimes, even when the OSARCH parameter is set to 64 and the <service-launch-mode> is set to 64-bit, the xCmd utility fails to run on the 64-bit system.
Workaround: Add the domain name to the user name in the Windows Command adapter request and run the request again.
For example, the following request contains the user name in a domain\user-name format.
<targets>
<target>
<host>10.128.249.15</host>
<userName>WIN-M0PGTNBAPUP\Administrator</userName>
<password>bmc@123</password>
<impersonate-user>true</impersonate-user>
<service-launch-mode>64bit</service-launch-mode>
<impersonate-user />
<character-set />
</target>
</targets>
<commands>
<command timeout-secs="500">ipconfig</command>
</commands>
</command-request>
Related topic