Move ADAM directory partition from 2003 srv 32-bit to 2008 64-bit?

jope

unread,

Apr 30, 2010, 3:04:01 AM4/30/10

to

We are trying to migrate from 2003 server to 2008.
What is the best practice for moving an AD LDS (ADAM) directory partition
from 2003 server to 2008, maybe someone can point me in the right direction.

Our special need is that the objectSids in ADAM remain the same after the
move, so export/import would not work for us.

We tried some different approaches but all failed so far.
- Backup/restore ?
Can this even be done with 32-bit to 64-bit files ?
- Replication ?
Seems to work initially, but after we transfer the naming master role and
schema to the new server and turn off the original server we get referral
error when trying to contact 2008 server directory partition.

Thanks
Johan P

jope

unread,

Apr 30, 2010, 8:04:01 AM4/30/10

to

Tried the replication way some more...
I got stuck a bit earlier than I thought, before I just tested with
2003->2003..

On 2008 R2 server, when trying to create a replica of an ADAM directory
partition from a ADAM instance in a 2003 server I can select the server and
partition in the wizard, but when doing the real action it fails.
Both machines is connected to same AD, logged in as domain administrator.
Someone know what credentials I should provide and where ???
Or why this dont work ?

Thanks

Error message:
Active Directory Lightweight Directory Services could not create the NTDS
Settings object for this Active Directory Lightweight Directory Services
instance CN=NTDS
Settings,CN=REQ2008$MyDirectory,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={97429456-1B07-4F15-83BC-EFE25CD2A23C}
on the remote AD LDS instance 192.168.0.25:389. Ensure the provided network
credentials have sufficient permissions.
Error code: 0x80070057
The parameter is incorrect.

From adamsetup.log:
adamsetup 5E0.380 042E 12:08:25.678 STATUS: Creating the NTDS Settings
object for this Active Directory Lightweight Directory Services instance on
the remote AD LDS instance 192.168.0.25:389...
adamsetup 5E0.380 042F 12:08:25.710 STATUS: EVENTLOG (Error): ADAM
[MyDirectory] Replication / DS RPC Client : 2513
Attempting to set the desired authentication protocol for a connection to
the following DSA failed.

DSA:

192.168.0.25:389

Additional Data:

Error:

87 The parameter is incorrect.

adamsetup 5E0.380 0430 12:08:25.710 STATUS: EVENTLOG (Error): ADAM
[MyDirectory] Replication / Setup : 1125
The Active Directory Lightweight Directory Services Installation Wizard
(Dcpromo) was unable to establish connection with the following domain
controller.

Domain controller:
192.168.0.25:389

Additional Data

Error value:
87 The parameter is incorrect.

adamsetup 5E0.380 0431 12:08:25.710 Enter GetErrorMessage 80070057
adamsetup 5E0.380 0432 12:08:25.710 AD Install Error (87): Active
Directory Lightweight Directory Services could not create the NTDS Settings
object for this Active Directory Lightweight Directory Services instance
CN=NTDS
Settings,CN=REQ2008$MyDirectory,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={97429456-1B07-4F15-83BC-EFE25CD2A23C}
on the remote AD LDS instance 192.168.0.25:389. Ensure the provided network
credentials have sufficient permissions.
adamsetup 5E0.380 0433 12:08:25.710 STATUS: EVENTLOG (Error): ADAM
[MyDirectory] General / Internal Processing : 1168
Internal error: An Active Directory Lightweight Directory Services error has
occurred.

Additional Data

Error value (decimal):
-1073741823

Error value (hex):
c0000001

Internal ID:
300162a

adamsetup 5E0.380 0434 12:08:25.803 STATUS: EVENTLOG (Informational):
ADAM [MyDirectory] General / Service Control : 1004
Active Directory Lightweight Directory Services was shut down successfully.

jope

unread,

May 3, 2010, 5:04:01 PM5/3/10

to

Problem solved, rejoin domain made the trick.

blakew

unread,

May 27, 2010, 11:24:34 AM5/27/10

to

Can you explain your solution more? Which machine did you demote and re-promote? We are a win2k3 going to win2k8r2 and are receiving the same error.

thanks

jope wrote:

Problem solved, rejoin domain made the trick."jope" wrote:

03-May-10