Customized Outlook Install Always Defaulting back to original Exchange Server

We are migrating to a new domain and new Exchange server.  Our PCs are built from a customized Office installation that forces Outlook to connect directly to a specific Exchange server.  We are trying to connect users to a different, new Exchange server.

We have tried creating an Outlook .prf file that points the user to the new server, but this doesn't work.  It always defaults back to the original server.

We've compiled a new MSP file which points to the new server, and this works perfectly for new users, but does not over-write existing users.  If we delete the existing user's Windows profile and have them login and recreate the profile when they open Outlook it uses the new MSP file and connects to the new server.

In the original profile we have also tried deleting the Outlook profiles and re-creating from scratch.  They always are forced to the old server.

The old server is Exchange 2003 and has no autodiscover records configured and we have done all the testing we could to rule out DNS issues.  It is definitely coming from the Office install / customization.

Anyone know how to force-overwrite this?  We have a case opened with Microsoft and we are awaiting a response but I was hoping someone on here may have some ideas.
LVL 10
Larry LarmeuPrincipal ConsultantAsked:
Who is Participating?

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

x
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.

Felix LevenSenior System and DatabaseadministratorCommented:
If the custom Office installation points to a CNAME in dns like EXCHANGE.yourdomain.com you can redirect the CNAME to the new server in DNS.
0
Larry LarmeuPrincipal ConsultantAuthor Commented:
It points to an A record, but that Exchange server is still existing and acting so we cannot do that because others need to access that server.
0
Felix LevenSenior System and DatabaseadministratorCommented:
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Larry LarmeuPrincipal ConsultantAuthor Commented:
Just tried that, doesn't appear to be working.  I do see that that is for Outlook 2003 and we are running Outlook 2007.
0
Larry LarmeuPrincipal ConsultantAuthor Commented:
Turned out to be a key that was in a GPO that set the following:

"HKCU\Software\Microsoft\Exchange\Exchange Provider" /v "DS Server" /t REG_SZ /d [server] /f

It overrides autodiscover and Office Customization Tool and queries a Global Catalog server for the Exchange provider.
0

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
Larry LarmeuPrincipal ConsultantAuthor Commented:
Found it myself
0
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
Outlook

From novice to tech pro — start learning today.