We help IT Professionals succeed at work.

Exchange 2007 Global address list

joshrosen
joshrosen asked
on
Medium Priority
541 Views
Last Modified: 2012-05-07
I have a new Exchange 2007 server installed that was migrated from an exchange 2000. Everything is working fine except for 1 issue. The Domain comntroller is sitting on a 2003 server as well as the GC. When we add a new mailbox using the exchange 2007 managment console the new user will show up in the Global catalog as long as you log into outlook web access but the Outlook clients on the network do not see the new users. How do I force the clients on the network to update their global catalog?
Comment
Watch Question

Commented:
See if your Outlook is in cached mode. Try checking the same in online mode.. If thats work try downloading the OAB ......OAB doesn't seems to be updating

Author

Commented:
How do you download the OAB?

Commented:
In outlook fo to Tools> Send Recieve > Download Address Book..
Expert of the Quarter 2009
Expert of the Year 2009
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
If I take a client and remove cached mode it starts working. I tried this on 1 client out of 250. On anouther client I tried the update address book and it did not work. There must be anouther way to update all cached mode clients besides going around to 250 workstations. Any thoughts?

Author

Commented:
When I re enable cached mode all new uers go away again.

Commented:
So it is sure issue with your OAB which is not updating?  

Commented:
Also check if there any Erros you can see in the App log

Author

Commented:
Process MSEXCHANGEADTOPOLOGY (PID=1604). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server.

Commented:
For better understanding oF OAB check http://msexchangeteam.com/archive/2006/11/15/431502.aspx 
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
The OAB update issue is something that you will have to live with.
While it is possible to have the OAB update more often, by changing the generation schedule, you cannot change the behaviour of Outlook when it comes to downloading a new copy of the OAB.
For most companies this isn't a problem because new users are not created that often.
Where there is a high turnover and no laptop use, then the OAB can be turned off. However if you have laptop users then it isn't advised.

Simon.

Author

Commented:
I do not understand if users have been using the GC for years in 2000 2003 why would things change. Does this mean that by upgrading to 2007 users must go to outlook 2007? How do you change the Generation schedule?
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
The behaviour hasn't changed since Exchange 5.5, if you are using Outlook 2003 or higher in cached mode. Cached mode is basically offline folders on steroids - offline folders have been around in every version of Outlook ever.

I cannot comment on how you had your Exchange 2000 server setup, but by default it would be the same for Outlook 2003 and higher in cached mode - OAB generation once a day, downloaded automatically once a day or when Outlook is restarted. Nothing has changed in Exchange 2007.

If you were seeing changes to the GAL immediately then I have to doubt that you were using cached mode. You cannot see GAL changes live in cached mode unless the OAB functionality is disabled. That is an Outlook setting, not an Exchange setting, therefore would still apply after a migration.

Simon.

Author

Commented:
Simon I created a user 6 days ago and the GAL was not updated only when I uncheck cahched mode.
all users are on chached mode. The client on all workstations is 2003 outlook.
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
You are incorrect - the GAL was not updated when you turned off cached mode. That is like saying your car was fixed after an accident because you bought a new car.

When you disabled cached mode you switched from using the Offline Address Book to using live information.

If the user was created six days ago then it sounds like the OAB is not updating correctly.
Did you follow the Microsoft guide for removing Exchange 2000 - including moving things like the OAB generation server and replicating the public and system folders?

Simon.

Author

Commented:
Yes I did and they all said replicated. Followed step by steb by kb articles.
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
Run

get-offlineaddressbook |fl

verify that every server in the results is valid. It should be pointing to your Exchange 2007 server and to a domain controller.

Simon.

Author

Commented:
Mestha when I do a get-offlineaddressbook it shows my current 2007 server no others.
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
If you run the command I provided above, then wait, and then look in the event viewer, does that show any errors related to the OAB?
Have you run the best practises tool from the toolbox?

Simon.

Author

Commented:
The only error message I get in the APp log is the one I have posted above. The BP analyzer comes back clean in the Health Check.

Author

Commented:
Process MSEXCHANGEADTOPOLOGY (PID=1604). When updating security for a remote procedure call (RPC) access for the Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object TTOPSCORP16 - Error code=8007077f.
 The Exchange Active Directory Topology service will continue with limited permissions.

and


Process MSEXCHANGEADTOPOLOGY (PID=1604). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server.

Author

Commented:
I ran the BPA on the exchange server itself and got under Non-Default settings the following

Default Global Adress List Changed:

The 'purportedSearch' attribute of the default Global Address List 'Default Global Address List' has been changed. Default: '(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=contact))(objectCategory=group)(objectCategory=publicFolder)(objectCategory=msExchDynamicDistributionList) ))'. Current: '(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=contact))(objectCategory=group)(objectCategory=publicFolder) ))'.
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
I would correct the GAL back to what it should be and also resolve any other issues the best practises tool says.

The earlier error is a little more of a concern and would tend to indicate a problem with the domain. Ensure that the Exchange server is only using the domain controllers for DNS - no external DNS servers.

Simon.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.