Here is my scenario:
I have three Win 2000 servers with active directory--server a, server aa and server b. I also have two groups--group a and group b (not actual activate directory groups—just lumps of users). Servers a and aa are physically in one location and server b is in a different location. Server a is our Exchange server the ENTIRE company.
When both servers are up and happy, I want group a to log in through server a or server aa and group b to log in through server b. Obviously, if one of the AD servers goes down, I want the system to automatically log everyone in through one of the two remaining servers that is online.
Why so I want to specify server login location? Mainly because group a is physically close to servers a and aa and group b is physically close to server b. The two areas are connected by a partial T-1 and I don't want anymore traffic over that partial than needed. Also we are having slow replication (not a big deal on most days). If I make a new user in group a, I won't see that user immediately in AD on server b. Therefore, if the handshake is attempted on server b, the brand new user is unable to log on.
Over in the “Windows 2000 server” forum, someone kindly suggested that…
“you have to create two sites with AD Sites and Services and put each site in a different subnet. This will achieve what you are looking for. You will need to manually set up a site-link between the two servers to get replication working, as automatic replication is only initiated between servers of the same site.”
So, servers a (Exchange server) and aa will be in site a and server b will be in site b. My question for this forum is how will multiple sites affect our single Exchange server? Or better yet, how will multiple sites affect our Exchange USERS that will be logging onto server b in site b?
Thanks in advance for your postings.
I have three Win 2000 servers with active directory--server a, server aa and server b. I also have two groups--group a and group b (not actual activate directory groups—just lumps of users). Servers a and aa are physically in one location and server b is in a different location. Server a is our Exchange server the ENTIRE company.
When both servers are up and happy, I want group a to log in through server a or server aa and group b to log in through server b. Obviously, if one of the AD servers goes down, I want the system to automatically log everyone in through one of the two remaining servers that is online.
Why so I want to specify server login location? Mainly because group a is physically close to servers a and aa and group b is physically close to server b. The two areas are connected by a partial T-1 and I don't want anymore traffic over that partial than needed. Also we are having slow replication (not a big deal on most days). If I make a new user in group a, I won't see that user immediately in AD on server b. Therefore, if the handshake is attempted on server b, the brand new user is unable to log on.
Over in the “Windows 2000 server” forum, someone kindly suggested that…
“you have to create two sites with AD Sites and Services and put each site in a different subnet. This will achieve what you are looking for. You will need to manually set up a site-link between the two servers to get replication working, as automatic replication is only initiated between servers of the same site.”
So, servers a (Exchange server) and aa will be in site a and server b will be in site b. My question for this forum is how will multiple sites affect our single Exchange server? Or better yet, how will multiple sites affect our Exchange USERS that will be logging onto server b in site b?
Thanks in advance for your postings.
