ADMT Problems

  • Thread starter Thread starter joe.beaulieu
  • Start date Start date
J

joe.beaulieu

Hi All,

I am migrating my NT4 domains to one new Win2003 AD. The process is
going quite well thanks to the ADMT v3. I have found only 3 issues
that I need help with.

1. Despite the fact I have added the Domain Admins group from the AD
domain to the Administrators Global Group on the NT4 domains ADMT
computer migration fails with a permissions issue (the tool does not
have permissions to access the admin$ share on the client computer). I
work around this by adding the Domain Admins group implicitly to the
local Administrators group on the target PC. This solves the problem,
but is obviously cumbersome. I have full two way trusts between the
NT4 and AD domains. Any clues?

2. I must change the DNS server listing on the client computer to point
to the new AD DNS server so that the ADMT migration client sees the
Global Catalog. I can do this easily for all of our DHCP clients, but
I still have many static users and servers that I need to address. Is
there a way to point my NT4 DNS server to the catalog?

3. Locally mapped drives are not migrating. We succesfully run the
ADMT and the clents profiles are migrated nicely. All desktop
features, printers, etc migrate perfectly. Only locally mapped drives
do not come across. Is there a way to get them to migrate with the
user profile?

Thanks in advance. I really appreciate the help and resource!

Joe
 
Hi

Check:
Migrating from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/downloads/...a0-76f0-4e25-8de0-19544062a6e6&DisplayLang=en

In Line
1. Despite the fact I have added the Domain Admins group from the AD
domain to the Administrators Global Group on the NT4 domains ADMT
computer migration fails with a permissions issue (the tool does not
have permissions to access the admin$ share on the client computer). I
work around this by adding the Domain Admins group implicitly to the
local Administrators group on the target PC. This solves the problem,
but is obviously cumbersome. I have full two way trusts between the
NT4 and AD domains. Any clues?
Click to expand...

Sounds like name resolution problems. Make sure that your NT servers DNS
properties point to your AD DNS server, and you can make Wins From your AD
DCs replicate with your Wins in Windows NT.
2. I must change the DNS server listing on the client computer to point
to the new AD DNS server so that the ADMT migration client sees the
Global Catalog. I can do this easily for all of our DHCP clients, but
I still have many static users and servers that I need to address. Is
there a way to point my NT4 DNS server to the catalog?
Click to expand...

- You only need a GC to logon if you have more than 1 Domain if your DFL is
at Windows 2000 Native or later. In your current configuration you must be
at Windows mixed that doesn't require GC to logon.
3. Locally mapped drives are not migrating. We succesfully run the
ADMT and the clents profiles are migrated nicely. All desktop
features, printers, etc migrate perfectly. Only locally mapped drives
do not come across. Is there a way to get them to migrate with the
user profile?
Click to expand...

- I don't know any way to migrate locally mapped drives, but assuming that
you're talking about mapped drives that your users manually created, if i'm
not mistaken they should come with the user profile.

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator
 
Back
Top