PU_Admin
asked on
Joining a remote server to a domain
I have a Windows 2003 Server at our main office that is a domain controller. We have a new location across town that requires a server and a couple workstations.
The remote server will mainly be used to run Sage TImberline software. Users at the main office will have to access Timberline remotely via terminal services.
What is the best way to join the remote server and remote users to the domain and allow terminal services access at the main office? We have a VPN connection. Is it best to just join the remote server and workstations to the domain through the VPN connection? The other option that I thought might work would be a site-to-site vpn but after looking into it, it seemed like that would complicate things.
Also, I should add that we are using ISA Server 2006 on the DC at the main office and our VPN connection is set up through that.
The remote server will mainly be used to run Sage TImberline software. Users at the main office will have to access Timberline remotely via terminal services.
What is the best way to join the remote server and remote users to the domain and allow terminal services access at the main office? We have a VPN connection. Is it best to just join the remote server and workstations to the domain through the VPN connection? The other option that I thought might work would be a site-to-site vpn but after looking into it, it seemed like that would complicate things.
Also, I should add that we are using ISA Server 2006 on the DC at the main office and our VPN connection is set up through that.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There really isn't a true need for a server at the remote site. It's a subsidiary of the main company so the idea was to have the application and files that pertained specifically to them hosted locally at their site. A couple users at the main office will have to access the Sage software package that is located at the remote office periodically for accounting and clerical purposes. It's definitely a bit of a backwards set up but it's what I was given to work with.
If it were entirely up to me, I would just either A) eliminate the remote server or B) bring it to the main office and have the remote users connect like yours. However, I don't have the luxury of making that decision.
If it were entirely up to me, I would just either A) eliminate the remote server or B) bring it to the main office and have the remote users connect like yours. However, I don't have the luxury of making that decision.
Since its not an option, I would recommend setting it up ( and joining it to the domain ) at your main office and then transporting it to the main office.
ASKER
As much as what he said should have been obvious to me, after reading his suggestion it made me realize that was the right way to go.
This helps in a few ways; you make sure its configured correctly and nothing is wrong with the hardware, you connect it to the server and then deliver it.
If users will be remoting into the server, why not follow what bryon said and just keep it in the main office?