virtual secondary domain controller bdc

Hiya

I have never quite got over (emotionally :sick:) my last issue I had with a BDC I installed that basically knackered everything up on the PDC through some bizarre authentication issue I never got to the bottom of, hence i am still re-living it (maybe therapy needed), and I was lucky to grab the roles with the BDC and avoid extra pain.

It was a mixed environment with 2003 and 2008 and then I was trying to authenticate with squid on a linux box using kerberos and things started to break!

Anyway...

I have always since been reluctant to introduce a secondary domain controller to the network, although I feel that for redundancy purposes i should have one so all the AD data is replicated in case one scrws up.

So I have never got round to it.

I was wondering whether a virtualised secondary domain controller is a good idea or a physical one?

Thanks

For DCs, virtualised is fine. It's nice to have a bare metal machine too just in case - but your existing DC is just that.

Quote:

---

Originally Posted by 3s-gtech

For DCs, virtualised is fine. It's nice to have a bare metal machine too just in case - but your existing DC is just that.

---

Just what he say's hehe! :)

Just don't ever snapshot your DC - if you restore from an old snapshot that'll knacker things up as well. Save system state and restore in the normal fashion. Basically treat it exactly the same as a physical one and you should be fine.

Argh BDC cunningly reinvented as RODC's :)

Ben

Sorry to hijack this :o)

When setting up my last server during the DCPROMO stage it displayed an error about not being able to use a RODC on this domain, which I believe is down to the method used while running adprep or domain prep.

Is it possible to either fix this or add a BDC?

RODCs need the server to be running at Server 2003 functional level, also have a look at this Prerequisites for Deploying a Read-Only Domain Controller (RODC)