Oracle Collaboration Coexistence Gateway and Exchange 2010

Hi,
in the Beehive 2.0 Integration Guide is said that the Collaboration Coexistence Gateway is compatible with MS Exchange 2003 and 2007.
Are there any plans to make in compatible to Exchange 2010 or is it even already compatible?
Thanks for your help!

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."

Similar Messages

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

Problems with a shared calendar using Outlook 2007 and Exchange 2010

Hello all,
We are having a problem with sharing a calendar using Outlook 2007 and Exchange 2010.
I will start with some background. I have just started my position with this company. I have been working with networks for awhile at the small business level. I have not had much production experience with exchange. There is only myself and my supervisor
who has inherited a midsized network which was built by five previous techs that are no longer with the company. Of course, the previous techs did not leave much documentation, so the original hows and whys for our system setup has been lost.
One of the managers has a calendar she shares with some of our users. I believe this calendar has been in use since sometime in 2006. A mailbox was created to hold this calendar to keep it separate from the managers calendar. I am not sure what version
of exchange they were using at that time, but I assume there was one or two migrations of it getting to its current state on our exchange 2010 server. At some point it was observed that the other workers she was sharing with were not able to access it correctly.
I am not fully sure what the original problem was (possibly some people not being able to see or connect to the calendar), but it was decided to give everyone who needed access to this calendar full access permissions through exchange. Correct me if I
am wrong, but I believe that gave everyone connected the ability to do anything with the calendar. Of course the manager was not happy about that. This is where I started working on the problem.
I removed everyone, except the manager who wants to control the calendar, from having "Full Access Permissions". This did have the effect of making some people just able to see the calendar and not make changes. Though there were others that were
able to connect to the calendar who I thought would not be able to. The manager that originally created the calendar did try to manage access to it through the Outlook interface, though it currently does not seem to be fully in effect.
So, to get to the point of what we are trying to do, is there a way to get the original manager back into control of the calendar though Outlook? It would be preferred to be able to keep the history of what they tracked of this calendar, so starting a new
one would be something we would rather avoid. After that, getting all of the users that need to connect to the calendar reconnected with the correct access permissions and making sure they are all synchronized.
I realize this is a big mess, and your help would be greatly appreciated.

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

Outlook 2010 and Exchange 2010 SP3

Hello,
we are planning to upgrade from Exchange 2010 sp1 to SP3, most of client PCs has Windows XP sp3 and Oultook 2010 with VSTO addins working with mapi properties.
I need to know if there are any known issues between this client environment and Exchange 2010 SP3 ??
thanks a lot,
Mauricio.
Mauricio

Windows XP is not supported in any scenario, so yes, I'd call that a known issue.
Mike Crowley | MVP
My Blog --
Planet Technologies

CallManager 7.01 and Exchange 2010 UM

We want to integrate CallManager 7.01 and Exchange 2010 UM. The plan is to build two Exchange 2010 UM servers. Who would be resonsible for load balancing (messanging) between the two Exchange 2010 UM servers? CallManager or Exchange? Does anyone know if there is any documentation on this?

I would guess you just make a SIP trunk to both UM servers. From here you can make a circular Route Group which would load balance the calls accross the UM's..
So I guess the answer is call manager!
HTH,
Chad

Outlook client requirements and Exchange 2010/2013 coexistence

Good morning!
A question regarding Exchange 2010/2013 coexistence and the Outlook client requirement. I am upgrading and about to install Exhange 2013 into an existing Exchange 2010 Org. The current 2010 Org is patched to SP-3 and Outlook Anywhere is currently disabled.
I have Outlook clients that do not yet meet the minimun requirements for 2013 (Outlook 2007/2010). When I install my first 2013 server will it effect the current downlevel clients? The mailboxes are still in 2010 so my thoughts were since the Office upgrade
including Outlook has not yet taken place I didn't want to wait for them to at least get 2013 into the Org. The 2013 server should effect the clients until I configure the CAS on 2013 and only when they are at the proper version, is this correct? Does Outlook
Anywhere need to be first enabled and configured on the 2010 CAS before I attempt the confgiuration on the 2013 CAS? I just dont want to install 2013 and have Outlook connectivity issues right out of the gate...
Thanks in advance!

Outlook 2007 and 2010 are supported for Exchange 2013, you just need to push out the latest patches.
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If you configure the URLs properly in Exchange 2013 to URLs that point to the Exchange 2010 servers, your clients shouldn't try to talk to the Exchange 2013 server.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

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

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."

Legacy integration between Exchange 2003 and Exchange 2010

