Question (in theory) on GC/DC failure and services starting

[wolfprince7]

So, I have a question, and wanted to see if anyone has feedback
(including supporting facts) to the following scenario:

Lets say I have a domain with multiple DC's and GC's, all in the same
site. One of the DC/GC servers goes down in the middle of the night.
So, in theory, domain logins will continue to be serviced. My question
is about IIS and it's corresponding accounts. Assuming that the IIS
server service accounts authenticated to the DC/GC that went down prior
to the outage, what would happen to IIS? Would the IIS server
essentially be down as the DC/GC that originally handled the login
request for the services is dead, or is IIS be smart enough to
automatically reauthenticate when the next incoming request was
handled?

If the latter is true, does anyone have a good (free) way of preventing
IIS being affected from this type of failure? I was thinking of writing
a script that would authenticate to the domain every 10 minutes or so,
and if the process failed, restart the IIS service...any other ideas on
this?

 

[Herb Martin]

So, I have a question, and wanted to see if anyone has feedback
(including supporting facts) to the following scenario:

Lets say I have a domain with multiple DC's and GC's, all in the same
site. One of the DC/GC servers goes down in the middle of the night.
So, in theory, domain logins will continue to be serviced.

Because you have at least one DC/GC available to
clients there.

My question
is about IIS and it's corresponding accounts. Assuming that the IIS
server service accounts authenticated to the DC/GC that went down prior
to the outage, what would happen to IIS?

Nothing different than a regular client, or user logging
into that server directly or using Terminal Services to
reach that IIS Server.

Would the IIS server
essentially be down as the DC/GC that originally handled the login
request for the services is dead,

Nope. Any "client" (which includes server class machine)
computer will fail over to another DC if one is available.

or is IIS be smart enough to
automatically reauthenticate when the next incoming request was
handled?

IIS knows nothing directly about any of this so it doesn't
"fail over" but rather just takes advantage of the way
authentication works for all users/services/computers.

If the latter is true, does anyone have a good (free) way of preventing
IIS being affected from this type of failure?

IIS is not affected any differently than any other
authentication by this.

I was thinking of writing
a script that would authenticate to the domain every 10 minutes or so,
and if the process failed, restart the IIS service...any other ideas on
this?

Unnecessary.