Sys Reqs for TS Management

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:

To enable terminal services management on Windows Vista:

Tags: , , , , , , , ,

5 Responses to “Sys Reqs for TS Management”


  1. 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. 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. 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. 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. 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


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




My Recent Tweets

Legal

The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

July 2008
M T W T F S S
« Jun   Aug »
 123456
78910111213
14151617181920
21222324252627
28293031  

%d bloggers like this: