Unable to see busy/free in outlook 2010 but works on 2003

I recently migrated few email account from exchange 2003 to 2010, but they are unable to see any calendar schedule for users that resides in 2010 or 2003 Exchange servers from Outlook 2010.  If a users switch to Outlook 2003 they are fine.
FundFireAsked:
Who is Participating?
 
.Commented:
0
 
ctc1900Commented:
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
FundFireAuthor Commented:
in AD site and services I check the autodiscover and I have my server listed there.  From the documentation I am not sure what else I need to do.  I do have PF created and I also assigned the PF to the Mailbox data base.  I am baffled.
0
 
.Commented:
Did you create a replica of the schedule+free busy folder?

0
 
FundFireAuthor Commented:
I actually did.  In Exchange 2003 Management console I went to system folder.  SCHEDULE + FREE BUSY folder and I added  the 2010 public folder to the Exchange Administrate Group.  That did not a a thing for me.  

One more thing; I run Test E--mail AutoConfiguration from my desktop and it fails.  In the Log I see some stuff about Autodiscover for https, so I do know this is a valid test.  Anyway I thought I should mention it.
0
 
.Commented:
on your Exchange 2010 Box open EMC, then drill down to Organization Config / Mailbox then under Database management select the DB where your mailbox is located and go to its properties. Select the Client Settings tab and click Browse against Default Public Folder Database and select the Public Folder Database on your Exchange 2010 box.
0
 
FundFireAuthor Commented:
Done that already.
0
 
FundFireAuthor Commented:
I looked over the document.  You see I have a different situation.  If I use 2003 I CAN access the free/busy.  If I use 2010 then I can not.  Does not matter what exchange server I am on (although I am on Exchange 2010)
0
 
.Commented:
Sorry, at this stage I would start googling this which I am sure you have done yourself. I will keep monitoring the question.
0
 
FundFireAuthor Commented:
OK.

Thanks.  It is for sure Autodiscover issue.  When I try to Autodiscover my exchange server, it does not work.  I have installed my certificate from my exchange 2003 on 2010 server.  Just in case you are interested, he is log:

[PS] C:\>$cred=Get-Credential money-media\ktest
[PS] C:\>Test-OutlookConnectivity -Protocol:http -Identity ktest -MailboxCredential $cred -verbose
VERBOSE: [18:07:38.327 GMT] Test-OutlookConnectivity : Active Directory session settings for 'Test-OutlookConnectivity'
 are: View Entire Forest: 'False', Default Scope: 'money-media.com', Configuration Domain Controller:
'prdc1.money-media.com', Preferred Global Catalog: 'DRDC1.money-media.com', Preferred Domain Controllers: '{
DRDC1.money-media.com }'
VERBOSE: [18:07:38.327 GMT] Test-OutlookConnectivity : Runspace context: Executing user:
money-media.com/Users/Administrator, Executing user organization: , Current organization: , RBAC-enabled: Enabled.
VERBOSE: [18:07:38.327 GMT] Test-OutlookConnectivity : Beginning processing &
VERBOSE: [18:07:38.327 GMT] Test-OutlookConnectivity : Instantiating handler with index 0 for cmdlet extension agent
"Admin Audit Log Agent".
VERBOSE: [18:07:38.327 GMT] Test-OutlookConnectivity : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
Scope(s): {}, Exclusive Configuration Scope(s): {} }
VERBOSE: [18:07:38.374 GMT] Test-OutlookConnectivity : Resolved server.  Server Name = 'EX02', Server FQDN=
'ex02.money-media.com'
VERBOSE: Target Mailbox = 'ktest'
VERBOSE: [18:07:38.374 GMT] Test-OutlookConnectivity : Resolved current organization: .
VERBOSE: [18:07:38.390 GMT] Test-OutlookConnectivity : Mailbox = 'ktest', Owner = '/o=Money Media/ou=First
Administrative Group/cn=Recipients/cn=ktest'
VERBOSE: [18:07:38.390 GMT] Test-OutlookConnectivity : SMTP address for Autodiscover request = 'ktest@money-media.com'
VERBOSE: [18:07:38.421 GMT] Test-OutlookConnectivity : When contacting
https://ex02.money-media.com/Autodiscover/Autodiscover.xml received the error The underlying connection was closed: An
unexpected error occurred on a send.
VERBOSE: [18:07:38.421 GMT] Test-OutlookConnectivity : When contacting
https://ex02.money-media.com/Autodiscover/Autodiscover.xml received the error Unable to read data from the transport
connection: An existing connection was forcibly closed by the remote host.
VERBOSE: [18:07:38.421 GMT] Test-OutlookConnectivity : When contacting
https://ex02.money-media.com/Autodiscover/Autodiscover.xml received the error An existing connection was forcibly
closed by the remote host
VERBOSE: [18:07:38.421 GMT] Test-OutlookConnectivity : <?xml version="1.0"?>
<Autodiscover xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:nil="true" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006" />

ClientAccessServer   ServiceEndpoint                               Scenario                            Result  Latency
                                                                                                                  (MS)
------------------   ---------------                               --------                            ------  -------
ex02.money-media.com                                               Autodiscover: Web service request.  Failure   -1.00
VERBOSE: [18:07:38.421 GMT] Test-OutlookConnectivity : Admin Audit Log: Entered Handler:OnComplete.
The cmdlet fails to find all the server information through pinging service providers or other topology discovery insid
e the domain. The cmdlet cannot continue. TopologyDiscoverMode = 'UseAutodiscover, UseAddressbook'.
    + CategoryInfo          : OperationStopped: (Microsoft.Excha...onnectivityTask:TestOutlookConnectivityTask) [Test-
   OutlookConnectivity], TopologyDiscoverException
    + FullyQualifiedErrorId : 228BA80D,Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask

VERBOSE: [18:07:38.437 GMT] Test-OutlookConnectivity : Ending processing &

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.