Dear Team,
we are using Microsoft Exchange 2003 & 2010 Server for Emails, now we have both servers are connected, we want to raise new Single incident request for doing this activity, we want disconnect 2003 server from 2010 server so accordingly need support,
we are ready to pay for this incident,
pls do the needful,
Thanks & regards
Anteshwar Bhosale

Hi Anteshwar,
If you want to remove Exchange 2003 from your coexistence environment, please perform the following procedure:
1. Move all mailboxes to an Exchange 2010 server in the organization.
2. Move all content from the public folder database on the legacy Exchange 2003 server to a public folder database on an Exchange 2010 server in the organization.
3. On Exchange 2003 servers, for each offline address book (OAB), move the generation process to an Exchange 2010 server.
4. Verify that Internet mail flow is configured to route through your Exchange 2010 transport servers.
5. Verify that all inbound protocol services (Microsoft Exchange ActiveSync, Microsoft Office Outlook Web App, Outlook Anywhere, POP3, IMAP4, Autodiscover service, and any other Exchange Web service) are configured for Exchange 2010.
If all above steps have been prepared, we can remove the last Exchange 2003 server from the Exchange 2010 organization from ADSIEdit. For detailed steps about this, please refer to:
https://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Synchronization between Oracle Calendar 10.2 and Exchange 5.5 calendar

We are going to migrate 1000 users from Exchange 5.5 to OCS 10.1.2.3.
Mail and Calendar migration is done with ES/EX-migrate, but we have a PABX system (Trio Present 2.3) that is integrated with Exchange Calendar,and this is not compatible with Oracle Calendar in its current release.
In simple terms Trio is integrated with the calendar to programme our phones to "Busy", "Home Sick", "Meeting" etc, based on calendar entries.
In order to preserve this functionality we have to "coexist" with Exchange's calendar.
I see in the Coexistence guide that this is possible to booke meetings in both alendars, but we need a synchronization feature, as the users can booke meetings through their phones, which are then inserted in Exchange, but not Oracle.....
Any idéas ?
Regards,
André

If you find a solution that actually synchronizes between Oracle Calendar and Exchange, let me know. I don't want the Outlook connector - which creates access to the Oracle Calender using Outlook - I actually want to synchronize between the Exchange calendar and the Oracle Calendar. This way, if I update Exchange (using Outlook), Oracle Calendar will be updated when I synch. Also, if I modify the Oracle Calendar, the Exchange Calendar will be updated. We are using Exchange 6.
Thanks,
Fuller Ming, Jr.
[email protected]

Windows 8.1 Mail app and Exchange 2010 EAS partnership - "Make Windows user account an Administrator" to meet security requirements?

As the title says, I have a new Windows 8.1 based device which I'm trying to connect to my Exchange 2010 box (SP3 Update Rollup 2). I currently have my iphone set up as an EAS client with no problems. I have an EAS policy on my mailbox
with the following settings surrounding passwords :
Require Password, Require Encryption, Allow Simple Password, Time without user input - 10 minutes. Allow non-provisional devices is also checked.
The Windows 8.1 device has Bitlocker enabled, which meets the encryption requirement - I know this because the 1st time I tried this it moaned about Bitlocker needing to be enabled to meet requirements, though at that time the local user account on the Windows
8.1 device was an admin level account so it never mentioned this issue, it worked normally.
Now, while using a std user account on the Windows 8.1 device and trying to connect up via EAS, it complains that my local windows user account must be an ADMIN level account to meet the security requirements...?
Anyone encountered this?

Did anyone solve this problem? I'm also struggling with this issue.
this is still a problem. I'm just hitting it now and it's not doing much for management's love of Microsoft devices.
Evidently, it has to be an admin to set the policies on the device to match the policies on the EAS. And once set, a user can be changed back.
But this is seriously not cool. Don't the "app" folks and the enterprise folks talk to each other?

ICal, Macbook Air, and Exchange 2010

I have a user whos iCal is not syncing with Exchange 2010. When creating a new event, it gives the message "iCal can't save the event "xxxx" to the Exchange server. The account "xxxx" currently can't be modified. To discard your changes and continue using the version of your calendars that's on the server, click Revert to Server. To save your changes on your computer until the problem is resolved, click Go Offline."
The user is on a 2011 13" Macbook Air, 1.86 GHz Core 2 Duo. Snow Leopard 10.6.7, iCal 4.0.4. Mail and Address Book sync fine. The calendar works fine from the users iPhone, Outlook Web Access, and Outlook 2011 on the computer.
I have tried deleting the account, deleting all caches, and recreating it, but it still doesn't work. I created the account on my Macbook and it works fine, no problems syncing over wired or wireless connections. Macbook is also on 10.6.7, iCal 4.0.4. So I was thinking it was an account issue. I created a new account on the Macbook Air, set up the exchange account in iCal, and I get the same problem as on the original account, no syncing.. I have everything set up exactly the same as on my Macbook, but the Macbook Air refuses to sync. This error only appears when an event created on the Macbook Air is in the calendar. It pulls events from the server fine, but once an event is created it refuses to cooperate.
Do Macbook Airs just not play nice with Exchange?

