Exchange online and Exchange 2010 on-premise calendar availability

I am running a hybrid exchange 2010 on-premise and online exchange environment. The online exchange users cannot see calendar availability of anybody on premise. The on-premise users can see the online exchange availability. I can see the
calendar if the calendar is shared, but trying to setup a meeting or calendar appointment still shows the unavailable through all days.
All of the users are using office 365 for outlook on premise and exchange online. If it is only working one way, could it be an autodiscover issue where it is not configured correctly on our on-premise exchange 2010 or online exchange? Which
side would be causing the issue?

I have done a little more research and ran the following in powershell:
[PS] C:\Windows\system32>Get-FederationInformation -domainname weiman.com
RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
TargetApplicationUri : outlook.com
DomainNames           : {Weiman.onmicrosoft.com, weiman.com, Weiman.mail.onmicrosoft.com}
TargetAutodiscoverEpr : https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc/WSSecurity
TokenIssuerUris       : {urn:federation:MicrosoftOnline}
IsValid               : True
[PS] C:\Windows\system32>Get-OrganizationRelationship | FL
RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
DomainNames           : {herbertstanley.com, weiman.com, Weiman.mail.onmicrosoft.com}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel   : LimitedDetails
FreeBusyAccessScope   :
MailboxMoveEnabled    : True
DeliveryReportEnabled : True
MailTipsAccessEnabled : True
MailTipsAccessLevel   : All
MailTipsAccessScope   :
TargetApplicationUri : outlook.com
TargetSharingEpr      :
TargetOwaURL          : http://outlook.com/owa/herbertstanley.com
TargetAutodiscoverEpr : https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact   :
Enabled               : True
ArchiveAccessEnabled : True
AdminDisplayName      :
ExchangeVersion       : 0.10 (14.0.100.0)
Name                  : On Premises to Exchange Online Organization Relationship
DistinguishedName     : CN=On Premises to Exchange Online Organization Relationship,CN=Federation,CN=WEIMAN,CN=Microsof
                        t Exchange,CN=Services,CN=Configuration,DC=herbertstanley,DC=com
Identity              : On Premises to Exchange Online Organization Relationship
Guid                  : 26b4ec5d-fe93-473e-b451-1f9aa2e94ebb
ObjectCategory        : herbertstanley.com/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass           : {top, msExchFedSharingRelationship}
WhenChanged           : 1/13/2014 1:25:54 PM
WhenCreated           : 12/17/2013 1:04:32 PM
WhenChangedUTC        : 1/13/2014 7:25:54 PM
WhenCreatedUTC        : 12/17/2013 7:04:32 PM
OrganizationId        :
OriginatingServer     : gemini.herbertstanley.com
IsValid               : True
I am not sure why we have that value for the OriginatingServer. That server is a backup domain controller, not the server that houses the on-premise exchange.
I then ran the set-OrganizationRelationship and get the below error.
[PS] C:\Windows\system32>Set-OrganizationRelationship -Identity weiman.mail.onmicrosoft.com -targetapplicationUri outloo
k.com -TargetAutodiscoverEpr https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
The operation couldn't be performed because object 'weiman.mail.onmicrosoft.com' couldn't be found on 'gemini.herbertst
anley.com'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Set-OrganizationRelationship], ManagementObjectNotFoundExceptio
   n
    + FullyQualifiedErrorId : F2215CB2,Microsoft.Exchange.Management.SystemConfigurationTasks.SetOrganizationRelations
   hip
How do I change the originating server to be my exchange server?

Similar Messages

Pre-requisites for e-Discovery from SharePoint Online to Exchange Online and On-prem

Hi,
I want to setup an O365 e-discovery site for SharePoint Online, Exchange Online and Exchange On-prem. My understanding is that to have e-Discovery from SPOnline to Exchange Online & Exchange On-prem, we need to setup Exchange hybrid with OAuth. Please correct
me if I am missing something. I have few questions regarding this setup -
1) Do we need to have Exchange 2013 On-premise for this setup? Or can it be done with Exchange 2010 too?
2) Is OAuth absolutely necessary for e-discovery to work between Exchange Online & On-prem? Or hybrid environment will work? Can OAuth be configured between Exchange 2010 On-prem and Exchange Online for e-discovery?
3) Any other pre-requisites?
Thanks.

