G
Guest
I have noticed that as we upgrade our computers to Windows XP SP2, I can no
long run some remote commands.
Here are some examples:
To query remote RDP sessions
qwinsta /server:<Servername>
To kill remote RDP sessions
rwinsta /server:<Servername>
To query remote processes
qprocess /server:<Servername>
All these commands come back with:
Error opening Terminal server <Servername>
Error [5]:Access is denied.
I can RDP to this computers with the same account. Connect to all the
administrative shares (C$,D$,Admin$) but these commands do not work remotely.
I can fire the same command locally and it works perfectly...but that
doesn't help me any for querying and killing remote RDP sessions.
I am assuming the security in SP2 lock some feature or API that these
commands were using. Is there a work around or reg hack to get these
commands to work? Are there any replacements to these commands?
Thanks in advanced for the help
Troy
long run some remote commands.
Here are some examples:
To query remote RDP sessions
qwinsta /server:<Servername>
To kill remote RDP sessions
rwinsta /server:<Servername>
To query remote processes
qprocess /server:<Servername>
All these commands come back with:
Error opening Terminal server <Servername>
Error [5]:Access is denied.
I can RDP to this computers with the same account. Connect to all the
administrative shares (C$,D$,Admin$) but these commands do not work remotely.
I can fire the same command locally and it works perfectly...but that
doesn't help me any for querying and killing remote RDP sessions.
I am assuming the security in SP2 lock some feature or API that these
commands were using. Is there a work around or reg hack to get these
commands to work? Are there any replacements to these commands?
Thanks in advanced for the help
Troy