Re: How to Eliminate NT Domain/Move Settings to Win2k
- From: Diane <Diane@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 3 Jul 2007 09:08:03 -0700
Thanks Danny for your clear explanation of the implications of moving to
native mode. Very helpful.
Diane
"Danny Sanders" wrote:
.. I have not tried ADMT as it requires native.
mode and I'm a little concerned about causing issues between the domains
that
would result in logon issues causing an immediate disaster.
The switch to native mode will affect the replication between a Win 2k DC
and a NT 4.0 BDC in the same domain. It has no affect on trusts, trusted
domains, clients in the NT or Win 2k domain, clients in trusted domains,
servers in trusted domains, BDCs in trusted domains. It ONLY prevents
replication between an AD DC and a NT 4.0 BDC in the same domain.
Add a user to a Win 2k native mode domain, using the Win 2k DC, and that
user will not get replicated to a NT 4.0 BDC in the same domain.
hth
DDS
"Diane" <Diane@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4DADC8CD-7811-424E-BD18-6745B531BC87@xxxxxxxxxxxxxxxx
Hello - I have seen the posts on migrating NT4 to a clean win23k
environment,
however, I have inherited a different situation and would greatly
appreciate
some guidance.
Environment:
Servers: (3) Win2k (non-SBS) - 2DCs, (1) Win2003, (1) NT4
Clients: About 50 (all XP Pro except for one win 2K Pro).
Domains: (1) on an NT4 PDC, (1) win2k/AD
The NT4 server is used only for network logons under one domain (no BC).
There is also a second win2K domain (mixed mode) set up for exchange 2003
along with some other server apps. There is a trust relationship set up
between the two domains and, all clients have the same username/password
in
both domains. We want to transition necessary settings from the NT box
to the Win2k environment and then upgrade the Win2k boxes.
1. I believe what has to be moved at this point is the client settings for
MS and 3rd party apps (e.g. Adobe, Blackberry Desktop and others). I
have
looked at ADMT and ran some tests with
XPs File and Transfer Settings Wizard and simply copying the profile. They
did a decent job on most of the
Microsoft apps and desktop settings, but did drop enough that the manual
rework would be very time consuming. Third party apps like Blackberry,
Adobe
and others were problematic. I have not tried ADMT as it requires native
mode and I'm a little concerned about causing issues between the domains
that
would result in logon issues causing an immediate disaster.
Most tools I have seen assume a transition from the old domain to a new
domain that does not already have all the accounts/computers set up. I'm
willing to try ADMT if moving the win2k domain to native mode will not
pose
a risk to the current environment. Please advise on this.
Also, are there other tools out there that would be better suited to the
task or, other approaches that make sense?
2. Are there other settings I need to worry about moving? Since the
clients
already have accounts in the Win2K domains, I'm not seeing a reason to try
to
move any security history, etc. Please advise if I'm missing something
here.
3. Any information or pointers to help educate me would be much
appreciated.
Thanks for your help.
- References:
- Re: How to Eliminate NT Domain/Move Settings to Win2k
- From: Danny Sanders
- Re: How to Eliminate NT Domain/Move Settings to Win2k
- Prev by Date: RE: ADMT v3
- Next by Date: RE: How to Eliminate NT Domain/Move Settings to Win2k
- Previous by thread: Re: How to Eliminate NT Domain/Move Settings to Win2k
- Next by thread: RE: How to Eliminate NT Domain/Move Settings to Win2k
- Index(es):
Relevant Pages
|
Loading
