supported. There are definitely a ton of useful things you can do with ADAM
on XP. This just doesn't happen to be one of them. :)
what the limitations are though. Finding documentation on ADAM is harder
"Glenn" <Glenn@discussions.microsoft.com> wrote in message
news:3014C85B-5A46-4F1D-BE1C-9B52139977CA@microsoft.com...
> Yes, it works on Windows Server 2003.
>
> I think that instead of saying that ADAM is supported on XP, Microsoft
> should say something like "While ADAM will 'run' on XP for development
> purposes, there are enough issues involved with ADAM's operatoin on XP
> that
> you should avoid it if possible."
>
> Thanks though.
>
> --
> Glenn Sills
>
>
> "Joe Kaplan" wrote:
>
>> I know that password policy enforcement like lockout doesn't work on XP
>> with
>> ADAM, so this may be a symptom of that. Try it on 2003 server and see if
>> that fixes it.
>>
>> Joe K.
>>
>> --
>> Joe Kaplan-MS MVP Directory Services Programming
>> Co-author of "The .NET Developer's Guide to Directory Services
>> Programming"
>>
http://www.directoryprogramming.net >> --
>> "Glenn" <Glenn@discussions.microsoft.com> wrote in message
>> news:0C62FA12-6F11-4C99-9B2C-373A8FA37571@microsoft.com...
>> > I'm using System.DirectoryServices.Protocols. I'm binding to an ADAM
>> > user.
>> > The basic functionality is working fine, correct passwords and user DNs
>> > successfully bind and incorrect passwords and user DNs fail.
>> >
>> > When the password is incorrect, but the user DN is correct I would
>> > expect
>> > that the badpwdcount attribute would be incremented. I'm not seeing
>> > that
>> > happen. Does anyone know why? I'm currently testing with ADAM
>> > installed
>> > on a
>> > Windows XP system. Has anyone seen this functionality work properly on
>> > Windows 2003?
>> >
>> > I
>> >
>> >
>> > --
>> > Glenn Sills
>>
>>
>>