Exchange 2007 SP1 Windows 2008 Server SP1 3 x Outlook 2007 Cached Mode on XP, Vista and Windows 7 3 Users with Outlook 2007 on XP, Vista, Windows7 respectively connected to our Exchange 2007 Server SP1 two or three users are not appearing in Global address list when they look up via MS Outlook 2007, so they can't schedule meetings etc However they can access it via OWA (fine). I deleted the *.OAB files (Windows7 - Outlook 2007) in %Username%AppData\Local\Microsoft\Outlook Re-Downloaded OAB via Outlook (Tools > Send & Receive > Download Address Book) Still the same thing - those 2 x users won't appear in there GAL / scheduling assistant I have read quiet a bit about this and people have mixed opinions : a) Re-Download OAB via Outlook after Updating it on the Server b) Primary SMTP and Windows Email Address should be the same Get-Mailbox -Identity "user.notappearing" | fl emailaddresses, windowsemailaddress Upon running the above powershell command, it reveals that both of the problem users "Windows Email Address" is different from their "SMTP" (Primary smtp address). Where does Exchange gets the Windows Email Address (Active Directory) ? How can I change there Windows Email Address to match with Primary SMTP address? Would that cause any problem for those users ? They have different aliases like fname.lastname@domain, fname@domain etc. I am running outlook 2007 on windows 7 in "NON-Cached" (ONLINE) Mode and I have the users listed no problem. Any suggestions ? Kind Regards PS : When I tried to switch to cached mode to re-produce the problem, some of my emails were missing - so i reverted back to Online Mode. What are the benefits of having cached mode vs online mode or vice versa ?

On Fri, 10 Dec 2010 12:07:54 +0000, RIHATUM wrote: [ snip ] >two or three users are not appearing in Global address list when they look up via MS Outlook 2007, so they can't schedule meetings etc [ snip ] >I have read quiet a bit about this and people have mixed opinions : > >a) Re-Download OAB via Outlook after Updating it on the Server This would only work if the OAL Generation was including them. >b) Primary SMTP and Windows Email Address should be the same If you increase the event logging level on the "MSExchangeSA\OAL Generator" to "High" you should see eventID 9325 in the applications log when that discrepancy is discovered. >Get-Mailbox -Identity "user.notappearing" | fl emailaddresses, windowsemailaddress >Upon running the above powershell command, it reveals that both of the problem users "Windows Email Address" is different from their "SMTP" (Primary smtp address). > >Where does Exchange gets the Windows Email Address (Active Directory) ? How can I change there Windows Email Address to match with Primary SMTP address? Would that cause any problem for those users ? They have different aliases like fname.lastname@domain, fname@domain etc. The set-user cmdlet is used to change the value. Use the "-WindowsEmailAddress" parameter. Or you can change it using ADUC if you prefer a GUI. >Any suggestions ? Increase the OAL even logging and fix the problem users. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich Matheisen, Thank you for your reply, would I use the following command to set the Event Log Level : Set-EventLogLevel -Identity "MSExchangeSA\OAL Generator" -Level High I know that set-user cmdlet will set the windows email address or any other address for that matter, but the QUESTION is : a) Will that effect any or the same user's mail flow or anyother problems - I mean when I change its Windows Email Address to be the same as its Primary SMTP Address? b) So after increasing the event logging level it should tell which entries are missed ? Thanks again for your answer !! will look forward to your reply and will update this tomorrow first thing. Kind Regards

What are the benefits of having cached mode vs online mode or vice versa ? Cached mode: - Outlook user can work offline, messages in Outbox leave when back online. - I believe it takes some of the load off the mailserver (may or may not be an issue depending on number of users, server specs). Online mode: I've seen it recommended when working with 3rd party software and devices like Blackberry. http://supportforums.blackberry.com/t5/BlackBerry-Professional-Software/Can-Outlook-cache-mode-cause-problems-for-BES-users/td-p/454411 http://www.blackberryforums.com/bes-admin-corner/139614-conflicts-outlook-cached-mode.html