Yes, you will need Exchange 2013 SP1 or later with OAuth configured to cross-premises eDiscovery searches in Exchange.
Additional information:
http://technet.microsoft.com/en-us/library/dn497703(v=exchg.150).aspx
Joseph Palarchio http://www.itworkedinthelab.com

How to set a thumbnail photo in Azure AD? Sync thumbnail photos between Exchange Online and Azure AD?

We're interested in downloading the thumbnail photo for users in an O365 tenant using the REST API, but we're stumped regarding how to set a thumbnail photo for a user in Azure AD. We haven't found a way to do it via the user interface and it doesn't
appear to sync between Exchange Online and Azure AD. The only sync reference we've been able to find is between Windows Server AD and Azure AD which is not applicable in our use case?
Any pointers on how to get the thumbnail photo set?

Greetings!
You may use the sample (Malar has shared above) which helps how to query Azure AD using the Graph API, demonstrates additional REST functionality to Get and Set User Details, including thumbnail photos.
Would like to add:
http://matthewyarlett.blogspot.co.uk/2013/08/add-or-update-user-profile-picture.html
You can use the AD module for PowerShell for getting / setting the AD user.
Would like to re-iterate that there are constraints on the sizes and formats supported for the
thumbnailPhoto Active Directory attribute. As a general guideline, keep your images to 96x96 pixels and under 10Kb, using JPG format.
Thank you,
Arvind

Exchange 2007 and outlook 2010 frequent disconnects

Hi,
Im having issues on SBS 2008 with exchange 2007 and outlook 2010.
Every so often users disconnect and outlook then requires them to put there password in but if you restart outlook all is fine till the next time its random aswell.
I have checked in IIS if windows and basic authentication are enabled which they are.
If i dont use outlook anywhere i still get this problem.
I have looked on the internet but everything i try doesnt seem to help me any ideas ?
Thanks

Hi,
Before going further, would you please let me confirm whether all users (with all Outlook) encounter this same
issue? Did you install any update or any third-party application on the server before this issue occurred?
à
Im having issues on SBS 2008 with exchange 2007 and outlook 2010.
Would you please let me confirm whether installed Exchange Server 2007 SP2 (or SP3)? Did you install all necessary
Update Rollups for the Exchange Server 2007?
Please type
outlook.exe /safe in RUN to start Outlook in Safe Mode, then check if this issue still exists. Meanwhile, please navigate to the website which contains Exchange Virtual Directories in IIS Manager, then enable kernel-mode authentication for each directory
and monitor the result.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

TS3999 I installed ic;oud on my iphone 4s and my pc laptop ruunning windows 7 and Outlook 2010, my new calendar information is not syncling? Thoughts?

I installed iCloud on my iPhone 4S and PC running Windows 7 and Outlook 2010. My calendar is not syncing when I put in new information. Solutions?

I would say that you would want to look into the "Exchange Mode" for GMail. That would allow your iPhone to sync calendars, contacts and email with GMail just fine. Doing the same with your outlook should also then sync those same with your PC using Outlook. I've done teh iPhone side of this, but I since I don't run Lookout for my email client, I'm not sure how that will work on the PC side.

Removing dead Exchange 2003 and Exchange 2000 Server from the domain

Hi Team,
I have come across a client who wants to migrate to O365 from existing Exchange 2003 environment through the Hybrid Model. I am trying to introduce 2010 Sp3 to the environment. While checking the environment using Exchange pre-deployment found 2 servers
in the environment which is not present on the network now. Client has no clue what they are.
One is Exchange 2003 and the other is Exchange 2000. The problem here is i cannot introduce Exchange 2010 Sp3 unless all the Exchange servers are running minimum Exchange 2003 Sp2.
At present i find only 2 exchange 2003 Sp2 server which are in production. Need kind assistance to move forward.

