Trying to set up remote office with 2003 Server Standard at main office
I am setting up a remote office to connect to our main office which has a Sonicwall Pro 2040 with VPN. The main office has DC, AD, Exchange 03, DHCP, on a Windows 03 Server Standard.
I was thinking of connecting this remote office (3 end users - no IT Dept) via a TZ 180 or similar product. We have a program in house (main office) that I want the remote office to use ( emulator) but have a question - would I need to add each user to our domain, albeit remotely, in order for them to use this program? I doubt that simply connecting the office via VPN would allow a remote user to access the software unless they are actually added to our domain. Am I correct in thinking this? If so, any special procedure in adding a remote office user to our domain?
Thanks in advance
I was thinking of connecting this remote office (3 end users - no IT Dept) via a TZ 180 or similar product. We have a program in house (main office) that I want the remote office to use ( emulator) but have a question - would I need to add each user to our domain, albeit remotely, in order for them to use this program? I doubt that simply connecting the office via VPN would allow a remote user to access the software unless they are actually added to our domain. Am I correct in thinking this? If so, any special procedure in adding a remote office user to our domain?
Thanks in advance
ASKER
The software I speak of is connected to the main office server already via serial port server. It is located on the actual 2003 Server and employees currently connect to it via Terminal Services.
I do believe we need to add the remote machines to the domain in order to manage more efficiently.
How would i go about putting another domain controller at the new office? Would I need a remote server there?
I do believe we need to add the remote machines to the domain in order to manage more efficiently.
How would i go about putting another domain controller at the new office? Would I need a remote server there?
Ok, if we assume that it is required that we add the remote machines to the domain, and the two sites will be connected via a WAN link, then we have two possibilities for connectivity.
What kind of internet connection do you have at the main office? At the remote office?
1) If both sites are connected via VPN, this is more or less and extension of the network at the main office (albeit very slow). You could simply join the remote machines to the domain like to would join any other machine. Since the remote machines would be contacting the domain controller across the WAN to login, the performance here may or may not be acceptable
2) You could put a second domain controller at the remote office, which, yes, would be another physical server. Clients logging in at the remote office would authenticate and login using this server to keep the performance high.
I didn't originally notice that this remote office only has 3 users, I don't know if solution #2 would be all that practical, and I would worry with #1 that your login performance, as well as the performance to your shared application in general.
What about using Terminal Server? You wouldn't need to setup any VPN WAN link between the two offices or join the host machines to the domain. You could setup a Terminal Server at the main office which would be part of the domain and have direct contact with your application/email/ect. The remote people would essentially just RDP in, and start working.
What kind of internet connection do you have at the main office? At the remote office?
1) If both sites are connected via VPN, this is more or less and extension of the network at the main office (albeit very slow). You could simply join the remote machines to the domain like to would join any other machine. Since the remote machines would be contacting the domain controller across the WAN to login, the performance here may or may not be acceptable
2) You could put a second domain controller at the remote office, which, yes, would be another physical server. Clients logging in at the remote office would authenticate and login using this server to keep the performance high.
I didn't originally notice that this remote office only has 3 users, I don't know if solution #2 would be all that practical, and I would worry with #1 that your login performance, as well as the performance to your shared application in general.
What about using Terminal Server? You wouldn't need to setup any VPN WAN link between the two offices or join the host machines to the domain. You could setup a Terminal Server at the main office which would be part of the domain and have direct contact with your application/email/ect. The remote people would essentially just RDP in, and start working.
ASKER
Currently we have about 15 users accessing via Terminal Services, but currently at the main office we only have one server so overloading the server is a concern, hence the reasoning behind setting up remote offices via VPN.
We have a T-1 currently at the main office, and each other remote location is different - some have broadband while a few have DSL.
I truly appreciate your detailed explanations!
We have a T-1 currently at the main office, and each other remote location is different - some have broadband while a few have DSL.
I truly appreciate your detailed explanations!
You could get an additional server and dedicate it to Terminal Services for all the remote users perhaps. This would take the user load off the main server so this wouldn't be a concern.
I can tell you in advance that a VPN tunnel with a T1 on one end, and DSL/cable on another is going to be painful, especially with all of the VPN overhead. You also have to worry about reliability with residential internet services. If the link on their end goes down, they can't login or access your application.
I can tell you in advance that a VPN tunnel with a T1 on one end, and DSL/cable on another is going to be painful, especially with all of the VPN overhead. You also have to worry about reliability with residential internet services. If the link on their end goes down, they can't login or access your application.
ASKER
I had not thought of that, the reliability of the connections itself - thank you.
I know this might be a whole other topic altogether but would adding a second server to our current main office setup be complicated?
I know this might be a whole other topic altogether but would adding a second server to our current main office setup be complicated?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you again for all your help
As far as adding another office to your domain, this is pretty straightforward. Assuming that you create a VPN tunnel between two sonicwall devices as you already mentioned:
1) Put another domain controller in the new office so they have local domain services
2) They can run Outlook in cached mode over the VPN to get their mail from the Exchange server in the main office
3) They can run the software they need