Outlook client in different subnet unable to connect to Exchange 2010 CAS using Windows 2008 R2 NLB multicast mode

Hi all,
need urgent assistance on the following issue
this is my Exchange 2010 setup
2 x CAS/Hub servers with HP network teaming, and load balanced using Windows NLB multicast mode. There are 2 VIPs on the NLB, one for outlook anywhere, one for autodiscover
2 DNS records were created for the 2 VIPs
Clients use Outlook Anywhere (HTTPS) to connect to the CAS servers from external segment via a Palo Alto firewall, which also acts as a layer 3 router
static arp was set on the Palo Alto firewall, with both virtual MACs pointing to the primary virtual MAC used by the NLB. 
Observations
1. within same segment - no issue accessing Exchange servers, even when one CAS node is offline
2. external segment (via firewall)
a. when both nodes are up
outlook client able to connect to Exchange CAS VIP on 443, but will disconnect after around 30 seconds. Client will retry and the pattern will repeat
Exchange CAS RPC logs shows client connections and disconnections to the outlook anywhere VIP address
Firewall logs shows allowed traffic from client to the VIPs
unable to complete profile creation
b. with only CAS2 (CAS1 stopped/deleted from NLB cluster)
no issues accessing Exchange servers, creating profiles etc
c. with only CAS1
same behaviour as (a)
reinstalled NLB, but doesn't resolve
deleted CAS1 from NLB cluster, and re-add. issue remain
Q1. is teaming supported? Teaming is currently set to automatic mode, instead of specified Fault Tolerant
Q2. are there additional settings we need to set or verify on the Palo Alto firewall, since the issue only happen to external segment? Thanks!

Yes - I've been scarred with this for many years :(
If it is just CAS 1 that is causing issues, then focus in on that.  The support statement for Win 2008 R2 is that NLB is still a 3rd party component and support may ask for it to be disabled.
http://support.microsoft.com/kb/278431 
Does CAS1 and CAS2 have the same NICs (firmware as well), driver, teaming software, and teaming config? 
I also want to ask what the network team did for configuring the switch ports on the servers?  This will vary from vendor to vendor  - did they do the same config on both?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne 
Twitter:   LinkedIn:
  Facebook:
  XING:
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.
Thanks Rhoderick, issue still persists
can you also help clarify what you meant by "configuring the switch ports on the servers"?
thanks again

