We are running Exchange 2007 sp2 and we have random user who cannot access their out of office assistant. They recieve the following error:Your Out of Office settings cannot be displayed , because the server is currently unavailable We have recreated their profiles, reset outlook with cmd switches. Had them log on to machines in which the out of office assistant worked for another customer - and still it would not work for them. Did a test mail auto configuration and recieved the following error:Autodiscover to https://servername/Autodiscover/Autodiscover.xml FAILEDAny ideals on how to fix this issue?ThanksEiram

Yes, fix Autodiscover!-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "Eiram Rulz" wrote in message news:0ccedc4f-82ba-4c3e-9226-468133114111...We are running Exchange 2007 sp2 and we have random user who cannot access their out of office assistant. They recieve the following error:Your Out of Office settings cannot be displayed , because the server is currently unavailable We have recreated their profiles, reset outlook with cmd switches. Had them log on to machines in which the out of office assistant worked for another customer - and still it would not work for them. Did a test mail auto configuration and recieved the following error:Autodiscover to https://servername/Autodiscover/Autodiscover.xml FAILEDAny ideals on how to fix this issue?ThanksEiram Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks. I know their is an issue with autodiscover - but what in particular only because it working for some and not others this seems to be a profile realated issue. I did the fix option according to the white papers.The autodiscover reconfiguration only seems to deal with the updating of the external url - but our issue seems to be the internal.Is there a cmd script that would correct this aspect in particular?

Domain members get their Autodiscover from the SPN in Active Directory. Check the settings for your CAS, particularly the AutoDiscoverServiceInternalUri property from Get-ClientAccessServer. http://technet.microsoft.com/en-us/library/bb125157(EXCHG.80).aspx -- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "Eiram Rulz" wrote in message news:1c383193-4eeb-408d-a5b9-72da57a405d3...Thanks. I know their is an issue with autodiscover - but what in particular only because it working for some and not others this seems to be a profile realated issue. I did the fix option according to the white papers.The autodiscover reconfiguration only seems to deal with the updating of the external url - but our issue seems to be the internal.Is there a cmd script that would correct this aspect in particular? Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Mr. Crowley,I am a co-worker of Eiram's and wanted to join this discussion. I/we checked the settings for our CAS server(s) (we have two) and they are both appear to be configured correctly. The AutoDiscoverServiceInternalURi is pointing to: https://FQDNofServer/Autodiscover/Autodiscover.xmlIs there anything else that you suggest that we check? Again, this is a problem that is only being experienced by a small percentage of our users. To add to what Eiram stated we have seen the following during testing:- Users exeriencing the problem can logon to another workstation and successfully access the OOF.- I/we are able to logon to a workstation where a user is experiencing the problem and bring up either their mailbox or our own and the OOF works fine. That being said it seems to be profile specific but only on that workstation yet our profiles are roaming - I don't get it???- We have attempted to create another Outlook profile for the user(s) experiencing the problem but that does not resolve the issue.Any additional help or guidance would be greatly appreciated. Domain members get their Autodiscover from the SPN in Active Directory. Check the settings for your CAS, particularly the AutoDiscoverServiceInternalUri property from Get-ClientAccessServer. http://technet.microsoft.com/en-us/library/bb125157(EXCHG.80).aspx -- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "Eiram Rulz" wrote in message news:1c383193-4eeb-408d-a5b9-72da57a405d3... Thanks. I know their is an issue with autodiscover - but what in particular only because it working for some and not others this seems to be a profile realated issue. I did the fix option according to the white papers.The autodiscover reconfiguration only seems to deal with the updating of the external url - but our issue seems to be the internal.Is there a cmd script that would correct this aspect in particular? Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

While I can't say for certain that we've discovered the actual cause for this problem we have found that the way we've been able to recover from it by resetting the roaming profile for users experiencing the problem. Attempts were made to delete specific files/folders within the profile however the only one that proved to resolve the issue was the NTUSER.dat.

Do none roaming users experiance the fault

Hi,The NTuser.dat file is the registry portion of the user profile. NTuser.dat is a cached copy of the Windows NT Registry HKEY_CURRENT_USER subtree on the local computer. The registry is a database repository for information about the computer's configuration, including the hardware, installed software, environment settings, and other information.There should have corrupt data under NTuser.dat which cannot make the Outlool client connect the Autodiscover.ThanksAllen

Hi Eiram,Have u got the answer or not?Thanks

were getting the same issue, we have as above related it to the users profiles, we have deleted the users roaming profiles on the local and server so they start with a completely freash profile but this still does not fix the problem. We are now going to try the NTUSER.dat will let you know -------------------------------------------------------- Update: we tried the NTUser and once we do anything with it the users roaming profile when logging in can not be found so unless you can give greater details of what you did with the User.dat we are no further nearer to solving this issue