by "xieyao" <yao450860487@[EMAIL PROTECTED]
>
Nov 28, 2008 at 03:53 PM
<elmar.heeb@[EMAIL PROTECTED]
> ????
news:cd257ce1-c76d-4f7e-ba92-b1a9caca5b69@[EMAIL PROTECTED]
Aug 26, 7:36 pm, "Joe Kaplan"
<joseph.e.kap...@[EMAIL PROTECTED]
> wrote:
> This data is actually stored in a proprietary binary format in a single
> attribute in AD and is not intended to be accessed directly. You are
> supposed to use the ADSI property methods on the IADsTSUserEx interface
(of
> which TerminalServicesProfilePath is a member) to access this data.
>
> Thus, you can't really use lower level LDAP tools to do anything with
this
> data. IMO, this design decision by the TS team sucks, but we are
currently
> stuck with it. I think they may be changing this for 2008 server but I'm
> not certain on the details yet.
Well, it is still binary in Windows 2008 Server. As we want to use
ADS in our OpenLDAP environment we needed to fill in this value.
Therefore, we did some analysis and came up with an algorithm that
works. It is described here: http://nic.phys.ethz.ch/readme/249
or
the commented version http://daduke.org/linux/userparameters.html
Not a substitute for a real do***entation but maybe it is of some
help.
-- esh