Hi,
I recommend you follow the steps below:
1. Please upgrade Exchange 2000 and Exchange 2003 to Exchange 2003 SP2 at first.
2. Deploy Exchange 2010 servers in this order: CAS, Hub, UM and Mailbox. For more information, here is an article for your reference:
Exchange 2003 - Planning Roadmap for Upgrade and Coexistence
http://technet.microsoft.com/en-us/library/aa998186(v=exchg.141).aspx
3. Install Exchange 2010 SP3.
Here is an article for your reference.
Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
About a hybrid deployment with Microsoft Office 365 using Microsoft Exchange Server 2010 servers, here is an article for your reference.
Understanding Upgrading Office 365 Tenants for Exchange 2010-based Hybrid Deployments
http://technet.microsoft.com/en-us/library/jj945383(v=exchg.141).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2013 and exchange 2000

Hy guys...
I have this problem...i have a dommain controller x.com and i installed Exchange 2013 on it. I have another dommain controler
y.com with Exchange 2000. Thex.com dommain sends and receives mails from other Exchange 2013 servers but when it comes to
y.com dommaind i am only able to send emails to
[email protected] I cannot send emails from y.com
(Exchange 2000) tox.com (Exchange 2013).
Bothx.com dommain controller and y.com dommain controller are in the same network and i fave connectivity between them.
What might be the problem?
Than u,
M.S

Hi,
Firstly, it’s not supported to install Exchange 2013 and Exchange 2000 in the same organization and it’s not recommended to install Exchange server on Domain Controller.
http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.exchange2000or2003presentinorg(v=exchg.150).aspx
To understand more about the mail flow issue, I’d like to confirm your meaning that two DCs are in the same network.
If they are in the same forest, it’s by design that Exchange 2013 and Exchange 2000 cannot coexist.
For general mail flow troubleshooting , we can use telnet to check it.
For more information, you can refer to the following articles:
http://technet.microsoft.com/en-us/library/bb123686(v=exchg.150).aspx
http://msexchangeguru.com/2013/07/29/troubleshooting-mail-flow-issues/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange Online and MS Access

Hi. I am a somewhat novice IT support with a non-profit. We have an Access based database already up and running. We're looking at moving to Outlook for the added function of creating Outlook appt's from the Access database. But, we have to have shared
calendars that only Outlook with Exchange will do. We currently use Google for calendar and email.
Will Exchange Online provide the same functionality with our Access db as a locally hosted Exchange will do?
Alan

What version of Exchange OnPrem are you looking to support ? On Exchange 2010 you can only use NTLM or Basic auth for OnPrem given that 2010 still makes up a large number of OnPrem seat's if your looking to support the widest client base you may just want
to stick with Basic and NTLM for any OnPrem installs and look to oAuth and the new REST API's for Office365.
Cheers
Glen

Exchange Server and Remote Access to Public Calendar

Hello:
We use Outlook 2010 with Exchange Server at the 45 person architecture firm I work at.
We have a public calendar (set up in public folders) that is used by staff to note their time away from the office (doctor’s appt, vacation, client meeting, etc). The owner of the company wants to be able to remotely access that public calendar to be
able to know when staff are out of the office. Can it be set up on his Surface 2 or phone (iPhone) so that when he’s not in the office, he can see that public calendar?
I’ve search online and from what I can tell, the only way to make it work is with third party software.
Is that true? Or is there another way to make it work? Is VPN an option?
Any help would be greatly appreciated.
Thanks.
Joe

I'm going to attempt to activate Anywhere soon, probably early next week. I found a site that does a step-by-step of the Anywhere setup and I have a couple of questions based on those steps (here's the site - http://exchangeserverpro.com/how-to-configure-exchange-server-2010-outlook-anywhere/)
After the Anywhere wizard opens, it says this - "The external host name you choose should ideally be one that is already included in the Exchange certificate configured on the Client Access server. Otherwise you will need to create a new certificate for
Exchange." So I can name the external host, where do I find the Exchange cert? When accessing the firewall to allow Anywhere through, it says this: To enable remote Outlook users to connect to Outlook Anywhere the perimeter firewall for the network must
be configured to allow the SSL/HTTPS connections to pass through to the Client Access server. The precise steps for this will depend on which firewall you are using in your environment. However the basic components of this configuration are: •A public DNS
record for the external host name you are using for Outlook Anywhere •A public IP address on the firewall that the public DNS record resolves to •A NAT or publishing rule to allow SSL/HTTPS connections to reach the Client Access server

Exchange 2007 and exchange 2010 Federation

Hi all I am trying to federate between Three organisations
org A exchange 2007 with exchange 2010 cas
org B exchange 2010.
org C exchange 2010.
I cannot share my calendar from org A to Org B
I can share Org B to Org A and Org B to Org C.
when I try from Org A to Org B or Org C
When I try to share free/busy fro the exchange 2007 with exchange 2010 cas. The user gets an error
"calendar sharing is not available with the following entries because of permission settings on your network."
-availabilityaddressspace. Autodiscover works TXT works. I have added a user from Org B as a contact in exchange.
The exchange 2010 server is not the CAS server for the exchange environment and I is not a proxy for exchange 2007. Is this where I am failing ?
Heeeelp

Hi Nigel,
How is the impact, just one user or all users, Outlook or OWA?
If just one user, it seems like an issue on the Outlook Client side.
Please trying to re-create new profile to fresh the caches.
Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
Found a similar thread for your reference:
Calendar Sharing not available error message
http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2003 and Exchange 2010 Coexistence Activesync Issue

Hello,
I am currently on the progress of migrating mails from Exchange 2003 SP2 to Exchange 2010 SP3. Before I can do actual migration, I need to make sure that OWA and Activesync works when Exchange 2010 becomes Internet facing.
Right now Exchange 2003 is Internet facing while Exchange 2010 is internal LAN only. OWA login from Exchange 2010 to a mailbox in Exchange 2003 works fine. However, trying to open a mailbox in Exchange 2003 from Exchange 2010 Activesync fails.
Activesync login from Exchange 2010 to a mailbox in Exchange 2010 works fine, as well as logging in from Exchange 2003 to mailbox in Exchange 2003.
Tests using AccessMyLAN ActiveSync Tester using Exchange 2010 as entry point are inconclusive. The test shows the app successfully contacting ActiveSync version 6.5 which is Exchange 2003, but results in "Activesync detected, but not correctly configured."
Tests using Test-ActiveSyncConnectivity from Exchange 2010 reveals Error HTTP 400 when contacting Exchange 2003. The cmdlet also shows it successfully contacting Activesync version 6.5 (Exchange 2003).
I have searched around, installed hotfix KB937031, enabled Integrated Windows Authentication on Exchange 2003 Microsoft-Server-Activesync, disabled Require SSL for Microsoft-Server-Activesync and exchange-oma, yet I still can't connect to a mailbox inside
Exchange 2003 through ActiveSync 2010. Website Multiple Identities for port 80 has been set correctly. Exchange 2003 has Forms-Based Authentication Enabled and is the one thing we haven't tried disabling yet.
We want to make sure everything works first, then make Exchange 2010 Internet facing, and finally do the mail migration. We do not want to migrate everyone in a single sitting. Please if anyone have ideas any help is welcomed!

Exchange 2010 will proxy ActiveSync for Exchange 2003. For OWA, it will redirect, so you need a legacy redirect URL. You can test all of this internally without changing your Internet connection. For ActiveSync you can use a WiFi connection.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013 and Exchange 2010 coexistense

We have a and exchange 2010 organization with SP3 on most servers except for one 2010 CAS server that still requires SP1 for the purpose of legacy application compatibility. Can we introduce exchange 2013 in the org or will the setup detect
that there is an exchange 2010 server still with SP1 and fails to continue?

