Archived from groups: microsoft.public.win2000.active_directory (More info?)
We current have an NT 4 PDC used for network logons (about 60 users) and a
few older apps (it is the only NT 4 box - no BDCs). We realize this
situation is not good and want to migrate as much as possible to an existing
win2k domain used primarily for email. We need to maintain the desktop
profiles and migrate any other system and computer accounts needed. The
win2k (mixed mode) domain already has the same users and computers in AD. We
have kept the user account information and passwords the same in both
domains. We have been advised to look at ADMT. It looks like a possible
tool to use, however, we discovered we have to go to native mode on the win2k
domain to run any trial migration tests - which we plan to do.
My questions are:
1. How do we get the user accounts to the AD (since they already exist)
and effectively "add" the NT profile/security info. to their win2k
information without causing issues with their current win2k accounts/email
(exchange 2000 - going to 2003) ?
2. Which of the NT4 system accounts, if any, will we need to migrate?
3. Do we need to migrate any computer accounts from the NT4 box since the
computers already exist in the win2k AD?
4. Users will still need access to the NT4 box for some of the older apps.
The firm has been reluctant to upgrade to newer versions for cost reasons.
Will going to native mode in the win2k domain have any impact on the NT to
win2k domains trusts currently in place (i.e. they won't work)? I have
tried to find information on what going to native mode actually means (other
then you can't have nt4 systems in the domain). How much risk is there
(since you can't go back)?
Thanks for your help and guidance - your suggestions or pointers to
resources would be much appreciated. This is a small firm with no spare
systems to experiment on, so we need to find a good process for making this
happen.
We current have an NT 4 PDC used for network logons (about 60 users) and a
few older apps (it is the only NT 4 box - no BDCs). We realize this
situation is not good and want to migrate as much as possible to an existing
win2k domain used primarily for email. We need to maintain the desktop
profiles and migrate any other system and computer accounts needed. The
win2k (mixed mode) domain already has the same users and computers in AD. We
have kept the user account information and passwords the same in both
domains. We have been advised to look at ADMT. It looks like a possible
tool to use, however, we discovered we have to go to native mode on the win2k
domain to run any trial migration tests - which we plan to do.
My questions are:
1. How do we get the user accounts to the AD (since they already exist)
and effectively "add" the NT profile/security info. to their win2k
information without causing issues with their current win2k accounts/email
(exchange 2000 - going to 2003) ?
2. Which of the NT4 system accounts, if any, will we need to migrate?
3. Do we need to migrate any computer accounts from the NT4 box since the
computers already exist in the win2k AD?
4. Users will still need access to the NT4 box for some of the older apps.
The firm has been reluctant to upgrade to newer versions for cost reasons.
Will going to native mode in the win2k domain have any impact on the NT to
win2k domains trusts currently in place (i.e. they won't work)? I have
tried to find information on what going to native mode actually means (other
then you can't have nt4 systems in the domain). How much risk is there
(since you can't go back)?
Thanks for your help and guidance - your suggestions or pointers to
resources would be much appreciated. This is a small firm with no spare
systems to experiment on, so we need to find a good process for making this
happen.
Facebook
Twitter
Instagram