[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 192
  • Last Modified:

Windows 2000 AD Upgrade

i haev a win 2000 ad environment that i inherited. I am now planning to upgrade the old outdated hardware that this runs on. I would also like to change the domain name it runs under as well as the company name has changed since it was installed.

Just wondering what people would suggest as a good seemless way of upgrading that would provide as little impact on end users as possible.

Cheers
0
kingcastle
Asked:
kingcastle
  • 2
  • 2
1 Solution
 
ocon827679Commented:
In doing an upgrade from W2K to W2K3 AD you won't be able to change the domain name until the upgrade is finished and you set the forest/domain levels to W2K3.  (There is a way to rename a W2K domain, basiically you have to be in mixed mode and you revert all of you dc's back to Windows NT, then do an upgrade.  Bad idea if you have Exchange 2K or greater in the environment.)  Once you get the domain to W2K3 then you can use the domain rename tool.  Read the documentation about this throughly, because if you have Exchange in your environment, then there is another Exchange tool that must be run to ensure that you don't blow away your Exchange infrastructure.

Take a look at KB article 325379 for upgrading from W2K to W2K3.  It talks about ensuring that your computers will be supported (checkupgradeonly) and also the adprep that you must run to prepare for W2K3 domain controllers.  If you are going to use the R2 version of W2K3 there is another prep tool that must be run.

Once you've done you checking and other prep work, the upgrade is fairly straight-forward.  Good luck.
0
 
kingcastleAuthor Commented:
hi cheers for this, what about all the file and folder security i have and the groups if i change the domain name will the get all messed up.

Would it be a good idea to start with a fresh new dns?

cheers
0
 
ocon827679Commented:
Your file and folder security as well as the groups, ect. should be fine.  I see no reason for a fresh dns as all of this is touched by the rename process.  Exchange is the big gotcha if you have it in your environment.  Just ensure that you have read "ALL" of the procedures for renaming a domain.  Typical MS gives you a good document on renaming the domain, but only a slight mention of Exchange.  Do a little more digging and you come to find out that Exchange poses a major concern, but there is a step by step process to get around it.

Download the domain rename tool and read the procedure document.  Pay attention to the pre-reqs and info on Exchange.  Don't start the process until you have read the doc at least once.  
0
 
kingcastleAuthor Commented:
cheers
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now