ADMT v3 ERR3:7585 The account replicator is unable to continue.

WINDOWS SERVER

    Sponsored Links

    Next

  • 1. Windows 2000 cluster to Windows 2003 cluster migration
    [Posted in microsoft.public.windows.server.clustering with no replies] Old cluster running on Windows 2000 Advanced Server. Old Kit. New cluster running on Windows Server 2003 Enterprise Edition. New Kit. All connected to same SAN and members of the same 2000 native domain. I would like to migrate all resources from the Old Cluster to the new Cluster. I created a test cluster group along with a test disk resource. Ensured it was working properly on both nodes of Old cluster. Deleted it as a resource of the old cluster. Unpresented the disk from the Old cluster and presented it to one node of the New cluster. Node detects the disk but sees it as Unknown and Unreadable. If rolling upgrades work where disks (and other resources) are assigned to one 2000 node, while the other is upgraded, and then the disks (and other resources) are flipped to the upgraded 2003 node while the other 2000 node is upgraded, it suggests to me that it can't be a 'moving 2000 disk to 2003 problem'. Does anyone have any suggestions on how to achieve the migration? Would prefer not to upgrade the existing cluster to 2003 first if at all possible. Thanks. Paul
  • 2. BIND Export/Import in the AD DNS during migration
    Hello. We're migrating from NT4 with BIND installed on Linux and need to import the BIND records into AD DNS. During testing, we saw that AD DNS installs as AD Integrated and uses the registry to store the zone info (as opposed the .dns file under \system32\dns). Is there a way to import the BIND entries into the AD Intergrated which is using AD and registry to store zones or do we have to make AD look use the \system32\dns\zone.dns file? If it needs to use the file, do we just drop the BIND entries in there or would it need some formatting first? THANKS IN ADVANCE!! Crunch time is here!!
  • 3. Linus BIND export/Import to AD DNS During migration
    Hello. We're migrating from NT4 with BIND installed on Linux and need to import the BIND records into AD DNS. During testing, we saw that AD DNS installs as AD Integrated and uses the registry to store the zone info (as opposed the .dns file under \system32\dns). Is there a way to import the BIND entries into the AD Intergrated which is using AD and registry to store zones or do we have to make AD look use the \system32\dns\zone.dns file? If it needs to use the file, do we just drop the BIND entries in there or would it need some formatting first? THANKS IN ADVANCE!! Crunch time is here!!
  • 4. Netware 4.11 - W2K3 MSDSS/FPNW auth issues
    I'm trying to provide a co-existence between a Novell 4.11 server and an AD I have set up. My DC is running SP1(and updates since) and the latest versions of the novell client and SFN (MSDSS). I can happily login to netware and see resources etc from the DC. My difficulty lies in the wizard in MSDSS. One step gets you to point to the tree/OU you want to sync, and credentials. I can see the OU I want and select it OK, but am getting an error with my login details (which I know are correct as I can login to windows with them). Error states: "Windows cannot authenticate to <path>... with the supplied credentials. The network path was not found." The reason behind this step is to get a netware client to be able to access files on another Windows 2003 server with FPNW on it. (This is a staged migration). On this server I can setup a share (via server manager!! - cant see how else to do that), that netware users ought to be able to see. They can see the alias of the server in the Novell connections (network neighbourhood idea), but cannot actually connect. My hunch is an authentication issue, hence MSDSS to create and sync user accounts. Incidentally I cannot see the netware tab in AD for my users, but can in computer management on the file server, so I know I am missing something here too! Any thoughts would be most welcome! Chris.
  • 5. moving data from win 2000 file server to win 2003 file server
    we had outgrown our old file server, so we have purchased a newer one with much more harddrive space. the old one was running windows 2000, the new one windows 2003. I am going to use the old one as a file server at one of our offsite plants, so they do not have to go across a VPN to access their files. I have a mixed domain, we have clients from windows 95, 98, 2000, and XP, currently have 2 windows 2000 servers (file server, email) and 1 NT 4.0. I have been looking at the Microsoft file migration wizard, but was wondering how it would work for me, as I was reading about it looks like most people were using this to move files from old server to new server, and then renaming the new server to have the same name as the old server? will I run into any curves since not all my clients can participate in active directory? I was thinking that the migration wizard might at least enable me to move files over to the new server so that I would only have to re-map drives on the windows 98 or 95 PCs, is that correct?

ADMT v3 ERR3:7585 The account replicator is unable to continue.

Postby QW5kcmV3IERvZGQ » Thu, 30 Apr 2009 20:06:02 GMT

Dear All,

I am in the middle of an office migration and I have hit a brick wall and I 
really need all your help...

