Ok, well I am hoping that someone can help me a little, as I am a little confused. Background Information - We have one server, which is a domain controller, Active Directory (With Three OU's), File Server, Print Server, DNS Server & DHCP Server. Currently local users (users who are on our main site) log on from their own workstation, with their own username and password to the domain called, lets say SERVER-001. Now users who are at our smaller site, 3 miles away, log onto the domain SERVER-001 but check the "Log On Using Dial Up Connection" and log on using a VPN connection. This can be slow at times. Our company has now invested in a second server, to be installed at our smaller site. Would it be possable to create a new domain, lets say SERVER-002 and then users can log on to the second domain BUT still be able to select SERVER-001 in the "Log on to" box at the login screen. In a nutshell, I would like to try and configure the second server, as a domain controller with active directoy that still have the same user information and OU's from the SERVER-001, but at a diffrent location. If it is possable, could someone walk me though the steps (briefly) with how to set a second domain and AD up. I have had many great experiances with Computing.net and you have all helped me greatly in the past. Thanks in advance for any help & support. Daimian P Williams

Our company has now invested in a second server, to be installed at our smaller site. Would it be possable to create a new domain, lets say SERVER-002 and then users can log on to the second domain BUT still be able to select SERVER-001 in the "Log on to" box at the login screen. It's been a few years and I admit my MS skills are rusting. But, if memory serves me, in a situation like this, you would configure that second server as a DC in a different site. You would enable replication (which I admit would be slow over dialup so you would want to set this bad boy up at your main office and allow the initial replication to happen over your LAN) and make it so the users at that remote site could then authenticate to that server. This reduces bandwidth usage and would speed up login for the users at that location. You'll have to do some research and reading on MS's site to get complete information on how to set this up.

OK, so when I go to install the domain on the second server, which option do you recommend I install. "Domain Controller for a new domain" or Additional Domain Controller"? Then which one after that? Thanks for your help and speedy responce. Daimian Daimian P Williams

Additional DC not new. You would be advised to put in a vpn capable router at your main office and put a DSL link at the other office. All pcs there would vpn [either as clients or make a site to site vpn if you put a vpn router at each site] via the internet/dsl link to the main office. Remote office would work like they were at the main office. Dialup between servers is a waste of time imo. MS does recommend two DCs for AD failover. Having one at each site is a good plan also for failover. Especially if you engage DFS and FRS to replicate your data between the two. Problem is the link between. Dialup will crimp that severely.