Windows Server - NT4 to AD2003 migration

Asked By wchar

04-Sep-07 12:42 AM

Hello all,

We are in the process of moving our entire domain from an NT4 domain
to a Windows 2003 Server R2 domain. We have setup a trust relationship
between the two domains and all is good. Until we try to migrate the
computer accounts using ADMT 3.0.

When we start the migration tool, it appears to run with no errors.
However when we try to perform the restart of the PC, the migration
reports says the following:


2007-08-23 11:34:45 The Active Directory Migration Tool Agent will be
installed on DPTEST1
2007-08-23 11:35:01 Started job: DPTEST1 000013_DPTEST1 {BFF4E7EE-
F639-4F11-B34F-6A3A9ACEABD9}
2007-08-23 11:39:41 ERR2:7711 Unable to retrieve the DNS hostname for
the migrated computer 'DPTEST1'. The ADSI property cannot be found in
the property cache.
(hr=0x8000500d)
2007-08-23 11:39:41 Post-check will be retried on the computer
'DPTEST1'.
2007-08-23 11:40:45 ERR2:7711 Unable to retrieve the DNS hostname for
the migrated computer 'DPTEST1'. The ADSI property cannot be found in
the property cache.
(hr=0x8000500d)

I searched this but with no luck. Could some perhaps guide me in the
right direction?

Thanks all, I really appreciate the help!

04-Sep-07 02:54 AM

Hello,

Thank you for using newsgroup!

Could you help us confirm if some users do not load old profile and instead
they get a new profile? If so, based on my research, this similar issue may
be related to NTFS permission. I suggest you try to run Security
Translation Wizard.

835991: How to use a SID mapping file with the ADMT tool to perform a
resource domain migration to Windows Server 2003
http://support.microsoft.com/kb/835991

Domain Migration Cookbook
Chapter 11: Intraforest Migration
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook
/cookch11.mspx

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security <http://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.





--------------------
04:42:59 GMT)
NET CLR 2.0.50727; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
cwix.com!newsfeed.cwix.com!newsfeed.gamma.ru!Gamma.RU!postnews.google.com!r3
4g2000hsd.googlegroups.com!not-for-mail
microsoft.public.windows.server.migration:2027

04-Sep-07 11:07 AM

Are you running the ADMT tool from a remote office?

Don't forget that once the agent runs on the workstation, when the
workstation reboots it is now workstation.newdomain.com and it registers
itself there.  If the ADMT is running from a remote office, it might take
time for replication to occur.

You can work around this issue by making sure that the DNS server that the
computer running ADMT is using is the same physical address that the
workstation is using.  Also, be sure that the client tcp/ip properties are
set to register the DNS name (or that their DHCP registers it for them).

Also, if you wait long enough, the postcheck should restart and complete
normally once the DNS propegates.  That is why the postcheck has adjustable
restart settings on the agent screen.

John R

11-Sep-07 06:49 AM

Hi,

I am just writing to see how everything is going. If you have any updates
or need any further assistance on this issue, please feel free to let me
know.

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security <http://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.





--------------------
microsoft.public.windows.server.migration:2028
instead
may
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook
rights.
SV1;
posting-host=202.82.183.10;
cwix.com!newsfeed.cwix.com!newsfeed.gamma.ru!Gamma.RU!postnews.google.com!r3