Remote Desktop Services (Terminal Services) Team Blog

I'm still sad that TS Gateway won't be included in Vista.

Este es un resumen del articulo publicado en Terminal Services Team Blog , en donde se describen las

what is "physical console"? without this I couldn't understand most of the article?

It's not very clear to me from the article, so I'm hoping someone can answer.

Currently in Windows Server 2003, we can actually have 3 TS sessions -- 2 normal ones plus the console, which has come in handy on occasion when 2 administrators have accidentally left sessions running. One can always usurp the console session, which is often easier than trying to use TS Manager to disconnect the other admin sessions.

Is this still the case in 2008 or are there now really only 2 sessions?

The Terminal Services Team blog has a good post about these changes. One of the most obvious changes

Sergey,

Thank you for the info. That sounds like a really well done change.

Perhaps the title of this post should be "Microsoft decreases the number of concurrent remote admin connections in windows 2008"

That's a lot more important than the functionality "gain" that is presented.

The main use my team has with the 3 sessions is troubleshooting issues on the servers.  To limit the number of concurrent sessions simply cripples these efforts.

The added functionality of allowing more disconnected sessions seems like a good way to waste more memory.  Perhaps this is good, I'm just pointing out a side effect.

Also, I'm struggling to understand the benefit of changing the command line switch for GUI based tool?

Sorry for the sarcasm, this "enhancement" is frustrating.

Bron: bink.nu Uit testen blijkt dat Windows Server 2008 RC0 erg veel sneller is dan de voorganger Windows

Forcing users, even admins in this case, to relearn a command for no good reason is really a waste of everyone's time.  There is no reason that Server 2008 couldn't just interpret the /console switch as "/admin" and be done with it.

Even better for users (admins) is that Microsoft in their wisdom will either silently ignore the switch (CLI) or posting a vague error, “An unknown parameter was specified in computer name field.” (GUI).  

If we REALLY have to change the switch, which I'm obviously not convinced makes sense at all, then wouldn't it be a nice idea to print out the usage parameters rather than fail silently, or in the GUI, I dunno, provide a link to a local help file that explains these changes?

I can understand that from Microsoft's point of view this should help some application run better than rely on being run in session 0, and I've seen a handful of such applications; however with 5 years of time for application vendors to correct the issue, this change seems to be a bit late.

In regards to the 3rd terminal server connection, I agree that is was definitely useful and I've even seen some instances where, especially SBS users, would use these 3 connections as a mini-terminal server.  These chahnges allow Microsoft to properly wring out every last cent...  err license features to those who need it.  

Seriously though, to a user (or again admin most likely for this case), the only potential benefit is that you might not break a handful of applications that require session 0, everything else is an annoyance.  i.e. relearn command switches, lose 3rd remote session, lose ability for small customers to use server for a handful of remote users without having the complexities with licensing etc. involved with running terminal services in application mode.

From a customer's point of view, I'd give this a C+ and only because of the handful of applications that should benefit from session 0 no longer being redirected.  Outside of that one benefit, from a customer's point of view, this new 'feature' is a FAIL.

'/console' equal 'connect to console:i:1' option in rdp file.

Now, What option is '/admin' in rdp file ?

I understood the rdp file option for /admin.

/console = "connect to console:i:1"

/admin = "administrative session:i:1"

This really suck, wasted hours before I figured this one out...

It is an arrogant move to not make the new option backwards compatible, and just another try at FORCING Vista and soon Windows 2008 down peoples throat...

You should have left the /console option, windows 2008 could easily have ignored this..

Poor job you guys.

Perhaps the question is with all the "positive" feedback here, one must wonder if MS even cares at all.  As with http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-connection-authentication-faq.aspx?CommentPosted=true#commentmessage where they got no positive feedback either, it seems like MS has decided that changes that no one likes are acceptable and are becoming common place.  It's like they sit around and ask themselves, 'hey, what can we do to irritate another block of customers today?' and then they brain storm and come up with the most annoying and idiotic changes one could possible envision.

