AD Account settings and Exchange 2007

Posted on 2010-11-17
Last Modified: 2012-05-10
This is going to be a long one so best grab yourself a tea or coffee before reading!

Background -

We have a single domain with 2 DCs - 2K3 AD, running Exchange 2K3 but in the process of migrating to Exchange 2K7 - Simple Exchange 2K7 install, nothing complicated. - Clients - XP SP3, couple of Windows 7 machines in testing for upgrading all XP machines.

The problem -

We have moved most (90%) of our users across and everything appears to be fine, they log on, launch Outlook which automatically reconfigured them to the new server and everything is happy.

Then we had a user log into a Windows 7 machine and setup their profile - unable to find the settings using Autodiscover - The usual error

Autodiscover to https://mailserver.domain/Autodiscover/Autodiscover.xml Failed (0x80072f78) - Now doing major amounts of research always points to the 2 same things as the cause - Certificates and permissions on IIS - However this is not the case.

Upon further testing I have found the following - Any new account that is created on the domain can quite happily login to XP or Win7 and autodiscover works a treat.
Accounts that have been created by myself in the past 2 years all work on both XP and Win7. (Prior to this date I wasn't the Network Admin)

So far every old account (Over 2 years old) fails on the Win 7 machines, but works Win XP.  I've used ADSIEdit and LDAP Browser to compare settings of working and non working accounts - Everything (Apart from GUID etc) are correct (Exchange details, legacy details, etc) in both working/non working accounts.

If I take a non working account, delete it, recreate it and reattach the mailbox then it happily works on both - This is a workaround, but not a solution, I'd rather not have to do this with all our users!

I've done a lot of research on this and found 1 other posting on the web where the same thing happened, they found a setting in the users AD account that they updated and it fixed the error (LegacyDN) but this fix doesn't work for us.

I'm 100% sure it's a setting somewhere in the users AD account that basically stops them from connecting to Autodiscover, but I'm at a loss as what.
Question by:GIFFER
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
  • 2
LVL 26

Expert Comment

by:Tony Johncock
ID: 34154003
I've seen something similar happen for activesync.

If you open up AD Users & Computers, and look at the properties of one of the affected accounts' security tab (may need to turn on advanced view if it isn't there). Click Advanced and ensure that the inherit permissions button it checked.

May not be relevant to your case, but definately worth a quick look.
LVL 24

Expert Comment

ID: 34154019
See if it helps for windows 7.

Can you rename the profile & ask the user to relogin & let new profile be created.

There is profile version difference between XP & win &
XP has V1 & win & V2, lets just try.

Author Comment

ID: 34154021
That was one of the first places I checked - Permissions are being inherited and a manual comparison for a working/non working user show the same results.
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.


Author Comment

ID: 34154037
@Awinish - We have the correct record for this (Already tried and tested).

I've ruled out profiles as the old user (having never logged into a Windows 7 machine before) doesn't have a V2 profile until they first login, but the issue is there.

Author Comment

ID: 34155737
More Testing and now more information -

I can kind of get things working, but in the process I end up losing another function.

In IE, if I tick the 'Automatically detect' settings option and remove the Proxy settings then Autodiscovery works - but the internet no longer works - reverse the setting and the Internet works but Autodiscover fails.

This only appears to the case on the Windows 7 machines - In XP, it doesn't make a difference if you have anything ticked or not, it works.
LVL 26

Expert Comment

by:Tony Johncock
ID: 34155795
Do you actually have a proxy server?

Author Comment

ID: 34155846
We have a Bloxx webfilter which doubles as a proxy box.
LVL 26

Assisted Solution

by:Tony Johncock
Tony Johncock earned 250 total points
ID: 34155932
Have you tried adding your autodiscover address as an exception in IE?
LVL 24

Accepted Solution

Awinish earned 250 total points
ID: 34156269
I think intranet client trying to go to internet for getting autodiscoverer host record to query exchange server for mailbox, as these records are in internal dns only.

Exclude the internal domain name from proxy using * & also create a host record in dns for intranet client to point o exchange server.

Author Closing Comment

ID: 34156602
All solved, thanks for your help guys.

I had to remove the 'Automatically detect' and add the * (internal) as an exception - The full url for the autodiscover couldn't be accepted but the domain was.
LVL 26

Expert Comment

by:Tony Johncock
ID: 34156626
You might want to look at dropping those settings down by group policy.

Thanks for the points and good luck.

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains the steps required to use the default Photos screensaver to display branding/corporate images
Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question