I am running an Exchange 2003 SP2 environment and I have had some permissions corruption with AD where the Exchange Domain Servers and Exchange Enterprise Servers groups lost their permissions to the Microsoft Exchange System Objects folder. Because of this, no new mailbox store would mount and any new public folder that I mail-enabled would not display it's email address information. I fixed the problem by giving full control permissions for Exchange Domain Servers and Exchange Enterprise Servers to the Microsoft Exchange System Objects folder and I am now able to mail enable public folders and new mailbox stores are mounting. However, I still have a problem where the Recipient Update Service will not generate emails for new mail-enabled public folders. The RUS is generating email addresses for new user accounts but not for new mail-enabled public folders. I manually created an SMTP and x.400 email address for a new public folder but it is not showing up in the Global Address List at all. I don't see any other error message related to this in the application log. I created a few more test mail-enabled public folders and they do not get email addresses either. Rebooting all the Exchange Servers didn't help. Can someone give me information on how email addresses are generated for mail-enabled public folder and tell me if I need more permissions to to fix this problem? Any ideas? Steve

HAve you run through the RUS troubleshooting steps? ( RUS also stamps the ShowInAddressBook, so thats why its not showing in the GAL. If you look at a pf that is, you can see what attributes need to be populated) Is inheritance enabled on that container? http://support.microsoft.com/kb/254030 Missing permissions cause the Recipient Update Service not to process accounts in Exchange 2000 Server and Exchange Server 2003 http://www.msexchange.org/articles/Troubleshooting-Exchange-Recipient-Update-Service-RUS.html http://support.microsoft.com/kb/822794 http://msexchangeteam.com/archive/2004/07/15/184356.aspx Ran ExBpa for health and permissions checks against the server?

HAve you run through the RUS troubleshooting steps? ( RUS also stamps the ShowInAddressBook, so thats why its not showing in the GAL. If you look at a pf that is, you can see what attributes need to be populated) Is inheritance enabled on that container? http://www.msexchange.org/articles/Troubleshooting-Exchange-Recipient-Update-Service-RUS.html http://support.microsoft.com/kb/822794 http://msexchangeteam.com/archive/2004/07/15/184356.aspx Ran ExBpa for health and permissions checks against the server?

I ran the ExBPA and it reported that 3 OU's do not have inheritance enabled? Do you think that is the issue? Inheritance is enabled on the MS Exchange System Objects folder.Steve

Well, probably not, but if you have inheritance disabled on OUs that hold mail-enabled objects, then you need to enable it.

hello all, I suspect that there is some issues with Enterprise RUS, because newly created users are getting email address but only mail enabled public folders not getting email address. i think Steve you should check the troubleshooting with enteprise RUS, and mean while you can check for "gatewayproxy" attribute on enterprise RUS in ADSIEDIT, if there are some values, take system state backup of schema master DC and clear them, and update entrprise RUS.

Thanks for replying, Prem. I do see entries in the gatewayproxy attribute for the enterprise RUS as well as the domain RUS. They match the e-mail address policy settings from the default recipient policy. There is also a 3rd custom RUS that has the email addresses repeated many times over and over again. Is this a problem? Do you think I need to clear them out in only the enterpeise RUS? Do they need to be cleared out of the other RUS's as well? Do you know why they got filled in in the first place? Please let me know. Thanks again for your help. SteveSteve

Thanks for replying, Prem. I do see entries in the gatewayproxy attribute for the enterprise RUS as well as the domain RUS. They match the e-mail address policy settings from the default recipient policy. There is also a 3rd custom RUS that has the email addresses repeated many times over and over again. Is this a problem? Do you think I need to clear them out in only the enterpeise RUS? Do they need to be cleared out of the other RUS's as well? Do you know why they got filled in in the first place? Please let me know. Thanks again for your help. Steve -- The 'gatewayProxy' attribute for Recipient Update Service 'Recipient Update Service (Enterprise Configuration)' contains old data that was not fully processed. Steve

The Best Practice Analyzer is reporting that the 'gatewayproxy' attribute does need to be cleared out of the RUSes. Do you think this is the problem? -- The 'gatewayProxy' attribute for Recipient Update Service 'Recipient Update Service (Enterprise Configuration)' contains old data that was not fully processed. Steve