Domain Controllers are fighting...
|
From: Christag on 7 May 2010 11:37 I have two domain controllers on my network and it seems both are fighting to be primary, (I think it has something to do with the primary being on 2003 SBS and the other on 2003) so we've decided to demote the second one. The problem is that when I run dcpromo.exe on the second server, I am told that it is the last DC and that my network will go down if it gets demoted. This doesn't make sense as the primary dc should be recognized and will pick up once the second goes off. Is it safe to demote this second controller and ignore its warnings? Or will I really lose everything.
From: kj [SBS MVP] on 7 May 2010 11:51 Christag wrote: > I have two domain controllers on my network and it seems both are > fighting to be primary, (I think it has something to do with the > primary being on 2003 SBS and the other on 2003) so we've decided to > demote the second one. > > The problem is that when I run dcpromo.exe on the second server, I am > told that it is the last DC and that my network will go down if it > gets demoted. > > This doesn't make sense as the primary dc should be recognized and > will pick up once the second goes off. > > Is it safe to demote this second controller and ignore its warnings? > Or will I really lose everything. You absolutly should not attempt to demote the SBS server. Sounds like the addition of the second DC never really completed or was performed correctly. Likely you will loose all changes that have been made using the second DC that were never replicated to the first DC. Why do you think they are 'fighting'. I'd suggest doing some troubleshooting first to ascertrain the depth of the problem before whacking off what appears to be an offending arm. -- /kj
From: Chris Puckett [MSFT] on 7 May 2010 12:18 It sounds to me like they are both in independent domains with the same domain name. Check each one to see if both of them show up as DC's in the Domain Controllers OU in AD Users and Computers. If they are in independent domains, just unplug the second one from the network to see if the problem goes away. -- Chris Puckett This posting is provided "AS IS" with no warranties, and confers no rights. "kj [SBS MVP]" <KevinJ.SBS(a)SPAMFREE.gmail.com> wrote in message news:eux3w0f7KHA.5808(a)TK2MSFTNGP02.phx.gbl... > Christag wrote: >> I have two domain controllers on my network and it seems both are >> fighting to be primary, (I think it has something to do with the >> primary being on 2003 SBS and the other on 2003) so we've decided to >> demote the second one. >> >> The problem is that when I run dcpromo.exe on the second server, I am >> told that it is the last DC and that my network will go down if it >> gets demoted. >> >> This doesn't make sense as the primary dc should be recognized and >> will pick up once the second goes off. >> >> Is it safe to demote this second controller and ignore its warnings? >> Or will I really lose everything. > > You absolutly should not attempt to demote the SBS server. Sounds like the > addition of the second DC never really completed or was performed > correctly. Likely you will loose all changes that have been made using the > second DC that were never replicated to the first DC. > > Why do you think they are 'fighting'. > > I'd suggest doing some troubleshooting first to ascertrain the depth of > the problem before whacking off what appears to be an offending arm. > > > -- > /kj >
From: kj [SBS MVP] on 7 May 2010 18:34 Could be too. For certain, a run of the sysinternals tool "psgetsid" against each DC would confirm as if they were part of the same domain, they'd have identical SIDS. If not, then they'd be different. http://technet.microsoft.com/en-us/sysinternals/bb897417.aspx Chris Puckett [MSFT] wrote: > It sounds to me like they are both in independent domains with the > same domain name. Check each one to see if both of them show up as > DC's in the Domain Controllers OU in AD Users and Computers. > > If they are in independent domains, just unplug the second one from > the network to see if the problem goes away. > > > "kj [SBS MVP]" <KevinJ.SBS(a)SPAMFREE.gmail.com> wrote in message > news:eux3w0f7KHA.5808(a)TK2MSFTNGP02.phx.gbl... >> Christag wrote: >>> I have two domain controllers on my network and it seems both are >>> fighting to be primary, (I think it has something to do with the >>> primary being on 2003 SBS and the other on 2003) so we've decided to >>> demote the second one. >>> >>> The problem is that when I run dcpromo.exe on the second server, I >>> am told that it is the last DC and that my network will go down if >>> it gets demoted. >>> >>> This doesn't make sense as the primary dc should be recognized and >>> will pick up once the second goes off. >>> >>> Is it safe to demote this second controller and ignore its warnings? >>> Or will I really lose everything. >> >> You absolutly should not attempt to demote the SBS server. Sounds >> like the addition of the second DC never really completed or was >> performed correctly. Likely you will loose all changes that have >> been made using the second DC that were never replicated to the >> first DC. Why do you think they are 'fighting'. >> >> I'd suggest doing some troubleshooting first to ascertrain the depth >> of the problem before whacking off what appears to be an offending >> arm. -- >> /kj -- /kj
From: Ace Fekay [MVP - Directory Services, MCT] on 10 May 2010 00:26 On Sat, 8 May 2010 14:08:04 -0700, "kj [SBS MVP]" <KevinJ.SBS(a)SPAMFREE.gmail.com> wrote: >Never tried it but since SBS doesn't support child domain or trusts of any >kind, it should not have created a child domain with the SBS server holding >the FSMO roles. If it did somehow join in the existing forest a metadata >cleanup would be needed or orphaned stuff is going to hang around with a >simple unplug it job. > > > I think from the description that he may have opted to make a new domain in a new forest while promoting. But not sure. Hope we hear a response. Ace
|
Pages: 1 Prev: Time out of sync on domain computers Next: Many Remote Desktop Redirected printer doc |