Autodiscover service overlap between Exchnage 2007 and 2013 mailboxes

Hi,<o:p></o:p>
I have Exchange 2007 Legacy environment and owa/rpc/activesync/autodiscover configured with DNS name owa.domain.com.<o:p></o:p>
I have installed Exchange 2013 and owa/rpc/activesync/autodiscover configured with DNS name mobile.domain.com.<o:p></o:p>
Its a requirement to retain different URL for Exchange 2007 and 2013.<o:p></o:p>
Now...Exchange 2007 users RPC over http is broken because their outlook rpc setting is automatically getting configured to mobile.domain.com which belongs to Exchange 2013.<o:p></o:p>
I know I have thought about updating the hostfile for Exchange 2007 clients to achieve this.Without changing the URL and
retaining the existing DNS names, can we prevent RPC over https outlook setting changes for Exchange 2007 users alone?

Hi,
You can deploy localxml for Exchange 2007 user:
http://support.microsoft.com/kb/2212902/en-gb
Thanks,
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 Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

  • Differences between SharePoint 2007 and 2013 security options?

    Hi,
    We just did a test upgrade from Sharepoint 2007 to Sharepoint 2013 by copying over the content database. One thing we are noticing is that users who had permissions to upload to a document library no longer have that option in 2013. Is there a difference
    between the 2007 and 2013 "contribute" permission?
    What can I do to fix this issue?
    thanks,
    Sherazad

    their is no difference between 2007 & 2013 for Contribute premission.
    Contribute having the same rights in 2007 and 2010.
    Read permissions, plus:
    Add Items
    Edit Items
    Delete Items
    Delete Versions
    Browse Directories
    Edit Personal User Information
    Manage Personal Views
    Add/Remove Personal Web Parts
    Update Personal Web Parts
    You can further check here:
    SP 2013: http://technet.microsoft.com/en-us/library/cc721640.aspx
    Moss 2007: http://technet.microsoft.com/en-us/library/cc721640(v=office.12).aspx
    May be you edit the Contribute permission level, make sure its on its default.
    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

  • 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

  • Coexistence Exchange 2007 and 2013 - Clients on 2013 cant connect to Outlook, OWA works fine

    Hi
    We are currently running all our users on Exchange 2007. I've installed Exchange 2013 on another hardware following several guides on coexistence between 2007 and 2013.
    I'm now testing with a few test users I've migrated from 2007 to 2013.
    Everything was working fine until I messed up with something. It's either the certificates and/or Exchange Web Services and/or activating Outlook Anywhere.
    Now, all my tests users on Exchange 2013 can connect and send/receive emails on OWA, but Outlook clients cannot connect to Exchange server.
    When I start Outlook, I get the error Unable to open the default mail folders
    When I try to create a new Outlook profile, I get the error: "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
    When I click on Check Name, I get: "The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action" 
    Thanks for any help you could provide
    Martin

    Changed the
    ExternalClientAuthenticationMethod  for the 2007 server.
    Output for  Get-OutlookAnywhere | fl *method*
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    Now everytime I try to create an Outlook profile whose mailbox is on Exchange 2013 it's
    asking for credentials.
    If I dig further and try to manually configure server settings:
    If I specify the Exchange 2013 server and try a 'Check
    Name', it says: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
    If I specify the Exchange 2007 server and try a 'Check
    Name', the server changes for the fqdn of the 2013 server and it does resolve 'Check Name' process. Clicking on Next at this point completes the 'Add new e-mail account wizard". But is I try to start Outlook, I got an error saying "Microsoft Exchange is unavailable"
    Any other thoughts on this issue?
    Thanks,
    Martin

  • ActiveSync in Exchange 2007 and 2013 Coexistence

    Hi,
    I have exchange 2007 and 2013 coexisting (exchange 2007 sp3 update rollup 13/exchange 2013 SP1)
    owa works fine from inside and outside, only that it requires users to authenticate twice when connecting from the external.
    autodiscover works well for users on both 2007 and 2013
    I have a public SAN certificate from verisign with 2 names on it, mail.mydomain.com and legacy.mydomain.com
    I have A records configured for both names on my public DNS and internal DNS
    THE ISSUES
    testing activesync from testconnectivity.microsoft.com works fine when i run the test using a mailbox on Exch2013 but fails for mailbox on Exch2007.
    New users on exch2007 & exch2013 are not able to setup email on their devices (blackberry and windows mobile),
    Existing users on exch2007 can no longer receive mails on their mobile devices
    URLs
    Exchange 2007
    Exchange 2013
    Internal owa
    mydomain.com/owa
    mail.mydomain/owa
    External owa
    legacy.mydomain.com/owa
    mail.mydomain.com/owa
    AutoDiscover
    mail.mydomain.com
    mail.mydomain.com
    EWS
    legacy.mydomain.com
    mail.mydomain.com
    ECP
    mail.mydomain.com
    Internal ActiveSync
    legacy.mydomain.com
    mail.mydomain.com
    External ActiveSync
    $null
    mail.mydomain.com
    OutlookAnywhere
    legacy.mydomain.com
    mail.mydomain.com
    I expect that users on exch2013 would be able to setup their mobile devices as the connectivity test completes successfully but it still does not.
    Any help on this would be much appreciated ..
    Richard ..
    ..forever is just a minute away*

    You don't need to use a legacy URL for ActiveSync in Exchange 2013.  It will proxy ActiveSync for Exchange 2007 just fine.  In fact, ActiveSync is usually the protocol that gives you the least amount of trouble in a transition.  I recommend
    you configure your URLs for the proxy configuration and point everything to Exchange 2013 CAS.
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Differences between the 2007 and 2009 160GB Ipod Classic?

    What are the differences between the 2007 and 2009 160GB Ipod Classic?

    The 2009 model is slimmer. Click here for more information.
    (50305)

  • Can anyone explain the main differences between CRM 2007 and CRM 7?.

    Can anyone explain the main differences between CRM 2007 and CRM 7?.
    Does CRM 2007 use the WebUI?.
    Jason

    My fault for not putting my question forward correctly.
    I have worked with CRM 7 a few times now, but my experience has jumped me from CRM 5 straight to CRM 7, having never touched CRM 2007.
    I now have an opening to work on CRM 2007 so I was intrigued to know what it physically looked like. I assume it does not use the WebUI interface?.
    Jas

  • 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 2013 coexistence

    Hi,
    we have exchange 2007 and 2013 coexistence. we have created a new url for 2007 legacy servers. Now, when using OWA url (now set for exchange 2013 server)  i am getting OWA exchange 2007 login page for exchange 2007 mailboxs.
    I was expecting exchange 2013 OWA page and then redirection to OWA 2007.
    Thanks

    Hello,
    Please check your DNS configuration and ISA/TMG rules.
    We recommend you use TMG or UAG.
    You can refer to the "TMG rules" section in the following article:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Cara Chen
    TechNet Community Support

  • OWA Coexistence 2007 and 2013

    Hi
    We are currently coexisting exchange 2007 and 2013 servers. Everything works fine, except OWA from the external.
    Our domain is limocar.int. 
    Exchange 2007: exch2007
    Exchange 2013: exch2013
    On our internal DNS server, I've created legacy.limocar.int pointing to exch2007's IP address.
    Exch2013 internal OWA: https://exch2013.limocar.int/owa
    Exch2013 external OWA: https://mail.ourcompany.com/owa (where "ourcompany" is our company name) 
    EXCH2007 internal OWA was set to $NULL
    EXCH2007 external OWA: https://legacy.limocar.int/owa
    From the outside, I can log any 2013 users. But when I try to log a 2007 user, it changes the browser url to legacy.limocar.int, which indeed gives an error "The page cannot be displayed"
    What am I doing wrong? instead of using legacy.limocar.int, should I use legacy.ourcompany.com? If so I will ask our public DNS to create legacy.ourcompany.com
    Thanks for your help,
    Martin

    The legacy namespace is used not only for OWA.
    As Krishna mentioned, all OWA users will hit the Exchange 2013 OWA URL (ex. OWA.yourcompany.com). The Exchange 2013 will check where the user mailbox resides and if it is an Exchange 2007 MBX, it will use the legacy URL that is configured in Exchange 2007
    (ex. legacy.yourcompany.com) and silently redirect the clients to it.
    The reason you need to seriously consider using the same external and internal URL (***.youcompany.com) and avoid using internal FQDN or NetBIOS names is the so called BR v1:
    ===================================================
    Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates, Version 1.0
    BR 1.0 - Adopted by CA/Browser Forum (includes over 30 CA members and major browser vendors: Microsoft, Apple, Mozilla, Google, Opera)
    Effective as of July 1, 2012
    • CA SHALL NOT issue a certificate with an Expiry Date later than 1 November 2015 with a SAN or Subject Common Name field containing a Reserved IP Address or Internal Server Name.
    • Effective 1 October 2016, CAs SHALL revoke all unexpired Certificates whose SAN or Subject Common Name field contains a Reserved IP Address or Internal Server Name.
    ===================================================

  • Difference between CRM 2007 and CRM 7.0?

    Hi Gurus
    Whatu2019s the Difference between CRM 2007 and CRM 7.0?
    Whatu2019s the Difference between CRM 2007 and CRM 5.0?
    Thanks
    Kumar

    Hi Kumar,
    please have a look at this thread:
    What are differences between CRM 7.0 and CRM 2007?
    Chech out also the CRM Wiki:
    http://wiki.sdn.sap.com/wiki/display/CRM/CustomerRelationshipManagement
    Kind regards
    Hannes

  • Autodiscover Exchange Server 2007 and 2013 Coexistence

    Hello
    We are having some issues where some users are not being notified when their mailbox is being migrated to E2013.
    Before 2013, we never had a load balanced solution for CAS in Exchange Server 2007 or a single name space.
    Below is our current config
    AutoDiscoverServiceCN          : Server2K7CASpd
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {USChicago, UKLondon, SGSingapore}
    AutoDiscoverServiceCN          : Server2k7CASdr
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {USChicago, UKLondon, SGSingapore}
    AutoDiscoverServiceCN          : Server2013CASPD01
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASPD02
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASDR02
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASDR01
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    I believe that we should change the AutoDiscoverServiceInternalUri on the two 2007 CAS to ALSO be the same as our 2013 CAS.
    We know that when Outlook is opened, Autodiscover will respond with any of the 6 available CAS, and we think that those Outlook clients that are misconfigured, are those that are not getting notified when their Mailbox is moved to E2013.
    Thanks

    We are also getting inconsistent results using the Test-OutlookWebServices PS
    Test 1
    Test-OutlookWebServices -Identity [email protected] | fl
    Id      : 1003
    Type    : Information
    Message : About to test AutoDiscover with the e-mail address [email protected].
    Id      : 1006
    Type    : Information
    Message : The Autodiscover service was contacted at https://legacy.domain.local/Autodiscover/Autodiscover.xml.
    Id      : 1016
    Type    : Success
    Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
              time was 76 milliseconds.
    Id      : 1015
    Type    : Success
    Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
              time was 0 milliseconds.
    Id      : 1014
    Type    : Success
    Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.domain.local/UnifiedMessaging/Service.asmx.
              The elapsed time was 558 milliseconds.
    Id      : 1016
    Type    : Success
    Message : [EXPR]-Successfully contacted the AS service at https://legacy.domain.local/EWS/Exchange.asmx. The elapsed time
              was 46 milliseconds.
    Id      : 1015
    Type    : Information
    Message : [EXPR]-The OAB is not configured for this user.
    Id      : 1014
    Type    : Information
    Message : [EXPR]-The UM is not configured for this user.
    Id      : 1013
    Type    : Error
    Message : When contacting https://mail.domain.local/Rpc received the error The remote server returned an error: (404) Not
              Found.
    Id      : 1017
    Type    : Error
    Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.domain.local/Rpc. The elapsed time was 93
              milliseconds.
    Id      : 1006
    Type    : Success
    Message : The Autodiscover service was tested successfully.
    Id      : 1021
    Type    : Information
    Message : The following web services generated errors.
                  Contacting server in EXPR
              Please use the prior output to diagnose and correct the errors.
    Test 2
    Test-OutlookWebServices -Identity [email protected] | fl
    Id      : 1003
    Type    : Information
    Message : About to test AutoDiscover with the e-mail address [email protected].
    Id      : 1006
    Type    : Information
    Message : The Autodiscover service was contacted at https://legacy.Domain.local/Autodiscover/Autodiscover.xml.
    Id      : 1016
    Type    : Success
    Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
              time was 46 milliseconds.
    Id      : 1015
    Type    : Success
    Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
              time was 0 milliseconds.
    Id      : 1014
    Type    : Success
    Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.Domain.local/UnifiedMessaging/Service.asmx.
              The elapsed time was 15 milliseconds.
    Id      : 1016
    Type    : Success
    Message : [EXPR]-Successfully contacted the AS service at https://legacy.Domain.local/EWS/Exchange.asmx. The elapsed time
              was 78 milliseconds.
    Id      : 1015
    Type    : Information
    Message : [EXPR]-The OAB is not configured for this user.
    Id      : 1014
    Type    : Information
    Message : [EXPR]-The UM is not configured for this user.
    Id      : 1017
    Type    : Success
    Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://legacy.Domain.local/Rpc. The elapsed time was 187
              milliseconds.
    Id      : 1006
    Type    : Success
    Message : The Autodiscover service was tested successfully.

  • Single name space in between Exchange 2010 and 2013

    Hi,
    In my current environment I have 2 Exchange 2010 servers with DAG no CAS NLB. I installed Exchange 2013 with 2 CAS with WNLB and 2 Mailboxes with DAG. The main requirement is to configure Single name space to access in between Exchange 2010 and Exchange
    2013. On Exchange 2010 DAG there is a URL using is owa.domain.com and I also configured in Exchange 2013 all the virtual directories with this name owa.domain.com but having an issue that when I open explorer and use the owa.domain.com URL the user on Exchange
    2013 gets their mailbox but user on Exchange 2010 gets error HTTP 403 blank page.
    I observed that in Exchange Organization settings CAS settings one server OWA, ECP etc shows their internal external URL but the other server unable to open the OWA, ECP URL and give error message that "An IIS directory entry
    couldn't be created. The error message is Access is denied. HResult = -2147024891"
    Please guide how to resolve this issue and use the same name URL in Exchange 2010 and Exchange 2013
    Thanks, 

    Hi,
    See the below brief:
    User will connect to mail.contoso.com as his namespace endpoint. CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox version is 2010 and is located within the local AD site. CAS2013 will proxy the
    request to an Exchange 2010 Client Access server which will retrieve the necessary data from the Exchange 2010 Mailbox server
    Go through the full blog for better understanding of the redirection.
    Client Connectivity with Exchange 2013
    Hope you have changed your DNS records to direct connections only to your new Exchange 2013 server. You'll move the host names (for example, mail.contoso.com) users have been using to connect to Outlook Web Access, Autodiscover, and so on, from your
    Exchange 2010 server to your Exchange 2013 server. When an Exchange 2010 user tries to open their mailbox, the Exchange 2013 server will proxy their request and communicate with the Exchange 2010 server on their behalf.
    Configuring DNS includes the following:
    Change the primary host names, such as mail.contoso.com, autodiscover.contoso.com, and owa.contoso.com (if used) to point to the external, publically-accessible, IP address of the Exchange 2013 Client Access server with your public DNS provider.
    Change the primary host names, such as mail.contoso.com (or internal.contoso.com if you're using different internal host names) and owa.contoso.com (if used) to point to the internal machine name of the Exchange 2013 Client Access server on your internal
    DNS servers.
    NOTE- Go through the Exchange Deployemnt Assitant - Configure DNS Records section
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Difference between Scom 2007 and Scom 2012 Gateway server setup.

    Hi All,
    Greetings!!
    I would like to know the differences for gateway server setup in Scom 2007 and 2012 versions..
    Are there any changes in the data collection or in the configuration? and also the prerequisites for it.
    Please let me know these info..
    Regards,
    Gokul

    There is no great different in settng up gateway server in SCOM 2007 R2 and SCOM 2012. As summary, it requires
    1.Request certificates.
    2. Import those certificates into the target computers by using the MOMCertImport.exe tool.
    3. Distribute the Microsoft.EnterpriseManagement.GatewayApprovalTool.exe to the management server.
    4. Run the Microsoft.EnterpriseManagement.GatewayApprovalTool.exe tool to initiate communication between the management server and the gateway
    5. Install the gateway server.
    However, the prerequisites has different between SCOM 2007 R2 and SCOM 2012
    SCOM 2007 R2 gateway server support folloiwng OS
    Windows Server 2003 Standard Edition with Service Pack 1 (SP1)
    Windows Server 2003 Standard Edition with Service Pack 2 (SP2)
    Windows Server 2003 Standard x64 Edition with SP1 or SP2
    Windows Server 2003 Enterprise Edition with SP1
    Windows Server 2003 Enterprise Edition with SP2
    Windows Server 2003 Enterprise x64 Edition with SP1 or SP2
    Windows Server 2003 R2 Standard Edition with SP1 or SP2
    Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2
    Windows Server 2003 R2 Enterprise Edition with SP1 or SP2
    Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2
    Windows Server 2008 Standard 32-Bit with SP1 or SP2
    The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2
    Windows Server 2008 Enterprise 32-Bit with SP1 or SP2
    The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2
    Windows Server 2008 Datacenter 32-Bit with SP1 or SP2
    The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2
    Windows Server 2008 R2
    Windows Server 2008 R2 with SP1
    SCOM 2007 R2 gateway server
    CPU :2.8 GHz or faster
    Memory: 2 GB of RAM or more
    available Space: 20 GB of available hard disk space
    NET Framework 2.0
    Microsoft Core XML Services (MSXML) 6.0
    SCOM 2012 Gateway server
    Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
    Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 Core Installation or Windows Server® 2012 R2.
    Processor Architecture: must be x64.
    Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
    Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
    .NET Framework 4 is required if the Gateway server manages UNIX/Linux agents or network devices.
    Roger

  • Exchange 2007 and 2013 coexistance Problem

    We are in the process to migrate our current Exchange 2007 to Exchange 2013.
    Our environment is as follows:
    HT01= Hub CAS Server (Exchange 2007)
    MB1, MB2 = Mailbox CCR Cluster (Exchange 2007)
    CAS1= CAS Server (Exchange 2013)
    MBNew1, MBNew2 = Mailbox Servers (Exchange 2013)
    Emails for users that are on Exchange 2007 can send and receive external emails. But they cannot send emails to users that are on Exchange 2013.
    Users on Exchange 2013 can send/receive externally, send to Exchange 2007 users, but cannot receive emails from Exchange 2007 Users.

    Are you getting any NDR? Post it.
    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.

Maybe you are looking for