User samification is failing when user is moved from non-dsfw container to DSfW container

The DSfW server is not the master of the partition where the user is being moved to.

User samification is failing when user is moved from non-dsfw container to DSfW
container.

The ndstrace.log  below is taken when moving a user "ss" from non-dsfw
container to dsfw container.

S-32-2:~ # [2010/04/22 16:50:03.321] SAM: Objecttype is unknown [0000806c]
<.grandchld.skp2.child.skp1.parent.kar.co.ra.RR-TREE.> 806c
[2010/04/22 16:50:03.333] SAM: Objecttype is unknown [00008805]
<.ss.Users.grandchld.skp2.child.skp1.parent.kar.co.ra.RR-TREE.> 8805
[2010/04/22 16:50:03.352] SAM: Objecttype is unknown [0000806c]
<.grandchld.skp2.child.skp1.parent.kar.co.ra.RR-TREE.> 806c
[2010/04/22 16:50:03.353] SAM: Objecttype is unknown [0000806c]
<.grandchld.skp2.child.skp1.parent.kar.co.ra.RR-TREE.> 806c

In OES2SP3 the DSfW server does not have to be the Master of the replicas of the domain.  The consequence that can result is users that are moved into the domain might not get provisioned or "samified" right away.  It can take up to 30 minutes before the users are provisioned for DSfW use.

If the users need to be provisioned immediately the solution is to run the domaincntl tool.

Example of provisioning users in a domain called novell.com:

domaincntrl --samify -a novell.com