I'm perfectly happy with RDP 5.2 on Vista and won't use 6.0 or 6.1 until MS listens.  The problem is they just don't care and make no $ off the RDP client so they have ZERO incentive to honour the wishes of customers.

Windows Server 2008: Zmena v RDP z hlediska administrace serveru

crosspost from http://blogs.msdn.com/rextang just upgraded my Windows Vista machine to Vista SP1 RTM

So this blog is documenting the changes to Windows Server 2008, and why "/console" is no longer needed in the new server.  Fine.

Unfortunately, the /console option behavior was removed from the CLIENT.  So if I use the new client to connect to a Windows Server 2003 server, I STILL can't use /console.  Forget the fact that there really, really, really is a physical console session on Windows Server 2003.

I'm agreeing with the other posters.  Symbolically, /console==/admin.  Session 0 is an irrelevant implementation detail.  The client should either give an error to the user for /console, or support both options with the same behavior, or both.

The decision to remove support for the "hidden" admin connection isn't such a big deal, but I can understand the cause for complaint.  Instead there is the benefit that *no* sessions get logged out when a 3rd (4th) logs on, they just get disconnected (user switching).  That's a pretty neat feature, and based on many admin usage patterns it may even be a lot more important.

Este es un resumen del articulo publicado en Terminal Services Team Blog , en donde se describen las

Its' really anoyng, i'm using a third party rdp-tool thats uses the /console switch but not the /admin switch.

I'm using this tool to connect to approx 50 Win2003 Server and are not able to connect to the consol-session anymore.

I just trough out the windows my new notebook with Vista SP1 and use my old notebook with XP further.

I don't think that on this way MS can bring us admins to use Vista SP1.

Bring a fix for this immediatly

The OSX version of RDC says: "This beta version of Remote Desktop Connection is out of date. You are using a beta version of Remote Desktop Connection Client for Mac 2.0. We recommend upgrading to the final release version. You can download the latest version of RDC at http://www.microsoft.com/mac/"

BUT THIS IS A LIE! There is no final release version on the M$ site. Why are you implementing a timeout and don't offer at least a replacement version?

Because of this annoying message, my .rdc files for various connections do not work anymore, RDC only remembers the login credentials of a single server now.

PLEASE PLEASE PLEASE offer at least a timeout-fixed version if you are not able to provide a final version.

I'm using Windows Vista (Client) and 2003 (Server). However the bug (or feature?) for playing/recording audio on the remote hardware is still not fixed. It is annoying that the workaround to log on the console (where I can both play and record audio files on the physical sound driver) will not work any longer -- my Vista client does not support "/console" while my 2003 server does not support "/admin".

How can I play / record audio remotely?

Is the only way to remove SP1 on my Vista client?

Will this be the end of my Media Services Installation, or should we offer silent films again?

Anyone have an idea how/when the Remote Desktops admin feature will support using the TS Gateway to connect to servers?

Thanks,

Steven

Who dropped the ball on this one? Removing the /console switch is just plain stupid. Release an update and add it back. I'll be uninstalling Vista SP1 from computers for the rest of the afternoon.

For the people that don't want to remove Vista SP1 or XP SP3 just replace the new TS files with the old ones. The two needed files AFAIK are mstscax.dll and mstsc.exe, and you can find them on system32 dir (XP).

This was a poorly thought out plan.  The changes break most 3rd party RDP utilities.  Why not leave /console as a valid switch and just interpret as /admin where applicable?  Lame job by the MS team.

This was a bad decision. /console no longer works on XP SP3.

Do you guys have any idea how much sysadmin time is going to be wasted because of this idiotic decision?

Do you think those system admins will be happy or upset?

I am using the Remote Desktops snap-in from the Windows 2003 Server Admin Tools, just like many other Admins here, to connect to several servers to the console, Session 0.  I don't think that Microsoft realized what problem this will present, not to also issue an update for this tool at the same time when the issued Service Pack 3 for XP.  Millions of admins around the world will be really, really mad!

I have to waste time to re-configure all my remote connections now using the Remote Desktop included with XP, which I don't like because it doesn't offer me the same efficiency and speed in my remote work on the servers.

So "/admin" replaces /console", but what replaces the following .rdp-file argument;

