Hello, I hope you can help me with a specific question but if there is a better way of tackling the bigger picture, please raise it. We have a single exchange server environment with multiple "web" domains and users from many businesses. We don't want them to see each other but still want all the functionality of exchange. We have found, if the user isn't listed in the OAB (because of privacy reasons), the user gets a send/receive error and out of office assistant doesn't work in Outlook 2007 running over https (outlook anywhere). You get a 0x8004010F error if they're not on the OAB and Out of Office errors with a dialog. If the user IS in the OAB and also has the policy created email... everything works over https. Yes, autodiscover is fine, the certificate is active, the oab is publishing to web. If you connect internally and not over the internet everything works fine. Is there a way of having users to users private but retaining this functionality?

Hello Timmy, Did you mean to say, OAB is not working when accessing it from the internet? I would like to know how many users are affected? How long its been happening? You are running Hosted Solution, what is recent change you made on the server?Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com

We're currently running an On Premise setup of Exchange Server 2010 SP1. I'm starting to think Multi-Tenant is the way to go? OAB is working, in Outlook 2007 users can't find themselves in it.

If user's can't find theme self that means the issue is with OAB or the GAL. Multi-Tenant is a good idea but i would like you to read this article, cause there are lot's of things which are not available. http://technet.microsoft.com/en-us/library/ff923251.aspx I am still waiting for the answer of some of my questions which i posted.Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com

Hello Timmy, Any update on the issue?Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com

We're currently running an On Premise setup of Exchange Server 2010 SP1. I'm starting to think Multi-Tenant is the way to go? OAB is working, in Outlook 2007 users can't find themselves in it. You can only use the multi-tenant option if its a new Exchange deployment. While this is the best option for multi-tenancy, you may also want to use the ABP feature of SP2 which should be out later this year: http://blogs.technet.com/b/exchange/archive/2011/01/27/gal-segmentation-exchange-server-2010-and-address-book-policies.aspx Regarding 0x8004010F, you may wish to see this: Troubleshooting Error 0x8004010F When Outlook 2007 Clients Download OAB Mike Crowley | MVP My Blog -- Planet Technologies

Timmy, any update here? Mike Crowley | MVP My Blog -- Planet Technologies