Source domain NT4
Target domain w2k3r2
The source account is in the target domains Built in Administrators group so 
should have total rights over the target domain.

When running the ADMT wizard it completes but doesn't create the computer 
object. As the account is in the Administrators group I haven't needed to 
delegrate the permissions to the OU.


[Settings Section]
Task: Computer Migration (29)
ADMT Console
    User:       CBEASG\GADMBRYAN
    Computer:   cbegbrasgdc01.c (CBEGBRASGDC01)
        Domain:     cb.winadroot.com (CB)
        OS:         Microsoft Windows Server 2003 R2 5.2 (3790) Service Pack 2
Source Domain
    Name:   CBEASG
    DC:     CBUKHX01
        OS:     Windows NT 4.0 
Target Domain
    Name:   cb.wi.... (CB)
    DC:     cbegbrasgdc01 (CBEGBRASGDC01)
        OS:     Windows Server 2003 5.2 (3790) Service Pack 2
    OU:     LDAP://cb.winadroot.com/OU=Workstations,OU=EMEA-G...
Intra-Forest: No
Translate Option: Add
Translate Files:         Yes
Translate Local Groups:  Yes
Translate Printers:      Yes
Translate Registry:      Yes
Translate Rights:        Yes
Translate Shares:        Yes
Translate User Profiles: Yes
Conflict Option: Ignore
Perform Pre-check Only: No

[Object Migration Section]
2009-04-29 11:18:15 Starting Account Replicator.
2009-04-29 11:18:35 ERR3:7585 The account replicator is unable to continue.  
 Access is denied.
2009-04-29 11:18:35 Operation completed.

[Agent Dispatch Section]


Re: ADMT v3 ERR3:7585 The account replicator is unable to continue.

Postby Meinolf Weber [MVP-DS] » Thu, 30 Apr 2009 20:13:59 GMT

Hello Andrew,

Make sure that the user account you logged on to run ADMT is added into following 
groups:

- Local Administrators group.
- Target Domain Admin group
- Source Domain Admin group

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers 
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!  http://www.**--****.com/ 





Re: ADMT v3 ERR3:7585 The account replicator is unable to continue.

Postby Meinolf Weber [MVP-DS] » Thu, 30 Apr 2009 20:17:58 GMT

Hello Andrew,

Also make sure you can verify the trust:
 http://www.**--****.com/ 

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers 
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!  http://www.**--****.com/ 





Similar Threads:

1.ADMT v3 ERR3:7585 The account replicator is unable to continue

2.ADMT v3 ERR2:7697 & ERR2:7585 During Group Acct Migration

3.ADMT v3 error message ERR3:7330 during profile migration

I am migrating from an NT4 domain to a Windows 2003 domain using ADMT v3.  
During the local user profile migration I am getting the message: 

ERR3:7330 Failed to open registry key \Software\Classes, rc=87  The 
parameter is incorrect.

I do not get ERR3:7331 as someone else has reported and the profile is okay 
when the user logs in.    The complete log is posted below.

We are hoping to go into production with this migration in the next couple 
of days and I would like to know how I can correct this error.

Thanks

************  complete log below   ***********
2007-03-09 08:47:42 Active Directory Migration Tool - scripted computer 
migration started.

[Settings Section]
Task: Computer Migration (121)
ADMT Console
    User:       NT\res_migrator
    Computer:   swodcore003.xxxx.ad.yyy.net (SWODCORE003)
        Domain:     xxxx.ad.yyy.net (MEDSTAR)
        OS:         Microsoft Windows Server 2003 R2 5.2 (3790) Service Pack 1
Source Domain
    Name:   NT
    DC:     NTDC01
        OS:     Windows NT 4.0 
Target Domain
    Name:   xxxx.ad.yyy.net (XXXX)
    DC:     swodcore003.xxxx.ad.yyy.net (SWODCORE003)
        OS:     Windows Server 2003 5.2 (3790) Service Pack 1
    OU:     LDAP://swodcore003.xxxx.ad.yyy.net/OU=Computers,OU=OPERATING 
ROOM,OU=lll,DC=xxxx,DC=ad,DC=yyy,DC=net
Intra-Forest: No
Translate Option: Add
Translate Files:         No
Translate Local Groups:  No
Translate Printers:      No
Translate Registry:      No
Translate Rights:        No
Translate Shares:        No
Translate User Profiles: Yes
Conflict Option: Ignore
Perform Pre-check Only: No

[Object Migration Section]
2007-03-09 08:47:42 Starting Account Replicator.
2007-03-09 08:47:58 CN=ORTEST1           - Created
2007-03-09 08:47:58 	- Set password for CN=ORTEST1.
2007-03-09 08:47:58 CN=ORTEST2           - Created
2007-03-09 08:47:58 	- Set password for CN=ORTEST2.
2007-03-09 08:47:58 Operation completed.

