Solved

Exchange Upgrade - External users cannot see others' calendars

Posted on 2013-11-11
6
200 Views
Last Modified: 2014-06-24
We are in the middle of an Exchange Upgrade Project, moving from Exchange 2003 to Exchange 2010.  We have about two dozen users moved to the Exchange 2010 Server.

One user has reported a problem that appears to occur under specific circumstances.  Let me see if I can organize the pertinent details:

{specific details have been changed to protect the... well, you know what I mean...}
URL:  https://mail.contoso.com
Email Domain Addresses:  @contoso.com
AutoDiscover URL:  https://mail.contoso.com/Autodiscover

For users on computers that are IN THE DOMAIN, everything works, including viewing calendars for users on both the 2003 and 2010 Exchange Servers, OOO, etc.

We currently have this one user who uses Outlook on a computer in a different domain, but accesses his email in OUR Domain.  He can get email without a problem, and he can get his calendar without a problem, but FROM HIS MACHINE, he cannot see anyone else's calendar availability when he tries to schedule a meeting.  

From his computer, if he logs onto OWA, he can see his calendar and he can see users availability when he tries to schedule a meeting, but ONLY for users already on the Exchange 2010 server.  He cannot see ANY Exchange 2003 users calendars.  If he logs onto or uses a computer that IS in the Domain, OWA works without an issue, including Exchange 2003 users.

This appears to have something to do with the fact that his system is not in our Domain.  Part of the issue may relate to the fact that our email addresses are in the form of user1@contoso.com, while our publicly accessible URL's are in the form of https://mail.contoso.com.  I'm uncertain how to proceed or evaluate this, but it'll need to be resolved before I move too many users.  People are going to end up trying to use OWA from Personal computers or other devices, so we need to make sure people using equipment outside the domain can do their work...

Thanks.

Atlas IT.
0
Comment
Question by:atlasdev
  • 4
  • 2
6 Comments
 
LVL 14

Expert Comment

by:Radweld
Comment Utility
I think most of this might be by design,

let me explain.

Free/Busy information on Exchange 2003 is accessed from public folders, Free/Busy information in Exchange 2010 is accessed directly from the mailbox using the availability service (aka autodiscover)

Domain joined Outlook clients can query a public folder and i assume you have configured public folder replication between Exchange 2003 and 201 but none domain joined outlook clients won't be able to query public folders and I seam to remember OWA cannot access public folders which explains why availability is only available for users who've been migrated.

So long term, once all your users are migrated to Exchange 2010 and as long as their using Outlook 2007 or later then there is no reliance on public folders any more. OWA would be able to query the availability of all Exchange users then.

Hope this helps.
0
 

Author Comment

by:atlasdev
Comment Utility
Just want to look to see if there's more options.  We have a number of other users that will be in the same scenario as this specific employee once they get migrated.  

We have a separate division with it's OWN domain, with no trust between our domains.  They access resources, though, in our Domain and have accounts in our Domain.  Basically, if what you say is true, Radweld, then they will not be able to use Outlook on their machines.

Atlas IT
0
 
LVL 14

Expert Comment

by:Radweld
Comment Utility
If you have some time, take a look at this blog as it will discuss the situation in detail,

http://www.msexchange.org/articles-tutorials/exchange-server-2010/migration-deployment/deep-dive-into-rich-coexistence-between-exchange-forests-part1.html

As previously stated your working with two different technologies for providing availability, mailboxes stored on Exchange 2003 uses a public folder and mailboxes stored on 2010 use the availability service. without checking I'm now not sure about my previous comment about non domain joined machines accessing public folders (it's been a while since I worked with Exchange 2003)

Thinking about this some more, did you configure a legacy redirect? this procedure involves pointing OWA, OA, EAS to Exchange 2010 and configuring a separate namespace which is associated with Exchange 2003, Exchange 2010 CAS is then able to proxy requests to Exchange 2003, worth checking this is set up correctly.

http://exchangeserverpro.com/exchange-2003-2010-coexistence/
0
Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

 

Author Comment

by:atlasdev
Comment Utility
Still looking into this...

Atlas IT
0
 

Accepted Solution

by:
atlasdev earned 0 total points
Comment Utility
Closing, as this is now a moot point.  We're fully migrated to Exchange 2010.
0
 

Author Closing Comment

by:atlasdev
Comment Utility
Not a solution -  just closing.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Sometimes Outlook might have problems sending a message. There may be various causes- corrupted PST, AV scanner etc. The message, instead of going to the Sent Items folder, sits in the Outbox indefinitely. To remove it you can use a free tool cal…
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video discusses moving either the default database or any database to a new volume.

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now