Re: AD users cannot logon to ADAM

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi

the transform needs to be done on the initial sync operation.
The "illegal modify operation" is often the result of an invalid
<target-object-class>.

Try following the example in the blog entry against a clean install of
ADAM. If you need extra attributes to be imported then you need to:
[1] include those attributes in your userProxy class in ADAM, see
the MS-UserProxyFull.ldf file for examples
[2] add those attributes to your <include> elements in the XML config

If you need more help please start a new thread as Joe suggested.

Thanks
Lee Flight

<terryoip@xxxxxxxxx> wrote in message
news:1183688549.285446.147680@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have followed the steps of the below link provided by Lee Flight
before, but I found that it cannot transform the user object to
userProxy object.


http://blogs.technet.com/efleis/archive/2005/09/23/adamsync-can-also-transform-users-in-to-proxy-users.aspx

I have strightly followed the steps provided and only changed the
<object-filter> from (objectCategory=person) to (objectCategory=*). It
is because I have other data would like to sync.

Besides, I have tried to change the objectClass "user" to "userProxy"
manually via ADSI Edit. However, I got the error "Illegal modify
operation. Some aspect of the modification is not permitted."

Can you please give me some advice? Thanks!

Terry

P.S.: My objective is to make sure Mac user can connect to the AD
through ADAM using Entourage.



.