Re: Odd Win2k3 Request

Tech-Archive recommends: Fix windows errors by optimizing your registry

clustering DCs is not supported

in your case you could configure/adjust the DNS priority of the SRV records
for DC1 you could configure the DNS priority of the SRV records to 50
for DC2 you could configure the DNS priority of the SRV records to 100
(default)

DC1 will always be the servicing DC until it is unavailable and in that case
DC2 is used. as soon as DC1 return it will be used again

don't use wacky configs just because of a bad app!

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"BernardHNY" <BernardHNY@xxxxxxxxx> wrote in message
news:1153483747.917454.147620@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have been tasked with what I think is an impossible request:

Environment:

Active Directory (2k3)
Two servers (Both are DC)

40 client machines.

The request is that ALL clients authenticate to only 1 machine, with
the second DC only being there for failover. Upon failover, all
machines report to the second DC. When the first DC comes back online,
all machines will only report to the second DC unless all are pointed
back to the primary machine with some manual process.

The reason for the request is long winded and silly (bad engineering of
a software solution) and the best bet is actually clustering the two
boxes and having the data reside on our SAN. Whichever machine owns the
F drive would be the primary machine and failover could be achieved by
manually moving the cluster resource....but alas, this is not an
acceptable solution (don't ask, its crazy).

This reminds me of functionality back in NT4 not in 2k3.

Anyone have any ideas on how to achieve this? Is this possible?

Thanks

Bernard



.