• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 341
  • Last Modified:

windows xp administration


I have a new domain with 500 clients. all standard domain user. Several times i need to connect to those client and making printer installation, registry settings, printer installation . This active must be performed by using the same user session , means i need to use run as all the times.

Are  there other ways that I can use in order to perfom printer installation , registry change , printer installation "within " the same standard domain user sessionm when I'm connect trough rdp ?

I have a problem when i i'm logged on as a standard domain user  and execute cmd  with run as by using admin credential and digit "control" as a admin , the control panel is not opening

Any ideas and tips it will be great for our help desk

  • 2
  • 2
2 Solutions
larry urbanDevOps EngineerCommented:
Windows XP and Windows Vista Terminal Services always allows remote desktop to access to console session (the same desktop in which user will see when standing in front of the monitor) if you log in using the current users log in and password in the RDP session.

Other options would be using a third party software. 2 examples would be VNC (install the server on the client PC) and TeamViewer.
larry urbanDevOps EngineerCommented:
Just a little added information for server products and Vista:

Whenever user uses “Remote Desktop Connection (RDC)” or Terminal Services client (TSC or mstsc) to remote desktop to a Windows Server family operating system such as Windows Server 2003 and Windows Server 2008, a new session is started and user will log on to a new desktop. The behavior is unlike Windows XP and Windows Vista Terminal Services which always allows remote desktop to access to console session (the same desktop in which user will see when standing in front of the monitor).

For user who need to connect and access console session with Remote Desktop can use a switch when running Remote Desktop Connection Terminal Services client (mstsc) in order to force Remote Desktop to connect to console session of remote server.

To connect to console session of Windows Server 2003 or Windows Server 2008, run the RDC or TSC with the following switch: /console. For example, for all remote desktop client except the one in Windows Vista:

mstsc /console

For Windows Vista remote desktop client, use /admin switch instead:

mstsc /admin

By logging in to console session of remote computer, all existing applications that are running and not yet closed when user is physically using the computer will be automatically appeared, instead of having users re-open all of them.
You could run RegEdit on your PC as an Administrator and connect to the "network registry" of any PC in your domain.

You could install the printers as part of a logon script

You could sign into the client PC's as a domain admin using RDP.

You may find that using Group Policies is a better solution for solving the 20% of the problems that take up 80% of your time.

You may find that a few carefully crafted VBScripts or PowerShell scripts might get round the "Control" issue.

You could use PSTools from Sysinternals (now part of Microsoft) to execute applications in an administrator context ==> http://technet.microsoft.com/en-us/library/bb896649.aspx

Hope this gets you started

... we use TeamViewer for remote troubleshooting.

+1 for Todar's solution.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now