[cifs-protocol] [REG:110011477385004] RE: userParameters attribute
hongweis at microsoft.com
Mon Feb 1 10:29:37 MST 2010
Could you please take a look at my question below so I can proceed with this request ? If you are busy, we can always come back to visit it whenever it is good time for you.
From: Hongwei Sun
Sent: Tuesday, January 19, 2010 9:31 PM
To: 'tridge at samba.org'
Cc: cifs-protocol at samba.org; pfif at tridgell.net; Michael Ströder; MSSolve Case Email
Subject: [REG:110011477385004] RE: userParameters attribute
How did you generate the UserParameters you mentioned in the e-mail ? I got a little bit different result. The steps I used are
(1) Open "Avtive Directory Users and Computers" -> "User" -> select a user such as "Administrator"
(2) In Properties windows , select "Sessions" tab and then change "Active session limit"
(3) Then the UserParametes attribute was added to the user object, the value is something like
UserParameters attribute is used for storing user specific data for individual programs, such as RAS and Terminal Service. I just want to make sure we are looking at the same tool.
From: tridge at samba.org [mailto:tridge at samba.org]
Sent: Thursday, January 14, 2010 2:55 PM
To: Interoperability Documentation Help
Cc: cifs-protocol at samba.org; pfif at tridgell.net; Michael Ströder
Subject: CAR: userParameters attribute
The userParameters attribute on a user in AD seems to be a bit of a
puzzle. Could you add some docs on it at some stage? Not a really high
priority, but we would eventually like to be able to offer admin tools
that manage things like session activity timeouts, and it seems that
we need to know how to parse and create userParameters to do that.
An example userParameters attribute from w2k8r2 (in base64 form) is this:
the above came from using the windows user admin tool to change the
session activity timeout for a test user.
Michael Ströder has also pointed out this page:
which documents a previous effort by the Linux thin client community
to work out the format of userParameters. I'm guessing the strange
encoding is used to try to keep the attribute as valid UTF8. If you
can confirm that the attribute is always valid UTF8 that would be
great (as otherwise we might corrupt it during replication with
As I mentioned, this is not a high priority, but it would be nice to
know the format at some stage.
More information about the cifs-protocol