New Users not showing in Global Address Book

[mlc9]

Have recently migrated from Exchange 2003 to Exchange 2010. Most things seem to be going well, but new Active Directory users are not appearing in our Global Address Book.

Procedure is to create the new user on the Exchange 2010 server, along with their mailbox obviously. That user replicates fine to our AD / domain controllers and is given proper email addresses per our recipient policy. The issue is that our Outlook clients can not see the new users in Global Address Book. Exchange services have been restarted (System Attendant, Information Store, etc), and server has even been restarted. These new users DO NOT have the box checked to "Hide from Global Address List"

Along with the Exchange upgrade, we also refreshed our domain by going from 2003 to 2008 domain controllers. Don't think that has anything to do with this, but thought I'd give all info possible.

Any thoughts what to check? Where to start? Thanks

 

[mlc9]

**Update**

Within my own Outlook 2007 client, I have "Cached Exchange Mode" enabled. When I chose to disable that, and restart Outlook, I can now see my new users in Global Address Book. When I switch back to Cached mode, I cannot see the users.

This is obviously the issue, but since all of our users are likely using cached Exchange mode, can anyone please tell me how to resolve this?

 

[mlc9]

**Update, Part II**

Ok, the more research I do, the more I keep answering my own question. But, I do not like what I am finding, so am still looking for help.

Microsoft seems to think that the solution to my issue is to create a registry key specific to your version of Outlook. This key controls how Outlook downloads OAB. Additionally, if your Outlook client has previously connected to your Exchange OAB, you need to basically delete your local Outlook email profile and re-create. This effectively re-downloads .oab files.

Sure enough, the combination of a new registry key and blowing away my local Outlook profile worked. I am now able to view new domain users in global address book. The problem is that there is no way I can do this for 80+ employees. Pushing out the registry key via Group Policy would be hard, because users are running Outlook 2003 and 2007. That means two different keys. Not to mention having to re-create Outlook profiles for all my users.

Does anybody have any ideas?

 

[58sniper]

This is widely documented. The OAB is generated once a day by default in Exchange. The client downloads the OAB once a day by default. As a result, it can take a couple of days for a users to show up in Outlook if Outlook is (and it should be) in cached mode.

If you log in via OWA, which does not use the OAB, you should see the user right after creation.

Stop by the new Tek-Tips group at LinkedIn. Come say hi, look for a job, have some fun.

http://www.linkedin.com/groups/Networking-TekTipscom-forums-members-3952395

Pat Richard MVP

http://www.exchangeblogs.com/

 

[mlc9]

Actually, this was not a replication issue that would take a few days to update. New users had been created two weeks ago, and still could not been seen in GAB.

I actually had to open up a case with Microsoft to resolve. It actually came down to DNS entries. Since Exchange 2010 pretty much runs everything securely via OWA, local clients must resolve the internal email server to owa address. Our local DNS entries point clients to FQDN of actual email server. I had to put in another entry that resolved the IP of email server to address of OWA. Otherwise, clients could not resolve and update the address book

 

[markdmac]

Is your internal DNS name the same as your external?

Sounds like you probably didn't have the Autodiscover DNS entry set internally.

I hope that helps.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[Zelandakh]

Yes, you'd need 2 entries in DNS, both server and server.domain.local pointing at the CAS plus you'd need autodiscover pointing at the CAS and the correct entries in the OWA config.