A common problem is with user rights on the target server. Windows 2008 in particular causes issues with User Access Control; when connecting remotely, even an administrative account can be granted a 'normal' user security token, which means you may not have the rights to get the executable copied across and the service started.
From the command-line on your AO box, try connecting to admin$ on the target server with the same credentials you're specifying for the AD adapter, e.g.:
net use t: \\targetserver\admin$ /user:domain\adminuser *
If it allows you to connect, can you copy a file across? If not, disable UAC on the target and try again.
The command worked and i was able to copy a file onto the admin share on the target system.
Thanks for posting that link to xCmd Utility. that was helpful.
Summary of my Problem,
I am running a AD adapter which is 20.11.03 version and still depends on the RCTRLX to do the remote executions.
I wanted to Update it to t20.12.03 where in which the RCTRLX was replaced by xCmd Utility. I can see the xCMD(followed by an ID).exe being copied onto the ADMIN share of the Target box and executing it.
But when it tries to perform an AD action ( ex : adding/deleting members from a group) , i see an error saying "In-sufficient rights to perform the mention operation "
when i run the same process using the previos version of the adapter (20.11.03) my operation succeeded.
On my peers i am running my BMC AO CDP service under a service account. That service account has Administrator rights and is a member of administrators group and has permissions set to logon as a service.
UAC is completely disabled.
Long story short, using my old version of adapter i am able to add/delete members to a ad group, and using the latest one i am un able to do that. I verified all the post - installation steps BMC provided in 20.12.03 AD adapter setup guide.
any suggestions ??
Check the user under which the xcmd service is running on the target machine (might require a keen eye on this machine's task manager).
Have you specified the "logon-with-user-credentials" parameter in the adapter configuration?