Can't demote DNS server

[cal060307]

Hi all

I got an old Domain controller with 2003 server installed.
Now I want to demote it to be a member server.
I ran DCPROMO, but I got error message.
What should I do before demoting it? I have read a lot of FAQ and forums, but I am still a bit confused.

It was a DC server then the IT person who already left the company, decided to get another DC server, and left the old DC doing nothing on the floor. So now I want to use it as member server.
So I bet it still has FSMO, it should be removed before DCPROMO /FORCEREMOVE, shouldn't it? please tell me how to remove it - not transfer since I don't want to mess up the current DC.

Thanks for your help in advance.

Cheers

 

[paella33]

Was it always connected to the acticave directory? Or was it just turned off for a long time?

 

[cal060307]

It was turned off for a long time.

Thanks

 

[Cstorms]

First of all, if you want to just put this on as a member server and you already have another 2003 box that has all 5 fsmo roles on it (check this first), then I would just reload Server 2003.

If this has been brought back into your enviroment and you are taking it out of the replication cycle and there are references in dns and sites and services and the like, you will need to clean these entries up in the new DC. I would run dcdiag and check for errors that jump out at you to verify this stuff. You can use the link below to transfer or seize roles (again if you are sure your new DC doesnt already have them).

http://support.microsoft.com/kb/332199

Again if the new DC already holds all the roles (which my guess is it does since you have been running it for a while and have no had problems) it may be easier to just reload the OS and start fresh. Are you aware at how the new DC was commissioned? Do some checking and get back to us with any other questions.

Cory

 

[Cstorms]

As a word of warning these procedures are dependant on conditions in your environment, be sure of what was/is the relationship of the "old" dc as it relates to your new dc. Good luck.

Cory

 

[cal060307]

Thanks for your replies

The current DC has worked Ok since I started here, I did check FSMO on it, there are 5. So it should not be problem with that.

The old one as I mentioned it was doing nothing at all, not connected to the network or whatsoever.

I thought demoting this server is a short-cut to bring it donw to be a member server. In fact, it already took longer than reloading server 2003 from the fresh.

But I'd say it is a good thing for me to learn how to demote a DNS server.

So that is it...Reloading server? or is another way to demote DNS server?

Thanks again

 

[Cstorms]

You are demoting the Domain Controller, not dns. Very different, and if you demoting normally you could just run dcpromo and follow the wizard to uninstall AD, otherwise if none of this worked you would use the forceremoval switch to pound it out. In this case a simple reload would take an hour or so including joining it to the domain. From here you could load whatever roles you wanted including making it a dns server.

Cory

 

[cal060307]

Hi

Thanks for correcting me that. I've tried with and without froceremoval switch, it does not like it.
I'll try it again see how I go, if not I will reload the server again.

Once again very much appreciated.

Cheers