Problems with adamsync between one AD LDS and two AD DS services

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



I am trying to use adamsync to sync user data from two separate ad forests
into a single AD LDS instance. I need all the user data to be in the same
partition because I want to add those users to groups within that same
partition.

I first started to experiment with ADAM SP1 on server 2003. I had a single
ADAM instance with a single application partition…dc=myadam,dc=myappdomain. I
had two OUs within the app partition that contained user data. The RDNs were
ou=corpdomain1users and ou=corpdomain2users. Each OU had its own
configurationFile which synchronized user data from dc=corpdomain1,dc=com and
dc=corpdomain2,dc=grp to ou=corpdomain1users,dc=myadam,dc=myappdomain and
ou=corpdomain2users,dc=myadam,dc=myappdomain respectively. I ran and initial
full sync and subsequent syncs without any issue.

However, now I am trying to set up a similar directory in AD LDS on server
2008. The partition and OU structure are identical. However, when I try to
install the configurationFile to either of my OUs (which are not heads of
partitions) I get the following error from Adamsync…..

The target partition given was not the head of a partition. AdamSync cannot
con
tinue.
DN of input: OU=corpdomain2users, DC=myadam, DC=myappdomain

Anyone know if:
This is a new feature in AD LDS over ADAM on server 2K3?
It is possible to change this behavior through configuration in the directory?
The format of the adamsync xml config has changed and if so where it is
documented? I have been all over technet and the doc bundled with AD LDS and
have found nothing.
There is a better way to do accomplish this?

Thanks in advance!

.



Relevant Pages

  • Re: Problems with adamsync between one AD LDS and two AD DS servic
    ... At first glance I would have assumed that checking that the source partition ... > into a single AD LDS instance. ... I need all the user data to be in the> same ... > configurationFile which synchronized user data from ...
    (microsoft.public.windows.server.active_directory)
  • Re: Problems with adamsync between one AD LDS and two AD DS servic
    ... At first glance I would have assumed that checking that the source partition ... had two OUs within the app partition that contained user data. ... configurationFile which synchronized user data from dc=corpdomain1,dc=com ... now I am trying to set up a similar directory in AD LDS on server ...
    (microsoft.public.windows.server.active_directory)
  • Re: Problems with adamsync between one AD LDS and two AD DS services
    ... At first glance I would have assumed that checking that the source partition ... had two OUs within the app partition that contained user data. ... configurationFile which synchronized user data from dc=corpdomain1,dc=com ... now I am trying to set up a similar directory in AD LDS on server ...
    (microsoft.public.windows.server.active_directory)
  • Re: SBS 2003 SP1 disk filling up.
    ... You should move the user data files or anything that grows, ... a separate set of drives/spindles. ... Using a single partition makes life easier, ... I have removed a lot of unused programs which gave me about 4GB, ...
    (microsoft.public.windows.server.sbs)
  • Re: New partition in Vista home basic?
    ... in the new partition, would I be able to open them as normal? ... and I know the vast number of pictures and documents and scans ... It is therefore imperative that you back up all user data onto an external drive or use your CD/DVD burning software to dopy user data onto CD/DVD. ...
    (microsoft.public.windows.vista.performance_maintenance)