Well thanks for the information. I inherited a domain that was upgraded from NT4 to win2k, I am begining to suspect that a straight forward upgrade might not be the way to go. The only problem I forsee is lack of resources to carry out a full test lab / new builds. I am particularly worried about the exchange 2000 server, which was upgraded from 5.5 and seems to have bits and pieces left behind. Thanks anyway for the info, I am begining to grasp to the full extent of the domain upgrade. Dave Sorin Srbu <sorin.srbu@xxxxxxxxxxxxx> wrote: Speaking of which, upgrading from win2k DCs to win2k3 DCs has a tendency (known to MS) to leave GPO-templates and policies from win2k. Ie they are not upgraded to the win2k3-level. If you upgrade this way, you may want to look this up. This has been the case when I did the upgrade on two domains, from win2k to win2k3. All kinds of weird problems can arise, w/o any apparent reason... Dunno if you were going this upgrade path, but thought it was worth mentioning, as doing a fresh install isn't always an option. HTH. -----Original Message----- From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx]On Behalf Of Dogers Sent: Thursday, November 10, 2005 5:11 PM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Re: Windows 2000 domain upgrade By the way what seems to be the great scare with in-place upgrades? In place upgrades make me feel dirty! I guess it's a throwback from 9x? Having a domain controller that potentially has "bits" left behind from a previous generation OS doesn't fill me with confidence.. I've not actually done a domain upgrade yet, so I don't know how good upgrades are nowadays - it's just the icky feeling it gives me ;) Andrew --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click.