Similar Messages

  • [Forum FAQ] "Unable to connect to the server by using Windows PowerShell Remoting" error while installing RDS roles on Server 2012 R2

    When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
    “Unable to connect to the server by using Windows PowerShell remoting”.
    Figure 1: Unable to connect to the server by using Windows PowerShell remoting
    First of all, we need to verify the configurations as it suggested:
    1. The server must be available by using Windows PowerShell remotely.
    2. The server must be joined to a domain.
    3. The server must be running at least Windows Server 2012 R2.
    4. The currently logged on user must be a member of the local Administrators group on the server.
    5. Remote Desktop Services connections must be enabled by using Group Policy.
    In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
    To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
    Enable-PSRemoting -Force
    Figure 2: Enable PowerShell Remoting
    However, if issue persists, we need to check whether it has enough memory to work.
    By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase
    the memory via the PowerShell command below:
    Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
    Then, you need to restart the server and the issue should be resolved.
    You can get more information regarding Remote Troubleshooting by below link:
    about_Remote_Troubleshooting
    If you need further assistance, welcome to post your questions in the
    RDS forum.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    i found another possible reason, this solution worked for me:
    http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
    I tried to set up powershell remoting on a server and kept getting this error:
    Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann
    ot process the request. It cannot determine the content type of the HTTP response from the destination comput
    er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to
    pic.
    After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very
    many security groups or in my case because of the SidHistory attribute.
    The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters
    If the keys does not exists you can create them, be sure to use the DWORD type.
    I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved.

  • Outlook 2007 on XPsp2 OEM unable to connect to Exchange Server 2003??

    Hi
    My outlook 2007 came part and package of the Microsoft Office 2007 Enterprise Edition, and our SBS server runs Exchange 2003.
    After setting up the connection in Outlook to connect too Exchange (when clicking test (check name) on configuration it is successful) --
    The Error Message is so upon start up :
    Cannot Open your Default e-mail Folders, You must connect to microsoft exchange with the current user profile before you can synchronize your folders with your offline folder file..
    When disabling the cached exchange mode the error message changes however, but it is still unable too actually open outlook.
    Cannot open your default E-Mail Folders. The Attempt too log on to the exchange server failed... (after in the configuration the test suceeded.)
    The computer has a fresh copy of XP SP2 OEM, as well as Microsoft Outlook, only other software on is SQL server 2000 (All microsoft Updates installed). The active user is domain controlled and has the same credentials as is used by Exchange.
    After selecting the checkbox under Control Panel -> Mail -> ......... "User Identification" -> Always prompt for login credentials no change is made to this error....
    I then disabled the use of offline folders..... "could not open your default email folders. The information store could not be opened"
    Please provide assistance in any way possible.... ASAP as well if possible.
    Thanks a lot
    Marc

    GedMarc,
    I had all the same problems you had, and did the exact same things you did to no avail.
    This is what solved my problem:
    http://support.microsoft.com/kb/913843
    1.
    Click Start, click Run, type regedit in the Open box, and then click OK.
    2.
    Locate and then click the following subkey:
    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC
    3.
    On the Edit menu, point to New, and then click DWORD Value.
    4.
    Type DefConnectOpts, and then press ENTER.
    5.
    Right-click DefConnectOpts, and then click Modify.
    6.
    In the Value data box, type 0, and then click OK.
    7.
    Exit Registry Editor.
    Best regards,
    T

  • Unable to connect to Exchange 2010 Management console after - Exchange 2010 SP3 Rollup 7

    We have been having issue with our Exchange Server 2010's Transport Service failing due to a database corruption. I was hoping that maybe applying the Roll-up 7 for Exchange might fix this issue, however after applying the patch we are unable to start the
    MSExchangeMailboxAssistants "Error 1053: The service did not respond to the start or control request in a timely fashion."
    Then I notice that we were unable to connect to the Management Console or through PowerShell. 
    Event 1000, Application Error
    Faulting application name: MSExchangeMailboxAssistants.exe, version: 14.3.210.2, time stamp: 0x53e2bf34
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
    Exception code: 0xe0434f4d
    Fault offset: 0x000000000000940d
    Faulting process id: 0x%9
    Faulting application start time: 0x%10
    Faulting application path: %11
    Faulting module path: %12
    Report Id: %13
    PowerShell error:
    Exception calling "TryLoadExchangeTypes" with "2" argument(s): "Could not load file or assembly 'Microsoft.Exchange.Man
    agement, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name va
    lidation failed. (Exception from HRESULT: 0x8013141A)"
    At C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1:75 char:92
    + $typeLoadResult = [Microsoft.Exchange.Configuration.Tasks.TaskHelper]::TryLoadExchangeTypes <<<< ($ManagementPath, $t
    ypeListToCheck)
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : DotNetMethodException

    Hi,
    Please try the following steps to narrow down the issue:
    1. Uninstall and reinstall .NET package in Exchange server.
    2. Under location C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG, took a copy of Machine.Config.default, renam it to Machine.config and copy it under this path again.
    3. Do IIS reset by running iisreset from a Command Prompt window.
    4. Reboot the server and verify whether the Exchange services are started.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Windows XP SP3 and Outlook 2010 can't connect with Exchange 2010 or Exchange 2013

    XP+SP3+Outlook 2010 can't connect to Exchange 2010&2013 in the internal network without safe mode.

    Hi,
    Did you get any error messages?
    Do you have Outlook Anywhere and autodiscovery set up properly?
    Can you ping the Exchange server?
    Please use Test Email AutoConfiguration
    to test if the Autodiscover service is configured properly. See:
    https://hosting.intermedia.net/support/kb/default.asp?id=2150
    We can also use the remote connectivity analyzer to troubleshoot the issue:
    https://testconnectivity.microsoft.com/
    In addition, turn off your firewall and anti-virus to check the result.
    Hope this helps.
    Best Regards,
    Steve Fan
    TechNet Community Support

  • Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

    Hi all ,
    on my side i would like to clarify few queries.
    Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
    Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
    the autodiscover service to exchange 2013 during coexistence.
    When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
    reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
    Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
    I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
    Internal Outlook Connectivity
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
    Please share me your suggestions and that would help me a lot .
    Regards
    S.Nithyanandham

    Hi Winnie Liang ,
    Thanks a lot for your reply.
    Scenario  1 : for internal outlook connectivity 
    We have below settings for exchange 2010 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
    We are going to have below settings for exchange 2013 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
    During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
    So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
    Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
    servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
    get it updated on user profile.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
    Scenario 2: For exchange services
    mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    What about the above services will it get affected during whole exchange 2013 environment failure ?
    Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

    Greetings!  I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
    I am running into some odd behavior.  Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I  receive errors.  OWA works just fine for these Exchange
    2010 mailboxes, it is just Outlook that has the problem.  This is what I am running into:
    1. Outlook uses autodiscover to locate server settings.  It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
    2. It then gives me the settings box for Exchange server and Mailbox.  This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role).  If I then change the server to the Exchange 2010 CAS server,
    and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
    3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
    I've been doing as much research on this as I can.  I've tried disabling IPv6 to no avail.  It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards. 
    Any suggestions?  Thanks in advance!

    Hi,
    Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
    You can use your original SSL Cert for your new Ex 2013 environment.
    In dns you want two host A records: mail.domain.com and autodiscover.domain.com
    On your 2013 set your internal and external virtual directories to mail.domain.com
    leave autodiscover and Powershell alone.
    Also set the autodiscover URI to your Certificate name ie. mail.domain.com
    Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
    Thanks.  I wanted to give some additional info before I run any commands.  I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP.  I have a 3 entries for mail.domain, for DNS round robin; basically
    it is listed 3 times for the IP of each of my Exchange 2013 servers.  Does any of this sound problematic?

  • Sir you have replied for my question, and i updated my software and all those things, yet it is showing unable to connect network, but i can use internet by sim, is it the problem related with hardware? can you tell me a solution for it?

    sir you have replied for my question, and i updated my software and all those things, yet it is showing unable to connect network, but i can use internet by sim, is it the problem related with hardware? can you tell me a solution for it?

    you seem to be referring to an ongoing issue
    click here to respsond -> sir help me to enable my network connection, my iphone 4s is not connecting with any wireless connection, what i should do for enabling network connection?
    CCC

  • TCP packet out of state: First packet isn't SYN & Outlook is trying to retrieve data from the Microsoft Exchange Server [CAS-ARray]

    We are transitioning from Exchange 2003 to Exchange 2010.  We found Outlook online mode (non-cached mode) have many warning "Outlook is trying to retrieve data from the Microsoft Exchange Server [CAS-ARray]", usually happen when users tried to open
    address book but sometimes even normal operation like click the Send button.  The problem does not affect OWA and extremely rare when Outlook is running in cached mode.  Check the firewall logs, we notice a lot of "TCP Packet Out of State" drops.
    We have a lot from the CAS/HT to DC/GC on TCP_3268 and LDAP.  And the errors are "TCP packet out of state: First packet isn't SYN" with tcp_flags FIN-ACK, PUSH-ACK.
    We also have a lot from CAS/HT to the Outlook Clients on the static RPC port (TCP_59933).   And the errors are "TCP packet out of state: First packet isn't SYN" with tcp_flags FIN-ACK, PUSH-ACK and RST-ACK, ACK.
    This happens even on Outlook 2010 which I though it has TCP Keep Alive implmented to keep the session active within 1 hour. 
    Can somebody tell me if these out-of-state are the cause of our problem?  And how to fix it?
    THANK 1,000,000

    Hello AndyHWC,
    I did some consulting with our CAS team and received the following feedback to your post:
    It is difficult to determine what is causing resets without seeing the captures first hand however, the concern is that you are seeing dropped packets on the firewall logs.  Where is this firewall located?
    Based on the description "Check the firewall logs, we notice a lot of "TCP Packet Out of State" drops." and "We have a lot from the CAS/HT to DC/GC on TCP_3268 and
    LDAP." indicates to me that the firewall is between CAS and GC.  This not supported under any circumstances and would explain the issue they are seeing with clients trying to "retrieve data from the GC".
    If there is not a firewall between the GC and CAS then a Microsoft support engineer would need to have concurrent Netmon Captures from client, CAS, GC during the
    issue to analyze.  If only one GC exists consider adding another GC to handle the client requests and for fault tolerance.
    Also verify that all NIC card drivers are updated to the latest driver version
    More information about firewalls with Exchange 2007/2010
    http://msexchangeteam.com/archive/2009/10/21/452929.aspx
    http://technet.microsoft.com/en-us/library/bb232184(EXCHG.80).aspx
    You can install the Client Access server role on an Exchange 2007 computer that is running any other server roles except for the Edge Transport server role. You
    cannot install the Client Access server role on a computer that is installed in a cluster. Installation of a Client Access server in a perimeter network is not supported.
    http://technet.microsoft.com/en-us/library/dd577077(EXCHG.80).aspx
    “The Installation of a Client Access Server in a Perimeter Network Is Not Supported
    Issue You may want to install an Exchange 2007 Client Access server in a perimeter network. However, this type of installation is not supported in Exchange
    2007.
    Cause The Exchange 2007 Client Access server role is not supported in any configuration in which a firewall is located between the Client Access server
    and a Mailbox server or a domain controller. This includes firewall devices, firewall programs, or any program or device that is designed to restrict traffic between two network locations.
    For correct operation, Client Access servers require typical domain connectivity to domain controllers and global catalog servers. Because any devices
    or programs that restrict or reduce access to domain controllers or global catalog servers may affect the correct operation of the Client Access server, we do not support this type of configuration.
    Resolution To resolve this issue, move the Client Access servers to the internal network. For more information about the ports that Exchange 2007 uses
    for various services, see Data Path Security Reference.”
    Thanks,
    Kevin Ca - MSFT
    Kevin Ca - MSFT

  • Error connecting to the SAP SRV on Windows 2008 Server platform

    Hi All
    We have a problem with one of our clients they bought a new sbs windows server 2008 and we loaded sql 2005 and sap b1 SP01 PL07.
    When we did the SBO install we experience connection issues and we created odbc connection on the server using named pipes and tcp/ip (used both server name and Ip address).
    We also configured the server in configuration manager and we managed to login and solved the slow system connection issue. We also created odbc connection on the client machines. (Machine are on a workgroup and users have administration access on all machines),we also installed native client on all machines.
    After the first batch of client installs we managed to have connection, they were other computers which were left out during the first client install and now the client want to do the remaining machines connected to SBO. On every machine that we install now we get the same error :-
    *Connection failed:
    SQLState:'08001'
    SQl Server error:10060
    [Microsoft][SQL Native Client] TCP Provider: A connection attempt failed because the connected party didnot properly repsond after a period of time, or established connection failed because connected host has failed to respond.
    Connectioin failed:
    SQLState:'HYT00'
    SQL Server Error:0
    [Microsoft][SQL Native Client]Login timeout expired
    Connection failed:
    SQLState:'08001'
    SQL Server Error: 10060
    [Microsoft][SQL Native client] An error has occurred while establishing a connection to the server. When connecting to the sql server 2005, this failure may be cause by the that*
    Please help as most user who need access can't login and they are the main users.
    rgds,
    Bongani Dlamini

    Hi Eric,
    yes we are using Windows 2008 SBS for the SAP EHP4 FOR SAP ERP 6.0/NW7.01 installation.
    we tried to create the key but it says access is denied.
    Actual thing is we got the server with Windows 2008 server 64 bit SBS (standard FE) with Domain Controller (DC) configuration.
    We have removed the DC using dcpromo to convert into Wokgroup and tried the SAP installation.
    I hope you got the idea and please let me know any further suggestions or it is the problem with the license.
    Thanks & Regards,
    Prabhu Reddy.

  • Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

    Hi Team,
    I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
    Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
    open and throws an error of some "cannot open set of folders".
    Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
    Kindly share some KB or tip. Any help is appreciated. Thank You.
    Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

    I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    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.

  • Unable to uninstall last Exchange 2010 server

    Hi,
    I am unable to uninstall last Exchange 2010 server from the organization.
    I get error message:
    Summary: 3 item(s). 2 succeeded, 1 failed.
    Elapsed time: 00:00:19
    Configuring Prerequisites
    Completed
    Elapsed Time: 00:00:00
    Mailbox Role Prerequisites
    Failed
    Error:
    Uninstall cannot continue. Database 'Mailbox Database 2105185066': This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, or arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox
    -Database <Database ID>. To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive. To get a list of all
    arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. To disable
    an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID> -Archive. Arbitration mailboxes should be moved to another server; to do this, run the command New-MoveRequest <parameters>. If this is the
    last server in the organization, run the command Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox. Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan
    <MailboxPlan ID> -Database <Database ID>.
    Click here for help...
    http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=4a96fd69-9cec-4a48-9571-5c9e8ab3cfe9
    Elapsed Time: 00:00:15
    Organization Prerequisites
    Completed
    Elapsed Time: 00:00:03
    I have deleted all the mailboxes, distribution groups, contacts, etc. but I am still unable to uninstall one database. When trying to delete the last database I get following error message:
    The mailbox database 'Mailbox Database 2105185066' cannot be deleted.
    Mailbox Database 2105185066
    Failed
    Error:
    This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, or arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database <Database ID>. To get a list of all mailbox plans
    in this database, run the command Get-MailboxPlan. To get a list of archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox
    -Database <Database ID> -Arbitration. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the
    command Disable-Mailbox <Mailbox ID> -Archive. Arbitration mailboxes should be moved to another server; to do this, run the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command Disable-Mailbox <Mailbox
    ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox. Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID> -Database <Database ID>.
    If I run command "Get-Mailbox -Database "Mailbox Database 2105185066" -Arbitration | ft -Wrap -Auto", I get following result:
    Name                                               
    Alias                                              
    ServerName Prohibit Send Quota
    SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} ex01       unlimited
    FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 ex01       1 MB (1,048,576bytes)
    I suspect it is because of these "maiboxes" why I am unable to delete the database.
    If I run command "Disable-Mailbox SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} -Arbitration -DisableLastArbitrationMailboxAllowed ", I get following error message:
    A positional parameter cannot be found that accepts argument 'e0dc1c29-89c3-4034-b678-e6c29d823ed9'.
        + CategoryInfo          : InvalidArgument: (:) [Disable-Mailbox], ParameterBindingException
        + FullyQualifiedErrorId : PositionalParameterNotFound,Disable-Mailbox
    Do you have any ideas how to delete the last database and uninstall the last Exchange 2010 server properly from the organization?
    Best regards,
    Toni
    www.triuvare.fi

    Hi,
    I agree with Martina. This should be solved somehow without need to use ADSI Edit.
    Martina, I did run the command you suggested (Get-mailbox -arbitration | disable-mailbox -DisableLastArbitrationMailboxAllowed), but unfortunately here is the result:
    The operation couldn't be performed because object 'Company.local/Users/SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}' couldn't be found on 'DC.Company.local'.
        + CategoryInfo          : InvalidData: (Company.local/U...8-e6c29d823ed9}:MailboxIdParameter) [Disable-Mailbox], ManagementObjectNotFoundException
        + FullyQualifiedErrorId : 63BA19E1,Microsoft.Exchange.Management.RecipientTasks.DisableMailbox
    The operation couldn't be performed because object 'Company.local/Users/FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042' couldn't be found on 'DC.Company.local'.
        + CategoryInfo          : InvalidData: (Company.local/U...bf-00a95fa1e042:MailboxIdParameter) [Disable-Mailbox], ManagementObjectNotFoundException
        + FullyQualifiedErrorId : 4002E2C8,Microsoft.Exchange.Management.RecipientTasks.DisableMailbox
    Connection between the Exchange server and the Domain Controller (DC.Company.local) is working.
    Best regards,
    Toni
    www.triuvare.fi

  • Exchange 2013 CAS server connection to Exchange 2010 Mailbox server

    Hi Guys,
    I have a quick question i am planning to upgrade my infra from Exchange 2010 to Exchange 2013 and i have come across a small question, my infra looks likes below
    3 Exchange server (CAS+ HT + MBX roles) Exchange 2010
    1 Exchange server MBX role For journlaing Exchange 2010
    1 CAS for internet owa access Exchange 2010
    Now i will be  installing exchange 2013 CAS on 2 box and MBX on 3 box 
    will decomm the 3 exchange box which has (CAS+ HT + MBX roles) and 1 CAS which we use for owa access.
    will keep the Journaling server as it is will not be decomming it as of now.
    My question is is will i be able to connect to the journaling mailbox's which are hosted on exchange 2010 journaling server without actually having any 2010 cas server, will exchange 2013 cas directly help me to connect to the journal mailbox or would i need
    to add CAS role on Exchange 2010 journaling server and enable outlook anywhere configure the directories with the url's to make it working.
    Please suggest on the same.
    BR/Deepak

    Hi TheLearner,
    Thank you for your question.
    Exchange 2013 didn’t connect to the journal mailbox directly when we access it by outlook/OWA. The journal mailbox will connect the former Exchange 2010 CAS. Or we could migrate Journaling mailbox to Exchange 2013. Because Exchange 2010  could communicate
    with Exchange 2010 by RPC, but Exchange 2013 could communicate with Exchange 2013 by HTTPS.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    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]
    Jim Xu
    TechNet Community Support

  • How other email server (sendmail) will make connection to Exchange 2010 mutli role server.

    Hi,
    We have 2 Exchange 2010 multi role server and one load balancer for Cas array.
    Now we do understand that DAG will be using for database and CAS can be in HA mode via Load balancer.
    Now question is, we do have other non-microsoft email server with same smtp address so when this sendmail server will try to make connection to exchange 2010, which server name/ip we need to give them.
    Will it be DAG ip/name or do we need to give both server IP.
    Amit Rawat | MCITP - Exchange 2007/2010| CCNA |MCSE- 2003| Lync 2010|http://blog.amitrawat.net

    you can use whatever Ip's are listening on port 25 on the 2010 hub transports. 
    If your load balancer is listening on port 25 and balancing that (probably only a https loadbalancer?) you can use that ip.
    If not you can put your 2 cas server IP's in the smart host connector from the sendmail box.
    It certainly wont be the DAG ip as the mailbox role has nothing to do with the hub transport.
    Foremost i don't have separate CAS here, I do have 2 Exchange(cas/HT/MBX) and DAG is configured.
    when sendmail send email to Exchange i need to use some common smtp address to point these servers, so that if one goes down sendmail server can still make connection via that common name.
    i can not put two name space(since these 2 exchange are HT server as well) for sendmail server. Any suggestion .
    Amit Rawat | MCITP - Exchange 2007/2010| CCNA |MCSE- 2003| Lync 2010|http://blog.amitrawat.net

  • Dynamic CRM connect outlook Client with different domain

    Hi Guys,
    I had installed CRM 2011 in cloud with different domain.
    If I use browser is working fine just that when i use Outlook client it show 
    15:24:16|  Error| Exception : The request for security token could not be satisfied because authentication failed.    at System.ServiceModel.Security.SecurityUtils.ThrowIfNegotiationFault(Message message, EndpointAddress target)
       at System.ServiceModel.Security.SspiNegotiationTokenProvider.GetNextOutgoingMessageBody(Message incomingMessage, SspiNegotiationTokenProviderState sspiState)
    I found that is because you must connect to the same domain.
    any idea that i can use my Outlook client to connect to CRM 2011 without changing my domain?
    Regards,
    Kim

    Yes - I've been scarred with this for many years :(
    If it is just CAS 1 that is causing issues, then focus in on that.  The support statement for Win 2008 R2 is that NLB is still a 3rd party component and support may ask for it to be disabled.
    http://support.microsoft.com/kb/278431 
    Does CAS1 and CAS2 have the same NICs (firmware as well), driver, teaming software, and teaming config? 
    I also want to ask what the network team did for configuring the switch ports on the servers?  This will vary from vendor to vendor  - did they do the same config on both?
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    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.
    Thanks Rhoderick, issue still persists
    can you also help clarify what you meant by "configuring the switch ports on the servers"?
    thanks again

Maybe you are looking for