As long as the logged in user has administrative rights on the non-accessible machine I would run this: I can use another server to check the status of the first one. Windows 2000+ (includes Windows XP and 2003) have two command-line tools called qwinsta and rwinsta that can query and reset a remote session.įor example, let's say that I can't gain access to a server using Terminal Services because both sessions are used up. Terminal Services Manager doesn't exist as a snap-in to connect to a remote machine and because the TermService service is a core system service, you can't even stop it on the local machine, let alone a remote one.įortunately there is an easy solution. Strangely, these obvious solutions aren't available. You would think this would be as easy as connecting to the remote server by adding the Terminal Services Manager snap-in to a MMC console or remotely stopping and starting the service (in a pinch). Yes, I do have the settings set to automatically disconnect and/or log off a user after X minutes of inactivity but even with that there are times when I need to be able to manage this remotely. This may happen if two people are legitimately using the servers or if someone forgot to log off. In both situations there are only 2 users allowed for administration so occasionally both are used up and I can't access the server.
Basically this is the same thing but it's packaged a bit differently on the two OSes. In W2K I use Terminal Services in Administration mode and in W2K3 I use Remote Desktop. I regularly administer Windows 2000 Server and Windows Server 2003 machine using Terminal Services.
0 kommentar(er)
