Hi Folks, Environement: Exchange 07 SP3 update2(just updated) Server 08 R2 Outlook 07 Clients (setup initially using the autodiscover service) I have an issue where users cannot see free/busy info nor use OOF feature, this was working fine before. Free/busy will in fact show up under OWA. running test-outlookwebservices cmdlet came back fine telling me autodiscover was tested successfully running outlook using the /cleanfreebusy did not work creating a new outlook profile did not work I enabled logging in Outlook, tested the free/busy and checked the olkdisc.log for outlook and all it says is resource manager terminated any other advice, and thanks in advance

From a user’s computer: ctrl+right-click the outlook icon on the system tray. Then choose test email autoconfiguration. Hit test. Verify the urls returned for these services are accessible from the cleint’s pc. Mike Crowley Check out My Blog!

yes everything comes back accessible

Does this occur for existing mailboxes only, or new as well? Can you try with a new Outlook profile to rule this out? Mike Crowley Check out My Blog!

This occurs for existing accounts, re-creating the users' profile does not help either. When i create a new user and setup a mailbox it keeps prompting for credentials ? One thing to note as well: When i created the new profile it used autodiscover to correctly identify the user and configure the new mail account..

When i create a new user and setup a mailbox it keeps prompting for credentials ? Perhaps this is the key. Did you change your Virtual Directory authentication settings? forget about the new mailbox for a moment. on an affected workstation, open IE and browse to https://server.domain.local/EWS/Exchange.asmx are you able to login? you should see an XML file like this: <?xml version="1.0" encoding="utf-8" ?> - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:s="http://www.w3.org/2001/XMLSchema" targetNamespace="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"> - <wsdl:types> - <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:import namespace="http://schemas.microsoft.com/exchange/services/2006/messages" schemaLocation="messages.xsd" /> </xs:schema> </wsdl:types> - <wsdl:message name="UploadItemsSoapIn"> <wsdl:part name="request" element="tns:UploadItems" /> blah blah blah Mike Crowley Check out My Blog!

Please also paste the results of: Get-WebServicesVirtualDirectory | fl id*, *auth* Mike Crowley Check out My Blog!

Yes I can login and see the xml data I havent changed anything with authentication unless updates would have done something Identity : ExchangeSVR\EWS (Default Web Site) InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated} ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated} BasicAuthentication : True DigestAuthentication : False WindowsAuthentication : True� n��Microsoft.Windows.MMC--------------------------------------�-- thanks Mike for troubleshooting with me

Ok, traced the issue back to DNS. Our dns guy changed owa and autodiscover entries to cname's instead of leaving them as A records. this causes issues with ssl and autodiscover, etc. so reverted back to a records flushed cache's and all ok

Hi, Thanks for your sharing. AllenAllen Song