Sys Reqs for TS Management « Dmitry’s PowerBlog: PowerShell and beyond

AD cmdlets allow you to easily manage terminal services properties for user accounts. You can get all TS attributes for a user by simply typing:

get-qaduser ‘Dmitry Sotnikov‘ | format-list Ts*

Get a report for a set of user by doing:

get-qaduser -searchroot mydomain.local/uk/london | format-table Name, TsProfilePath

Or change them by:

get-qaduser -searchroot mydomain.local/uk/london | set-qaduser -TsHomeDrive ‘P:‘

Now, here comes the tricky part. By default, this will only work on server versions of Windows, namely Windows Server 2003 and Windows Server 2008.

To enable terminal services management on Windows XP:

Install Windows Server 2003 Administration Tools Pack on the XP workstation.

To enable terminal services management on Windows Vista:

Follow these instructions on enabling TS management on Windows Vista.

My Recent Tweets

The Experts Conference 2010: TEC is one of the most advanced (400 level sessions are norm!) conferences... http://bit.ly/6se2go #powershell 19 hours ago

New cmdlets to manage AD computer accounts: Up to version 1.3, we used to have one cmdlet for computer ... http://bit.ly/7dwqBX #powershell 3 days ago

@alanrenouf @makovec What is the usecase? Could you post the details on what and why you want to do to the forums at http://powergui.org ? 5 days ago

@alanrenouf I'll ask Santa. Glad that you did not pick a specific year! Flexibility is good. 5 days ago

@alanrenouf I like the way you assign multiple types to values in your PowerPack http://bit.ly/4p2Diy to handle action inheritance. 5 days ago

5 Responses to “Sys Reqs for TS Management”

Feed for this Entry Trackback Address

1 Tom Barnum July 23, 2008 at 7:57 pm

Can you help explain this for me:

The Quest CMDLET Get-QadUser (1.1) returns something like:
PasswordLastSet : Wednesday, February 20, 2008
PasswordAge : 153 days
PasswordExpires : Wednesday, February 20, 2008

The Default Domain Policy/../../../Account Policies/Passowerd Policy settings are Maximum password age 180 days

Why does the passwordExpires property show the same as passwordLastSet?

2 dmitrysotnikov July 24, 2008 at 12:17 pm

Tom,

This looks weird… Could you submit this to the AD PowerShell forum – http://www.powergui.org/forum.jspa?forumID=173 – so the dev guys can work with you to troubleshoot the issue?

Dmitry

3 Christopher DeRemer July 24, 2008 at 12:52 pm

What about setting the Remote Control options. I would like to set all users to not have to prompt for control.

Cheers
Chris

4 dmitrysotnikov July 25, 2008 at 1:31 pm

Tom,

We could reproduce the issue on the current release. This will get fixed in our next drop. Meanwhile please use:

$PasswordExpires = $user.PasswordLastSet.Value + $user.Domain.MaximumPasswordAge.Value

Dmitry

5 dmitrysotnikov July 25, 2008 at 2:33 pm

Christopher,

Do you mean Remote Control options on each desktop? Why not just use group policy?

http://technet2.microsoft.com/windowsserver/en/library/a0cf3d25-e08e-4c4b-a8e3-3b5f62249dc91033.mspx?mfr=true

Dmitry

Dmitry’s PowerBlog: PowerShell and beyond