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

WINDOWS SERVER

    Sponsored Links

    Next

  • 1. Undoing Single-Level Domain
    I had an NT domain named FM with a PDC and half a dozen BDCs. Except for these NT servers, all the clients in the domain are XP or 2000. I upgraded the PDC to Windows 2003, ran DCPromo, and created the AD domain "FM". DCPromo warned me against using a single-level domain, but since this location is the authority for this TLD, I went ahead with it. For the clients, this upgrade was transparent. In troubleshooting an issue with the DNS server on the Windows 2003 machine, I've had several people point out that the single-level domain is a "bad idea." What are my options at this point for undoing this decision? Can I "simply" rename the domain? How would doing this impact my NT BDCs and my clients, all of which still think they are living in an NT domain (ie they still log on to the FM domain)? The Windows 2003 machine is the only DC in the domain. Can I run DCPromo to return it to a regular server and then run it again giving it a two-level domain name? If I do this, will the current user and computer accounts be preserved?
  • 2. Win2k DC PDC to Win2k3 PDC
    From reading several of the postings I feel I have a good idea of how I want to do this but I just want conformation. I have a Win2k DC (Schema, PDC, Domain Naming masters) I want to use the same hardware and make it a Win2k3 DC (same Rolls) adprep has been run on the appropriate servers successfully. I believe from the articles I've read and the postings I can do the following. 1) Move all the rolls off to another DC 2) Demote the DC from the domain. 3) Remove it from the domain 4) Rebuild it from scratch as a Win2k3 server (stand alone) 5) Join the domain (member server) and promote it to a DC 6) Move all the above rolls back to it. Done. Additional Info: The server was originally a WinNT 4.0 PDC (first DC) upgraded to Win2k. This is why I want to rebuild it. It hasn't been reformatted in several years. As I go to Win2k3 I want to build it fresh. All the DC's I have were WinNT 4.0 upgraded to Win2k. I also have 2 other DC's (RID & Infrastructure masters) and WINS servers, and 1 is a DHCP server. I want to do this same process to these servers as well. Maybe 1 a week or so. If there is anything I missed or just don't know about, any suggestions would be greatly appreciated. Thanks
  • 3. specific problem with migration
    Dear friends, I'm writing you because I have a very specific problem with migration. I have one Windows 2000 Server which is Domain Controler for my domain, and another Windows 2000 server which is secondary domain controler. On PDC I also have DNS and DHCP. Now I want to migrate to Windows 2003 server, and in my testing enviroment everything went well. I've created another domain, create trust between them and migrated users and groups from one domain to another. In real situation I have 2 problems: 1. Target domain must keep the same name as the first one, because some applications wont work if domain name is changed. 2. I cann't join Windows 2003 server in existing domain because exept users, lot of junk and useless data will be copied from old domain. Does anyone knows what is the best way to solve this problem? Thank you for your help! Best Regards
  • 4. How to migrate CA to New DC
    Greetings, I have read the other post in this group, however it really doesn't answer my question. I have a very similar situation to the other poster, however I am decomissioning the server that one of our issuing CA's resides on. I have SERVERA which has the CA installed on it. SERVERB will replace the SERVERA functionality. I, like the other poster, cannot find any information on how to gracefully move the CA from one server to another. What's the best practice? Should I change the issuing CA in the directory and let all the PCs grab new certs? We use the computer certs for 802.1X so I don't want any interruption in service, etc. SERVERA is a Windows 2000 server and SERVERB is a Windows 2003 server. The hardware SERVERA is on is slated for decommission. Please help! Thanks! TMR
  • 5. Accessing shared folder from Service in 2003
    Our system consists of 2 machines, our service runs on both machines which needs to access a shared folder on the other machine. With W2k, we set the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Services\LanmanServer\ \Parameters\RestrictNullSessAccess to 0 and our service work fine. But in our new system which installed with 2003 standard edition, our service is not able to access the shared folder on the other machine even with that registry key set to 0. Our service starts up as system account with interactive turn on. Is there any other parameters in 2003 we need to set before a null session could access the shared folder ? -- Thanks and Regards.

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 85 guest