On Mon, 13 Dec 2010 15:54:01 +0000, RIHATUM wrote: >Hi Rich Matheisen, Thank you for your reply, would I use the following command to set the Event Log Level : Set-EventLogLevel -Identity "MSExchangeSA\OAL Generator" -Level High I know that set-user cmdlet will set the windows email address or any other address for that matter, but the QUESTION is : a) Will that effect any or the same user's mail flow or anyother problems - I mean when I change its Windows Email Address to be the same as its Primary SMTP Address? The fact that the "mail" attribue and the primary SMTP proxy address aren't identical is a problem that must be fixed if you want that mailbox to show up in the OAB. If you don't fixt it it will work just as wel as it does today. If you do fix it the only side-effect is that your Exchange server will (or should) refuse to accept any e-mail sent to the address that's in the in the "mail" attribute now. As it stands, Exchange will not refuse to accept e-mail sent to that address, but it won't be able to deliver it. So, the short answer is that the change will only be beneficial. b) So after increasing the event logging level it should tell which entries are missed ? You'll see the errors recorded in the Allications Log. Not all errors prevent the mailbox from inclusion in the OAB. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

OALGen will skip user entry 'user1.lastname@domain.com' in address list '\Global Address List' because the SMTP address '' is invalid. - Default Offline Address Book OALGen will skip user entry 'user2.lastname@domain.com' in address list '\Global Address List' because the SMTP address '' is invalid. - Default Offline Address Book Hi Rich, Thanks for your explanation, above were the events logged as Event ID 9325, now : User1 : Primary SMTP is "firstname@domain.com", WindowsEmailAddress : "firstname.lastname@domain.com" User2 : Primary SMTP is "firstname.lastname@domain.com, WindowsEmailAddress : "firstname@domain.com" "If you do fix it the only side-effect is that your Exchange server will (or should) refuse to accept any e-mail sent to the address that's in the in the "mail" attribute now. As it stands, Exchange will not refuse to accept e-mail sent to that address, but it won't be able to deliver it." With above do you mean that when I will change the "Windows Email Address" to match the Primary SMTP for USER2 they won't be able to receive email on "firstname@domain.com" because now there Windows email address would be "firstname.lastname@domain.com" ? As you can see that I have two users with this problem but there Windows Email Addresses are opposite to each other (One has firstname.lastname@domain and the other has firstname@domain). If I add firstname@domain.com as yet another smtp alias for USER2, will they be able to get there emails if sent to firstname@domain.com ? Thanks for your support - I hope I have made sense :-) Kind Regards

On Tue, 14 Dec 2010 09:54:31 +0000, RIHATUM wrote: >OALGen will skip user entry 'user1.lastname@domain.com' in address list '\Global Address List' because the SMTP address '' is invalid. - Default Offline Address Book >OALGen will skip user entry 'user2.lastname@domain.com' in address list '\Global Address List' because the SMTP address '' is invalid. - Default Offline Address Book >Hi Rich, Thanks for your explanation, above were the events logged as Event ID 9325, now : >User1 : Primary SMTP is "firstname@domain.com", WindowsEmailAddress : "firstname.lastname@domain.com" >User2 : Primary SMTP is "firstname.lastname@domain.com, WindowsEmailAddress : "firstname@domain.com" >>"If you do fix it the only side-effect is that your Exchange server will (or should) refuse to accept any e-mail sent to the address that's in the in the "mail" attribute now. As it stands, Exchange will not refuse to accept e-mail sent to that address, but it won't be able to deliver it." >With above do you mean that when I will change the "Windows Email Address" to match the Primary SMTP for USER2 they won't be able to receive email on "firstname@domain.com" because now there Windows email address would be "firstname.lastname@domain.com" ? If a message is sent to the address in the "mail" property (and that address isn't in the proxyaddresses property) the e-mail address will be found (it's in the AD). However, it's unlikely that Exchange would actually deliver that message since it's not in the "proxyaddresses" property. If you want firstname.lastname to be useful, add it to the e-mail addresses assigned to the mailbox (probably as a secondary SMTP proxy address). If the "mail" property doesn't change to be the same as the primary SMTP proxy address you can use the ADUC or the set-user cmdlet to put the primary SMTP address into the mail property. >As you can see that I have two users with this problem but there Windows Email Addresses are opposite to each other (One has firstname.lastname@domain and the other has firstname@domain). If I add firstname@domain.com as yet another smtp alias for USER2, will they be able to get there emails if sent to firstname@domain.com ? Yes, they will. >Thanks for your support - I hope I have made sense :-) Kind Regards --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP