Backup Server

In a spasm of caution, I thought a side-by-side server setup would be of
great advantage. I would get twin machines and install Server2003 on both,
then keep them mirrored somehow. Then if server machine "A" went down, I
could just plug in server machine "B" and domain users would hardly know the
difference.

But - isn't there a machine id somewhere which would tell users at logon
that this is not your proper logon domain/name/password (even though it
worked on the other server machine!)?

Maybe raid array would be better? Any help would be greatly appreciated.

Bob

What would be the role of this server?

Domain controller? File server? etc...

--
Mike
Microsoft MVP - Windows Security

"InOverMyHead" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> In a spasm of caution, I thought a side-by-side server setup would be of
> great advantage. I would get twin machines and install Server2003 on both,
> then keep them mirrored somehow. Then if server machine "A" went down, I
> could just plug in server machine "B" and domain users would hardly know
> the
> difference.
>
> But - isn't there a machine id somewhere which would tell users at logon
> that this is not your proper logon domain/name/password (even though it
> worked on the other server machine!)?
>
> Maybe raid array would be better? Any help would be greatly appreciated.
>
> Bob
>
>

Domain controller. (16 workstations)

Bob


"Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> What would be the role of this server?
>
> Domain controller? File server? etc...
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "InOverMyHead" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > In a spasm of caution, I thought a side-by-side server setup would be of
> > great advantage. I would get twin machines and install Server2003 on
both,
> > then keep them mirrored somehow. Then if server machine "A" went down, I
> > could just plug in server machine "B" and domain users would hardly know
> > the
> > difference.
> >
> > But - isn't there a machine id somewhere which would tell users at logon
> > that this is not your proper logon domain/name/password (even though it
> > worked on the other server machine!)?
> >
> > Maybe raid array would be better? Any help would be greatly
appreciated.
> >
> > Bob
> >
> >
>
>

You can add another DC and replicate AD between the two. If one DC goes down
the users can still log in to the domain without them noticing any problems
on their end. Where you might have issues is if your sharing any resources
on a DC that are not available on the other like shares, e-mail (if on the
DC), etc. Also it's always a good idea to have a mirror or raid setup on
your DC, regaurdless if your adding a second server or not.

Hope this helps,

--
Louis Vitiello Jr.
------------------------------
MCSE, MCSA, MCP, A+/N+
ERCP XP Pro / Net Concepts

"InOverMyHead" <(E-Mail Removed)> wrote in message
news:ulc3$(E-Mail Removed)...
> Domain controller. (16 workstations)
>
> Bob
>
>
> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> What would be the role of this server?
>>
>> Domain controller? File server? etc...
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>> "InOverMyHead" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>> > In a spasm of caution, I thought a side-by-side server setup would be
>> > of
>> > great advantage. I would get twin machines and install Server2003 on
> both,
>> > then keep them mirrored somehow. Then if server machine "A" went down,
>> > I
>> > could just plug in server machine "B" and domain users would hardly
>> > know
>> > the
>> > difference.
>> >
>> > But - isn't there a machine id somewhere which would tell users at
>> > logon
>> > that this is not your proper logon domain/name/password (even though it
>> > worked on the other server machine!)?
>> >
>> > Maybe raid array would be better? Any help would be greatly
> appreciated.
>> >
>> > Bob
>> >
>> >
>>
>>
>
>

Hi,

I agree. Just make sure that:
- both servers are DNS servers
- both servers are DHCP servers (if you use DHCP) and split scopes between
both of them
- both servers are GC (global catalogs)

and make sure that clients have both servers listed as DNS servers.

--
Mike
Microsoft MVP - Windows Security

"Louis Vitiello Jr." <louv-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> You can add another DC and replicate AD between the two. If one DC goes
> down the users can still log in to the domain without them noticing any
> problems on their end. Where you might have issues is if your sharing any
> resources on a DC that are not available on the other like shares, e-mail
> (if on the DC), etc. Also it's always a good idea to have a mirror or raid
> setup on your DC, regaurdless if your adding a second server or not.
>
> Hope this helps,
>
> --
> Louis Vitiello Jr.
> ------------------------------
> MCSE, MCSA, MCP, A+/N+
> ERCP XP Pro / Net Concepts
>
> "InOverMyHead" <(E-Mail Removed)> wrote in message
> news:ulc3$(E-Mail Removed)...
>> Domain controller. (16 workstations)
>>
>> Bob
>>
>>
>> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> What would be the role of this server?
>>>
>>> Domain controller? File server? etc...
>>>
>>> --
>>> Mike
>>> Microsoft MVP - Windows Security
>>>
>>> "InOverMyHead" <(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>> > In a spasm of caution, I thought a side-by-side server setup would be
>>> > of
>>> > great advantage. I would get twin machines and install Server2003 on
>> both,
>>> > then keep them mirrored somehow. Then if server machine "A" went down,
>>> > I
>>> > could just plug in server machine "B" and domain users would hardly
>>> > know
>>> > the
>>> > difference.
>>> >
>>> > But - isn't there a machine id somewhere which would tell users at
>>> > logon
>>> > that this is not your proper logon domain/name/password (even though
>>> > it
>>> > worked on the other server machine!)?
>>> >
>>> > Maybe raid array would be better? Any help would be greatly
>> appreciated.
>>> >
>>> > Bob
>>> >
>>> >
>>>
>>>
>>
>>
>
>