User not showing up in GAL

Recently we had a major exchange failure.  We moved the mail stores to another exchange server and reconnceted the user's mailboxes to their AD accounts.  Unfortunately, one user is still unable to log into their Outlook.  It seems that even though her mailbox is connected to her AD account, the default policies within Exchange have yet to replicate to her AD account.  So for instance, she should have x number of email addresses within her AD account, but nothing has propogated over.  I had to manually add in an email account for her to receive email.  Unfortunately this still does not resolve the entire issue since she still does not show up within the GAL and when trying to recreate her Outlook profile, Outlook is unable to find her account through the address list.  To get around this, I have added in some email addresses manually through AD and am able to access her email through OWA.  However, we need to be able to resolve this issue all together.  
nvr8981Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jessie Gill, CISSPTechnical ArchitectCommented:
On the exchange server open active directory users and computers, then go to her user account properties , then select the exchange advanced tab and make sure hid from exchange address list is not checked.
0
lollygagrCommented:
Good description of a Recipient Policy problem.  Did you rehome the Recipient Updates Service to reflect the new server?  In the System Manager, go to Recipients - Recipient Update Services, and find any service that is homed on your old Exchange server.  In the properties, change the Exchange server value to your new server and make sure the domain controller is valid and the update interval is either Always Run or at least every hour.

Hope that helps you out.

DanG
0
abraham808Commented:
First thing to check is the event viewer for error messages and go from there.

Go to the ESM and then Recipients and check the Recipient Update Services.

Depending on how many Domains you have Make sure that info is correct.  

Are your exchange servers communuicating with the Global Catalog?

0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

nvr8981Author Commented:
Thanks Guys,

Great answers, however I have a few additional pieces of information.  First, I made sure that the Hide from Exchange feature was not checked off on AD.  Second, we have tried to force an update through Recipient Update Services and tried to change the exchange server and DC to make sure that everything updates.  But even then, we moved 87 users the exact same way last night and they all seem fine.  Its only this user and maybe one other user.  Any additional ideas or suggestions.  

Again, thanks again for all your help.
0
lollygagrCommented:
Have you tested by creating a new mail-enabled user and checking to see if the email addresses are automatically applied per your Recipient Policy?  If not, it would be a good way to see if it's the account or RUS that is having the issue.

If your new account doesn't receive email addresses, and if you haven't rebooted your dc since these changes, you could give that a shot.  I have found that sometimes a swift dc kick can jumpstart your Recipient Updates service into working again.
0
abraham808Commented:
Check under the email addresses tab and make sure there is a check under Automatically update e-mail addresses based on recipient policy
0
nvr8981Author Commented:
Just created a new mail enabled account and all of the email addresses have propogated over to this account.  
0
lollygagrCommented:
While you are working on the RUS, you can "fix" the one user by manually creating an x400 address for her - that will ensure GAL inclusion, though you may have OAB issues as well that can affect your cached mode users.  In any case,  look at the x400 string generated for another user to see which fields to populate, then fill out the x400 address properties "form", and then check the string in this new account against the others.  
0
nvr8981Author Commented:
OK, it seems the user had her Outlook running in a different location.  When we moved the mailbox, it seems that AD had a hard time finding the new Exchange server.  We ended up seperating her mailbox from her account in AD, deleted/recreated her AD account, and re-attached her email to the new AD account.  
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.