2 Exchange 2013 Cas and mailbox on both in defferant ad sites with multiple main domains

Hi
I have 2 Exchange servers in a single AD forest. Mail1 and mail2
2X 2012 R2 Dc's
There are 2 AD sites Site 1 and site 2
Site 1 = DC1 and Mail 1
Site 2 = DC2 and Mail2
One exchange organisation
2 email external domains = domain1.com and domain2.com
2 wildcard certs *.domain1.com on mail1 and *.domain2.com on mail2
2 different Internet connections one for site 1 and other for site 2 and 2 external Ip address's
Requirements where to split the servers so that domain1.com users send form a different IP address than those of domain2.com. This has been done and works fine by simply setting a exchange connection cost of 100.
Domain1.com users live on mail1 MD1 and domain2.com users are on Mail2 MD2
I am facing an issue on how to connect outlook anywhere so that users in the 2 domains are connecting to their own exchange servers and outlook anywhere will work with autodiscover.
At the moment I have set the outlook provider to domain1.com and this work fine but outlook anywhere will not work for domain2.com
I have only come up with an idea to requester a 3rd mutual domain and then issue a SAN cert that would have all 3 domains in set the outlook provider to domain3.com it and then direct the outlook anywhere users to use the new domain to connect their outlook
anywhere clients with.
I don't think the client is going to go for this as he wants the names to be separate .
Any help would be appreciated

The EXPR provider is a global setting.
Since you are doing this
"2 wildcard certs *.domain1.com on mail1 and *.domain2.com on mail2"
Can you not get both onto the same cert?  Though accessing a SAN entry on a cert will not work for clients older that Vista SP1.
Alternatively use a generic name.  That is what hosting companies do.  Dedicated hosting is not really multitenant before that comes up :)
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.

