[windows2000] Re: Active directory conversions

  • From: "Rick Fogarty" <rick@xxxxxxxxxxxxx>
  • To: <windows2000@xxxxxxxxxxxxx>
  • Date: Fri, 5 Sep 2003 07:50:39 -0400

That's what I'm doing right now.... Keeping an upgraded domain controller
(to me) spelled trouble.

Here's a link from MS:
http://www.microsoft.com/windowsserver2003/upgrading/nt4/default.mspx

Rick

-----Original Message-----
From: windows2000-bounce@xxxxxxxxxxxxx
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Dennis Appelboom
Sent: Friday, September 05, 2003 5:23 AM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: Active directory conversions


Hmm, I wonder if you would be better of with clean windows 2000
installations, instead for new NT4 upgraded win2k servers. Personally, I wou
upgrade one nt4 box, run DCPROMO, than add a second win2k server. Move the
AD roles to the new server. Then reinstall the other servers one by one
while moving over the apps and files to the fresh win2k servers. But of
course it's a lot of work, and you would need an extra server.

Just my 2 eurocents.

Regards,

Dennis Appelboom
marviQ.

-----Original Message-----
From: Brian Lilley [mailto:Brian.Lilley@xxxxxxxxxxxxx] 
Sent: vrijdag 5 september 2003 11:01
To: 'windows2000@xxxxxxxxxxxxx'
Subject: [windows2000] Re: Active directory conversions


Also, In order to have a totally clean Active Directory 'PDC', I would build
a fresh NT4 BD box, promot it to a PDC and then upgrade that box first....

-----Original Message-----
From: AndyWang [mailto:andywang@xxxxxxxx]
Sent: 04 September 2003 23:18
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: Active directory conversions


Craig,

Here is what I did and it works. Hope it helps.

1.      Add 2 temporary BDCs and sync all BDCs.
2.      Reserve a BDC as backup.
3.      Isolate the PDC and Upgrade to Windows 2000.
4.      Run DCPROMO and setup WINS (backward compatibility) and DNS.
Make sure all the zone entries in  your-company.com are mapped to AD DNS
zone.
5.      Check Directory Integrity and Insert the system back into the
network
6.      Check the user account and password synchronization.
7.      Check Trust Relationship w/ other domain.
8.      Allow update to complete ~ 24 hrs.
9.      Update the DHCP server with local DNS information.
10.     If all goes well, upgrade the other BDCs.




Andy Wang/MIS
September 4, 2003
 
This e-mail is confidential and is intended solely for the use of the
individual or entity to whom it is addressed. If you are not the intended
recipient and you have received this e-mail in error then any use,
dissemination, forwarding, printing or copying of this e-mail is strictly
prohibited and you should contact the sender by e-mail and then delete all
material from your system. Any views or opinions expressed in this message
are those of the individual sender, except where the sender expressly, and
with authority, states them to be the views of FICA. 
This e-mail does not form part of a legally binding agreement. We have taken
precautions to minimize the risk of transmitting software viruses, but we
advise that you carry out your own virus checks on any attachment to this
message. We cannot accept liability for any loss or damage caused by
software viruses



-----Original Message-----
From: Craig Gauss [mailto:GauCra@xxxxxxxxxxxxxxxxx] 
Sent: Thursday, September 04, 2003 2:48 PM
To: 'windows2000@xxxxxxxxxxxxx'
Subject: [windows2000] Active directory conversions


Does anyone have any guidelines they have followed when converting an NT 4
domain to a Windows 2000 AD domain?  I am working on planning our conversion
and any pointers, tips or guidelines would be greatly appreciated.  Thanks.

**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.

http://thethin.net/win2000list.cfm

**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.

http://thethin.net/win2000list.cfm

_____________________________________________________________________

This message has been checked for all known viruses on behalf of Vivista by
MessageLabs. 

http://www.messagelabs.com or Email: mailsweeper.info@xxxxxxxxxxxxx

Vivista formerly Securicor Information Systems for further information
http://www.vivista.co.uk  



**********************************************************************
The information contained in this e-mail message is intended only for the
individuals named above.  If you are not the 
intended recipient, you should be aware that any 
dissemination, distribution, forwarding or other duplication 
of this communication is strictly prohibited.  The views 
expressed in this e-mail are those of the individual author 
and not necessarily those of Vivista Limited.  
Prior to taking any action based upon this e-mail message 
you should seek appropriate confirmation of its authenticity. If you have
received this e-mail in error, please immediately 
notify the sender by using the e-mail reply facility.
**********************************************************************


_____________________________________________________________________

This message has been checked for all known viruses on behalf of Vivista by
MessageLabs. 

http://www.messagelabs.com or Email: mailsweeper.info@xxxxxxxxxxxxx

Vivista formerly Securicor Information Systems for further information
http://www.vivista.co.uk  


**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.

http://thethin.net/win2000list.cfm

**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.

http://thethin.net/win2000list.cfm


**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.

http://thethin.net/win2000list.cfm

Other related posts: