Subscribe to my RSS Feed
Join 2,575 other subscribers
My ramblings on the stuff that holds it all together
Post here on the terminal services team blog, about why they’ve changed this switch to /ADMIN in Windows 2008/Vista SP1/XPSP3.
This is the first I’ve heard of it, not a huge issue but I can see a potential problem where the /console switch is ignored, again not huge but a bit of an annoyance just to change a bit of syntax?
if you have device CAL’s and normally use the /console switch to remotely administer a machine to my understanding that doesn’t allocate a device CAL to your admin machine (or whatever machine you are admin’ing from at the time)
What if you use this method to administer terminal servers, doesn’t this silently ignoring just eat one of your device CALs (permanatly if you do it often enough from a machine)?
The article says:
The /console switch is silently ignored. You will be connected to a session to remotely administer the server.
The /console switch is silently ignored. You will be connected to a standard Remote Desktop session that requires a Terminal Services client access license (TS CAL).