Cannot use autodiscover on new domain

We set up a new domain and migrated all our workstations and the user profiles to the new domain.

We have configured a brand new Exchange server as part of this as well.

We migrated all the profiles using the Profile Migration Tool (which works great)

The only issue we are currently facing is that computers that were on the old domain and migrated to the new one - Exchange autodiscover does not work.

On new PC's that were never on the old domain, Autodiscover works fine.  If you are out of the office - autodiscover works.

It seems to only affect the PC's that were on the old domain.

We are using Outlook 2010 with a couple Outlook 2012 as well.
LouisvilleGeekAsked:
Who is Participating?
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.

Will SzymkowskiSenior Solution ArchitectCommented:
Are the users using cached exchange mode on the machines that have been migrated? Have you tried creating a new Outlook profile to see if this corrects the behavior? If it is working on new machines and old machines got migrated successfully it seems like settings of the old domain autodiscover has been cached somewhere.

Will.
0
Nick RhodeIT DirectorCommented:
You can sort through this article.  Basically autodiscover is still contained within the registry if it was not configured previously to point to the new exchange.

http://support.microsoft.com/kb/2644437
0
LouisvilleGeekAuthor Commented:
Will:  We created new profiles and set up Exchange to the new server on all the machines prior to migrating to the new domain.

NRhode:  I checked those registry keys and everything looks OK.  I deleted the "RedirectServers" keys and closed, re-opened Outlook to let it recreate that key.  Still same issue.


The main issue we are having here is when we goto create an Out Of Office in Outlook we get the message that that server is unavailable.  I did some research on that error and it points to an autodiscover issue.  That is why I am trying that avenue here.  I am welcome to any and all ideas though.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Will SzymkowskiSenior Solution ArchitectCommented:
Refer to the below link for your OOO issue.
http://support.microsoft.com/kb/970123
0
LouisvilleGeekAuthor Commented:
Spec,

I did that registry fix with no luck.  We are running Office 2010 if that makes any difference.
0
Cliff GaliherCommented:
Will was on the right track. Outlook contains its own profile information, so when you say "We migrated all the profiles using the Profile Migration Tool" you also migrated the Outlook profile. Note that this is *different* than the AD user, the Exchange setup on the server, and even different than the local user's profile. This is specific to Outlook. It is also one of the more significant risks in building a new domain vs. migrating. Migrating is almost always better.

With that said, I'd try what Will suggested. Create a new OUTLOOK profile and see if things work better.  More info:

http://support.microsoft.com/kb/829918

That is at least a start.
0
Jakob DigranesSenior ConsultantCommented:
Can you press the CTRL-Key and click on Outlook icon ins system tray - then you'll get the option to Test Email Autoconfiguration. Then deselect GuessSmart options and enter email-address and password for an affected user.
Compare results with a working user
Is this error machine specific or user specific? you can use different usernames with this test.

So if you have a non-working PC with a non-working user, try a working user on that PC and the non-working user on a working PC
0
LouisvilleGeekAuthor Commented:
cgaliher, we did create new Outlook profiles.  We migrated the windows profiles.

The issue only seems to affect PC's that were on the old active directory domain.  We deployed new PC's to the new domain and they are fine.
0
Cliff GaliherCommented:
Roaming user profiles or local?
0
LouisvilleGeekAuthor Commented:
They have redirected desktop and my docs through Group Policy.
0
Cliff GaliherCommented:
Redirected folders are not the same as roaming profiles. And to properly troubleshoot the problem, it'd be helpful to know if we are dealing with local profiles or roaming profiles.
0
Jakob DigranesSenior ConsultantCommented:
Did you test autoconfiguration via Outlook?
0
LouisvilleGeekAuthor Commented:
They are local profiles with a redirect desktop and my docs.
0
Cliff GaliherCommented:
Then the next step I would take is create a new test user and see if the problem still exists when the new user logs into an old "troublesome" machine. This should help isolate the problem to a profile issue or something in the local machine configuration.

-Cliff
0
LouisvilleGeekAuthor Commented:
Autoconfiguration in Outlook fails.

When it autodiscovers to https://exchange.company.com/Autodiscover/Autodiscover.xml Failed (0x800C8203)
0
LouisvilleGeekAuthor Commented:
I created a new user and logged into a problem PC.  Same problem.

I should have mentioned in the beginning.  This is a brand new install of Exchange 2013 and a new Active-Directory domain to go with it.
0
Cliff GaliherCommented:
Okay. It is either a permissions issue or a data file got corrupted in the process of disjoining and joining domains.

Let's eliminate the former. Add this test user to the administrators group on the local machine (making them a local admin, not a domain admin.) Then log out, log back in, and see if things still break or if they start working.

-Cliff
0
LouisvilleGeekAuthor Commented:
Cliff,

All of the users are local admins.

I even logged into one of the machines with a domain admin account and set up an Outlook profile, same error.
0
Cliff GaliherCommented:
Sadly I am not surprised. I had hoped it would work as permissions issues are easier to fix. The only thing I can think of to do now is uninstall and reinstall Outlook.
0
SteveCommented:
When it autodiscovers to https://exchange.company.com/Autodiscover/Autodiscover.xml Failed (0x800C8203)

try connecting to that page from a PC with the issue and one that works fine to see if they get the same page.

ping/nslookup the usual autodiscover addresses to confirm they resolve to te right IP and can be reached
(usually autodiscover.domain.com for example)
0
LouisvilleGeekAuthor Commented:
Pinging/resolving works great in office and out of office.

We are going to try reinstalling Outlook.
0
SteveCommented:
And did you try to connect to the https address listed?
Does it have a valid ssl? Can you view the page?
0
LouisvilleGeekAuthor Commented:
Totally:  We did.  It does.  We can.

We uninstalled and reinstalled Office to no avail.

We are going to reinstall Windows on the machines.  That is the only solution we can think of at this point.
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
SteveCommented:
try installing the exchange management console on another machine as a test.
if it works fine it's the console at fault, if not it's the exchange servers at fault.
0
LouisvilleGeekAuthor Commented:
It was the only solution that worked.
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
Exchange

From novice to tech pro — start learning today.