I think the decision depends a little on the number and size of the domains in the forest. For example, if there are 5 domains with a whole lot of changes going on the link to the remote site could be hit fairly hard with replication traffic to the remote DC/GC. On other other hand if Jennifer has a single domain or a 1 + 1 (empty forest root) structure then I would say definitely go ahead and make the DC in the remote location a GC.
In fact in a single domain forest I would make all DCs GCs. In a 1 + 1 (empty forest root) environment I would make all the DCs in the child domain GCs. In any case, the delay when sending an email doesn't sound like a GC issue to me. The GC is (directly or indirectly) needed for name-to-address resolution (post Exch 5.5), but once the name is resolved there should be no further delay on the client. The sending delay is probably more likely to be simply that the Exchange server is remote to the client. Have you considered configuring the Outlook clients at the remote site to use offline folders (ost) and synchronization? You lose some functions (such as viewing other people's calendar info), but it is more efficient for the network and the users won't see a delay when sending. The new Outlook client (2003) is more efficient with the local store and has improvements to synchronization, so you might want to look at that for the remote users. Tony ---------- Original Message ---------------------------------- From: "Rick Kingslan" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Tue, 19 Aug 2003 21:10:12 -0500 Jennifer, Make the DC at the remote a GC - it is going to greatly speed up the resolution of many functions that are not exactly unique to Exchange, but do play a part in it's operation. Even if the Exchange server is remote to the user, they will use a GC local to them. Rick Kingslan MCSE, MCSA, MCT Microsoft MVP - Active Directory Associate Expert Expert Zone - www.microsoft.com/windowsxp/expertzone -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jennifer Fountain Sent: Tuesday, August 19, 2003 7:33 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] Global Catalog placement I need some advice on placing a GC at one of my remote locations. I have a 256kbps connection to my remote site that only contains 20 people. I have a DC installed at that location but users connect to their email at my location. Currently when they click to send an email, it takes 19-20 seconds to send. - outlook 2000 sp3 (receiving seems to be ok) I am wondering - if making their existing DC into a GC, it may speed up? grasping here? I hate to put an exchange server at that location with only 20 people but according to this article: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodt echnol/windowsserver2003/proddocs/deployguide/dssbd_topo_dljo.asp it is not advised to put a GC at that location - granted this seems to be for windows 2003 and we have 2000 - not sure if ths still pertains. any advice would be greatly appreciated. Jenn List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
