Out of Office Assistant
- I migrated a user's mailbox from exchange 2003 to exchange 2007. The user happened to have the Out of Office Assistant turned on, now we can't get it to turn off. It returns the following error:
"Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later."
Any clues?
All Replies
Hi,
You MUST be the owner of the mailbox to open the OOF assistant so that means that you must be logged using the user's domain account.
Creating just the profile on a machine that has no joined your domain or using a domain account that is not the owner of the mailbox will not work.
You can ALWAYS enable/disable the OOF from OWA.
Regards.
- Proposed As Answer bysdhand Friday, January 08, 2010 3:19 AM
- I was able to turn it off via OWA...however now the only way she can put herself OUT/IN the office she has to OWA. I had her log into multiple PCs to make sure that it wasn't her PC and she gets the same error. Deleted her OUTLOOK profile...nothing :-(
- I had the same problem with a mailbox migrated from exchange 2000 to ex2k7. I fear I will have to exmerge the 4GB of email out, delete the mailbox, recreate the mailbox and exmerge the email back in. Hopefully microsoft has an explanation/fix for this since using OWA to solely manage out of office is not the intended design.
-Norm - I have the same problem on a mailbox migrated from ex2k to ex2k7. I fear I'll have to export the email from exchange with outlook, delete the mailbox, re-create the mailbox, and re-import all the email. Hopefully there is an easier way.
-Norm - what is wrong with these forums?
- I hope that's not the only answer. I now have two users
We are running into this as well. i found this online:
Status:
Active; No resolution pending
Last Updated:
5/1/2007
More Information:
This problem occurs for users who login to their PCs using a child domain account and use Outlook 2007 (Outlook 2003 does not exhibit the same problem) as their e-mail client. As a result of this issue with Outlook 2007 and the inclusion of additional settings not available in Outlook 2003, we recommend that users utilize the tools available from Outlook Web Access (OWA) to set out of office settings in all instances. The out of office settings are available in OWA by clicking Options > Out of Office Assistant. This issue is also mentioned in the FAQs section of this site.
The users affected here are using Outlook 2007 only. so we believe it's something between the E2K7 and Outlook 2K7.
has anyone had any more luck with this??
Where did you find this information? Did it come from Microsoft?
We are having the same issue -- can't use the Out of Office settings directly from Outlook but they work from OWA. We have a brand-new install of Exchange 2007 (never used Exchange before) and Outlook 2007.
- I pulled this from Google. i havent found anything on the MSFT site yet...
Try running the clean rules switch, cleaning all the rules you have on that computer.
If there are no rules running on that computer make a rule then run the clean rule switch and then try the Out of Office assistant again.
The reason you are running the clean rule switch is because someone might be setup as a delegate on that computer so if they are that's whats keeping the Out of Office assistant from working. Let me know if this works.
Rod ,
I tried the /cleanrules process but still get the same message. I created a new rule then used the /cleanrules command. The rule was gone but still get the OOA error when trying to use it.
Keith
- At my site we are having similar errors. We also just updated from Exchange 2003 to Exchange 2007. Only a handful of users are working in Outlook 2007 so far, 95% are still on Outlook 2003 and thus far all our problems with Out of Office assistant have been on machines with the Outlook 2003 client. However, we are not getting errors when turning on, we are getting two messages sent. One will be the last message that the Outlook client sent prior to the migration and the other will be the newly configured out of office message. We also have been unable to fix the issue without using OWA. We have not attempted any outlook profile removal/recreation yet. Nor have we used any of the Outlook startup switches, but clean rules seems like a likely choice. However, I KNOW none of our problem users have had delegates yet. If anyone comes up with solid documentation on the migration to Exchange 2k7 and OOF problems it would be nice to have here. I suspect it is something in the Outlook cache on the local client - not in the profile. I make this comment b/c OOF assistant in Outlook remembers your last message. Does anyone know if this is contained in the outlook.nk2 file in ...documents and settings\user profile\application data\microsoft\outlook (XP) or ...Users\user profile\AppData\Roaming\Microsoft\Outlook (Vista)? This is the file that stores frequently used email addresses in cache for the user to select from the pop-up menu in Outlook. Just a thought. Or is it as a co-worker suggests something in the mailbox itself in Exchange. I will try to test it and see.
I have the same problem Only Outlook 2007 users cannot open OOF.
I to onl;y have a hand full of users on outlook 2007
and 90% on 2003
and 5% on 2002.
and only outlook 2007 users can not access OOF thru outlook.
I managed to fix my OOF by updating exchange 2007 Autodiscover settings.
I had it pointing to the "default web site" which on my environments is incorrect.
http://technet.microsoft.com/en-us/library/aa996324.aspx
Outlook 2007 must be able to locate the autodiscover service on Exchange 2007 server in order to have OOF and some other calendaring stuff work correctly.
Hi,
As a few have stated you need to get the autodiscovery service to function properly.
The best to try this is to hold down the ctrl key and click the Outlook icon in the activity bar (bottom right) and select "Test Email AutoConfiguration..."
In the log pane you should see some hints on why it doesn't work. Could be as simple as a missing DNS entry in the local DNS.
What I have seen is when antivirus software scans the inetsrv folder (%Systemroot%\system32) the metbase can easily be corrupted and you need to recreate the autodiscovery virtual site (after disabling scanning that is).
Syntax (you need to specify details) for doing this is:
Remove-AutodiscoverVirtualDirectory
New-AutodiscoverVirtualDirectory
Hope it helps!
- Previous poster mentioned problem with duplicate OOF messages being sent out when set via Outlook 2003 on an Exchange 2007 environment. We are having the exact same problem, with the only resolution being these users must set their OOF via OWA. This has become extremely frustrating, especially since that means an assistant needs a user's password to set via OWA as opposed to using Outlook 2003 w/ full mailbox rights and setting OOF.
I of course tried the auto-discover reinstall (Actually by removing the CAS and then adding) and verified Autodiscovery is working with the Test-OutlookWebServices powershell, but still the same OOF problems. It really looks like the internal/external OOF features for 2007 are the culprit and I have no way to fix at this point.
I see this problem from others on various other forums, but have yet to find a resolution. If anyone has any advice that would be great! I just got off the phone with Microsoft having the same problem with Outlook 2007 Out of Office assitant. I too was having the message "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later."
Here is the resolution that fixed the problem for me:
1. Test E-mail Autoconfiguration shows the OOF URL but could not access the OOF URL from IE.
2. Removed the anonymous authentication and configure integrated and basic authentication for EWS directory in IIS on Exchange 2007 server.
3. Stopped and started IIS.
- Proposed As Answer byTom Andrews Friday, March 20, 2009 10:47 AM
When outlook 2007 wants to set OOF, it communicates with 'Exchange Web Servises' (EWS) virtual firectory in IIS. Outlook 2007 does not know path to EWS virtual directory in IIS so i queries the autodiscover service on Exchange 2007 server.
Therefore the autodiscovery service must be correctly configured when using Outlook 2007.
Outlook 2007 "finds" autodiscover service either by query AD or DNS.
- Proposed As Answer byTom Andrews Friday, March 20, 2009 10:46 AM
- i have started having this problem with two of my users. we have a fresh 2007 ex std deployment. most users are using Outlook 2003 (including the two in question)
first the problem was two DIFFERENT OOF emails that were being sent: the current one and one that was stuck from the past (basically a previous message that somehow got stuck in the system)
following this post
http://hellomate.typepad.com/exchange/2003/10/when_oof_doesnt.html
i was able to get the users to at least sent the correct OOF email out even though it is still sent out twice.
if anybody can shed some light on how to fix this i would appreciate it.
the tool gives you a TON of info as well as functions, but a lot of it is very cryptic.
ps: ALSO look up MFCMAPI. seems like it is a similat tool but maybe a bit better
In my limited testing, it appears Exchange 2007 OOF has 2 different configurable messages. Internal (within ones organization) and external (outside the organization). Using an older client (outlook 2003 or older) the Outlook cannot display the necessary wizard to allow you to modify both messages so as such when you create an OOF in Outlook (older than 2007) the server then gets confused and takes a previous OOF message as one and the currently configured OOF message as another and before you know it, users are getting 2 OOF messages of different times.
At this point in my organization we have told users to set OOF via OWA.Thanks Lasse, your guidance works 100%. Using the "Test Email AutoConfiguration" - I found outlook was trying to connect externaly (via our Internet Proxy). We fixed it by modifying IE settings, which can be done manually or as in our case by modifying Group Policy to bypass the proxy server for our Exchange Server. We also added a DNS Alias record (CNAME) to autodiscover.domain.com ("domain.com" being a placeholder for our own domain ofcourse) which points to our Exchange 2k7 Server just for good measure. Thanks a mil!
HI,
i had about 10 users with OOF stuck on after migrating to ex07 from 2003 - - THIS IS THE FIX FOR OUT OF OFFICE STUCK ON.
MS added a legacy layer in to which older OOF would be migrated and if you accessed through outlook 2k3 or below it would be used
if you had previously had an OOreply set - but had since deleted it - it recorded null string which the upgrade script to 2k7 replaced with null - which is pants its an exchange bug ! (They should have a catch on that exception and replace it)
so anyway
use wireshark to see how the browser set it when logged in to owa
and replicate it in a script for any user so it no longer becomes null = no error remember give yourself permission over the faulty mailbox and run the script job done!! 4 days of hunting around fixed in 10 mins
- Can you explain further how you determined what values the Autodiscover settings had and how you set them appropriately. I am trying to figure out the syntax of the commands.
Please can you help me.
OOF only works for us using webmail. For users still using Outlook 2003 it works perfect without no problem but this is an issue for Outlook 2007.
We are using exchange 2007
My exchange server name is grkms1
domain name is gorkana
I have tried using this two command in exchange shell to delete and creating new autodiscover but it does not work at all.
Remove-AutoDiscoverVirtualDirectory -Identity "grkms1\Autodiscover(Default Web Site)"
N
ew-AutoDis coverVirtualDirectory -websitename "Default Web Site" -WindowsAuthentication $true -Dige
stAuthentication $truePlease help what wrong with the cmd am using.
Please can you help me.
OOF only works for us using webmail. For users still using Outlook 2003 it works perfect without no problem but this is an issue for Outlook 2007.
We are using exchange 2007
My exchange server name is grkms1
domain name is gorkana
I have tried using this two command in exchange shell to delete and creating new autodiscover but it does not work at all.
Remove-AutoDiscoverVirtualDirectory -Identity "grkms1\Autodiscover(Default Web Site)"
N
ew-AutoDis coverVirtualDirectory -websitename "Default Web Site" -WindowsAuthentication $true -Dige
stAuthentication $truePlease help what wrong with the cmd am using.
- In my situation, the Autoconfiguration settings are correct and so are all other settings mentioned in this post. I do not believe this is an Outlook Anywhere issue either. The issue is caused by opening outlook while logged on to your computer as a different user than your email account, even though you enter the correct e-mail account information while Outlook is loading. It seems as though OOF is not using the logon information that you enter into Outlook.
If you right-click on Outlook, select Run As..., then enter your email account information, OOF works, because Outlook is running under the correct user account.
I have this issue because our Exchange 2007 environment is installed as a separate resource domain, which means our users never open Outlook using their e-mail account, even though they enter their e-mail account information when prompted by Outlook.
I would say you have this issue when connected via Outlook anywhere because of the same reason. I would bet OOF only works seamlessly if your user domain and Exchange domain were one in the same. In our environment the issue was because we use a proxy server, and had a typo in our local server exceptions list. As soon as we added our domain - LEG* in the list this problem went away. Funny how it didn't affect our Outlook 2003 clients.
Hopefully someone will find this useful.
For me worked well restart of IIS at the Exchange server.
Try deleting and recreating the profile using Autodiscover that fixed it for me!!
This is what has worked for us
You receive an error message when you try to start the Out of Office Assistant in Outlook 2003
Article ID : 823472 Last Review : July 27, 2006 Revision : 2.5 For a Microsoft Outlook 2002 version of this article, see 327353 (http://support.microsoft.com/kb/327353/).SYMPTOMS
When you click Out of Office Assistant on the Tools menu in Microsoft Outlook, you may receive the following error message:The command is not available. See the program documentation about how to use this extension.CAUSE
This behavior may occur if the following key is present in the registry:HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\ResiliencyRESOLUTION
To resolve this problem, quit Outlook, rename the Resiliency registry key, and then restart Outlook. To do this, follow these steps. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows1. Quit Outlook if it is running. 2. Press CTRL+ALT+DELETE, and then click Task Manager. 3. On the Processes tab, verify that Outlook.exe does not appear in the list of processes. If it does, click Outlook.exe and then click End Process. 4. On the File menu, click Exit Task Manager. 5. Click Start, and then click Run. 6. In the Open box, type regedit and then click OK. 7. Locate and then click the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook8. Right-click the Resiliency subkey (if it exists), and then click Rename. 9. Type Resiliency.old, and then press ENTER. 10. Quit Registry Editor. 11. Start Outlook, and then click Out of Office Assistant on the Tools menu. We have the same exact problem. exchange 2007 allow outlook 2003 to use out-of-office assistance but not outlook 2007 any it is working when uinsg OWA but I would love to find out why outlook 2007 still not working.
Please email me to let me if there is any solution in the future for this issue.
I am sure Microsoft will find a solution it is just a matter of time.
Greetings,
I have been investigating this issue for a customer today, I know this is an old post but i'm sure others will find their way here too. I stumbled over HenrikR's post (http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2885438&SiteID=17) and that gave me an answer to our issue.
I figured I would link it here, since this post is regarding migrations. In shot, the issue was that the primary smtp domain for the users who had the issue wasn't the same at the autodiscover domain.
Take care!
/\/\artin
- Eric Draven_ said:Eric Draven is flat-out wrong. You *can* login to Windows as user X, open Outlook as user Y, and configure the OOF. In my case, I needed to create a DNS A record for autodiscover.<myFQDN>.
You MUST be the owner of the mailbox to open the OOF assistant so that means that you must be logged using the user's domain account.
Creating just the profile on a machine that has no joined your domain or using a domain account that is not the owner of the mailbox will not work.
- Actually..... Eric is correct... if you are talking about a person logging into a child domain... opening outlook.. and connecting to a mailbox attached to a resource or other domain account..
if you do a "RUNAS" to start outlook and use the mailbox owner account yes.. OOF will work... otherwise it will not...
see this :
http://support.microsoft.com/kb/954574
I have reproduced this exact issue....
Alternatively you could also grant the child domain account full access .. this would allow OOF to function correctly...
Steve- Proposed As Answer byCorbett Enders Monday, April 27, 2009 7:38 PM
- WayCoolKennel, you rock. So obviously this is an Outlook 2007 bug...
When you try to set an Out-of-Office (OOF) reply in Outlook 2007, you may receive the following error message:This problem occurs when the user account that you use to log on to the computer differs from the user account that you use to log on to Outlook 2007.Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later.
Thank you for posting that support article. - Hey..
I have this problem on one of my users.. we are using 2003 but the servers have all been upgraded to 2007.
The above resolution seems to work.. The only problem is that it will not work with the Runas function in regedt32.. It will then create the current user to be the admin that im using runas with.
i`ve also tried the network connect in regedit.. and that cannot connect to the current user settings either.
Is there any way to find the information of the user logged in on regestry ? Even if i use runas?
i cannot change the policies for this for only one user.. we have over 2000 users on the same system.
EDIT: Its all fixed now. it was a profile problem that created a regestry error.. (how odd is that) Anyways.. The poblem is now solved. - For me this was a client issue and I just deleted all my mail profiles and then started Outlook. If I've understood this right the autoconf will configure it right if you do it like this. Atleast it worked for me.
- Here is what worked for me:
The problem everyone is describing ultimately leads to outlook not knowing how to get to the autodiscover settings of Exchange 2007.
I noticed that our home user's (who is not on our domain) outlook was trying to go to "autodiscover.{domain}.com". This was trying to
resolve to our web server since "*.{domain}.com" is usually setup on DNS servers as a catch-all for websites.
I added an alias in our DNS server "autodiscover.{domain}.com" and pointed it to the EMail server specifically.
I then flushed the user's DNS and tested with a ping to verify it was resolving to the email server first.
Started up outlook and Out Of Office worked perfectly! It did prompt her for her login/password upon first
starting outlook since she is not a domain user, but after supplying the credentials, she was working without a hitch!
The above is much easier than most other steps I've seen in other links and resolves the ultimate issue that outlook is trying to find
"autodiscover.{domain}.com" and can't.
~ Raestlin Hi. Solution that worked for me:
Create another mail profile.
Delete the old one.
Use the new one.
http://support.microsoft.com/kb/312354
Best regards,
Valery Vainkop.- Proposed As Answer byVainkop Valery Tuesday, September 01, 2009 12:49 PM
- I beat my head on this for a while...first it was the unified communications certificate, then auto discovery, then ews directory and now DNS. <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman","serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; color:black;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->
My final solution was DNS related.
I had to point the outside address of the exchange 2007 box that the Outlook 2007 Auto discovery was looking for back to the inside address so that OOF would work.
We use a proxy for IE so I took my proxy off which I knew would not let me outside to the Internet. Of course Outlook balked when I attempted the OOF again. Then, I modified the local hosts file and pointed the outside name to the inside ip address. Worked like a charm. Then, I knew I had to modify the DNS.
this link helped me get a grip on it.
http://technet.microsoft.com/en-us/library/bb124251.aspx
Good Luck,
D
- Proposed As Answer byHappy_New_Year Monday, November 30, 2009 2:14 PM
Some how our users were not running correct policy, so we preformed a gpupdate /force from a command prompt which realign the user's system w/ current Policy. This corrected the issue. Remember to reboot after the gpupdate.
- I had the same problem all clients got this error 'Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later.
I just installed NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET versions 2.0 through 3.5 (KB951847) x64
rebooted the server wolla! it works
/Soeren I had the same problem all clients got this error 'Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later.
I just installed NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET versions 2.0 through 3.5 (KB951847) x64
rebooted the server wolla! it works
/Soeren
Dude, you're a genius! :D- I cannot resolve this "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later."
I moved mailboxes to 2007 this weekend. I have a single AD domain. I have a single Exchange server.
I did everything in 940726. (As I had certificate errors.)
I have checked my web.config file and it shows the explicit path to the Exchange install dir.
I ran the Test Auto Configuration from my Outlook client and it returned the correct Autodiscover URL and it claimed all connections successful.
I edited authentication in IIS EWS and Autodiscovery directories so that Anonymous is Disabled.
I have manually edited my host file and pointed the public autodiscover address to my CAS internal IP. Still no go.
I have installed .Net 3.5 SP1 and the update for 3.5 SP1.
I have deleted my outlook profile completely and then had my new profile auto-configured.
I have rebooted both the server and my computer.
I have no idea what else to try. I think its stupid that this feature is supposed to make life 'easier' yet somehow ive spent a day and a half on it.
M - Thanks Tom, this worked for us.
- I resolved this issue by doing the folowing:
In the Exchange power shell I ran this command:
get-WebservicesVirtualDirectory |fl server,name,internalurl,externalurl
and I saw that the "ExternalUrl : " value was blank
I then used this command to set that value. For me it should have been https://mail.mypublicdomain.com/EWS /Exchange.asmx
The command was:
Set-WebServicesVirtualDirectory -identity "EX-SRV1\EWS (Default Web Site)" -externalurl https://mail.mypublicdomain.com/EWS/Exchange.asmx
note that EX-SRV1 is the local name of my exchange server so you will need to change that to match yours
Thanks to everyone who helped get me on track with this one...
*note I edited this to include a " that was missing in the Set-WebServicesVirtualDirectory command the first time I posted.
- I Had a lot of the issues people are talking about, OOF not working internally but working externally, internal autodiscover authentication prompts that I had to click cancel so I could work etc. - Initially everythng worked great, until I decommissioned my 2003 environment, then I started getting all the described problems. After trolling many web sites and trying everything under the sun i.e registry fixes to clear ipv6, I finally got it solved.
I started off by removing everything and starting over, ok not everything just the autodiscover virtual directory, the web services virtual directory and disabling outlook anywhere
so, Remove-WebServicesVirtualDirectory -Identity "CAS01\EWS (Default Web Site)"
Remove-AutoDiscoverVirtualDirectory -Identity "CAS01\Autodiscover (Default Web Site)"
Disable-OutlookAnywhere
If you have multiple CAS servers I suggest disabling doing them one at a time and not disabling the second until you get the first enabled.
Also when I got this going initially I was using the external name internally for certificate reasons because we used .int in our domain and we couldn't put that on a SAN certificate - so on our SAN certificate we have the internal bios name without the domain and the fully qualified external names as so
autodiscover.domain.com
mail.domain.com
cas01
cas02
Note: In my environment - mail.domain.com NATs to my Ironport box which serves as my edge server and autodiscover.domain.com NATs to my NLB CAS servers
So to rebuild I used
New-WebServicesVirtualDirectory - just like that makes it easy, adds default stuff - customize in next command
New-AutoDiscoverVirtualDirectory
Then customize for your environment - just remember to put them exactly the way you have in the certificate - and if your using https which is the default make sure you go into IIS manager on your CAS and make sure SSL is checked- it wasn't for EWS for me
To customize I used
Set-WebServicesVirtualDirectory -Identity “CAS01\EWS (Default Web Site)” -ExternalURL https://autodiscover.domain.com/EWS/Exchange.asmx -WindowsAuthentication:$true
Set-WebServicesVirtualDirectory -Identity “CAS01\EWS (Default Web Site)” -InternalURL https://CAS01/EWS/Exchange.asmx -WindowsAuthentication:$true
Set-AutodiscoverVirtualDirectory -Identity 'autodiscover (default Web site)' -InternalUrl 'https://CAS01/autodiscover/autodiscover.xml'
Set-AutodiscoverVirtualDirectory -Identity 'autodiscover (default Web site)' -WindowsAuthentication $True -BasicAuthentication $False -DigestAuthentication $False
Set-AutodiscoverVirtualDirectory -Identity 'autodiscover (default Web site)' -ExternalUrl 'https://autodiscover.domain.com/autodiscover/autodiscover.xml'
If above internal command doesn't work this will I forget I think I used both
Set-ClientAccessServer -Identity CAS01 -AutoDiscoverServiceInternalUri https://CAS01/Autodiscover/Autodiscover.xml
Then I enabled outlook anywhere again
Enable-OutlookAnywhere -Server:CAS01 -ExternalHostname:autodiscover.domain.com -ClientAuthenticationMethod:NTLM -SSLOffloading:$false
And the annoying errors went away- Proposed As Answer byP-H-A-R-O Thursday, January 14, 2010 5:43 PM
- Hey guys, you might wanna give this site a good look...
http://www.pro-exchange.eu/modules.php?$1&name=News&file=article&sid=686 - Hey Guys,
I hope this helps.
Please bear in mind that any work I do to my Exchange environment has to be approved by a person who has no Exchange experience... I have MCITP Exchange Administrator... wonder why they hired me?
I recently upgraded from Ex2007 to Ex2010 changing our Exchange 07 CAS server to legacymail.ourcompany.com and moving mail.ourcompany.com to the Exchange 2010 CAS server was not approved, I did tell them that their would be problems. both servers internally are using mail.ourcompany.com "Not good I know" I have to wait for approval hopefully in the next few days.
One of the users (Office 2007) was on leave and had the auto reply set when their mailbox was moved.
I showed the user how to turn off the auto reply in OWA to allow more time to work out the problem.
I ran the Test Email Autoconfiguration in Outlook and noticed that the test was bouncing from the old server to the new server.
I modified the users hosts file with mail.ourcompany.com with the new servers IP address.
Told the user to log out and then log back in again and report the results.
The user reported back the they can now manage the out of office assistant from Outlook again.
Autodiscover uses DNS, if their is something wrong with the DNS the autodiscover will not function correctly always verifiy that you can reslove your server names. - Slightly different fix for me.....i dont have the external url setting enabled but as a quick fix i added in an exception to ie on group policy - i added in the internal server "https://INTserver.domain.com" and also the external "https://EXTserver.domain.com" as we also run through a proxy, now it works. this was also affecting the calender access as well.
