Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ADMT agent and migration of workstations

0 views
Skip to first unread message

Мишуров Вячеслав Геннадьевич

unread,
Jan 21, 2005, 12:49:40 AM1/21/05
to
Hello !
For the beginning I am sorry for my English :)

I have a problem with migration of computers from one domain Win2k3 in
another (in different forests).

Users accounts and groups I have transferred, now migrate computers, all of
them on WinXP.
I start ADMT on target domain DOMAIN2 and logged in as user of source domain
DOMAIN1\Administrator.
The trust between domains is established.

So: ADMT writes, that the agent is established, works, then speaks is
completed.
Registration record for a computer in the new domain is created, but the
computer remains in the old domain,
profiles of users are not transferred, the computer is not reloaded.
I.e. it is real ADMT Agent does nothing.

I has transferred Win2k3 server from source domain to target
(not the controller of the domain, simply a member of the domain) - all has
passed without errors.
This server has joined the target domain, profiles of users, rights on files
migrated, and itself it was reloaded ...
That with XP not so...

Who than can help? In what direction to search?

Yours faithfully, Vyacheslav.

P.S.
Here that we have in logs:

1. On the target domain - Migration.log

2005-01-21 10:39:40
2005-01-21 10:39:40 Active Directory Migration Tool, Starting...
2005-01-21 10:39:40 Starting Account Replicator.
2005-01-21 10:39:40 Account Migration DOMAIN1 DOMAIN2 CopyUsers:No
CopyGlobalGroups:No CopyLocalGroups:No CopyComputers:Yes
2005-01-21 10:39:40 CN=MYCOMP - Created
2005-01-21 10:39:40 - Set password for MYCOMP.
2005-01-21 10:39:41 Operation completed.
2005-01-21 10:44:46 ***** Start of Agent Completion Status Summary *****
2005-01-21 10:44:46 Machine Name Completion Status Error Message
Log File Path

If on the domain controller language set to English:
2005-01-21 10:44:46 MYCOMP.DOMAIN1 Status Unknown
If on the domain controller language set to Russian:
2005-01-21 10:44:46 MYCOMP.DOMAIN1 Finished

2005-01-21 10:44:46 ***** End of Agent Completion Status Summary *****


2. On the target domain - Dispatch.log

2005-01-21 10:39:55 Created account input file for remote agents:
DCTCache.048
2005-01-21 10:39:55 Installing agent on 1 servers
2005-01-21 10:39:55 The Active Directory Migration Tool Agent will be
installed on \\MYCOMP.DOMAIN1
2005-01-21 10:39:59 The agent is installed on \\MYCOMP.DOMAIN1
2005-01-21 10:39:59 Started job:\\MYCOMP.DOMAIN1 MYCOMP72308656
{F10A49FE-33DA-4EC3-96F3-372AA356148A}
2005-01-21 10:39:59 All agents are installed. The dispatcher is finished.


3. On the target domain - Dispatch.csv

2005-01-21 10:39:54 C:\Program Files\Active Directory Migration
Tool\Logs\Dispatch.log
2005-01-21 10:39:54 C:\Program Files\Active Directory Migration
Tool\Logs\Agents\
2005-01-21 10:39:55 1
2005-01-21 10:39:55 \\MYCOMP.DOMAIN1 WillInstall 0
2005-01-21 10:39:55 \\MYCOMP.DOMAIN1 JobFile 0,0,C:\Program Files\Active
Directory Migration Tool\Logs\Agents\MYCOMP72308656
2005-01-21 10:39:55 \\MYCOMP.DOMAIN1 RemoteResultPath
\\MYCOMP.DOMAIN1\C$\Program Files\OnePointDomainAgent\
2005-01-21 10:39:59 \\MYCOMP.DOMAIN1 Install 0
2005-01-21 10:39:59 \\MYCOMP.DOMAIN1 Start
0,MYCOMP72308656,{F10A49FE-33DA-4EC3-96F3-372AA356148A}
2005-01-21 10:39:59 All Finished 0


4. On the workstation - Migration.log

If on the domain controller language set to English:
File is not created


If on the domain controller language set to Russian:

