I hate to be blunt here, but if you aren't familiar with VPNs and such, then I wouldn't continue to try to do it by yourself. Your network specialist (I really think people should verify what they mean by network specialist) should be able to set this up.
First, VPN is an acronym that should be deleted from everyone's mind. Don't get me wrong, it is great when used in the right place, but everyone thinks that a VPN is the end all and be all of remote networking. It is much too slow as Sandeep says.
You do NEED two servers. You do not want people logging into the main server, plus you would not be able to use multiple connections.
Basically, it is set up like this. You have your regular network at the main office with a server/client setup. AC and SQL would be installed on that server. Then you set up a second server as a terminal server. You must have licenses for the OS and those who log in. The beauty of this is the terminal server accesses AC on the server and then allows each user from the remote office to log in to AC via the terminal server as if it is their own AC and AC connection.
There are multiple ways to go, but, in my opinion, using a terminal server and Remote Desktop Protocol or RDC as it is now referred to is the best way to do this. You do not need a server at the remote site.
I would go through the phone book and fine a computer store with networking that uses Microsoft Certified Technicians to set this up.
The network specialist is recommending to switch from SERVER Terminal service set up to Remote Desk Top setup.
That makes no sense. A terminal server just allows you to have multiple remote connections whether you use RDP (preferred) or LMI or whatever.
