RE: How to Eliminate NT Domain/Move Settings to Win2k



Ken,

Thanks for your references. It appears they too tackle the subject from
the perspective of moving from an NT domain to a new win2k domain. In this
situation, the win2k domain has been in place for years and the AD is already
populated with the users, groups, and computers. Can you advise further on
what settings must be moved in this case to retire the NT domain? My
thinking is it is only the client profiles. If so, can you further advise on
your recommendation for this task?

Thanks again,

Diane

""Ken Zhao [MSFT]"" wrote:

Hello Diane,

Thank you for using newsgroup!

From your post, thanks for Danny Sanders's information. The following
information is for your reference:
Upgrading a Windows NT Domain to Windows 2000 Active Directory
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/ac
tivedirectory/deploy/upgrdmigrate/upgrnt.mspx

Migration of a Windows NT 4.0 Account Domain to Active Directory
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook
/cookchp9.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.





--------------------
| Thread-Topic: How to Eliminate NT Domain/Move Settings to Win2k
| thread-index: Ace8wTTPZfINdgHkQI6SqpH3nFcBGA==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?RGlhbmU=?= <Diane@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: How to Eliminate NT Domain/Move Settings to Win2k
| Date: Mon, 2 Jul 2007 08:54:00 -0700
| Lines: 44
| Message-ID: <4DADC8CD-7811-424E-BD18-6745B531BC87@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.migration
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.migration:1568
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| 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.
|
|
|
|


.



Relevant Pages

  • RE: How to Eliminate NT Domain/Move Settings to Win2k
    ... Microsoft Global Technical Support Center ... How to Eliminate NT Domain/Move Settings to Win2k ... | the perspective of moving from an NT domain to a new win2k domain. ... |> Upgrading a Windows NT Domain to Windows 2000 Active Directory ...
    (microsoft.public.windows.server.migration)
  • Re: Problems browising for users/groups on Trusted Win2K3 domain from
    ... needed for browsing a 2003 domain from an NT4 domain. ... will be similar and the settings are the same. ... domain from my Win2K domain member servers. ...
    (microsoft.public.win2000.active_directory)
  • Re: Default Startup Environment Settings
    ... It is because you have win2k domain if you upgrade to win2k3 domain then you ... >>I don't know why you don't see the TS settings. ...
    (microsoft.public.windows.terminal_services)
  • Migrating mail between domains
    ... will be moving to Win2k domain in the near future. ... Win2003 server) in Win2k domain and have exchange 2003 operational ... Exchange 2003 has already been installed in the Win2k domain. ...
    (microsoft.public.exchange.admin)
  • RestrictAnonymous
    ... We are looking at moving from 0 to 1 on our ... Win2k Domain, however, we are concerned that our trust ... with a remote NT4 domain is going to "blow up" to put it ...
    (microsoft.public.win2000.security)