This is not an issue with the Macbook Air. I have had this same problem since upgrading to Lion. One solution suggested (from MacRumors.com forum reply) was to
1) Open iCal and go into the iCal Menu/Preferences. Go to Advanced tab and enable Time Zone Support. Close iCal
2) Open System Preferences and click on Date & Time. Click on Time Zone tab and enable the checkbox for auto detect time zone.
I did this several times without success before I finally got rid of the errors. I have been error free for 3 weeks, but today the error is back (with no apparent changes made by me). I'm still struggling to get rid of it now.

Mail 4.4 and Exchange 2010: not staying connected

I am using Mail 4.4 connected to an Exchange 2010 account, and with an SMTP server instead of the actual Exchange connection to send outgoing mail due to the "no from: field" issue.
I have noticed that Mail is not staying connected to the server. IIRC, Exchange is intended to be a live connection, and messages that arrived quite some time ago are nowhere to be seen until I click "Get Mail." Up to now, I've relied on IMAP with IDLE for mail, as I'd rather receive everything in real time instead of relying on a scheduled polling interval.
Why is this? Is it just an issue of being Exchange 2010 instead of Exchange 2007, or is there something I can do to fix it?
My iPhone running iOS 4.2 works perfectly with the same Exchange account.

IMAP with IDLE for mail, as I'd rather receive everything in real time
Certainly in the current version of Mail, you'll get more of a push effect if you use IMAP IDLE instead of EWS for communication with an Exchange server. Exchange Web Services feel less responsive.
The Get Mail routine is much quicker with IMAP IDLE than with EWS. With EWS: the more mailboxes you have, the longer it takes.
However: if you use IMAP instead of EWS, some features of Exchange will appear less graceful. Noticeable with e.g. messages relating to calendaring.
(Note to self: I should review this after our organisation has completed its transition from Exchange Server 2003 to Exchange Server 2010.)
messages that arrived quite some time ago are nowhere to be seen until I click "Get Mail."
Using EWS: in the absence of a real-time/push effect, three approaches come to mind:
a) pull manually (click Get Mail)
b) prefer a schedule
c) simply move or delete any message to trigger an update of that mailbox.
For my Inbox, I prefer (c). An update of the Inbox alone is much faster than the (Get Mail) update of all mailboxes.
Eventually, I guess that Apple will improve Mail to make it respond immediately to changes on the EWS side.
Then, I'll go back to using e.g. GrowlMail to weed most messages immediately, as each one appears (much more pleasing than ploughing through a massive Inbox).

Problem with Assigning Policy button in Outlook 2010 and Exchange 2010

First of all, I'm posting here because I'm not sure how to post in the previous version of Exchange forums.
Secondly, I'm re-posting this from the Outlook forums as I'm not getting any responses there despite of views.
Hi,
I'm having an issue in Outlook 2010 where I can't assign personal policies to folders. I have setup personal tags and added the mailbox to the right policy. I have also ran Start-MangedFolderAssistant in Exchange 2010 Shell against the mailboxes.
When I go into OWA, everything shows up perfectly, I can right-click and assign policies at will, but when I open Outlook 2010 then the Assign Policy button never appears. I force added it to the ribbon and I can see from there that the button stays grayed
out irregardless of where I click in the folder structure. I have even assigned the mailbox user Owner rights to all the folders to see if it will make a difference.
If anyone can help me solve this problem I will very grateful, I'm pulling my hair out here and I'm certain I could just be missing something very obvious somewhere,
It might be worth mentioning that the company has been using .prf files to configure Outlook thus far, I'm
looking to eliminate that. I'm not sure if that will have any effect on my current problem.
Thanks for your time.
Nico

Thanks for the reply Max, that's a pretty good link.
Like is I said though, I have the policies all set up in the Exchange configuration side of things, when I use OWA all the options for applying tags appear. It's just in Outlook 2010 Standard that the Assign Policy button stays grayed out.
Thanks.
EDIT:
This has been solved, looks like version problem with Outlook.
http://office.microsoft.com/en-us/outlook-help/license-requirements-for-personal-archive-and-retention-policies-HA102576659.aspx

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?

Oracle Collaboration Coexistence Gateway and Exchange 2010

Similar Messages

Maybe you are looking for