[Agent Dispatch Section]
2007-03-09 08:47:59 Read 207 accounts from the database that were previously 
migrated from the domain 'NT' to the domain 'xxxx.ad.yyy.net'.
2007-03-09 08:48:00 Created account input file for remote agents: 
Accounts000121.txt
2007-03-09 08:48:01 Installing agent on 2 servers
		 		
2007-03-09 08:48:01 The Active Directory Migration Tool Agent will be 
installed on ORTEST1
2007-03-09 08:48:01 The Active Directory Migration Tool Agent will be 
installed on ORTEST2
2007-03-09 08:48:04 Started job:  ORTEST1 000121_ORTEST1 
{E5AA4913-33C7-48DF-BC36-ECA2AD4B7C4F}
2007-03-09 08:48:07 Started job:  ORTEST2 000121_ORTEST2 
{103BF0C8-6103-45C0-8373-B9F1510FDE03}
2007-03-09 08:52:31 Done waiting for the computer 'ORTEST2' to reboot.
2007-03-09 08:52:31 Post-check passed on the computer 'ORTEST2'.  The new 
computer name is 'ORTEST2'.
2007-03-09 08:53:01 Done waiting for the computer 'ORTEST1' to reboot.
2007-03-09 08:53:01 Post-check passed on the computer 'ORTEST1'.  The new 
computer name is 'ORTEST1'.
					

[Agent Summary Section]
***** Start of Pre-check Summary *****
Machine Name	Status	Message
ORTEST1     	Passed	
ORTEST2     	Passed	
***** End of Pre-check Summary *****
***** Start of Agent Operation Summary *****
For more information about operations that completed with warnings or 
errors, refer to the Agent Details section.
Machine Name	Status               	Message
ORTEST2     	Successful           	
ORTEST1     	Completed with Errors	
***** End of Agent Operation Summary *****
***** Start of Post-check Summary *****
Machine Name	Status	Message
ORTEST1     	Passed	
ORTEST2     	Passed	
***** End of Post-check Summary *****

[Agent Details Section]

Details for ORTEST1
ocal Machine
    Computer:   ortest1 (ORTEST1)
        Domain:      (NT)
        OS:         Microsoft Windows XP 5.1 (2600) Service Pack 2
2007-03-09 08:48:06 Starting Security Translator.
2007-03-09 08:48:06 Agent is running in local mode.
2007-03-09 08:48:06 Read 207 accounts from 
C:\WINDOWS\OnePointDomainAgent\Accounts000121.txt
2007-03-09 08:48:06 SecurityTranslation Profiles:Yes RecycleBin:Yes 
TranslationMode:Add NT xxxx.ad.yyy.net 
2007-03-09 08:48:06 Starting
2007-03-09 08:48:06 Translating local machine.
2007-03-09 08:48:08 Skipping A:\, rc=21   The device is not ready.
2007-03-09 08:48:08 Processing C:\
2007-03-09 08:48:08 Processing recycle bin files and folders on C:\.
2007-03-09 08:48:08 Examining: S-1-5-21-2564294346-3307217056-2826650621-500
2007-03-09 08:48:08 Examining: S-1-5-21-357464061-3564997506-3233852318-500
2007-03-09 08:48:08 Skipping D:\.  D:\ is a CD-ROM drive.
2007-03-09 08:48:08 Translating user profile, source account='Altiris', 
target account='Altiris'
2007-03-09 08:48:22 Translating user profile, source account='kimyd', target 
account='kimyd'
2007-03-09 08:48:23 ERR3:7330 Failed to open registry key \Software\Classes, 
rc=87  The parameter is incorrect.
2007-03-09 08:48:24 Translating user profile, source account='kielyj', 
target account='kielyj'
2007-03-09 08:48:31 Translating user profile, source account='kimmimi', 
target account='kimmimi'
2007-03-09 08:48:33 Translating user profile, source account='kid1', target 
account='kid1'
2007-03-09 08:48:34 ERR3:7330 Failed to open registry key \Software\Classes, 
rc=87  The parameter is incorrect.
2007-03-09 08:48:35 ------Account Detail---------
2007-03-09 08:48:35 The account detail section uses the following format: 
AccountName(OwnerChanges, GroupChanges, DaclChanges, SaclChanges).
2007-03-09 08:48:35 Altiris (18, 0, 4150, 0) 
2007-03-09 08:48:35 kid1 (35, 0, 1626, 0) 
2007-03-09 08:48:35 kielyj (31, 0, 1621, 0) 
2007-03-09 08:48:35 kimmimi (33, 0, 1621, 0) 
2007-03-09 08:48:35 kimyd (39, 0, 1628, 0) 
2007-03-09 08:48:35 -----------------------------
2007-03-09 08:48:35 60 users, 147 groups
2007-03-09 08:48:35 207 accounts selected.  207 resolved, 0 unresolved.
2007-03-09 08:48:35            Examined        Changed     Unchanged
2007-03-09 08:48:35 Files              0              0             0
2007-03-09 08:48:35 Dirs               0              0             0
2007-03-09 08:48:35 Shares             0              0             0
2007-03-09 08:48:35 Members            0              0             0
2007-03-09 08:48:35 User Rights        0              0             0
2007-03-09 08:48:35 Exchange Objects          0              0             0
2007-03-09 08:48:35 Containers         0              0             0
2007-03-09 08:48:35 DACLs           9308           8539           769
2007-03-09 08:48:35 SACLs              0              0             0
2007-03-09 08:48:35            Examined        Changed     No Target   Not 
Selected     Unknown
2007-03-09 08:48:35 Owners         9308            156          9152         
     0           0
