RE: NT4 to Server 2003 Migration



Hello,

Thanks for posting!

I understand that you want to upgrade a small Windows NT 4.0 environment to
Windows 2003 but the new hardware will not support Windows NT 4.0. You may
refer to the following method.

First you will need to get a transition machine that can support both
Windows NT 4.0 and Windows 2003. This can be a workstation class machine.
It will only be used as a transition server.

1. Install Windows NT 4.0 on the transition machine. Install SP 6 also.
2. Make this machine a BDC to the existing Windows NT 4.0 domain.
3. Formulate your back out plan. (create a good back up, or take a domain
controller off line.
4. Make sure replication has taken place.
5. Promote it to the Primary Domain Controller.
6. Plan your DNS. Will it be on the new DC or another machine.
7. Upgrade it to Windows 2003. AD is now installed.
8. Build a new Windows 2003 server on the new hardware.
9. Run dcpromo and make it a domain controller for the existing domain.
10. Move all FSMO rolls to the new domain controller. See FSMO What? Pull
it together and "How to view and transfer FSMO roles in Windows Server
2003".

As to the exchange migration issue, I suggest you open in the
microsoft.public.exchange.general newsgroup. That newsgroup is primarily
for issues involving Exchange. We recommend posting appropriately so you
will get the most qualified pool of respondents, and so other partners who
regularly read the newsgroups can either share their knowledge or learn
from your interaction with us. Thanks for your understanding!

Best Regards,

Jason Tan

Microsoft Online Partner Support
Get Secure! - 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.

--------------------
| NNTP-Posting-Date: Tue, 07 Feb 2006 18:42:55 -0600
| From: "Megan" <megan_grubb@xxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.migration
| Subject: NT4 to Server 2003 Migration
| Date: Tue, 7 Feb 2006 19:43:06 -0500
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
| Organization: VIF Internet b4
| Message-ID: <1139359375.426047@xxxxxxxxxxx>
| Cache-Post-Path: www.vif.com!unknown@xxxxxxxxxxxxxxxxxxxxxxx
| X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/)
| Lines: 43
| NNTP-Posting-Host: 216.239.64.140
| X-Trace:
sv3-KJViZOTNmakJhH5ojLpAvf+sKPDO7C3rfmiXqAujUJYR4OQrIkZ/4uQuY0iIw7cq5iLakOXt
DOO/DfI!pYVAYtlv/+eteITpIZEUpn9VP1lv4w1Q26UxDhxZwHjKMRhEZvFw5Wu0a+JZbQN8
| X-Complaints-To: abuse@xxxxxxx
| X-DMCA-Complaints-To: abuse@xxxxxxx
| X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
| X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your
complaint properly
| X-Postfilter: 1.3.32
| Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.gigan
ews.com!local01.nntp.dca.giganews.com!nntp.vif.com!news.vif.com.POSTED!not-f
or-mail
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:22362
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Planning on migrating from NT4 to 2003, and have a few questions I have
| found the answers to in various MS white paper.
|
| The network runs NT4, has 4 BCDs (all of which perform other various
| functions, too), 1 PDC (only function is to be a PDC), and a few member
| servers.
|
| BDC 1 - RAS, Print Server, File Storage (90% inactive data)
| BDC 2 - RAS, Goldmine, Quotewerks, and 2 license servers
| BDC 3 - Licensing server, file storage (active data)
| BDC 4 - Exchange 5.5, proxy through IIS, file storage (80% active data)
|
| Member Server 1 - Blackberry server (approx. 12 users who require
blackberry
| service)
| Member Server 2 - (2000 Adv Server) OWA (don't really care about this
| server, no one uses it)
| Member Server 3 - (2000 Adv Server) Inactive Exchange 5.5 server, file
| storage (no active data)
|
| The PDC put in place is temporary, as it's only a P4 3.0.
| The hardware for BDC 1 and 2 will not support Windows 2003 Server. I
fear
| the hardware in BDC 4 is slowly dying...
|
| From my understanding, I first need to upgrade the PDC to Server 2003.
It's
| my understanding that each BDC will see the new 2003 PDC as a NT4 PDC.
| There's a few things I'm curious about...
|
| Will Exchange will be able to properly communicate and authenticate after
| the PDC upgrade?
| Will clients using RAS be affected? Or will it all be transparent?
|
| Now comes the next issue....I also need to deploy AD so I can later on
setup
| clustered Exchange servers.... However, the PDC I currently have cannot
be
| permanent, this is only in place because the new server purchased for the
| PDC doesn't support NT4. How should I go about doing this? In the end, I
| need to make the new server a PDC running Windows 2003 with AD, and
| decommission the P4 PDC. I'd like to get the current PDC out of there
ASAP.
|
| I apologize for my ignorance, but this is such a huge learning curve for
me
| and have been given very little time to plan and implement the new network
| (this is only the tip of the iceberg). Any input is greatly
appreciated!!!
|
|
|

.



Relevant Pages

  • Re: minimum and recommended hardware requirement
    ... SMS Site Server System Requirements ... Windows 2000 Datacenter Server ... Microsoft's SMS 2003 support for server operating systems requires ...
    (microsoft.public.sms.setup)
  • RE: Upgrade Problem
    ... How to Gather Information After a Memory Dump in Windows XP ... If the suggestions do not help, please contact Microsoft Product Support ... | During the final installation stages of upgrading a DC I ... | BSOD for less than one second and then reboots the server ...
    (microsoft.public.windows.server.migration)
  • Re: Application Hang
    ... provide free email support, sorry. ... >> Windows XP Pro system on a network with Celeron CPU (small cpu since ... >> it works as a so called printer server as well). ... >> The system is running a printer which is shared by the whole network, ...
    (microsoft.public.windowsxp.general)
  • Re: Windows 2000 domain upgrade Windows 2003
    ... >From the Windows 2003 MPS report, I find the DNS Event log is empty. ... you didn't install DNS server on it. ... Please install DNS service on Windows 2003 and test again. ... Microsoft Online Partner Support ...
    (microsoft.public.windows.server.migration)
  • RE: Internet Connection Wizard failing at Firewall Config and Secu
    ... You can use the Dcdiag.exe (Domain Controller Diagnostic Tool) included ... in Windows Support Tools to verify the AD status. ... Windows Server 2003 Active Directory Diagnostics, ...
    (microsoft.public.windows.server.sbs)