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

Similar Messages

  • 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

  • How to choose between Exchange 2007 and Exchange IMAP if you have choice?

    I'm running a silver intel macpro at a company that is predominantly PC.
    I just installed snow leopard and have an Exchange account that I had already moved to Exchange IMAP so I could access it with Leopard (although I was never able to get it to work under Leopard).
    Ideally I'd like to use Mail/iCal as much as possible for interacting with Exchange, and only revert to XP under Fusion occasaionally.
    Given that goal, would appreciate any insights into whether I'd be better off connecting via Exchange 2007 or Exchange IMAP.
    Thanks.

    Thanks for info - I was unable to get mail to autoconfigure to my exchange account, but after I configured iCal, it correctly configured mail (and address book) to access my exchange server.
    I'm thrilled so far with what I've seen - it's so refreshing to be able to use my Mac apps for work.
    Just to clarify, if I set up my account using IMAP, would I notice any differences in functionality, or is just a matter of ease of setup?
    James

  • Free/Busy not working Exchange 2007 and 2013 co-existence

    Hi,
    I'm migrating our Exchange 2007 environment to Exchange 2013. Now I am in a co-existence environment where all the mailboxes except some test-users resides on Exchange 2007. Between Users on the same Exchange MBX Server athe FREE/BUSY Information sharing
    works correctly, but between Exchange 2007 and 2013 it's not working.
    I verified my settings and also the EWS virtual directory on 2007 CAS Servers using Get-WebServicesVirtualDirectory.
    The internal and the external URLs are set to https://legacy.mydomain.com/....
    What am I missing?
    Thanks & Kind Regards,
    Jürgen

    Hi,
    According to your description, I understand that the free/busy information between Exchange 2007 and Exchange 2013 is not available for your coexistence environment. To narrow down the issue, please check the following points:
    1. Does the issue happen to all users or specific users?
    2. Although a user on Exchange 2013 can't get free/busy information from a user on Exchange 2007, please confirm whether Exchange 2007 user can get free/busy information from Exchange 2013 users.
    3. Close Outlook and only access user mailbox from OWA to check whether the issue persists. For Outlook client,
    create a new Outlook profile
    to have a try.
    4. Please make sure the virtual directories settings are configured correctly in both Exchange 2013 and Exchange 2007.
    Virtual directories settings in Exchange 2007:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Certificate and Virtual directories settings in Exchange 2013:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
    5. Restart IIS service in Exchange server by running iisreset /noforce from a command prompt window.
    If possible, please run Test E-mail AutoConfiguration in Outlook to check whether the autodiscover service can get correct Availability service URL in the results. If there is any event logs, please collect some for further analysis.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Cannot send email from Exchange 2007 to Exchange 2013 - Coexistence

    Existing Exchange 2007 SP3 1 MBX, 2 CAS/HT, 2 ET servers.
    I have added an Exchange 2013 server with MBX/CAS role.
    Email will flow from Ex2013 server no problem.  Mail from Ex2007 systems cannot deliver to Ex2013 boxes, it dies in queue with a 4.4.7 expired message after issuing a delay message.
    I can telnet to ports 25, 587,717,465,475, and 2525 from Ex2007 HT role to new Exchange 2013 server.  I can send email from Ex2007 HT role server to new Exchange 2013 server using telnet to port 25.
    A ‘get-mailbox’ from the Ex2007 HT role server returns the server and database properly on the test users on Exchange 2013 server.
    The only strange thing I am seeing is from the Ex2007 systems, a ‘get-exchange server’ command shows the new Ex2013 server as role ‘16439’ which looks to perhaps be normal.
    Why is email not flowing to the new users on Exchange 2013?

    You should have exchange server authentication ticked in Default Receive connector in Exchange2007.
    Exchange 2007 and Exchange 2013 in the same subnet/network. if not please check any spam agent running between the networks. Are you running antispam on Exchange2013 ?
    MAS

  • Establish mail flow from Exchange 2007 to Exchange 2013

    I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
    Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

    Was this question answered.  We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped.   Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
    using "Custom Settings" - manually entered IPs for DNS in the Exchange  Admin Center "DNS Lookups".
    Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.  
    Any assistance will be greatly appreciated.  

  • Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

    We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them. 
    With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
    For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
    In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
    I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
    I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
    So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
    In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
    Questions are, Is this the right way to migrate all the users to Exchange 2013?
    Will it affect the operation of existing Exchange 2007 server?

    Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
    For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
    However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
    2013 for standardization.
    Refer article for configuring URLs -
    http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
    - Sarvesh Goel - Enterprise Messaging Administrator

  • Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

    Hello, everyone, my name is rafl
    I have a problem with exchange 2013 active sync.
    I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
    but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
    (legacy.domain.com)
    the process of moving mailboxes successfully without error.
    Access OWA for exchange 2007 and exchange 2013 is running normally
    access mail from Outlook running normally
    Certificate request has been installed and has no problem with it
    The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
    The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
    ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
    user mailboxes are still on exchange 2007 is not problematic.
    only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
    but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
    only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
    any ideas for this problem, and what should I check on the exchange server ..?

    i have run the activesync test connectivity and get some error :
    Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 3091 ms.
    Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21072 ms.
    Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21049 ms.
    I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
    for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

  • Upgrade exchange 2007 to exchange 2013 on SBS 2008

    Hi,
    I need to upgrade EX07 to EX13 on small business server 2008, So I am looking for the documents or steps which will help in Implementation.
    Thanks in advance!
    -av

    Hi,
    Any update about the issue?
    In-place upgrade is not possible. According to the MS article:
    When you're upgrading your existing Exchange 2007 organization to Exchange 2013, there's a period of time when Exchange 2007 and Exchange 2013 servers will coexist within your organization. You can maintain this mode for an indefinite period of time, or
    you can immediately complete the upgrade to Exchange 2013 by moving all resources from Exchange 2007 to Exchange 2013, and then decommissioning the Exchange 2007 servers. You have a coexistence scenario if the following conditions are true:
    Exchange 2013 is deployed in an existing Exchange organization.
    More than one version of Microsoft Exchange provides messaging services to the organization
    Upgrade from Exchange 2007 to Exchange 2013
    https://technet.microsoft.com/en-us/library/jj898581%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
    Regards.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • 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

  • Getting UConn 8.5 to work with both Exchange 2007 and 2010

    According to the document below, I should be able to set up one Unified Messaging service to access mailboxes on both Exchange 2010 and Exchange 2007 servers.  I setup my service to point to 2010 CAS servers and I can access 2010 mailboxes, but testing 2007 mailboxes comes up with an http 200 error.  If I setup the CAS server as 2007, I can access 2007 mailboxes, but get an error on 2010 mailboxes.  This will be a real pain if I can't do this with one service.  I don't want to have to keep Unity Connection updated as users get moved from 2007 to 2010!  Anyoe know how to do this?
    http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg020.html#wp1198171        

    I got this to work!  My Unified Messaging Service was originally setup to Specify an Exchange Server.  That is where I had put the  DNS name of the  CAS server (and that DNS entry pointed to several CAS servers).  I changed the Service to Search for Exchange Servers instead and used that same DNS name in the Active Directory DNS Domain Name.  When I do the test of this service, it tells me it Failed to locate a Domain Controller via DNS, but that is just informational.  It also says it successfully connected to the Exchange CAS server with the autodiscover.xml.  Now my mailboxes on both Exchange 2007 and 2010 are able to receive voicemail messages with this one Service configured.

  • Difference between Exchange 2007 and 2010

    Hello, 
    I want to know what are the differences between Exchange 2007 & 2010, i mean what was missing in 2007 which is addresses in 2010. Both from Administrator point of view and client point of view. How admins are going to benefit from 2010 and how clients
    will see changes in their outlook 2010 because of Exchange 2010? 
    Hasan

    Hello,
    Can you Please help me out, what is the Difference? 
    Difference between Exchange 2003 and 2007
    Difference between Exchange 2007 and 2010
    Thanks 

  • Exchange 2007 and 2010 with Unity Connection 8.6

    Hi all,
    We have unity connection 8.6 and exchange 2007 currently in place and runnign fine. I am ready to start migrating mailboxes over to our new exchange 2010 farm and as such we will be in co-exsistance with exchange 2007 and 2010 for awhile. What are the steps or procdures to also include exchange 2010 with the 2007 in unity connections? Currently under Smart Host is the IP address of our exchange 2007 server.
    Thank you.

    Hi,
    This depends on how you plan on performing the migration. I would suggest the following:
    -Creating a new unified messaging service for Exch 2010. You can re-use the same service account name as long as you completed the configuration steps for that integration.
    -As you move over user's mailboxes from 2007 to 2010, you can delete the 2007 UM service and add the new 2010 UM service. If you want to change many users at a time you'll need to use bulk administration to change them. If you use BAT to change accounts, see the link below where I have listed them out for another CSC user.
    -You can change the Smart Host setting once you have configured the Exch 2010 enviornment to handle your main corporate mail (changing the MX records to point to a 2010 Edge Transport).
    Changing the UM service with BAT:
    https://supportforums.cisco.com/message/3572200#3572200
    Good luck.

  • Exchange 2007 to Exchange 2010 Migration

    Hi all,
    I am migrating to exchange 2007 to exchange 2010 .This is not a migration data only migration like i am exporting mailboxes and importing it to new mailboxes .But email address and SAM account name will be same as per the source.Post migration i will point
    the auto discover to new organisation.May i know what will be the impact to users??need to reconfigure outlook profile or does it will look for auto discover and prompt for new email id?
    Jayakumar K

    Is it in the same forest of or both the servers are different forest?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2007 to Exchange 2010 URL redirection

    Hi,
    I am performing exchange 2007 to exchange 2010 migration in co-existence. When i am accessing exchange 2010 OWA and logged in with exchange 2007 user then silent redirection is happening.
    But when i am accessing the exchange 2007 OWA and logged in with exchange 2010 user, this is asking for manual redirection to exchange 2010 OWA url.
    Please suggest the silent redirection method from exchange 2007 to exchange 2010 URLs.
    All exchange servers are in same active directory site.
    Regards Sunny Chauhan

    Hi  Sunny,
    You can run the below command to resolve this error
    Set-OWAVirtualDirectory <CAS2007>\OWA* -LegacyRedirectType Silent
    The LegacyRedirectType parameter specifies the type of redirect that Outlook Web App uses to a legacy Client Access server or front-end server when forms-based authentication isn't used on the Exchange 2013 Outlook Web App virtual directory.
    The following values are valid for this parameter:
    •Silent
    •Manual
    Silent causes a standard redirect. Manual displays an intermediate page that shows the legacy URL so that users can change their bookmarks.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
    Regards,
    Sathish

Maybe you are looking for