We have two Windows 2003 domain controllers. The backup one (second domain
controller) has failed. Until I can get that replaced (three days) I need
to make one of the other servers a domain controller.

I have three bad choices. Which is the least bad?

Windows 2000 Exchange 2003 server.
Windows 2000 SQL and IIS.
Windows 2000 Terminal Server.

As you can see, I really don't want to put it on any of them. Which one
should I make the new (temporary) DC?

Thanks, Neal.

Hi Neal

What's driving the need to get another DC up temporarily? Is there a load
problem with the remaining DC?

TS = really bad choice. You need to give users access to the machine for TS
and you don't want this on a DC.

My guess at the best choice would be the Exchange box provided it's not
having a problem load wise as it is.

Preferred option would be to grab a stray desktop machine, clean install
2000 Server on it with latest updates and temporarily promote it. Better
yet, don't do this at all if you can avoid it and get the failed box back
online as soon as you can.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (E-Mail Removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

"Neal" <neal_@_ap0yar_dot_co_dot_nz> wrote in message
news:(E-Mail Removed)...
> We have two Windows 2003 domain controllers. The backup one (second
> domain
> controller) has failed. Until I can get that replaced (three days) I need
> to make one of the other servers a domain controller.
>
> I have three bad choices. Which is the least bad?
>
> Windows 2000 Exchange 2003 server.
> Windows 2000 SQL and IIS.
> Windows 2000 Terminal Server.
>
> As you can see, I really don't want to put it on any of them. Which one
> should I make the new (temporary) DC?
>
> Thanks, Neal.
>
>

Thanks for the info.

All the servers are in a hosting center and it often takes the team involved
three or four days to get in there with a new box. In the meantime, the
only existing DC has a single old disk.

(-:


"Mark Renoden [MSFT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Neal
>
> What's driving the need to get another DC up temporarily? Is there a load
> problem with the remaining DC?
>
> TS = really bad choice. You need to give users access to the machine for
TS
> and you don't want this on a DC.
>
> My guess at the best choice would be the Exchange box provided it's not
> having a problem load wise as it is.
>
> Preferred option would be to grab a stray desktop machine, clean install
> 2000 Server on it with latest updates and temporarily promote it. Better
> yet, don't do this at all if you can avoid it and get the failed box back
> online as soon as you can.
>
> Kind regards
> --
> Mark Renoden [MSFT]
> Windows Platform Support Team
> Email: (E-Mail Removed)
>
> Please note you'll need to strip ".online" from my email address to email
> me; I'll post a response back to the group.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Neal" <neal_@_ap0yar_dot_co_dot_nz> wrote in message
> news:(E-Mail Removed)...
> > We have two Windows 2003 domain controllers. The backup one (second
> > domain
> > controller) has failed. Until I can get that replaced (three days) I
need
> > to make one of the other servers a domain controller.
> >
> > I have three bad choices. Which is the least bad?
> >
> > Windows 2000 Exchange 2003 server.
> > Windows 2000 SQL and IIS.
> > Windows 2000 Terminal Server.
> >
> > As you can see, I really don't want to put it on any of them. Which one
> > should I make the new (temporary) DC?
> >
> > Thanks, Neal.
> >
> >
>
>