How Do I Disable Current Outlook Config in Group Policy - Server 2008 SBS

We have a domain running on Windows Server 2008 SBS. We used to use the built-in Exchange to manage our email. However, we have now migrated our email system over to Office 365.

We are having a problem configuring Outlook 2010 on the client workstations to use Office 365. We tried creating new Mail profiles that point to Office 365. However, as soon as the user logs out of Outlook and logs back in, Outlook reverts back to using the old mail profile that points to the local Exchange server (which of course, no longer receives email since the MX records are pointing to Office 356). Looks like there must be a Group Policy in AD that keeps pushing out that original (and now obsolete)  Outlook configuration to each work station.

We need to find that GPO Outlook setting and disable it. Assume this will be done be modifying the GPO, but don't have any experience modifying GPO.

There may also a client side app/setting that is being used to configure SBS clients. If so, we will need to disable that as well.

Thanks in advance.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

David Johnson, CD, MVPOwnerCommented:
check your autodiscover records
Vasil Michev (MVP)Commented:
The registry keys (they correspond to the GPO settings) you need to update are listed here:

You can block everything apart from the HTTP redirect method, as that's what O365 will use.
James NewportCommented:
You need to disable auto discover on your SBS box. You can use

Ok heres what I did to disable auto discover
Open EMS
Run the following cmdlet Get-ClientAccessServer
Set-ClientAccessServer -Identity "CASxx" -AutoDiscoverServiceInternalUri $NULL

Where "CASxx" is the name of the CAS server that was discovered in step 2

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 Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

anuneznycAuthor Commented:
Thanks for all the suggestions, Guys. I will have access to this server after close of business today.

@relnyonit By EMS, you the mean the Exchange Management Shell? I don't think that component is installed on our SBS server.
anuneznycAuthor Commented:
I have also been told that Small Business Server has a group policy object that is forced on clients that configures the exchange stuff on each workstation.

We have to stop the GPO from pushing out that client app.
James NewportCommented:
I'm sure the ems is installed by default on sbs

I did this when we migrated to o365 and it works no problems
anuneznycAuthor Commented:
@relyonit Thanks. Do you know the command I can use to launch EMS directly from the Run command or command prompt?
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
Windows Server 2008

From novice to tech pro — start learning today.