[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 627
  • Last Modified:

Exchange 2010 free/busy and entourage and outlook

Running exchange 2010 with half my users on Entourage WSE and the other half on a mix of outlook 2003/2007.

Some of the outlook users are unable to see the free/busy information for ANY entourage user. Some of the outlook users are able to see the free/busy information for ALL of the entourage users.

I suspected it was a problem with outlook 2003 and I started moving those folks over to outlook 2007 only to find the problem still persists. However, they are able to see free/busy from the OWA.

If I have one of the users who cannot see the free/busy info log into the machine of one of the users who can, then all of a sudden they can see the information.

So, anyone have any ideas?
0
MrBlister
Asked:
MrBlister
  • 10
  • 6
1 Solution
 
sunnyc7Commented:
did you try starting outlook 2003 with

outlook /cleanfreebusy ?
0
 
MrBlisterAuthor Commented:
I did. That didnt seem to work.
0
 
sunnyc7Commented:
Can you try it on other workstations - lets see if that works on *all outlook 2003* or some of them ?

thanks
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
MrBlisterAuthor Commented:
I said the /cleanfreebusy did not work. Either on outlook 2003 or outlook 2007
0
 
sunnyc7Commented:
oops. my bad.

on exch shell

get-webservicesvirtualdirectory | fl

Please output the results here.

Are you running a CAS array / or just one Exchange 2010 server ?

thanks
0
 
MrBlisterAuthor Commented:



RunspaceId                    : aa33d681-40bb-4f0b-820d-ec5cba5a6644
CertificateAuthentication     :
InternalNLBBypassUrl          : https://mail2.site.net/ews/exchange.asmx
GzipLevel                     : High
Name                          : EWS (Default Web Site)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication    : False
WSSecurityAuthentication      : True
LiveIdBasicAuthentication     : False
BasicAuthentication           : False
DigestAuthentication          : False
WindowsAuthentication         : True
MetabasePath                  : IIS://mail2.site.net/W3SVC/1/ROOT/EWS
Path                          : E:\Exchange\ClientAccess\exchweb\EWS
Server                        : MAIL2
InternalUrl                   : https://mail2.site.net/EWS/Exchange.asmx
ExternalUrl                   : https://mail.site.net/ews/exchange.asmx
AdminDisplayName              :
ExchangeVersion               : 0.10 (14.0.100.0)
DistinguishedName             : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=MAIL2,CN=Servers,CN=Exchange Adm
                                inistrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=SITE,CN=Microsoft E
                                xchange,CN=Services,CN=Configuration,DC=site,DC=net
Identity                      : MAIL2\EWS (Default Web Site)
Guid                          : e4a09b1f-c94a-46c9-85bb-8063b79be7c9
ObjectCategory                : site.net/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass                   : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged                   : 12/5/2009 11:46:31 AM
WhenCreated                   : 12/4/2009 4:43:56 PM
WhenChangedUTC                : 12/5/2009 7:46:31 PM
WhenCreatedUTC                : 12/5/2009 12:43:56 AM
OrganizationId                :
OriginatingServer             : PDC1.site.net
IsValid                       : True



[PS] C:\Windows\system32>
0
 
MrBlisterAuthor Commented:
Just a single 2010 server
0
 
sunnyc7Commented:
Whats the FQDN of your internal server ?
pdc1.site.net ?


InternalUrl                   : https://mail2.site.net/EWS/Exchange.asmx
ExternalUrl                   : https://mail.site.net/ews/exchange.asmx

Internal URL should point to internal FQDN of your mail server
External URL should point to external FQDN (Lowest prio MX record)
0
 
MrBlisterAuthor Commented:
They do. I changed the server names to something generic.

internalurl is mailserver2.internalDS.domain.net

external is mail.domain.net

0
 
MrBlisterAuthor Commented:
pdc1.site.net is the fqdn for our primary domain controller.
0
 
sunnyc7Commented:
a) So this is correct (after obfuscation)
InternalUrl                   : https://mail2.site.net/EWS/Exchange.asmx

where mail2.site.net is the internal FQDN of exchange server - mailserver2.internalDS.domain.net
do you have an A-record in DNS for mailserver2.internalDS.domain.net - pointing to Exchange Server LAN IP
Just checking

b) Do you have a UCC/SAN Certificate installed with the following domain names

mail.domain.com (external FQDN)
autodiscover.domain.com (external autodiscover in external DNS)
mailserver2.internalDS.domain.net (internal FQDN of mail server)
mailserver2 (Exchange server name)

Thanks
0
 
MrBlisterAuthor Commented:
I have all of this.

I have to believe it's something on the end users machine, it's the only thing that makes sense at this point.
0
 
sunnyc7Commented:
If all those settings are correct and free/busy is working for some, it might be a client side issue.

I will post back if I come up with something.

0
 
MrBlisterAuthor Commented:
Free/busy is working for some and if I have a user who does not have it working log into the machine of a person who does have it working then it works on that machine.

It also always works in OWA.
0
 
MrBlisterAuthor Commented:
Turns out I have to delete the mail account setting on the users local machine and recreate in order for the free/busy to reappear.
0
 
MrBlisterAuthor Commented:
Was a client side issue.
0

Featured Post

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.

  • 10
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now