A lot of people had problems with the original version of this update http://support.microsoft.com/kb/2412171 It seemed that the best option was to uninstall it.
From the cached version of http://blogs.office.com/b/microsoft-outlook/archive/2011/01/13/fixes-for-issues-with-december-update-for-outlook-2007-have-been-released.aspx
janegilring
15 Jan 2011 11:23 AM
Ive experienced problems with Autodiscover when setting up new Outlook-profiles after installing this update. Instead of pre-populating the E-mail address field with the user s primary SMTP-address, the user`s UPN was used. This of course caused Autodiscover to fail since the UPN was not an alias on the mailboxes.
After uninstalling the latest Outlook 2007 update the issue was resolved, and the primary SMTP-address was pre-populated.
I`ve also experienced the issue with Outlook 2010, removing the latest hotfix package resolved the issue.
The affected updates:
Description of the Outlook 2010 hotfix package: December 14, 2010
support.microsoft.com/.../2459115
Description of the Office Outlook 2007 update: January 11, 2011
support.microsoft.com/.../2412171
The Outlook 2007 update are released to Windows Update/WSUS, while the Outlook 2010 hotfix package must be requested afaik.
Is this a known issue, and is it due to be fixed in upcoming updates?
To Uninstall:
How to uninstall this update Click
Start, and then click Run. Type
appwiz.cpl, and then click OK. Use one
of the following procedures, depending
on the operating system that you are
running: Windows 7 and Windows Vista
Click View installed updates. In the
list of updates, locate and click
update 2412171, and then click
Uninstall. Windows XP Click to select
the Show updates check box. In the
list of updates, locate and click
update 2412171, and then click Remove.
The problem is Outlook is preferring the autodiscover information it is finding in Active Directory via SCP and SRV records.
You can enter a few registry values to change that behavior. This registry file is for Office 2010 but if you change the version number it will also work with older version.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover]
"ExcludeSrvRecord"=dword:00000001
"ExcludeScpLookup"=dword:00000001
"ExcludeSrvLookup"=dword:00000001
This link describes the problem in more detail: http://support.microsoft.com/kb/956955
Best Answer
You could solve this through DNS.
One way is by having an ourcompany.com.local zone defined on your DNS server and setup the appropriate addresses to resolve (ie: autodiscover.ourcompany.com.local) and on your DHCP server set the DNS suffix of .local to be given to your clients.
That way, when the PC goes to look for autodiscover.ourcompany.com, it will first look for autodiscover.ourcompany.com.local and get the address from your local DNS server with the Exchange server's internal IP address.
If a user tries to go to www.ourcompany.com and you haven't defined www.ourcompany.com.local then it will find www.ourcompany.com as it did before.
This way is useful if some of your services are internal and others are not, so you don't want to replace all of the records of ourcompany.com with local addresses.
Another similar way, is to just define ourcompany.com on your local DNS server and configure all of the records appropriately, then you don't have to get into the DHCP/DNS Suffix situation.