DAG Query - Exchange 2010

Hello Team
Recently i have decommissioned the DAG in one the server (TWO node DAG) indlbmb01 and ndlbmb02 .
Logged in to the indlbmb01 and moved all the active  DB's to the server INDLBMB02 
Removed the mailbox database copies from the server indlbmb01 
and finally removed the DAG from the server INDLBMB01.
All went fine without any issue and all the DB's are available in INDLBMB02 
Now, i reconfigured the DAG again and i would like few database in the DAG shuld be mounted in INDLBMB01.
but all the databases are mounted in INDLBMB02 , how can i mount the few databases in INDLBMB01 permanently 
Cuurently all the DB1, DB2, DB3 DB4 are mounted in INDLBMB02, but my need is DB1 and DB3 should always mounted in INDLBMB01. i checked the checked the activation preference but no help .

If all the replication is done and there are no copy queue length and replay length.
Simply failover DB1 and DB2 to INDLBMB01 and change the activation accordingly.

Similar Messages

  • DAG with Exchange 2010 & Exchange 2013

    Hello,
    I'd like to implement DAG in the system, but I was wondering if it is possible to use DAG in Exchange 2010 and 2013 environment? 
    Estimated amount of servers:
    Exchange 2010 Standard
    Exchange 2013 Enterprise
    Exchange 2013 Enterprise
    What I'm planning to do is moving all the mailboxes, public folders from Exchange 2010 Standard to Exchange 2013 Enterprise, then start using DAG and make Exchange 2010 as a member of DAG. Is it possible? 
    Thank you in advance.

    Hello,
    You cannot mix Exchange 2010 and 2013 versions in the same DAG. In your situation you need
    to create Exchange 2013 DAG and migrate all resources (mailboxes, public folders, mailflow settings etc). When finished, you will be able to decommission old server.
    Hope it helps,
    Adam
    CodeTwo: Software solutions for Exchange and Office 365
    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

  • Installing and configuring DAG in exchange 2010

    Hi All,
    I have one DC, and I Exchange 2010 server which all roles in a single server. I want to have a replication of my exchange server for disaster recovery.
    Please can anyone explain me how I can do all this?
    regards
    Yusuf Kamruddin

    DR site needs to include:
    Separate AD site and IP address.
    At list one DC.
    Exchange 2010 with HUB, CAS and Mailbox.
    Another CAS Array.
    Configure the mailbox as part of the DAG.
    For more help use this great series:
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html
    and
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/high-availability-recovery/designing-site-resilient-exchange-2010-solution-part1.html
    and on TechNet:
    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx 
    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

  • Exchange 2010 SP3 - Can DAG member be on OS 2012 R2 STD?

    Hi guys.
    We have Exchange 2010 SP3 on 2008 r2 enterprise.
    now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
    with best regards,
    bostjanc

    Hi guys.
    We have Exchange 2010 SP3 on 2008 r2 enterprise.
    now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
    with best regards,
    bostjanc
    No. It wont let you do that. 
    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx
    DAGs are available in both Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition. In addition, a DAG can contain a mix of servers running Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition.
    Each member of the DAG must also be running the same operating system. Exchange 2010 is supported on both the Windows Server 2008 and Windows Server 2008 R2 operating systems. All members of a DAG must run either Windows Server 2008 or Windows Server 2008
    R2. They can't contain a combination of both Windows Server 2008 and Windows Server 2008 R2.
    In addition to meeting the prerequisites for installing Exchange 2010, there are operating system requirements that must be met. DAGs use Windows Failover Clustering technology, and as a result, they require the Enterprise version of Windows.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2010 dag migration to exchange 2013 help

    If I want to use the Same mailbox servers and upgrade them to exchange 2013, what is the recommended way? I have a 4 member exchange 2010 DAG.
    I was thinking (where A,B,C,D are mailbox servers, A,B are in one site and C,D another active directory site):
     A  B  -------------- C D
    Remove A and C from the 2010 DAG, Format and install Exchange 2013 on both, and create a 2013 dag :
    A1 ----------- C1
    B ------------- D
    Then move across all mailboxes from B to A1. Upgrade B and D to exchange 2013 and put them in the DAG
    A1 B1 ----------- C1 D1
    Does this make sense ? I am trying to do this while having as much high availability as possible during the transition. I have no extra servers so I have to use the existing server hardware.
    Anand_N

    Hi,
    When you want to migrate a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated
    to the Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
    Here is an article about migration DAG from Exchange 2010 to Exchange 2013 for your reference.
    Migrating an Exchange 2010 DAG to Exchange 2013
    http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

    Hi guys (and girls)!
    Hear me up. The idea is like this:
    A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
    doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
    Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
    because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
    One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
    with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    bostjanc

    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    already answered by PS CL above
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    Just install the Edge Transport Server and make sure you install ADLDS services.
    as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
    Where Technology Meets Talent

  • Issue sending bulk email after Exchange 2010 to 2013 migration

    Hi!
    I have an issue with some reporting software sending bulk emails after our Exchange 2013 migration. 
    I can see the connections in the firewall and I can see the first connections under the protocol logs in the Exchange servers. What happens is that after ~10 emails, within the same amount of seconds from what I can tell, the mail flow just stops to the
    Exchange server. I cant seem to find an error message anywhere within the Exchange logs and I've tried updating the receive connector with higher timeouts / Connection limits but the users still cant send all the invoices etc right away. 
    We have multiple applications / receive connectors with this issue and the users did not report any issues with Exchange 2010 so I am assuming that this issue did not exist there. 
    We're running two multi-role (CAS/MB) Exchange 2013 servers in a DAG. Exchange 2010 is not fully decommissioned yet but all links and users are moved to 2013.
    Any help is much appreciated!

    Hi ,
    To avoid the issues when relaying the emails from application server through exchange then we need concentrate on the below mentioned parameters on the receive connectors in exchange 2013 cas servers and also we need to set the parameter value as per your
    environment requirement.
    Please check the below mentioned values on the dedicated receive connectors in exchange 2013 cas server to relay emails from the application server
    Parameters :
    ConnectionInactivityTimeout
    ConnectionTimeout
    MaxInboundConnection
    MaxInboundConnectionPercentagePerSource
    MaxInboundConnectionPerSource
    MaxRecipientsPerMessage
    MessageRateLimit
    Note : In case if none of the above changes help you then the final option would be to enable the protocol logging on the receive connector utilized by the application server to relay emails via exchange server and with the help of the logs we can can came
    to know that why the connections from the application server to exchange server is disconnecting after some emails has send.
    Thanks & Regards S.Nithyanandham
    Here are the relevant values for the receive connector, doublechecked and it's the same on both DAG members;
    ConnectionTimeout                       : 00:20:00
    ConnectionInactivityTimeout             : 00:05:00
    MaxInboundConnection                    : 5000
    MaxInboundConnectionPerSource           : Unlimited
    MaxInboundConnectionPercentagePerSource : 100
    MaxRecipientsPerMessage                 : 200
    MessageRateLimit                    
    : Unlimited
    Adding logs for one big connection spike from the customer. About 50 inbound connections to the Exchange servers . 
    SMTP Receive;
    2015-01-26T18:02:46.991Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,0,DAG member 01:587,Customer IP:60262,+,,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,1,DAG member 01:587,Customer IP:60262,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,2,DAG member 01:587,Customer IP:60262,>,"220 DAG member 01 Microsoft ESMTP MAIL Service ready at Mon, 26 Jan 2015 19:02:46 +0100",
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,3,DAG member 01:587,Customer IP:60262,<,EHLO customerdomain.com,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,4,DAG member 01:587,Customer IP:60262,>,250-DAG member 01 Hello [Customer IP],
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,5,DAG member 01:587,Customer IP:60262,>,250-SIZE 36700160,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,6,DAG member 01:587,Customer IP:60262,>,250-PIPELINING,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,7,DAG member 01:587,Customer IP:60262,>,250-DSN,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,8,DAG member 01:587,Customer IP:60262,>,250-ENHANCEDSTATUSCODES,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,9,DAG member 01:587,Customer IP:60262,>,250-STARTTLS,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,10,DAG member 01:587,Customer IP:60262,>,250-AUTH LOGIN,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,11,DAG member 01:587,Customer IP:60262,>,250-8BITMIME,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,12,DAG member 01:587,Customer IP:60262,>,250-BINARYMIME,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,13,DAG member 01:587,Customer IP:60262,>,250 CHUNKING,
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,14,DAG member 01:587,Customer IP:60262,<,STARTTLS,
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,15,DAG member 01:587,Customer IP:60262,>,220 2.0.0 SMTP server ready,
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,16,DAG member 01:587,Customer IP:60262,*,,Sending certificate
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,17,DAG member 01:587,Customer IP:60262,*,CN=server,Certificate subject
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,18,DAG member 01:587,Customer IP:60262,*,CN=server,Certificate issuer name
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,21,DAG member 01:587,Customer IP:60262,*,server;DAG member 01,Certificate alternate names
    2015-01-26T18:02:47.053Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,22,DAG member 01:587,Customer IP:60262,*,,TLS negotiation succeeded
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,23,DAG member 01:587,Customer IP:60262,<,EHLO customerdomain.com,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,24,DAG member 01:587,Customer IP:60262,*,,Client certificate chain validation status: 'EmptyCertificate'
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,25,DAG member 01:587,Customer IP:60262,*,,TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,26,DAG member 01:587,Customer IP:60262,>,250-DAG member 01 Hello [Customer IP],
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,27,DAG member 01:587,Customer IP:60262,>,250-SIZE 36700160,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,28,DAG member 01:587,Customer IP:60262,>,250-PIPELINING,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,29,DAG member 01:587,Customer IP:60262,>,250-DSN,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,30,DAG member 01:587,Customer IP:60262,>,250-ENHANCEDSTATUSCODES,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,31,DAG member 01:587,Customer IP:60262,>,250-AUTH LOGIN,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,32,DAG member 01:587,Customer IP:60262,>,250-8BITMIME,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,33,DAG member 01:587,Customer IP:60262,>,250-BINARYMIME,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,34,DAG member 01:587,Customer IP:60262,>,250 CHUNKING,
    2015-01-26T18:02:47.085Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,35,DAG member 01:587,Customer IP:60262,<,AUTH LOGIN,
    2015-01-26T18:02:47.085Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,36,DAG member 01:587,Customer IP:60262,>,334 <authentication response>,
    2015-01-26T18:02:47.100Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,37,DAG member 01:587,Customer IP:60262,>,334 <authentication response>,
    2015-01-26T18:02:47.131Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,38,DAG member 01:587,Customer IP:60262,*,SMTPSubmit SMTPAcceptAnyRecCustomer IPient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
    2015-01-26T18:02:47.147Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,39,DAG member 01:587,Customer IP:60262,*,[email protected],authenticated
    2015-01-26T18:02:47.272Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,40,DAG member 01:587,Customer IP:60262,*,,Proxy session was successfully set up. Session [email protected] will now be proxied
    2015-01-26T18:02:47.272Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,41,DAG member 01:587,Customer IP:60262,>,235 2.7.0 Authentication successful,
    2015-01-26T18:02:47.819Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,42,DAG member 01:587,Customer IP:60262,-,,Local
    SMTP Send
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,0,,DAG member 02:465,*,,attempting to connect. Client proxy session for [email protected]
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,1,DAG member 01:57446,DAG member 02:465,+,,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,2,DAG member 01:57446,DAG member 02:465,<,"220 DAG member 02 Microsoft ESMTP MAIL Service ready at Mon, 26 Jan 2015 19:02:46 +0100",
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,3,DAG member 01:57446,DAG member 02:465,>,EHLO DAG member 01,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,4,DAG member 01:57446,DAG member 02:465,<,250-DAG member 02 Hello [DAG member 01],
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,5,DAG member 01:57446,DAG member 02:465,<,250-SIZE 36700160,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,6,DAG member 01:57446,DAG member 02:465,<,250-PIPELINING,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,7,DAG member 01:57446,DAG member 02:465,<,250-DSN,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,8,DAG member 01:57446,DAG member 02:465,<,250-ENHANCEDSTATUSCODES,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,9,DAG member 01:57446,DAG member 02:465,<,250-STARTTLS,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,10,DAG member 01:57446,DAG member 02:465,<,250-X-ANONYMOUSTLS,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,11,DAG member 01:57446,DAG member 02:465,<,250-AUTH GSSAPI NTLM,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,12,DAG member 01:57446,DAG member 02:465,<,250-X-EXPS GSSAPI NTLM,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,13,DAG member 01:57446,DAG member 02:465,<,250-8BITMIME,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,14,DAG member 01:57446,DAG member 02:465,<,250-BINARYMIME,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,15,DAG member 01:57446,DAG member 02:465,<,250-CHUNKING,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,16,DAG member 01:57446,DAG member 02:465,<,250-XEXCH50,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,17,DAG member 01:57446,DAG member 02:465,<,250-XRDST,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,18,DAG member 01:57446,DAG member 02:465,<,250 XSHADOWREQUEST,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,19,DAG member 01:57446,DAG member 02:465,>,X-ANONYMOUSTLS,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,20,DAG member 01:57446,DAG member 02:465,<,220 2.0.0 SMTP server ready,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,21,DAG member 01:57446,DAG member 02:465,*,,Received certificate
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,23,DAG member 01:57446,DAG member 02:465,*,,Proxy target certificate
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,24,DAG member 01:57446,DAG member 02:465,*,"CN=*.email.com, OU=IT, O=X, L=X, S=X, C=SE",Certificate subject
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,25,DAG member 01:57446,DAG member 02:465,*,"CN=DigiCert High Assurance CA-3, OU=www.digicert.com, O=DigiCert Inc, C=US",Certificate issuer name
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,28,DAG member 01:57446,DAG member 02:465,*,*.email.com;email.com,Certificate alternate names
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,29,DAG member 01:57446,DAG member 02:465,>,EHLO DAG member 01,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,30,DAG member 01:57446,DAG member 02:465,<,250-DAG member 02 Hello [DAG member 01],
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,31,DAG member 01:57446,DAG member 02:465,<,250-SIZE 36700160,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,32,DAG member 01:57446,DAG member 02:465,<,250-PIPELINING,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,33,DAG member 01:57446,DAG member 02:465,<,250-DSN,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,34,DAG member 01:57446,DAG member 02:465,<,250-ENHANCEDSTATUSCODES,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,35,DAG member 01:57446,DAG member 02:465,<,250-AUTH GSSAPI NTLM LOGIN,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,36,DAG member 01:57446,DAG member 02:465,<,250-X-EXPS EXCHANGEAUTH GSSAPI NTLM,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,37,DAG member 01:57446,DAG member 02:465,<,250-X-EXCHANGEAUTH SHA256,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,38,DAG member 01:57446,DAG member 02:465,<,250-8BITMIME,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,39,DAG member 01:57446,DAG member 02:465,<,250-BINARYMIME,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,40,DAG member 01:57446,DAG member 02:465,<,250-CHUNKING,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,41,DAG member 01:57446,DAG member 02:465,<,250-XEXCH50,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,42,DAG member 01:57446,DAG member 02:465,<,250-XRDST,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,43,DAG member 01:57446,DAG member 02:465,<,250-XSHADOWREQUEST,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,44,DAG member 01:57446,DAG member 02:465,<,250-XPROXY,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,45,DAG member 01:57446,DAG member 02:465,<,250-XPROXYFROM,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,46,DAG member 01:57446,DAG member 02:465,<,250-X-MESSAGECONTEXT ADRC-2.1.0.0 EPROP-1.2.0.0,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,47,DAG member 01:57446,DAG member 02:465,<,250 XSYSPROBE,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,48,DAG member 01:57446,DAG member 02:465,>,X-EXPS EXCHANGEAUTH SHA256 ,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,49,DAG member 01:57446,DAG member 02:465,>,<Binary Data>,
    2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,50,DAG member 01:57446,DAG member 02:465,<,235 <authentication information>,
    2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,51,DAG member 01:57446,DAG member 02:465,>,XPROXY SID=08D2051B7AE3DA8E IP=Customer IP PORT=60262 DOMAIN=customerdomain.com CAPABILITIES=0 
    2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,52,DAG member 01:57446,DAG member 02:465,<,250 XProxy accepted and authenticated,
    2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,53,DAG member 01:57446,DAG member 02:465,*,,Proxy session successfully set up for [email protected]. Inbound session will now be blindly proxied
    2015-01-26T18:02:47.819Z,Client Proxy Send Connector,08D2051B7AE3DA8F,54,DAG member 01:57446,DAG member 02:465,-,,Remote
    Nothing after these logs indicating any type of issue with the receive connector. Tried to make the logs as anonymous as possible. Hope they still make sense.
    Note; Database was active on DAG member 02 but all incoming traffic on port 587 was directed to DAG member 01.

  • Exchange 2010 mail storing Architecture

    hi I just need to know what is the method that exchange server 2010 use to store the mail,
    if I elaborate more when one user sends a mail to few people in the same organization does that mail copies to every users mail box or exchange just uses the referencing method to one single mail.
    please help one of my clients using DAG in exchange 2010 and their mail box sizes increasing rapidly. I need to provide a solution to them. please let me know if you want more details
    please help me with some links that reveals about these in detail.
    thanks In Advance.

    Every mailbox will get a copy of the message. Single Instance Storage (SIS) is history.
    Dude, Where's My Single Instance?
    http://blogs.technet.com/b/exchange/archive/2010/02/22/3409361.aspx
    Martina Miskovic

  • Mirgrating to Exchagne Server 2013 from Exchange 2010

    Hi Team,
    I am in the phase of migrating to Ex 2013 server from Ex 2010 SP3. I've few queries:
    Can I use existing Ex2010 DAG to add Ex2013 Servers?
    If no, then creating a new DAG means I need everything new, such as, storage, network... right?
    Can I use 2010 witness in 2013 DAG and other way around?
    What coexistence means if a new DAG is created.
    and kindly sahre some reading resources about this topic.
    Really appreciete your help.
    Thanks.
    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

    Hi,
    As DareDevil suggested, you need to setup everything on the new Exchange 2013 servers. After finishing the configuration on Exchange 2013, start to do the migration.
    What's more, I would like to clarify the following thing:
    When migrating a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated to the
    Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
    For more information, here is a blog for your reference:
    Migrating an Exchange 2010 DAG to Exchange 2013
    http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
    Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any information found there. Please make sure that
    you completely understand the risk before retrieving any suggestions from the above link.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2010 DAG Replication - too much data crossing the wire

    I’m replicating 3 Exchange databases from our production active Exchange 2010 server across the WAN to another passive Exchange 2010 server at our DR site. 
    The Exchange server at the DR site does not have any active databases, i.e. no users are hitting that server. 
    We are running Update Rollup 8 for Exchange Server 2010 SP1 on both these servers. 
    The two sites are connected via a 10Mb/s MPLS connection and all the databases are in sync and the replication is working fine. 
    I have setup a network sniffer at the primary site and see a sizable amount of data crossing the wire from the production Exchange server to the DR Exchange server. 
    When I query the production Exchange server using the Tracking Log explorer and only choose the EventID ‘RECEIVED’ that should show me the amount of data that has been committed to the database. 
    If I choose a date range that is the same exact range that I have used to capture the raw data with my sniffer the amount of data the sniffer shows crossing the wire is 10 fold compared to what the Tracking Log Explorer shows. 
    If I actually count up the data in the LOG files it is about 20% more than what is crossing the wire but that seems to be because the DAG is compressing the data. 
    If in a one hour timeframe there is 500MB of data crossing the wire to the DR Exchange server the tracking log explorer will show only 50MB. 
    I would like to know why the data crossing the wire far exceeds the amount of data that is truly being sent/received from the primary exchange server. 
    Perhaps I’m simply not getting a true view of the amount of data being committed to the exchange server using the Tracking Log Explorer. 
    Maybe there is a better way to report how much data is being committed to the exchange databases. 
    Any assistance would be appreciated…

    Two things.
    1 - you must update Exchange to SP3 and a recent RU.  Willard has already provided the links, which point back to my blog if you want to see the lifecycle map for Exchange 2010.  SP1 has been out of support since January 2013.  Time to move
    on pllease
    2 - Looking at the tracking log is not sufficient.  I would not expect that to show everything.
    I want to know what traffic you see as excessive.  What ports are you seeing used here?
    My money is on content indexing.  CI will use additional traffic over and above log repl traffic.  Expect CI traffic to be roughly the same again.  You can test this by disabling CI on the database or stopping the services on the DR server. 
    To disable the CI for the database:
    Set-MailboxDatabase DBName -indexEnabled $False
    Or stop the Exchange search services on the DR box to leave production unaffected.
    Again - you need to update Exchange.  You would be better to do that now rather than when something breaks and Microsoft support cannot fully assist you since you are not uptodate.    I'll leave discussion of the security issues resolved
    in recent Exchange RUs aside. 
    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.

  • Exchange 2010 SP3 and UR6 Query - Order of Install

    hi,
    I need to update my Exchange 2010 SP2 Servers to SP3 and Update Rollup 6.
    Can someone confirm the update order for me?
    I have 5 servers;
    Live Data Centre:
    2 x HUB / CAB (Using Windows NLB)
    2 x Mailbox (DAG)
    Disaster Recovery:
    1 x Multi-Role Server (CAS / HUB and Mailbox) - this is also Part of the DAG
    Two Questions:
    1.) What is the Order in which I install SP3 on these Servers? Should it be Live Data Centre: HUB / CAS, Mailbox Servers and THEN the Multi-Role Server at DR?
    2.) When Upgrading each server, should I do SP3, reboot, check and THEN install Update Rollup 6 - or should I upgrade all Servers to SP3 and then start the process again to get to Update Rollup 6?
    Thanks in advance for your help with this query.
    Regards,
    Adam

    1) Internet facing CAS first in each AD site. Order: CAS> HUB> UM> MBX
    2) Personally, I would install SP3, reboot, then install SP6, but its really up to you.
    http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
    Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • CMD=Ping&log query is taking long time-taken when checked in IIS logs.... Exchange 2010 SP3..

    Query regarding the ActiveSync and parameter time-taken from ActiveSync IIS logs.
    Here what I see for from the logs.
    [email protected] 45.101.90.185 Apple-iPad2C3/1202.410 200 0 0 1501129
    443 [email protected] 45.101.90.185 Apple-iPad2C3/1202.410 200
    0 0 22105
    443 [email protected] 45.101.90.185 Apple-iPad2C3/1202.410 200
    0 0 452
    443 [email protected] 45.101.90.185 Apple-iPad2C3/1202.410 200
    0 0 936
    443 [email protected] 45.101.90.185 Apple-iPad2C3/1202.410 200
    0 0 656238 
    In the above log, highlighted are the time-taken and I just want to check what is the ideal time-taken value, some value above should be causing some problem, like the one of the top 1501129 ?
    ?AND I see its for POST event and CMD=Ping&log query.......
    We have Mobile Iron in the environment and we are seeing few timeout errors on MobileIron server and for users intermittently. They usually see below error... However we don't see any end users issues, but just want to get rid of below error. MobileIron guys
    are pointing it to time-taken value which is high intermittently.
    IOException connection to server [email protected] -- java.io.IOException:
    awaitUninterruptibly was stopped by timeout
    @BALA

    Hi,
    To understand more about the issue, I’d like to confirm the following information:
    1. What’s your Exchange 2010 version? 
    http://support.microsoft.com/kb/2536517/en-us
    2. Do you install other software, like SQL, on the same Exchange Server?
    3. Change another admin account to access EMS.
    Thanks,
    Angela Shi
    TechNet Community Support

  • [SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

    Hi there!
    I have a problem which makes me very angry already :)
    I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
    I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
    Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
    LOGS on the second nodes: 
    Application Log
    "Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
    Failover Clustering Diagnostic Log
    "[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
    CMDLET Error:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:06:21
    MSC-CO-EXC-02V
    Failed
    Error:
    A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
    (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
    An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
    This operation returned because the timeout period expired
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
    Warning:
    Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
    Warning:
    The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
    Exchange Management Shell command attempted:
    Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
    Elapsed Time: 00:06:21
    UPD:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.
    Please, help me if you can.

    Hi, Jared! Thank you for the reply.
    Of course I did it already :) I have new info:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.

  • Removing mailbox server from Exchange 2010 DAG - Node not fully cleaned up

    Hi,
    We are in the process of decommissioning some old Exchange 2010 servers. I have just attempted to remove one of our mailbox servers and have received a number of errors, related to its removal from the DAG.
    I have already removed the Public Folder replicas and all mailbox database copies. I then tried to evict the server from the DAG and received the following warning:
    I then ran the command that was recommended, from another server and in an administrative command prompt:
    I have looked in this log on both the server I ran the command on, a CAS server, and the mailbox server itself and can see no evidence of this error 2 that is listed here.
    If I run the Powershell command to look at the DAG I cannot see it there any more. I am assuming that this error message might only be an issue if I was planning on re-using this server somewhere else in Exchange or perhaps adding this server to another
    DAG. But I just want to decommission it.
    Can anyone put my mind at rest as to whether this is a genuine concern or not. If not my next step is to uninstall Exchange 2010 from this server and turn it off.

    Hi Belinda,
    I get the following:
    [PS] C:\Windows\system32>Get-DatabaseAvailabilityGroup
    Name             Member Servers                                                         
    Operational Servers
    DAG01            {WSR-EX-01, WSR-EX-101, WSR21}
    It doesn't look like that server is part of the DAG any more as far as I can see. I just can't explain that error message reported from the cluster command. As far as I can see the server is isolated. I already removed its database copies as a pre-requisite
    before removing it from the DAG as per this guide:
    http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27039933.html
    I found a nice little script that gave reports on your Public Folder configuration and it highlighted that some of our folders were not being replicated properly across our mailbox servers. This helped me in removing these services from the server.
    It is currently doing nothing at this time as far as Exchange Services are concerned.

  • Exchange 2010 DAG netowrk replications issues - Causing database copies to be disconnected and resynchronizing.

    My
    environment is as follows.<o:p></o:p>
    We have 3 exchange 2010 servers.<o:p></o:p>
    EX1, EX2, DREX1. All servers are exchange 2010 14.2 build 247.5<o:p></o:p>
    EX1 and EX2 have two nics, one LAN and one for BACKUP <o:p></o:p>
    The dag is configured to to communicate to all three.<o:p></o:p>
    The IP for EX1 is 192.168.100.51 - LAN, switch A; 160.100.3.51 - BACKUP, switch B<o:p></o:p>
    The IP for EX2 is 192.168.100.52 - LAN, switch A; 160.100.3.52 - BACKUP, switch B<o:p></o:p>
    DREX1 is located in another network. It is in another building connected via vpn. The ip
    for DREX1 is 192.170.100.51. There is no BACKUP network for this server<o:p></o:p>
    (These are not the actual address, but the concept is similar)<o:p></o:p>
    The dag network configuration is as follows.<o:p></o:p>
    DAGNetworkDR has a subnet of 192.170.100.0/24; Network Interface of 192.170.100.51<o:p></o:p>
    DAGNetwork01 (LAN) has a subnet of 192.168.100.0/24; Network Interfaces of 192.168.100.51
    and 192.168.100.52<o:p></o:p>
    DAGNetwork02 (BACKUP) has a subnet of 160.100.3.0/24; Network Interfaces of
    160.100.3.51 and 160.100.3.52<o:p></o:p>
    Last Friday, 3/7/14 something happened.<o:p></o:p>
    To lead up to that, I noticed the issue because we have DPM 2010 making 15minute express
    full backups of our exchange databases when I reviewed the backup jobs, the
    exchange database backups using dpm2010 failed all weekend long starting at
    11:00pm that Friday.<o:p></o:p>
    The issue that occurred was that the database copies went to a status of Disconnected and
    Resynchronizing, and after about 30 seconds, the status would show
    Resynchronizing.<o:p></o:p>
    All attempts to resolve this with the research methods failed.  Deleting the
    logs and reseeding failed, suspending, then rebuilding failed.<o:p></o:p>
    Creating a new database worked, creating a database copy worked, but seeding the copy
    failed. All with the same pattern, a status of Disconnected and
    Resynchronizing, and after about 30 seconds, and the status would show
    Resynchronizing.<o:p></o:p>
    The database was mounted on EX2, and seeding to EX1
    DREX1 has no issues.<o:p></o:p>
    All the DAG networks were in a good status, all Green and all up.  I could ping from
    EX1 to EX2 and from EX2 to EX1 on both networks fine.<o:p></o:p>
    In the middle of the week, about 3/12/14, we resolved the issue. We rebooted EX1, no
    fix, but after rebooting EX2, it all resolved.  It did a fail over to DREX1. I think it failed to do the failover to EX1. However, when it came back up, it was happy, it was reseeding slowly. After about an hour and a half, it
    was all healthy.<o:p></o:p>
    We thought it was all good EXCEPT, on Friday night at 11:00pmish on 3/14/14, the same
    issue occurred; a status of Disconnected and Resynchronizing, and after about
    30 seconds, the status would show Resynchronizing.<o:p></o:p>
    The database was mounted on EX2 and seeding to EX1 again. I did not notice the
    issue until I performed my review of the backup jobs again on Monday.<o:p></o:p>
    Late Monday morning, my boss and I were looking at more articles, but all the same results,
    delete the database copy and reseed. Which we knew would not work.<o:p></o:p>
    I mentioned that it was strange because the networks were all up. What made us try the next
    scenarios was just "luck" I guess. I made a statement about not remembering
    which networks DAG replication took place over.  Again, we have a LAN and
    a BACKUP network.  Bother were listed to use replication, so we decided to
    disable replication over the BACKUP network in the EMC. Immediately, the
    database copies switch to healthy and started seeding.<o:p></o:p>
    Later that evening I enabled replication over the BACKUP network and it failed again with
    a status of Disconnected and Resynchronizing, and after about 30 seconds, the
    status would show Resynchronizing.  I disabled the replication over the
    BACKUP network and the database copy went back to healthy<o:p></o:p>
    The last round of windows updates were pushed to these boxes the Friday before the
    issues began, 2/28/14.  I don't believe the updates to be the issue. <o:p></o:p>
    Can anyone make any suggestions as to where to look?  It worked with the BACKUP
    network enabled to so long that is eluding me as to why the issues would start
    all of a sudden. I am also confident that the switch configuration for the
    BACKUP network has not been changed at all in at least 2-3 months.  I am
    still open to look at the config. Please help if you can.<o:p></o:p>
     <o:p></o:p>
    Lastly, this is more of a monitoring thing, if anyone can suggest a good way to monitor
    the database copies so that I can be alerted when the status changes.  We
    use WhatsUpGold 16.2 to monitor the devices.  <o:p></o:p>
    Thanks for any future assistance.<o:p></o:p>
    Ian
    Ian

    You don't have to enable the Replication on Backup Network.
    You should collapse your DAG network.
    http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
    http://blogs.technet.com/b/samdrey/archive/2012/12/04/exchange-2010-dag-collapse-the-mapi-networks-in-a-dag.aspx
    Post the result of Below command:
    Get-DatabaseAvailabilityGroupNetwork 
    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

  • How do I create a hyperlink in Pages for iPad?

    In Pages for Mac, or Word, I can easily create a hyperlink "under" a word or phrase. So far, I've been unable to do the same in Pages for iPad. Is it me or the iPad? JLG

  • Grouping similar movies under one thumbnail

    Hi, I've bought a few movies from iTunes that are part of a series, like Star Trek, Die Hard, etc. I want to group such moves together so that (for example), all the Star Treks appear together under one thumbnail - like episodes are grouped in season

  • User Exit in 10g - To get client info

    Hi all We have a user exit call in forms 4.5 which returns client info (OS version). As we are going for 10g, the user exits will reside in AS. Is there any way by which i can use the same user exit to get client info now ? Thnx and Regards Sriram

  • Not getting email verification message

    I am stuck at the emil verification stage for Facetime. Following another support articlae, I went to

  • Everytime I try to send a text message it fails

    My friend just bought an iphone 4 and she can not send regular text messages out.. only imessages to people that have iphones. She gets the alert notification saying it failed to send. Also she set up her email like it told her to and now her contact