2005-01-21 10:57:48 Active Directory Migration Tool, Starting...
2005-01-21 10:57:48 Wrote result file C:\Program
Files\OnePointDomainAgent\MYCOMP72308656.result
2005-01-21 10:57:48 Operation completed.


4. On the workstation - Application Events, source ADMTAgent

10:57:46 Initializing OLE subsystem.
10:57:46 Registering Components
10:57:46 Registered McsVarSetMin.dll
10:57:46 Registered McsDctWorkerObjects.dll
10:57:46 Registered ADMTAgnt.exe
10:57:46 Creating Instance of agent.
10:57:46 Agent service has not been locally installed, rc=2,
10:57:46 Initializing RPC connection.
10:57:46 Listening...
10:57:48 Starting plug-in file registration.
10:57:48 Done Registering plug-in files.
10:57:48 Started job: {F10A49FE-33DA-4EC3-96F3-372AA356148A}

If on the domain controller language set to English:

10:58:48 Monitoring job {F10A49FE-33DA-4EC3-96F3-372AA356148A}, Status: In
progress
10:59:48 Monitoring job {F10A49FE-33DA-4EC3-96F3-372AA356148A}, Status: In
progress
11:00:48 Monitoring job {F10A49FE-33DA-4EC3-96F3-372AA356148A}, Status: In
progress
..........
11:10:48 Monitoring job {F10A49FE-33DA-4EC3-96F3-372AA356148A}, Status: In
progress
11.11.48 Monitoring job {F10A49FE-33DA-4EC3-96F3-372AA356148A}, Status:
Completed with Errors

On the workstation language was set to Russian.


Rebecca Chen [MSFT]

unread,
Jan 21, 2005, 8:43:22 AM1/21/05
to
Hello,

I would like to confirm the following information:

1. What is the Operating system version on both DCs, English version or
Russian version?

2. What is the meaning of "If on the domain controller language set to
English, File is not created"?

3. Have you added the DOMAIN1\Administrator to DOMAIN2\Domain admins group
and add DOMAIN2\Administrator to DOMAIN1\Domain admins group?

I suggest you take a carefully look at the following KB and follow the
steps to check the status:

326480 How to Use Active Directory Migration Tool Version 2 to Migrate from
Windows 2000 to Windows Server 2003
<http://support.microsoft.com/?id=326480>

Active Directory Migration Tool Overview
http://w
ww.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.asp

Any update, let us get in touch!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Мишуров Вячеслав Геннадьевич

unread,
Jan 23, 2005, 11:23:13 PM1/23/05
to
Hello. Thanks for the answer.

> 1. What is the Operating system version on both DCs, English version or
> Russian version?

English version with MUI.

> 3. Have you added the DOMAIN1\Administrator to DOMAIN2\Domain admins group
> and add DOMAIN2\Administrator to DOMAIN1\Domain admins group?

Yes.

> I suggest you take a carefully look at the following KB and follow the
> steps to check the status:
>
> 326480 How to Use Active Directory Migration Tool Version 2 to Migrate
> from
> Windows 2000 to Windows Server 2003
> <http://support.microsoft.com/?id=326480>
>
> Active Directory Migration Tool Overview
> http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.asp

I have already closely studied the documents specified by you.

Here that I have found out on Friday:

If the current language on DC chooses Russian ADMT writes, that the agent is
established-> works-> has successfully finished work, but on a workstation
the agent does nothing.
If the current language on DC chooses English ADMT writes, that the agent is
established-> works-> the status is unknown, and on a workstation the agent
all carries out correctly.

There was one mistake. ADMT Agent does not reload a workstation.
On the workstation: Event viewer -> Application -> ERR2:7267 The agent
service will not perform the requested action. The caller may not be an
administrator on this machine, rc=5 Access denied.

I start ADMT on target domain DOMAIN2 and logged in as user of source domain
DOMAIN1\Administrator.

Group "DOMAIN1\Domain Admins" is included into local group "Administrators"
on a workstation.

Best regards,
Vyacheslav.

Rebecca Chen [MSFT]

unread,
Jan 25, 2005, 5:30:57 AM1/25/05
to
Hello,

According to your description, this issue seems to relate to the language.
A follow up question is what the OS version on the client? In other word,
is the client OS English version or Russian version?

We may need detailed ADMT logs and client's event logs to do the further
research.

0 new messages