Hi,
For Exchange 2013 coexistence with Exchange 2010, the mininum version of Exchange server is Exchange 2010 SP3 on all Exchange 2010 servers in the organization. For more information about it, please refer to the Coexistence of Exchange 2013 and earlier versions
of Exchange server part in the article below:
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Personal suggestion, please upgrade your legacy application to the latest version which is supported with Exchange 2010 SP3 or higher Exchange version.
Regards,
Winnie Liang
TechNet Community Support

Connector help ( Coexistence Exchange 2003 and Exchange 2010)

Dear all,
we are in a Coexistence state where all the mailboxes are not yet migrated to Exchange Sever 2010.
On Exchange server 2003 we have two connectors 1) Internal 3) External
1) Internal connector is used to have mail flow between postfix mail and Exchange server.
2) External Connector is used for sending/receiving emails from External domains (like gmail,yahoo etc...)
3) when we added first Exchange 2010 that time it created one RGC used for sending/receving emails between Legacy and new server.
What I want to achieve is created new two more connectors on Exchange server which will act as Internal & External connector.
if these works then delete connectors on legacy server and go ahead with for rest migration
is it possible if not then how do it ?
TheAtulA

Hi AtulA,
Thank you for your question.
Internal:
To support coexistence between these two routing topologies, all Exchange 2010 servers are automatically added to a single routing group when Exchange 2010 is installed. The Exchange 2010 routing group is recognized in Exchange System Manager in Exchange
2003 as Exchange Routing Group within Exchange Administrative Group.
During the installation of the first Exchange 2010 Hub Transport server in an existing Exchange organization, we must specify an Exchange 2003 bridgehead server to which to establish the first routing group connector. We recommend that you select a bridgehead
server located in a hub routing group or in a routing group that has many mailboxes. The routing group connector links the routing group where the Exchange 2003 server resides and the Exchange 2010 routing group. The Exchange 2010 routing group includes all
Exchange 2010 servers, regardless of the Active Directory site in which they reside.
Notice: Don't move Exchange 2010 servers out of Exchange Routing Group (DWBGZMFD01QNBJR), and don't rename Exchange Routing Group (DWBGZMFD01QNBJR) by using a low-level directory editor. Neither action is supported. Exchange 2010 must use
this routing group for communication with Exchange 2003.
External:
We could create send connector and receive connector to send/receive email from Internet, we should modify the firewall setting to point to Exchange 2010.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Lync onpremise, exchange online and UM ports requirement

Hello Team,
Could you, please point us to the relevant articles or answer my question in the email.
For the scenario with Lync on-premises and Exchange on-premises there is a requirement to have 60000-64000 ports open between Lync client and UM server in both directions for
SRTP/RTCP traffic. Our questions are:
1.
What are ports requirements for Lync 2013 on-premises with Exchange UM in Office 365?
2.
How to limit ports used by client for UM traffic? (is it with
Set-CsConferencingConfiguration?_
Please advise. MANY THANKS.

Hi SBHV,
As far as I know, it does not require special port.
You need to configure the Edge Server for federation, because the traffic will through Edge.
60000-64000 ports won’t be used in this case, they are used with on-premises.
Best regards,
Eric

Data sync between exchange 2003 and exchange 2013

Need assistance on a general direction.
There is a 2003 domain with exchange 2003 currently in use. On this domain there is also a contact management application that is heavily integrated and cannot be update at this time. I would like to bring up a new 2013 exchange server.
Is there a method that I could have user data synchronized between the 2013 exchange data and the 2003 exchange? In this manner users could use the 2013 exchange as primary and the Contact manage application could use the sync copy of exchange 2003. For
now I am only concerned about he the calendar however I am sure the other information will need to be sync as well.
Please let me know. Thank you.

Hi There,
Once you install Exchange 2013 it will use the same data your Exchange 2003 is using \ seeing because both of them use Active directory for Directory information.
Exchange 2013 will see all the users that are 2003 without you needing to sync \ move data.
If you need to users to be on Exchange 2013 and keep Exchange 2003 all you need to do is move the mailboxes to Exchange 2013.
Cheers,
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Exchange online and Exchange 2010 on-premise calendar availability

Similar Messages

Maybe you are looking for