MS Winblows Server 2003

**Modulok** · Posted: Mon, 31 Jul 2006 16:29:29 Post Subject: MS Winblows Server 2003

IDK who here would have this experience but I figured I would ask here first.

Back in early June we were forced to demote our primary DC. (I know MS says primary DC doesn't exist but it does) Our problem was our DC's were not replicating properly...this was discovered when trying to implement a group policy which wasn't replicated to the other 3 DC's.

That DC had All FSMO roles, schema, domain naming, rid master, pdc emulator, infrastucture master. Since it was the Primary DC it was the only DC in the forest/domain to have schema and domain naming. We transfered schema to another DC without problems but domain naming would not go over (because of the replication issue we had). DUH

We ended up trying a dcpromo to demote the DC. It didn't work because...you guessed it, the replication error we had didn't let the demotion go through. So we did a dcpromo /forceremoval which dropped the domain naming FSMO. We are looking to get that back now incase it comes back to bit us in the a$$ later like the replication failure did.

Sound familiar to anyone?

Thanks a bunch!

knight0334 · Posted: Mon, 31 Jul 2006 16:37:37 Post Subject:

I was on the Beta team for Win2k3, never experienced what you're going through.. ...then again, I've never had to delve that dip in Win2k3.

Hopefully one of the others can give a suggestion.

BeerCheeze · Posted: Mon, 31 Jul 2006 18:20:19 Post Subject:

I have never experienced that exactly.

However we did once have to force about 20 laptops to become all the FSMO masters (long story). You can do it all, but it's a royal pain in the butt. It's been like a year, so I don't recall all the exact commands but if you need them I can find them.

Spire · Posted: Mon, 31 Jul 2006 19:19:57 Post Subject: Re: MS Winblows Server 2003

**Modulok** · Posted: Mon, 31 Jul 2006 22:02:42 Post Subject:

LMAO @ Spire

The domain naming FSMO says is just for new forests, which we should never need a new one or change our current, but I'm sure it will bit us in the a$$ when we want to do something later...like upgrade to longhorn server :-x

mrweasel · Posted: Tue, 01 Aug 2006 10:11:24 Post Subject:

try using -seize or something like that. I know we had to do that to a 2k DC once. it may work under 2k3.

**Modulok** · Posted: Tue, 01 Aug 2006 11:25:16 Post Subject:

but will seize work when the FSMO has already been forceably removed? I think seize only works when the role is assigned to a DC.

mrweasel · Posted: Tue, 01 Aug 2006 13:51:33 Post Subject:

<---- confused

thought you took the Dc out of the domain and were putting it back in.

nevermind, just ignore me. My brain is all squishy from boredom

**Modulok** · Posted: Tue, 01 Aug 2006 15:01:28 Post Subject:

the DC was demoted forcefully then promoted the same night.

mrweasel · Posted: Tue, 01 Aug 2006 15:45:59 Post Subject:

appartently my brain has ceased to function....as I've forgotten what you need help with