Link to home
Start Free TrialLog in
Avatar of LLong29
LLong29

asked on

removing broke domain controller...then upgrading to MS Win 2K12

Hello…

The solutions to my problems may have already been answered from other questions. In which case, please refer me to the proper links. Thank you.

The premise…
Our domain consists of multiple Windows 2003 servers and two Windows 2000 servers as the domain controllers. The plan is to move from the two Windows 2000 servers to two Windows 2012 servers as domain controllers. Because there is no direct path to upgrade from Win Server 2000 to Win Server 2012, we need to upgrade the current two domain controllers to Windows 2003 (or Windows 2008) then upgrade to Windows Server 2012.

The short version of the problem….
Of the two current Windows 2000 server domain controllers (DC1 and DC2), DC1 has problems. We get the message, ”There are no endpoints available from the endpoint mapper.” This and other problems affects its ability to replicate and communicate with the DC2. And we cannot transfer FSMO roles between the two DCs because of these problems.

The basic solution to the problem…
From what’s been relayed to me, it appears my best course is: a) to shutdown DC1 and 2) use DC2 to seize the FSMO roles. And move forward from that point. What’s a little unclear to me is once I seize the remaining FSMO roles and move those roles to DC2:
 
“Should I simply run adprep on that single domain controller DC2?” (and move forward to Windows 2012 from there.)

“Or should I promote a new Windows 2000 server to domain controller and once again have two Windows 2000 servers for domain controllers?” (and move forward to Windows 2012 from there.)

And once adprep has run successfully, shouldn’t I simply be able to promote a new Windows Server 2003 (or Windows Server 2008) to domain controller and move some or all the FSMO roles to the Win 2K3 (or Win 2K8) server?

But the underlying point here is that I am past trying to fix DC1. I need to find the best way to: 1) gracefully remove DC1…2) run adprep on the remaining domain controller (whether its DC2 or another domain controller)….and 3) move forward to upgrading to Windows Server 2012 as the final steps. I need to make sure to do whatever is needed before I shutdown and remove DC1.

You input is appreciated and if you have questions, please ask.

Thank you.  

L Long
SOLUTION
Avatar of Mike Kline
Mike Kline
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of LLong29
LLong29

ASKER

Hello...

Thank you for your comment.

Ever since I have been having problems with DC1, I build a Windows 2000 Server and added it to the domain. That server is literally not doing any work other than being powered up and logged into. It's my "backup Windows 2000 server". My thoughts were to use that server as my "second domain server" after I remove DC1 and seize the roles using DC2.

I considered that if I removed DC1 and got DC2 to run adprep within a day or so maybe I could simply use the single DC. But certainly (as you pointed out) , it makes better sense to maintain two DCs at all times.

And Thank you for the information about the metadata.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of LLong29

ASKER

Hello...

Mr. Mahesh, thank you for your information. If its possible, we may pick upgrading to 2008 r2 instead of 2003. But that will depend on some other factors...

And Mr. Premkumar, thank you also for the links you sent. I believe I may have seen one of those links before. But I am happy that more than one source has suggested the same procedure.

Thank all of you gentlemen. We hope to start this procedure within the next week or so.

L Long
Avatar of LLong29

ASKER

Hello... This is just to let you gentlemen know that we will be shutting down broke DC controller next week April 22nd. We had to delay shutting down broke DC controller because of scheduling concerns. On April 23rd I will post results of the shutdown.   L Long