Ever since We upgraded our 2003 AD domain to 2008R2, using the exchange 2007 managment console when we check the "Hide from Address List" and then check the global address list, the user's email address is still there. Looked in the attributes of the user account the and the attribute for msexchhidefromaddresslists is listed as true. Please help there is not much about this issue out there.

Hi, Are u checking in OWA or Outlook? Run following command in Exch Management Shell Update-GlobalAddressList "Default Global Address List" and then check in OWA. Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

Is your Outlook in cached mode? The OAB doesn't get regenerated right away. Change to Online Mode and try again or try in OWA like Laeeq suggested.Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

OAB update can also be helpful here - Update-OfflineAddressBook -Identity "My OAB" Are there any errors in the logs that may help?MCITP: Enterprise Messaging Administrator

Outlook is not in cached mode, I have run these commands several times on different days, waited for everything to update and they still don't hide. It has something to do with our AD upgrade to 2008 R2, because we never had the problem until I upgraded the AD to 2008 R2.

Hi, Plz confirm in OWA whether GAL in OWA have these users or not, whom u have hidden from address lists. Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

Confirmed, they still show in OWA.

Confirmed, they still show in OWA. If the hidden users are still being shown in OWA it means that it is GAL problem, not OAB. Do u have multiple DCs in your environmnt? if so is there any replication latency among the DCs? RegardsLaeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

Confirmed, they still show in OWA. Also some days ago another person was having similar sort of problem, when he was modfiying the user attribute "msExchHideFromAddressLists" using ADSIEdit.msc. The users were still being shown in GAL, and he fixed this issue by clearing another user attribute "ShowinAddressBook", using ADSIEdit.msc. Plz have a look into this post: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/thread/d3c510c0-e1e0-467b-a815-805e4e9e973e So at your end, for test purposes, also clear the attribute "ShowinAddressBook" for user, and then run Update-GlobalAddressBook "Default Global Address Book" and then check in OWA. Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

clear the attribute "ShowinAddressBook" for user, and then run Update-GlobalAddressBook "Default Global Address Book" Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com This worked like a charm, now my question is, thru 2008 R2 AD when the check box is selected why does it not clear that attribute out like it use to??

This worked like a charm, now my question is, thru 2008 R2 AD when the check box is selected why does it not clear that attribute out like it use to?? Dont know about this bug, but in my ex2007 SP2 with Win 2003 SP 2 DC, it is running fine and on Ex2010 with Win 2008 R2 DC also running fine. If you have not applied service pack 2 (SP3 is there but I wont recommend installing it for such an issue becasue it has been released few days back and may take time to mature for production usage) or Rollups, then I will suggest u to install it. Also backup everything in production envrionment before applying Exchange SPs. Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

On Mon, 28 Jun 2010 13:24:58 +0000, COY_John wrote: >clear the attribute "ShowinAddressBook" for user, and then run > >Update-GlobalAddressBook "Default Global Address Book" >Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.comThis worked like a charm, now my question is, thru 2008 R2 AD when the check box is selected why does it not clear that attribute out like it use to?? If you're asking about the Actiove Directory Users and Computers snap-in, don't use it to manage Exchange attributes. Remove it from the machines and use the Exchange Management Console and/or Exchange management Shell. The ADUC doesn't know about any new attributes and property values, and it hasn't since 2007. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

If you're asking about the Actiove Directory Users and Computers snap-in, don't use it to manage Exchange attributes. Remove it from the machines and use the Exchange Management Console and/or Exchange management Shell. The ADUC doesn't know about any new attributes and property values, and it hasn't since 2007. Yes I know this, but even from the exchange management console it still was not being removed. Microsoft really needs to blend the two systems back together, it makes more sense, plus is easier and quicker to manage all aspects of the domain thru one interface instead of many different ones.

Yes I know this, but even from the exchange management console it still was not being removed. Microsoft really needs to blend the two systems back together, it makes more sense, plus is easier and quicker to manage all aspects of the domain thru one interface instead of many different ones. Microsoft has published an article over this change: http://technet.microsoft.com/en-us/library/bb266972(EXCHG.80).aspx Here is an excerpt from this article: Why We Made the Changes When Active Directory was introduced in Exchange 2000 Server, we found that many organizations used separate administrators for Exchange and Active Directory. This, of course, meant that there was a need to delegate administrative functions. In these scenarios, operations were decentralized so that separate teams managed aspects of Exchange and Microsoft Windows (Active Directory). Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

On Wed, 30 Jun 2010 12:07:14 +0000, COY_John wrote: >If you're asking about the Actiove Directory Users and Computers snap-in, don't use it to manage Exchange attributes. Remove it from the machines and use the Exchange Management Console and/or Exchange management Shell. The ADUC doesn't know about any new attributes and property values, and it hasn't since 2007. > >Yes I know this, but even from the exchange management console it still was not being removed. So the msExchHideFromAddressLists property value was still set to "TRUE"? What was in the property showInAddressLists? Setting msExchHideFromAddressLists to "FALSE" with the ADUC just changes that property value. It (the ADUC) assumes that there's a pre-Exchange 2007 server that running a RUS in the domain. It's the job of the RUS to figure out what what to put into the showInAddressBook property. If there's no RUS and the showInAddressBook isn't populated then there's no address book specified to show the objec in, even if msExchHideFromAddressLists is "FALSE". Conversely, simply setting msExchHideFromAddressLists to "TRUE" doesn't remove the property showInAddressBook. If there are other problems with the properties of the user it's possible that the EMC wasn't able to figure out what to do with the user. In that case, using the update-addressbook cmdlet is the correct thing to use. >Microsoft really needs to blend the two systems back together, it makes more sense, plus is easier and quicker to manage all aspects of the domain thru one interface instead of many different ones. Some days I'd agree with you. Some days I wouldn't. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP