|
|
 FAQ
 Search
 Memberlist
 Usergroups
 Register
 Profile
 Private messages
 Log in
|
|
| Author |
Message |
goneill
Guest
|
 Posted: Wed Jul 04, 2007 7:03 am Post subject: Raising Domain Function Level problem |
 |
|
We have a Windows 2003 SBS Server running Active Directory as a Primary
Domain Controller in Windows 2000 Native mode.
I wish to upgrade it to Windows 2003 native mode, but when get a message
telling me I can’t upgrade it because the domain still has another DC running
Windows 2000.
The Windows 2000 server it is referring to is no longer on the domain, and
literally no longer exists. Perhaps the mistake I made was not removing its
DC role before removing it from the domain, but I simply removed it from the
domain (by deleting it from the ‘Domain Controllers’ organizational unit in
Active Directory Users and Computers).
How can I now convince AD that this old domain controller is no longer
around and thus allow me to raise its function level?
NB. A thought has just occurred to me – I haven’t rebooted the Primary
Domain Controller since deleting the other DC from the domain. I’d rather
not reboot for a little while yet due to existing work domains on the server,
but is that something I need to do? |
|
| Back to top |
|
 |
|
|
Ryan Hanisco
Guest
|
| Posted: Wed Jul 04, 2007 7:03 am Post subject: RE: Raising Domain Function Level problem |
|
|
Hi goneill,
First off, let me give you props for using "NB" correctly in your post. 
You are right that just removing the old domain controller is the most
likely source of the problem. When you don't carefully demote a domain
controller it leaves metadata in the directory that cna lead to replication
problem, orphaned objects, and domain operation problem (as you are noting).
The process for fixing this isn't terribly difficult from server 2003 as the
tools have seen vast improvements from their first versions. You will want
to use NTDSUTIL to perform what is called a metadata cleanup. If you jsut
have the one SBS DC you are probably fine, but in a larger domain structure
you would want to validate DNS and do a Domain health check.
Directions for the metadata cleanup can be found at:
http://support.microsoft.com/default.aspx/kb/216498
or
http://technet2.microsoft.com/windowsserver/en/library/012793ee-5e8c-4a5c-9f66-4a486a7114fd1033.mspx?mfr=true
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL
Remember: Marking helpful answers helps everyone find the info they need
quickly.
"goneill" wrote:
| Quote: | We have a Windows 2003 SBS Server running Active Directory as a Primary
Domain Controller in Windows 2000 Native mode.
I wish to upgrade it to Windows 2003 native mode, but when get a message
telling me I can’t upgrade it because the domain still has another DC running
Windows 2000.
The Windows 2000 server it is referring to is no longer on the domain, and
literally no longer exists. Perhaps the mistake I made was not removing its
DC role before removing it from the domain, but I simply removed it from the
domain (by deleting it from the ‘Domain Controllers’ organizational unit in
Active Directory Users and Computers).
How can I now convince AD that this old domain controller is no longer
around and thus allow me to raise its function level?
NB. A thought has just occurred to me – I haven’t rebooted the Primary
Domain Controller since deleting the other DC from the domain. I’d rather
not reboot for a little while yet due to existing work domains on the server,
but is that something I need to do?
|
|
|
| Back to top |
|
|
|
|