connect to console:i:1

?

I've changed all my shortcuts from /console to /admin, but I don't know what to add to my rdp-files (which uses no shortcuts, hence no command line arguments.)

This silent change cost me quite a bit of time trying to figure out why I could not connect to the console session on Windows Server 2003 servers.  In fact, in a few instances, I had to physically go to the servers to access the console session because I already had apps running in that session.  Unfortunately, one of these servers was over an hour away.

Since installing XP SP3, the functionality of mstsc has changed. I used to be prompted for credentials before actually connecting to a server. Then, once the correct information was entered, the server gave me the warning dialog, and when accepted, logged me into the system.

Since I use multiple servers in multiple environments (multiple domains, and standalone), and since I also use a password manager with automatically generated passwords with a high complexity level, this was a great setup. I could copy/paste my passwords from the manager without ever exposing them to anyone (including myself).

I also use a management tool that allows me to have hot keys assigned to various functions. Selecting a server and executing a hot key against it will automatically launch the following command - "C:\WINDOWS\system32\mstsc.exe /console "C:\admintools\Default.rdp" /v:%E% /w:1024 /h:768"

This would launch against the servername (%E%), and use my default.rdp. The bonus to this setup was that my name (domain or computer)\username was prepopulated correctly. I did not need multiple .rdp files.

With 6.1, this is gone. How do I regain this functionality?

This is such typical arrogant behavior by Microsoft.  I, too, like everyone on this blog just spent a TON of time trying to figure this out?!?  

But Microsoft DOESN'T CARE!  In the past, they used to only ignore end users who they think don't know anything any way.  They used to pay attention to admins and techs.  But now, they really showed they don't care about us either?!?

I'm SOOO glad I decided to use CentOS for my last 2 installs!  It JUST WORKS!  None of this CRAP!

Sorry, Microsoft!  (NOT!)

If you have to change this, how hard would it have been to simply detect the /console switch and pop up a message that says, "/console has been replaced with /admin, please try again"?

Meanwhile, both the application-specific Help file and the Windows XP Help and Support Center still list the missing /console switch and do not mention the /admin switch. If you're going to "silently" remove functionality, at least update the documentation!

Remote Desktop Connection (Terminal Services Client 6.1) e opzione console

For us Lotus Notes Domino server users, the Notes console ONLY works on the physical console. This required us go and use VNC.  Really love the brains behind this new featue.

Eric, you do realize that simply using /admin will get you console access on pre-Vista machines, right?  While I'll grant it's a headache to figure out the change, once you know how to do it, it works just like it did.   In fact, by adding both version of the setting to your .rdp file, you can make one file that enable the setting on any machine.  Just add both of these to any file that needs it:

connect to console:i:1

administrative session:i:1

and it will work with any version of Remote Desktop.

One issue the I have run into with the /admin command and terminal services 2008 deals with the "initial program" setting.

In 2003, if you have specified an application to launch when users log into the terminal server, they do not receive the desktop.  In order for an admin to manage the system using the desktop, the /console switch could be used.

In 2008, when an application is specified to launch on logon, the /admin command no longer provides local administrators with the desktop.

This is problematic when using the TS RemoteApp feature.  Users have to be a member of the "Remote Desktop Users" group on the system to use app published to RemoteApp.  This also means that they have the ability to create a regular remote desktop connection to that server and receive the full desktop.  To prevent this, I set the initial launch application in TS Config to "logoff.exe" expecting that the /admin (/console) command would provide a user with local admin rights the desktop.  This is not the case, the user with rights to use /admin is also logged off the system.  The only way I have found to resolve this is to physically log in at the console and modify the settings.  I now have to use a script to check the user name and logoff "non allowed" users defined in the script.  This seems like a backwards way of doing things.

-Kevin

forget it, I find the charmming "tsdiscon"

Как обычно необычные вопросы на форумах TechNet-RU, когда на них нет ответа, оставляют чувство...

Trying to get multiple RDP admin sessions running on WindowServer 2008....via remote PC's running WinXP sp3.

