Managing Terminal Services attributes with PowerShell
Wednesday, 20 February 2008 by Michel Roth
Powershell is the bomb(shell)! Sorry, I couldn't resist. No but seriously, Powershell is coming whether you like it or not. In two years you'll have to do most of your "scripting" in Powershell. Scripting Terminal Services attributes for example...

Of course the Terminal Services attributes can also be set using Powershell. It just takes some digging to find out what's what. Dmitry Sotnikov has done the digging for you. He says retrieving terminal services properties is easy. You just execute "Get-QADUser" and the objects retrieved will have the corresponding properties. It's important to note that Terminal services properties are only available when AD cmdlets are run on Windows Server 2003 or 2008. Workstation operating systems (XP, Vista) do not support programmatic TS administration so the properties will not be retrieved.

Read Dmity's article here. (thanks to the MSTerminalServices.org blog for the pointer)


Related Items:

Powershell GUI: PowerGUI (23 April 2008)
Windows PowerShell and Windows Server “Longhorn” (17 November 2006)
"Monad" Renamed To Windows Powershell (26 April 2006)
Windows PowerShell RC1 Refresh (8 May 2006)
VMware VI Powershell Support Available In Beta (17 March 2008)
Terminal Server Script Repository (29 January 2005)
Scripting for Server Based Computing: Part 2 Terminal Services Server and Connection Settings (10 November 2005)
Terminal Server Properties Editor (19 December 2007)
What’s new in Terminal Services Licensing for Longhorn? (Part 5) (2 May 2007)
Comments (0)
Show/Hide comment form