"Allen" <> wrote in message
news:1hmphuhj1djfr$.i4xgwspxp6w4$... .
> My company have off site replication of our servers for the event of a
> disaster. We have a contract with a company that will provide office space
> for our staff in just such an event. They hold an image file of our PC's
> ready to roll out if needed. The PC's will then need to be joined to our
> domain using the remote offsite replicas. We will have site to site VPN
> between teh temporary office and the remote replicas. Is there a step by
> step guide to joining a PC to a remote domain. The servers will be
> running
> Win 2008 Standard.
>
> TIA
> --
> ats@work
>
> Every year is the same
> And I feel it again,
> I'm a loser - no chance to win
>
> The Who - I'm One
If you have a site to site VPN, the clients are not really "remote". The
whole point of a VPN (Virtual Private Network) is to make the clients appear
to be on the same network. If the site to site VPN is set up correctly the
clients are not aware of the fact that they are remote. The are simply in
another subnet connected through an (admittedly slow) IP router. AD only
becomes involved if you have a DC in the second site and you want the
clients to use that DC rather than the DC at the main site. This is done
through AD Sites and Services.
|
Similar Threads
Linear Mode
