|
|
|
date: Wed, 23 Apr 2008 23:47:02 -0700,
group: microsoft.public.exchange.connectivity
back
Re: Closest Gc doesn't help Outllok to connect to the nearest GC
Usually this happens because the subnets were not defined and associated
with sites in AD Sites & Services. In that case, all the subnets are
assigned to the default first site. In your case, you state that the AD
network is well structured with sites for subnets. Given that, you need to
look at the event ID 2080s in the application log to see what Exchange
thinks are GCs in site and out of site, roles, and connectivity. A careful
examination should provide a clue to what's happening.
"Manoj_Ikon26" wrote in message
news:6B85B890-C265-4D45-8ECF-E9844039FA3A@microsoft.com...
> We have done the Closest Gc reg key entry in thye client system, and
> observed
> that
> A lot of out Outlook client are getting connected to other site Gc for
> Directory lookup. we have 3 sites in Asian and 1 in Europe and 1 in
> America
> with DC's.
> servers.
> The AD network is well stuctured with sites for the subnets.
>
> The Clients dialog boxes shows Exchange servers that are far away,
> connected
> though not really fast WAN connections. Clients from e.g. a asian site
> get connected to european site Gc for Directory Lookup ( Checked the
> connecttion Status ).
>
> [HKEY_CURRENT_USER\Software\Policies\Microsoft\Exchange\Exchange Provider]
> "Closest GC"=dword:00000001
>
> Can anyone has any clue why this is hitting other site Gc inspite of
> having
> the Gc at the same Site. Also if i use the DS Server Reg key , i am able
> to
> point out the client to hit the site specific Gc, but this i don't want to
> enforce it.
>
> [HKEY_CURRENT_USER\Software\Policies\Microsoft\Exchange\Exchange Provider]
>
> "DS Server"="Domain.Com"
>
> Thank you
>
date: Mon, 28 Apr 2008 10:43:25 -0400
author: John Fullbright
Re: Closest Gc doesn't help Outllok to connect to the nearest GC
Thanks John, This is what i am geting the event log on Ht Cas Server.
Event Type: Information
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2080
Date: 4/30/2008
Time: 11:07:33 AM
User: N/A
Computer: GUREXHT02
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=6140). Exchange Active
Directory Provider has discovered the following servers with the following
characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable |
PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
asgur001.ASIAN.AD.ARICENT.COM CDG 1 7 7 1 0 1 1 7 1
Out-of-site:
ASBJN001.ASIAN.AD.ARICENT.COM CDG 1 7 7 1 0 1 1 7 1
ASBGH002.ASIAN.AD.ARICENT.COM CDG 1 7 7 1 0 1 1 7 1
ADROOT01.AD.ARICENT.COM CDG 1 7 7 1 0 1 1 7 1
EUBGH002.EUROPEAN.AD.ARICENT.COM CDG 1 7 7 1 0 1 1 7 1
ambgh002.americas.AD.ARICENT.COM CDG 1 7 7 1 0 1 1 7 1
asche001.ASIAN.AD.ARICENT.COM CDG 1 7 7 1 0 1 1 7 1
EUIEV001.EUROPEAN.AD.ARICENT.COM CDG 1 7 7 1 0 1 1 7 1
AMPAL001.americas.AD.ARICENT.COM CDG 1 7 7 1 0 1 1 7 1
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I
Event Type: Information
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2081
Date: 4/23/2008
Time: 12:01:22 AM
User: N/A
Computer: GUREXHT02
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=5072). Exchange Active
Directory Provider will use the servers from the following list:
Domain Controllers:
asgur001.ASIAN.AD.ARICENT.COM
Global Catalogs:
asgur001.ASIAN.AD.ARICENT.COM
The Configuration Domain Controller is set to asgur001.ASIAN.AD.ARICENT.COM.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
am still clue less whta make the outlook look for the other site GC, as the
G/D/C is approachable from all the site to exchnage server.
Thanks,
"John Fullbright" wrote:
> Usually this happens because the subnets were not defined and associated
> with sites in AD Sites & Services. In that case, all the subnets are
> assigned to the default first site. In your case, you state that the AD
> network is well structured with sites for subnets. Given that, you need to
> look at the event ID 2080s in the application log to see what Exchange
> thinks are GCs in site and out of site, roles, and connectivity. A careful
> examination should provide a clue to what's happening.
>
>
>
>
> "Manoj_Ikon26" wrote in message
> news:6B85B890-C265-4D45-8ECF-E9844039FA3A@microsoft.com...
> > We have done the Closest Gc reg key entry in thye client system, and
> > observed
> > that
> > A lot of out Outlook client are getting connected to other site Gc for
> > Directory lookup. we have 3 sites in Asian and 1 in Europe and 1 in
> > America
> > with DC's.
> > servers.
> > The AD network is well stuctured with sites for the subnets.
> >
> > The Clients dialog boxes shows Exchange servers that are far away,
> > connected
> > though not really fast WAN connections. Clients from e.g. a asian site
> > get connected to european site Gc for Directory Lookup ( Checked the
> > connecttion Status ).
> >
> > [HKEY_CURRENT_USER\Software\Policies\Microsoft\Exchange\Exchange Provider]
> > "Closest GC"=dword:00000001
> >
> > Can anyone has any clue why this is hitting other site Gc inspite of
> > having
> > the Gc at the same Site. Also if i use the DS Server Reg key , i am able
> > to
> > point out the client to hit the site specific Gc, but this i don't want to
> > enforce it.
> >
> > [HKEY_CURRENT_USER\Software\Policies\Microsoft\Exchange\Exchange Provider]
> >
> > "DS Server"="Domain.Com"
> >
> > Thank you
> >
>
>
>
date: Wed, 30 Apr 2008 02:45:00 -0700
author: Manoj_Ikon26
|
|
