Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » NT4 to 2003 upgrade - client setup
NT4 to 2003 upgrade - client setup [message #393025] Tue, 16 February 2010 15:47 Go to next message
drzaius2000  is currently offline drzaius2000
Messages: 2
Registered: February 2010
Junior Member
I am performing an upgrade from NT4 to 2003 and have done a bit of testing
but I am still unsure of the behavior of workstations and servers when they
suddenly find themselves on an upgraded domain.

Currently, the plan is this:

1. Take a NT4 BDC on a virtual machine and upgrade it to 2003. Add
NT4Emulator key.
2. Configure DNS, etc. Verify everything transferred over. Remove
NT4Emulator key.
3. Reboot.
4. Configure clients to use new DNS server.
5. Shutdown all other NT4 BDCs.

Im uncertain at what happens between steps 3 and 4. Will the workstations
continue to be able to authenticate on the domain before I change their DNS?
On my test machine, it looks like hung up, so I was forced to reboot it
before it accepted being a member of the AD domain. I could see its domain
name changed from "domain" to the FQDN I chose "domain.local".

Are reboots required? Will there be interruption of service?

Thanks
Re: NT4 to 2003 upgrade - client setup [message #393299 is a reply to message #393025] Wed, 17 February 2010 00:39 Go to previous message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello drzaius2000,

See the answer in microsoft.public.windows.server.migration and pleaase avoid
multiposting, use crossposting instead with a newsreader like outlook express
or windows mail.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I am performing an upgrade from NT4 to 2003 and have done a bit of
> testing but I am still unsure of the behavior of workstations and
> servers when they suddenly find themselves on an upgraded domain.
>
> Currently, the plan is this:
>
> 1. Take a NT4 BDC on a virtual machine and upgrade it to 2003. Add
> NT4Emulator key.
> 2. Configure DNS, etc. Verify everything transferred over. Remove
> NT4Emulator key.
> 3. Reboot.
> 4. Configure clients to use new DNS server.
> 5. Shutdown all other NT4 BDCs.
> Im uncertain at what happens between steps 3 and 4. Will the
> workstations continue to be able to authenticate on the domain before
> I change their DNS? On my test machine, it looks like hung up, so I
> was forced to reboot it before it accepted being a member of the AD
> domain. I could see its domain name changed from "domain" to the FQDN
> I chose "domain.local".
>
> Are reboots required? Will there be interruption of service?
>
> Thanks
>
Previous Topic:Restored Object (Computer) from AD Deleted Items gives Error of Duplicate Name on the Network! (Ad
Next Topic:Change User Default Keyboard language using GPO
Goto Forum:
  


Current Time: Wed Jan 17 04:12:29 MST 2018

Total time taken to generate the page: 0.01934 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software