2007-03-09 08:48:35 Groups         9308              0          9308         
     0           0
2007-03-09 08:48:35 DACEs         48558          10646         37912         
 37912           0
2007-03-09 08:48:35 SACEs             0              0             0         
     0           0
2007-03-09 08:48:39 Changed domain affiliation of local computer to 
medstar.ad.medstar.net.
2007-03-09 08:48:39 The local machine will be rebooted in 1 minutes.
2007-03-09 08:48:39 Wrote result file 
C:\WINDOWS\OnePointDomainAgent\000121_ORTEST1.result
2007-03-09 08:48:39 Operation completed.



4.ADMT v3.0 ERR3: 7438 no NTUser.DAT file for "user" was found

I am doing an interforest migration and trying to migrate a user from
domain a (source domain) --> domain b (target domain).  We are
currently housing profiles using DFS (on a Windows Server 2003 R2
server) on a box named File01 which is in domain a.
When ADMT v3 is ran(translate roaming profile option selected) for a
test user we receive an error like the one below in the log.  I am
specifically concerned about is "ERR3: 7438 no NTUser.DAT file for
testuser was found.  The roaming profile cannot be migrated"



[Settings Section]
Task: User Migration (9)
ADMT Console
User: NEWDOMAIN\administrator
Computer: domctl2.newdomain.local (DOMCTL2)
Domain: newdomain.local (NEWDOMAIN)
OS: Microsoft Windows Server 2003 5.2 (3790) Service Pack 2
Source Domain
Name: olddomain (olddomain)
DC: sc-domctl1.olddomain (SC-DOMCTL1)
OS: Windows 2000 Server 5.0 (2195) Service Pack 4
OU:
Target Domain
Name: newdomain.local (NEWDOMAIN)
DC: domctl2.newdomain.local (DOMCTL2)
OS: Windows Server 2003 5.2 (3790) Service Pack 2
OU: LDAP://newdomain.local/OU=newdomainUsers,DC=newdomain,DC=local
Intra-Forest: No
Password Option: Generate passwords, only for new objects = Yes
Password File: 'C:\WINDOWS\ADMT\Logs\passwords.txt'
Migrate Security Identifiers: No
Update Rights: Yes
Translate Roaming Profiles: Yes
Fix group membership: Yes
Conflict Option: Ignore
Source Disable Option: Leave source account
Source Expiration: Do not expire source account
Target Disable Option: Enable target account
Migrate groups: No
Migrate service accounts: Yes

[Object Migration Section]
2007-05-24 10:45:17 Starting Account Replicator.
2007-05-24 10:45:18 CN=Test User - Created
2007-05-24 10:45:18 CN=Test User - Strong password generated.
2007-05-24 10:45:18 WRN1:7874 Disabled the "password never expires"
account option for account 'CN=Test User'.
2007-05-24 10:45:18 ERR3:7438 No NTUser.DAT file for testuser was
found in \\newdomain.local\C$\DFSRoots\User\Profile\testuser. The
roaming profile cannot be migrated.
2007-05-24 10:45:18 Updated user rights for CN=Test User
2007-05-24 10:45:18 Operation completed.

5.ADMT Error 7585: Access Denied when migrating users with group

6. ADMT Error 7585: Access Denied when migrating users with groups

7. Importing existing ADMT v3 database to another ADMT v3 server

8. ADMT v3 Automatically disables migrated account



Return to WINDOWS SERVER

 

Who is online

Users browsing this forum: No registered users and 37 guest