Scott Forsyth's Blog

Postings on IIS, ASP.NET, SQL Server, Webfarms and general system admin.

Cloud Resources

IIS Resources

tsadmin command change in Windows Server 2008

I use Remote Desktop all the time to manage servers remotely, and often I join other people's sessions to troubleshoot something with them, or walk through something or other.

In Windows Server 2003 (and Windows 2000 Server), the easy way to start up Terminal Services Manager is Start -> Run -> 'tsadmin' -> [Enter].  This calls us Terminal Services Manager where I can right-click on a user and click 'Remote Control', and if they approve, I can join their session.

This doesn't work in Windows Server 2008 anymore.  The change is ever so slight.  In Windows Server 2003 the tool was tsadmin.exe, so typing 'tsadmin' was all that was required to start the tool.  Now, in Windows Server 2008, this has been moved to a MMC snap-in and is called tsadmin.msc (plus tsadmin.dll is used silently).

So, to spin up Terminal Services Manager in Windows Server 2003, you can click on Start and your cursor focus will already be in the search box.  Type 'tsadmin.msc' and press [Enter] and you'll be in Terminal Services Manager.

If you really don't want to type the '.msc' each time, you could create a batch file to do it for you.  Create a file in c:\windows\system32 (which is in the system path already), call it tsadmin.bat and type 'tsadmin.msc' (without the quotes) in the body of the file.  Save it and you'll be set.  The disadvantage of doing this though is that you won't be practiced up on typing tsadmin.msc on fresh servers, so personally I prefer to just remember the extra .msc now on Windows Server 2008.

Note: If you don't type this often enough to remember 'tsadmin.msc', this has always been available from the Administrative Tools folder.  In Windows Server 2003/2000 it's directly under Administrative Tools.  In Windows Server 2008 it's one folder deeper under 'Terminal Services'.

 

Comments

Brett said:

Cheers that's what I needed

# February 1, 2011 8:13 PM

balun said:

Thanks from France

# March 24, 2011 6:06 AM

Dan said:

Great info, thanks a lot :)

# May 16, 2011 5:51 PM

phill said:

Hi, it seems one has to connect each individual TS manually, rather than all the saved TSs connecting on app start. I have 50+ terminal servers, so that really bites

# June 22, 2011 5:50 AM

OWScott said:

Hi Phill,

I don't quite understand your configuration, but have you considered any of the RDP Tools out there?  Do a google search for "RDP tools" and give some of them a try.  There are good options for managing a lot of servers.  Another option (one that I use) is to generate RDP files for each server and then add the folder to your Windows taskbar.  

# June 22, 2011 9:47 AM

Brian said:

Is there a way to run this program as another user?  I am logged in as a basic user and want to run this program as a Domain Admin so I can kick users off their session.  Do you know of a way to do that?

# July 12, 2011 2:49 PM

OWScott said:

Brian, you could log into the server as the admin user (the obvious solution), and you can also consider using runas from the command line, to run as a different user.  Also, using sysinternal's psexec, it's possible to run it under another account.

# July 12, 2011 2:59 PM

Sam said:

thanks this article helped.

# September 2, 2011 11:11 AM

Ronu said:

Thanks much. I was after this info.

# September 22, 2011 1:41 AM

Zephan said:

3.5 years later and this article is still relevant and handy. Just what I was looking for. Thanks Scott.

# October 12, 2011 3:39 PM

Sean said:

Thanks for the tip.

# November 21, 2011 10:36 AM

ZANDRA said:

I have a cuestion?

who's the comamd that I can in WINDOWS 7 but comunicate between a pc and other PC.thanks...... for tu answer

I'm PERÚ-LIMA

NOTE:I use tsadmin but not funtion in my computer.what's the problem,who's the diferent?

# June 1, 2012 9:19 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)