How can I get this working ?   (Right now..when the 2nd session initiates the first is getting terminated....unlike Win2003..where I'm having no issues.)

Thanks.

-Brian

yes....we were using the same default Admin account.

-Brian

Currently uninstalling XP SP3.  The fact that over a year has passed without restoring (or even addressing the issue!) the ability for Administrators to use the "Connect to Console" option in the MMC Snap-In to connect to 2003 servers is completely unacceptable.

MS, you really dropped the ball on this one.  As with Vista, your assumption that everyone would immediately jump in and starting using Server 2008 was a pipe dream.

Why would anyone, who's had stable applications running on 2003 server for years, even dream about a major server OS upgrade?  So we can waste even more hours on stupid undocumented "tweaks" like this mstsc.exe snafu?

I've just run into this same problem with a recent XP SP3 upgrade, which is now no longer able to connect to the Windows 2003 server I've been connecting to from here for the last year+.  First, I waste a frustrated hour trying to figure out why /console stopped working, then it appears that the RDC/mstsc just doesn't work at all any more.

I understand that things change with various upgrades, service packs, and the like.  But change without notification or warning -- and seemingly without reason or benefit -- is generally not an appreciated thing, and changes that outright break previously useful/vital functionality are a good way to drive your customers to other competing providers.

Has there been any sort of MS response, explanation, or fix for any of these issues on XP SP3?

This one issue alone may well be reason enough for some of us to uninstall XP's SP3...

This switch from /console to /admin doesn't really bug me.  What bugs me is that my 2008 server, twice in the last week, has gotten into a state where I cannot log-in and I have to open a support case with my hosting provider to reboot the machine.

My "fix" is to set the machine to reboot every night so I have a chance in the morning to log-in.

The machine pings fine.  Serves web-pages, etc... but MSTSC.EXE with or without /admin won't connect.  Bleh.

If "Restrict each user to a single session" setting is enabled in tsconfig.msc, you should be able to reconnect to your console session by simply connecting remotely as the same user.

Thx,

Sergey.

Hi !

Additional notes:Taking over a console session is possible. Open another RDP session, do a "qwinsta" to obtain the session-id for the console [usually 1]. Then do a "tscon 1" and you're there.

The big mess is:This works only, if there is someone logged on !! If not, you'll receive an error message!!!!

:-(  :-(

So this is what has broken my Console access to client SBS 2003 servers via Remote Web Workplace.

I will get this RWW functionality back how?

Sir,

In windows 2003 server's user environment setup, we can define the startup application. With this once user is authenticated through remote desktop connectivity automatically the application executes. User need not to remember the appliation name, path etc.

But the same configuration setup is not working in windows 2008 server. After the user is logged in through remote desktop connection, it goes to upto to the server desktop. The defined appplication is not getting executed. Can any one help me on this. This is very critical for us because we are going on live with multiple location using multiple version of software application. (srini1705@gmail.com) this my mail id, can anyone give some solutions please

Yet another example that Microsoft development team for the server OS does not appear to talk to real world server admins.

Wherever functionality is to be changed or decreased, there should be some serious discussion before going forward.

This is true not just with this RDP change, but in the server admin tools on Server 2008. Change for the sake of change is not progress.

Or how about the fact that the Exchange admin tools don't run on Vista, and you have to use RDP from Vista to a server with the tools - and now you alter the way it connects to the console connection as well? A case of cascading changes resulting in admin pain.

I have not found a way to enable this other than installing the Terminal Services role. Rob responded in October 2008, stating that you could install RemoteApp Manager separately.

I have not found this listed as a separate installation anywhere.

Thanks for the pointer. On my system, the Remote tools hierarchy was slightly different (Terminal Server Tools/Terminal Services rather than RemoteApp Manager). This installed the tools, but not the role.

Unfortunately, even when I followed the original instructions to "either list the allowed programs, or allow users to start unlisted programs", the application would not launch.

Just for clarification, I'm using the Remote Desktop client feature where you can specify to "Start a program" on connection.

If I DO NOT have Terminal Service role installed, the desktop appears. If I DO have Terminal Service installed (no other changes), then the application launches successfully.

HansW