Similar Messages

  • Exchange 2013 Database and Mailbox sizing configuration feedback?

    Hello,
    I am in the process of deploying Exchange 2013 in our environment, it will co-exist with Exchange 2010 until we move everyone over to the new server.
    My question is regards to the disk storage design, we have a SAN that Exchange will share with the rest of our Virtual Machines. I plan to have 20 live databases and 20 archive databases so I can balance out mailboxes per database so that each db is roughly
    100GB in size.
    The goal is is to keep the size down so that any database specific maintenance can finish quicker and if I ever had to deal with db corruption it is faster to restore, backup, etc.
    My question is, is there a lot of overhead I will be adding onto the Exchange server by having 40 databases mounted?
    Currently 300 users, 3.5TB in exchange databases between live and archive mailboxes (no mailbox caps), with 40 databases (20/20) it spreads out nicely with roughly 15 users per db, and db size is roughly 100GB. 
    My concern is having 40 databases mounted on a single EXCH2013 multi-role server? We have no DAG, etc.
    The machine is a 4vCPU/32GB and the disks are on a Compellent tiered SAN shared among other VMs.
    Thanks.

    Hi,
    It depends on various things. I would suggest you to start with Server Role Requirement Calculator to see your hardware is sufficient to handle the load or not...
    http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
    http://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Exchange 2013 CAS-MBX recipient validation rejects entire message if any of recipients are invalid

    Hi,
    How can I enable recipient validation work in this design:
    2 Exchange 2013 servers with CAS and MAILBOX roles both, DAG and Hardware Load balancer for HTTP and SMTP traffic.
    From Exchange documentation:
    http://technet.microsoft.com/en-us/library/bb125187%28v=exchg.150%29.aspx
    Although the Recipient Filter agent is available on Mailbox servers, you shouldn't configure it. When recipient filtering on a Mailbox server detects one invalid or blocked recipient in a message that contains other valid recipients, the message is rejected.
    If you install the anti-spam agents on a Mailbox server, the Recipient Filter agent is enabled by default. However, it isn't configured to block any recipients. For more information, see
    Enable Anti-Spam Functionality on Mailbox Servers.
    If You have a setup like this:
    Install antispam agents:
    Identity Enabled Priority
    Transport Rule Agent True 1
    Malware Agent True 2
    Text Messaging Routing Agent True 3
    Text Messaging Delivery Agent True 4
    Content Filter Agent True 5
    Sender Id Agent True 6
    Sender Filter Agent True 7
    Recipient Filter Agent True 8
    Protocol Analysis Agent True 9
    Have Recipient validation enabled:
    Name                  Enabled RecipientValidationEnabled----                  ------- --------------------------RecipientFilterConfig    True                      True
    Have AcceptedDomain AddressBook enabled:
    DomainName DomainType AddressBookEnabled
    contoso.com Authoritative True
    Then You have a situation, where a single invalid recipient on an incoming email message would reject the entire message! I guess this is because the recipient filtering happens on the mailbox server.
    So .. HOW? Is it possible without Edge servers? Have I missed something?
    I hope this feature isn't "missing by design", because it will be very difficult to explain to the client, that such an expensive product cannot do what any mail server can - reject unknown recipients before taking E-Mail data. There are a lot
    of issues with this feature missing (possible DDOS with max attachments, or spoofed sender e-mail address that is a spamtrap, so NDR from Exchange would get You to SBL, etc.).
    Sincerely,
    Vince

    Hello Vince,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    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

  • Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

    I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
    1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
    on our system".
    2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
    I've followed this post as a guide but it hasn't resolved my issue.
    https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
    My Exchange environment looks like this:
    Site 1:
    exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
    exch2 - CAS/Mailbox, part DAG13
    exch3 - CAS/Mailbox, part of DAG13
    Site 2:
    exch2dr - CAS/Mailbox, part of DAG13
    exch3dr - CAS/Mailbox, part of DAG13
    DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
    Any help is greatly appreciated. I'd love to get rid of Unity. 
    EDIT:
    I just found this event in the event logs:
    The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
    but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

    9.1.2 I think it is, we upgraded to avoid the known DNS bug
    I cant see how to PM you either
    The crux of it was outlined below with some tweaks
    http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
    As we have multiple combined role servers, our trunks are set up as follows:
    1. 1 x CAS Trunk - contains all CAS Servers on port 5060
    2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
    On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
    Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
    Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
    as any other CAS based service - point to 2013, and it will handle the rest

  • Exchange 2013 CAS incorrectly proxying after mailbox move to Exchange 2013

    Hi,
    I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
    on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
    other clients are working.
    This time I move another user this time it did not work for 3.5hrs.  I had to reboot Exchange 2013 CAS server after that it worked.
    There is must be something that is not refreshing on Exchange 2013 CAS server.  
    Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move.  Currently we are in Pilot mode and only moving few
    mailboxes at a time.
    Thanks,
    Raman

    Hi,
    I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
    on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
    other clients are working.
    This time I move another user this time it did not work for 3.5hrs.  I had to reboot Exchange 2013 CAS server after that it worked.
    There is must be something that is not refreshing on Exchange 2013 CAS server.  
    Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move.  Currently we are in Pilot mode and only moving few
    mailboxes at a time.
    Thanks,
    Raman
    Does simply recycling the ActiveSync app pool speed things up?
    Also, I would recommend installing CU6 instead of SP1.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • 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

  • Some Outlook clients getting internal FQDN of newly installed Exchange 2013 CAS server as Outlook Anywhere Proxy address

    Hello Folks,
    I have this problem and is making me crazy if anyone have any idea please shed some light on this:-
    1. Working Outlook 2010 and 2013 clients with webmail.xyz.com as Outlook Anywhere proxy address.
    2. Installed new Exchange 2013 server (server02)with CAS and Mailbox role, Exchange install wizard finished and server is rebooted.
    3. Server came up online started changing internal and external FQDN's of Virtual Directories and Outlook Anywhere to webmail.xyz.com
    4. As soon as Fqdn's changed some outlook clients create support request that Outlook suddenly white's out and after reopening it is giving error  cannot connect to exchange. upon checking Clients Exchange Proxy address is set to http://server02.xyz.com,
    even though OA/OWA/ECP/OAB/EWS/Autodiscover/ActiveSync FQDN's Point to webmail.xyz.com, on all servers if i create new outlook profile for same user it picks up correct settings through autodiscover and connects fine, this is happening to about 20% of outlook
    clients every time i am introducing new Exchange 2013 server in Organization. we have around 2000 users and planning on installing 4 exchange servers to distribute load and everytime changing outlook profile of close to 150-200 users is not possible.
    Any help is greatly appreciated.
    Thanks
    Cool

    Here are the EXCRA results
    Here IP (x.x.x.x) returned is my Load Balancer IP (Webmail.xyz.com).    
    Connectivity Test Successful with Warnings
    Test Details
         Testing Outlook connectivity.
         The Outlook connectivity test completed successfully.
              Additional Details
         Elapsed Time: 9881 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
         Autodiscover was tested successfully.
              Additional Details
         Elapsed Time: 2063 ms.
              Test Steps
              Attempting each method of contacting the Autodiscover service.
         The Autodiscover service was tested successfully.
              Additional Details
         Elapsed Time: 2063 ms.
              Test Steps
              Attempting to test potential Autodiscover URL https://xyz.com:443/Autodiscover/Autodiscover.xml
         Testing of this potential Autodiscover URL failed.
              Additional Details
         Elapsed Time: 186 ms.
              Test Steps
              Attempting to resolve the host name xyz.com in DNS.
         The host name couldn't be resolved.
           Tell me more about this issue and how to resolve it
              Additional Details
         Host xyz.com couldn't be resolved in DNS InfoNoRecords.
    Elapsed Time: 186 ms.
         Attempting to test potential Autodiscover URL https://autodiscover.xyz.com:443/Autodiscover/Autodiscover.xml
         Testing of the Autodiscover URL was successful.
              Additional Details
         Elapsed Time: 1876 ms.
              Test Steps
              Attempting to resolve the host name autodiscover.xyz.com in DNS.
         The host name resolved successfully.
              Additional Details
         IP addresses returned: x.x.x.x
    Elapsed Time: 338 ms.
         Testing TCP port 443 on host autodiscover.xyz.com to ensure it's listening and open.
         The port was opened successfully.
              Additional Details
         Elapsed Time: 173 ms.
         Testing the SSL certificate to make sure it's valid.
         The certificate passed all validation requirements.
              Additional Details
         Elapsed Time: 318 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.xyz.com on port 443.
         The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
              Additional Details
         Remote Certificate Subject: CN=webmail.xyz.com, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US.
    Elapsed Time: 219 ms.
         Validating the certificate name.
         The certificate name was validated successfully.
              Additional Details
         Host name autodiscover.xyz.com was found in the Certificate Subject Alternative Name entry.
    Elapsed Time: 1 ms.
         Certificate trust is being validated.
         The certificate is trusted and all certificates are present in the chain.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05,.
         One or more certificate chains were constructed successfully.
              Additional Details
         A total of 1 chains were built. The highest quality chain ends in root certificate CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign,
    Inc.", C=US.
    Elapsed Time: 36 ms.
         Analyzing the certificate chains for compatibility problems with versions of Windows.
         Potential compatibility problems were identified with some versions of Windows.
              Additional Details
         The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature
    isn't enabled.
    Elapsed Time: 5 ms.
         Testing the certificate date to confirm the certificate is valid.
         Date validation passed. The certificate hasn't expired.
              Additional Details
         The certificate is valid. NotBefore = 1/3/2013 12:00:00 AM, NotAfter = 11/16/2015 11:59:59 PM
    Elapsed Time: 0 ms.
         Checking the IIS configuration for client certificate authentication.
         Client certificate authentication wasn't detected.
              Additional Details
         Accept/Require Client Certificates isn't configured.
    Elapsed Time: 289 ms.
         Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
         The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
              Additional Details
         Elapsed Time: 756 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.xyz.com:443/Autodiscover/Autodiscover.xml for user [email protected].
         The Autodiscover XML response was successfully retrieved.
              Additional Details
         Autodiscover Account Settings
    XML response:
    <?xml version="1.0"?>
    <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
    <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
    <User>
    <DisplayName>Test Exch1</DisplayName>
    <LegacyDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1</LegacyDN>
    <DeploymentId>4ec753c9-60d9-4c05-9451-5b24e2d527a7</DeploymentId>
    </User>
    <Account>
    <AccountType>email</AccountType>
    <Action>settings</Action>
    <Protocol>
    <Type>EXCH</Type>
    <Server>[email protected]</Server>
    <ServerDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
    <ServerVersion>73C0834F</ServerVersion>
    <MdbDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <PublicFolderServer>webmail.xyz.com</PublicFolderServer>
    <AD>DC-03.domain.xyz.com</AD>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>off</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXPR</Type>
    <Server>webmail.xyz.com</Server>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>on</ServerExclusiveConnect>
    <EwsPartnerUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsPartnerUrl>
    <GroupingInformation>Default-First-Site-Name</GroupingInformation>
    </Protocol>
    <Protocol>
    <Type>WEB</Type>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <Internal>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://webmail.xyz.com/owa/</OWAUrl>
    <Protocol>
    <Type>EXCH</Type>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    </Protocol>
    </Internal>
    <External>
    <OWAUrl AuthenticationMethod="Fba">https://webmail.xyz.com/owa/</OWAUrl>
    <Protocol>
    <Type>EXPR</Type>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    </Protocol>
    </External>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>webmail.xyz.com</Server>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>webmail.xyz.com</Server>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    </Account>
    </Response>
    </Autodiscover>HTTP Response Headers:
    request-id: 9d325a80-f1fd-4496-ac48-2be6bb782c28
    X-CalculatedBETarget: Server01.domain.xyz.com
    X-DiagInfo: Server01
    X-BEServer: Server01
    Persistent-Auth: true
    X-FEServer: Server01
    Content-Length: 11756
    Cache-Control: private
    Content-Type: text/xml; charset=utf-8
    Date: Mon, 25 Aug 2014 19:12:25 GMT
    Set-Cookie: X-BackEndCookie=S-1-5-21-1293235207-2459173341-1304346827-14544=u56Lnp2ejJqBypqcnsfJx5nSy8ucnNLLnJzP0sfKz8/Sy5nHmsiamZrMyZrLgYHPxtDNy9DNz87L387Gxc7Nxc3J; expires=Thu, 25-Sep-2014 00:12:26 GMT; path=/Autodiscover; secure; HttpOnly
    Server: Microsoft-IIS/8.5
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 756 ms.
         Autodiscover settings for Outlook connectivity are being validated.
         The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.
              Additional Details
         Elapsed Time: 0 ms.
         Testing RPC over HTTP connectivity to server webmail.xyz.com
         RPC over HTTP connectivity was verified successfully.
              Additional Details
         HTTP Response Headers:
    request-id: 835acf95-78b7-40ae-b232-117318d1577e
    Server: Microsoft-IIS/8.5
    WWW-Authenticate: Basic realm="webmail.xyz.com",Negotiate,NTLM
    X-Powered-By: ASP.NET
    X-FEServer: Server01
    Date: Mon, 25 Aug 2014 19:12:26 GMT
    Content-Length: 0
    Elapsed Time: 7817 ms.
              Test Steps
              Attempting to resolve the host name webmail.xyz.com in DNS.
         The host name resolved successfully.
              Additional Details
         IP addresses returned: x.x.x.x
    Elapsed Time: 107 ms.
         Testing TCP port 443 on host webmail.xyz.com to ensure it's listening and open.
         The port was opened successfully.
              Additional Details
         Elapsed Time: 180 ms.
         Testing the SSL certificate to make sure it's valid.
         The certificate passed all validation requirements.
              Additional Details
         Elapsed Time: 303 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server webmail.xyz.com on port 443.
         The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
              Additional Details
         Remote Certificate Subject: CN=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign,
    Inc.", C=US.
    Elapsed Time: 224 ms.
         Validating the certificate name.
         The certificate name was validated successfully.
              Additional Details
         Host name webmail.xyz.com was found in the Certificate Subject Common name.
    Elapsed Time: 0 ms.
         Certificate trust is being validated.
         The certificate is trusted and all certificates are present in the chain.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05,
         One or more certificate chains were constructed successfully.
              Additional Details
         A total of 1 chains were built. The highest quality chain ends in root certificate CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign,
    Inc.", C=US.
    Elapsed Time: 34 ms.
         Analyzing the certificate chains for compatibility problems with versions of Windows.
         Potential compatibility problems were identified with some versions of Windows.
              Additional Details
         The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature
    isn't enabled.
    Elapsed Time: 5 ms.
         Testing the certificate date to confirm the certificate is valid.
         Date validation passed. The certificate hasn't expired.
              Additional Details
         The certificate is valid. NotBefore = 1/3/2013 12:00:00 AM, NotAfter = 11/16/2015 11:59:59 PM
    Elapsed Time: 0 ms.
         Checking the IIS configuration for client certificate authentication.
         Client certificate authentication wasn't detected.
              Additional Details
         Accept/Require Client Certificates isn't configured.
    Elapsed Time: 298 ms.
         Testing HTTP Authentication Methods for URL https://webmail.xyz.com/rpc/[email protected]:6002.
         The HTTP authentication methods are correct.
              Additional Details
         The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic, Negotiate, NTLMHTTP Response Headers:
    request-id: 835acf95-78b7-40ae-b232-117318d1577e
    Server: Microsoft-IIS/8.5
    WWW-Authenticate: Basic realm="webmail.xyz.com",Negotiate,NTLM
    X-Powered-By: ASP.NET
    X-FEServer: Server01
    Date: Mon, 25 Aug 2014 19:12:26 GMT
    Content-Length: 0
    Elapsed Time: 296 ms.
         Attempting to ping RPC proxy webmail.xyz.com.
         RPC Proxy was pinged successfully.
              Additional Details
         Elapsed Time: 454 ms.
         Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 0 ms.
    Elapsed Time: 1007 ms.
         Testing the MAPI Address Book endpoint on the Exchange server.
         The address book endpoint was tested successfully.
              Additional Details
         Elapsed Time: 2177 ms.
              Test Steps
              Attempting to ping the MAPI Address Book endpoint with identity: [email protected]:6004.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 906 ms.
    Elapsed Time: 918 ms.
         Testing the address book "Check Name" operation for user [email protected] against server [email protected].
         The test passed with some warnings encountered. Please expand the additional details.
           Tell me more about this issue and how to resolve it
              Additional Details
         The address book Bind operation returned ecNotSupported. This typically indicates that your server requires encryption. The Microsoft Connectivity Analyzer will attempt the Address Book test again with encryption.
    NSPI Status: 2147746050
    Elapsed Time: 825 ms.
         Testing the address book "Check Name" operation for user [email protected] against server [email protected].
         Check Name succeeded.
              Additional Details
         DisplayName: Test Exch1, LegDN: /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1
    Elapsed Time: 433 ms.
         Testing the MAPI Referral service on the Exchange Server.
         The Referral service was tested successfully.
              Additional Details
         Elapsed Time: 1808 ms.
              Test Steps
              Attempting to ping the MAPI Referral Service endpoint with identity: [email protected]:6002.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 953 ms.
    Elapsed Time: 949 ms.
         Attempting to perform referral for user /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1 on server [email protected].
         We got the address book server successfully.
              Additional Details
         The server returned by the Referral service: [email protected]
    Elapsed Time: 858 ms.
         Testing the MAPI Address Book endpoint on the Exchange server.
         The address book endpoint was tested successfully.
              Additional Details
         Elapsed Time: 626 ms.
              Test Steps
              Attempting to ping the MAPI Address Book endpoint with identity: [email protected]:6004.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 156 ms.
    Elapsed Time: 154 ms.
         Testing the address book "Check Name" operation for user [email protected] against server [email protected].
         Check Name succeeded.
              Additional Details
         DisplayName: Test Exch1, LegDN: /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1
    Elapsed Time: 472 ms.
         Testing the MAPI Mail Store endpoint on the Exchange server.
         We successfully tested the Mail Store endpoint.
              Additional Details
         Elapsed Time: 555 ms.
              Test Steps
              Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 234 ms.
    Elapsed Time: 228 ms.
         Attempting to log on to the Mailbox.
         We were able to log on to the Mailbox.
              Additional Details
         Elapsed Time: 326 ms.

  • Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

    I am deploying Exchange 2013 CAS in a Exchange 2007 organization. Will all the clients be directed to the Exchange 2013 CAS servers for autodiscover. Will there be any issue with outlook clients connecting to their mailbox servers in Exchange 2007

    All clients should be pointed to the Exchange 2013 CAS for the autodiscover service. This means:
    A. For local clients
    You need to modify the autodiscover Internal URI on the Exchange 2007 server and point it to Exchange 2013. For example, if you are using split-brain DNS on the Local Network and mail.yourdomain.com is resolved to Exchange 2013 local IP, the Exchange 2007
    Autodiscover Internal URI should be "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml" 
    Exactly the same way, you should modify the Exchange 2013 Autodiscover Internal URI and use the same address "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
    B. For remote clients - all clients will hit the Exchange 2013 CAS first (ex. mail.yourdomain.com)
    If the user's mailbox is on Exchange 2007 server, the correct XML will be generated and provided, and the user will be proxied for Outlook Anywhere/ActiveSync and redirected for OWA/WebServices
    If the user's mailbox is on Exchange 2013 server, the correct XML will be generated and provided
    Bottom line - based on the location of the user's mailbox, Exchange 2013 will generate and provide the correct XML file (there is not proxying involved in providing the Autodiscover info).

  • Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

    Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
    I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
    Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
    Error look like - cannot find exchange server.
    I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
    Someone have the same problem with migrated mailbox? How to solve it?
    Truly, Valery Tyurin

    You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
    Moreover, you can try this utility (
    http://www.exchangemigrationtool.com/ ) to accomplish this task.

  • Exchange 2013 CAS - Round Robin DNS not working properly

    I have exchange 2013 server (2MB, 2CAS) server. I created two dns records for mail.test.com, autodiscover.test.com pointing to my two CAS servers.
    But the problem is if i switched of one cas server, client outlook not connecting automatically to other CAS server. By restarting the outlook also its not working. By restarting the system or running the command ipconfig /flushdns in command prompt, it
    working.
    is there any configuration iam missing, please advice how to achieve decent load balancing in Exchange 2013 CAS without going for third party Loadbalancer...

    I have exchange 2013 server (2MB, 2CAS) server. I created two dns records for mail.test.com, autodiscover.test.com pointing to my two CAS servers.
    But the problem is if i switched of one cas server, client outlook not connecting automatically to other CAS server. By restarting the outlook also its not working. By restarting the system or running the command ipconfig /flushdns in command prompt, it
    working.
    is there any configuration iam missing, please advice how to achieve decent load balancing in Exchange 2013 CAS without going for third party Loadbalancer...
    If a CAS role server is down or unable to service clients, you have to remove it from  DNS round-robin consideration manually. There is no health check with DNS round-robin unlike a true load balancer.
    Also, I would set the TTL to a low value for the CAS servers in the round-robin.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 migration and Lync server

    hi guys,
    i wanna upgrade my exchange 2010 to 2013 in our company.
    but i faced with a question
    will exchange migration has effect on Lync server an should i reinstall it again in our caompany or not?
    plz help me 
    thanks guys

    Hi,
    you will need to config IM in OWA for Exchange 2013 server.As i can remember voice and everything else should be fine.
    Here is a guide for enabling IM in OWA:
    http://www.expta.com/2010/09/how-to-integrate-lync-server-2010-with.html
    Just remember to point DNS to the New Exchange 2013 server and it should be fine.
    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. Thank you! Off2work

  • I have just had a system update a safari 5.1.7 a security update 2012-200 and a app update and now when i go into a site with flash it says i do not have adobe flash.  I have installed it but still no luck?  any help would be much appreciated  Cheers Dave

    I have just had a system update.  Safari 5.1.7, a security update 2012-200 and Remote app update and now when I go into a site with flash it says I do not have adobe flash.  I have installed it from the site but still no luck?  any help would be much appreciated  Cheers Dave

    Select Help ▹ Installed Plug-ins from the Safari menu bar. Besides the following, what plugins are listed?
    iPhotoPhotocast
    Java
    QuickTime
    WebKit built-in PDF

  • We have a Exchange 2013 server and the Mailbox Database folder is filling up with .log files.

    We are migrating from Exchange 2010 to Exchange 2013.  We have installed the Exchange 2013 but it only has a couple of mailboxes on this server, all the mailboxes are still on the Exchange 2010 server.
    I have run a Windows Backup of the Exchange 2013 but I am still seeing a ton a log files in the mailbox folder.
    Also the database file is only about 1.1 GB but the backup is now 40 GB.  
    Is there something that can be done to truncate these logs and make the backup smaller?

    Hi ,
    1.Does the full backup completed successfully ?
    2.what about the status for the below mentioned command ? Does the mailbox database headers updated with the latest time and date ?
    Get-MailboxDatabase -Status | ft name,*full* -au
    3.Just check the application event logs for the event id
     2046  and that should state that the log truncation for the mailbox databases has been initiated or not.
    4.Before initiating the backup just make the exchange writer is not on error.
    vssadmin list writers
    In case if it on error state ,please restart the Microsoft exchange replication service and check the exchange writers status again by using the above mentioned command.
    Thanks & Regards S.Nithyanandham

  • Exchange 2010 CAS proxy to Exchange 2013 CAS: Use the following link to open this mailbox with the best performance:

    Hello,
    I've installed Exchange 2013 into Exchange 2010 infrastructure
    [ single Exchange 2010 server; single AD site; AD = 2003 ],
    and moved one mailbox [ Test user ] to Exchange 2013.
    When I login internally through 2013 OWA to access mailboxes on 2010, then proxy works fine.
    When I login internally through 2010 OWA to access mailboxes on 2013, then a message appears:
        Use the following link to open this mailbox with the best performance: with link to 2013 OWA...
    What is wrong ?
    I've checked and changed settings by:
    Get-OwaVirtualDirectory, Set-OwaVirtualDirectory
    [PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex10\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
    Server                        : EX10
    Name                          : owa (Default Web Site)
    ClientAuthCleanupLevel        : High
    InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
    BasicAuthentication           : True
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : True
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    RedirectToOptimalOWAServer    : True
    LegacyRedirectType            : Silent
    Url                           : {}
    SetPhotoURL                   :
    Exchange2003Url               :
    FailbackUrl                   :
    InternalUrl                   : https://ex10.contoso.com/owa
    ExternalUrl                   : https://ex10.contoso.com/owa
    [PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex13\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
    Server                        : EX13
    Name                          : owa (Default Web Site)
    ClientAuthCleanupLevel        : High
    InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
    BasicAuthentication           : True
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    RedirectToOptimalOWAServer    : True
    LegacyRedirectType            : Silent
    Url                           : {}
    SetPhotoURL                   :
    Exchange2003Url               :
    FailbackUrl                   :
    InternalUrl                   : https://ex13.contoso.com/owa
    ExternalUrl                   :
    best regards Janusz Such

    Hi Janusz Such,
    Based on my knowledge, CAS proxy can only from later version to previous version.
    Some like CAS2013 to CAS2010/2007, CAS2013 to CAS2013. 
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 - Public Folder Mailbox and Single Item Recovery

    Hello,
    I recently had a request to recover some messages that an ex-employee deleted from the "recover deleted items" folder in their public folder. Since this resides on a public folder mailbox and it does have the option for
    "Single Item Recovery" to be enabled on the box (which I enabled not knowing if this really works or not), is there a way I can still recovery these items or do I have to go to a backup to obtain those messages. Since ExFolders does not work that
    is not an option. I've seen commands to restore a public folder that was deleted but not items that were deleted directly from a public folder. I checked using MFCMAPI and I do see the dumper root and the public folder dumpster for each folder but it
    looks to be only the "deletions" folder and don't see anything similar to a "purges" type folder. Any ideas or am I stuck recovering from backup? Thanks in advance!

    So I think you are stuck and will need to restore the EDB to a Recovery Database to restore the items because when the end user purged the items from the "Recover Deleted Items" it removes them from the Recoverable Items/Deletions folder. 
    Check out this article
    http://blogs.technet.com/b/exchange/archive/2013/08/23/recovering-public-folder-information-in-exchange-2013.aspx
    I have not played with the recoverable items settings on the 2013 public folder enabled mailbox EDB  but you might try checking out Litigation or In Place Hold to use as a safety mechanism moving forward.  That said this will also increase the
    DB size so consider all the options before implementing
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

Maybe you are looking for