Exchange Server 2010 - Message Tracking Logs - Log file creation

Hi,
I would like to find out on the behavior of the exchange server in the way that it logs the message tracking.
Currently the parameter used is 
MessageTrackingLogMaxDirectorySize - 10GBMessageTrackingLogMaxAge - 30daysI would like to check when the Max Directory Size has exceeded the value indicated, does Exchange server immediately deletes the oldest log file to make space for the new logs?And in the event that the oldest file is being open or locked, will exchange server delete the next oldest file? or it will reattempt to delete the "locked" file for a period of time?Lastly, when these "oldest" files is not able to be deleted, will exchange server stops logging new tracking events?Thanks!

Hi Zack,
Thank you for your question.
If you have configured the parameter of “MessageTrackingLogMaxDirectorySize” and “MessageTrackingLogMaxAge”, we think you have enable circular logging, it will delete the oldest message tracking log files for new log file when the either of the following
conditions is true:
The message tracking log directory reaches its specified maximum size.
A message tracking log file reaches its specified maximum age.
In addition, it didn’t exceeded the value indicated.
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

Similar Messages

  • Move Exchange Server 2010 SP1 databases and log files to another partition

    My company has been running Exchange Server 2010 SP1 on virtual machine for almost three years. My colleague created this virtual machine (Windows Server 2008 R2 SP1) before Exchange Server installation with following partitions:
    C partition - for Windows Server 2008 R2 SP1 OS (size 40 GB)
    E partition - for Exchange Server 2010 SP1 databases and logs (size 410 GB)
    Those two partitions are on the same virtual hard disk "next to one another" so I can not extend C partition which gets filled up with IIS logs (when C partition free space is under 10 GB I am backing up these logs with backup software and afterwards
    deleting them thus freeing up space on C partition). I have 2 databases (along with Public Folders) and size of these databases and their logs is around 235 GB.
    Is it safe to move these databases and their logs to another partition which I would create on separate virtual hard disk for this purpose only and how much time this process might take since during this process databases
    would be dismounted and inaccessible to all users? He made big blunder in my opinion but I have to solve this.

    Yes, its safe to move the DB/Logs. You can follow the procedure mentioned in this article to do it via EMC or Shell... http://exchangeserverpro.com/move-exchange-2010-database-folder/
    But it depends on various factors on how long it is going take, like size of the database/logs, server performance, storage performance etc...
    Besides this, upgrade Exchange 2010 SP1 to SP3, SP1/SP2 aren't supported anymore! http://blogs.technet.com/b/rmilne/archive/2014/04/09/end-of-exchange-2010-sp2-support.aspx
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • MS Exchange server 2010 messages will be placed in the poison queue and the transport service will crash

    Can any1 please help.
    We have Exchange server 2010, we just upgraded it with SP3 and then the issue occers that we were unable to send n receive mail outside of our LAN...i mean from gmail or hotmail..
    we have then updated with CU4 which is the latest but still messages will be placed in the poison queue and the transport service will crash.
    We have disabled the antivirus also but issue remains same.
    We have CAS 1 n 2 as of Clustering environment and we upgraded sp3 for both. but we did CU4 on CAS1 to see the results to resovle this issue but no luck

    Hi,
    Did you get any NDR message now when you send a email to outside? And vice versa.
    In addtion,I recommend you telnet to port 25 to test SMTP communication.
    If any question,please feel free to post here.
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Event logs fails to start on Exchange Server 2010

    My Exchange server 2010 R2 SP1 Enterprise single server is down.  All exchange services fail to start.  It appears like the Microsoft Exchange Active Directory Topology service isn't starting which is a dependency for all other services.
    The error I get when trying to start this service is:
    Windows could not start the Microsoft Exchange Active Directory Topology on Local Computer.  For more information, review the System Event Log.  If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code
    -2147024882
    To make matters worse, the event viewer is not starting either.
    When trying to start the Windows Event Log, I get the error:
    Windows could not start the Windows Event Log service on Local Computer. Displays Error code 5
    This is running on a Windows Server 2008 R2 SP1 Standard box.
    Any assistance is appreciated.

    When trying to start the Windows Event Log, I get the error:
    Windows could not start the Windows Event Log service on Local Computer. Displays Error code 5
    Hi,
    Based on this error, this problem happens if any of the following conditions are true:
    The built-in security group EventLog does not have permissions on the folder %SystemRoot%\System32\winevt\Logs
    The Local Service account does not have default permissions on the following registry key: HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability
    To solve this problem, we need to restore the default permissions in the list below on %SystemRoot%\System32\winevt\logs.
    Authenticated user - List folder/read data, Read attributes, Read Extended attributes, Read permissions
    Administrators - Full control
    SYSTEM - Full control
    EventLog - Full control
    Please try the following methods:
    Method 1
    To restore the default permissions on folder %SystemRoot%\System32\winevt\logs, follow these steps.
    Right-click on %SystemRoot%\System32\winevt\logs and select Properties.
    Select the Security tab.
    Click Edit button and click the Add button in the permissions dialog box.
    In Select users, computers, or Groups dialog box ensure that under object types Built in Security Principals and the location as local computer name is selected.
    Enter the object name as "NT SERVICE\EventLog" without quotes. And click OK. This group should have full control on the folder.
    Once EventLog group is added add the rest of the groups with above mentioned permissions.
    Method 2
    Identify a Windows Server 2008 machine with default permissions.
    Click Start, and then type cmd in the Start Search box.
    In the search results list, right-click Command Prompt, and then click Run as Administrator.
    When you are prompted by User Account Control, click Continue.
    Type the command CD %SystemRoot%\SYSTEM32.
    Once the working directory is changed to %SystemRoot%\SYSTEM32 type the command icacls winevt\* /save acl /T.
    This will save a file named ACL in %SystemRoot%\SYSTEM32. Copy this file to the C: drive on the problem computer.
    On the problem computer, open command prompt with administrator privileges (refer to previous steps 1-3).
    Change the working directory to %SystemRoot%\SYSTEM32.
    Execute the command icacls winevt\ /restore acl.
    Default permissions on the registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability should be:
    CREATOR OWNER - Full control
    SYSTEM - Full control
    LOCAL SERVICE - Query Value, Set Value, Create Subkey, Notify and Delete
    Administrators - Full control
    Users - Read
    To set the permission on this registry key:
    Click the Start menu, select Run and type Regedit.
    Go to the location HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability.
    From the Edit menu click Permissions.
    Add the permissions for the accounts as listed above.
    In addition, Exchange 2010 SP1 and SP2 are end of support.
    https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=exchange%20server%202010&Filter=FilterNO
    Best Regards.
    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]
    Lynn-Li
    TechNet Community Support

  • When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

    Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
    now, so I’m posting here in order to share this among others.
    Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
    Symptoms
    E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
    “#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
    user wasn’t found.> #SMTP#”
    Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
    “Log Name: Application
    Source: MSExchange Store Driver
    Event ID: 1020
    Level: Error
    Description:
    The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
    Cause
    In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
    Group) remains with a Servers container, but no servers inside it.
    During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
    Resolution
    To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
    Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
    2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
    at your own risk.
    1.      
    Start the ADSI Edit MMC Snap-in. Click Start, then
    Run, and type adsiedit.msc, and then click OK.
    2.      
    Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
    CN=Configuration,DC=DNSDomainName,DC=com.
    3.      
    Expand CN=Services, and then CN=Microsoft Exchange, and then expand
    CN=YourOrganizationName.
    4.      
    You will see an empty Administrative Group. Expand the
    CN=YourAdministrativeGroupName.
    5.      
    Expand CN=Servers.
    6.      
    Verify there are no server objects listed under the
    CN=Servers container.
    7.      
    Right click on the empty CN=Servers container and choose
    Delete.
    8.      
    Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
    Applies to
    Exchange Server 2010, Standard Edition
    Exchange Server 2010, Enterprise Edition
    Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
    | E-mail: [email protected]

    Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
    When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
    Exchange 2003 server into the domain/forest. 
    You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
    So it sounds like you are not looking in the right location within ADSIEdit. 
    You may find the following article also helpful for this issue which is the same resolution:
    http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
    I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
    http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

  • Exchange Server 2010: Undeliverable Message

    Dear All,
    We are using exchange server 2010 to send a email to a client, however, we got this message back. How can i solve this problem?
    Thanks for your attention and help!
    次の受信者またはグループへの配信に失敗しました:
    [email protected] 受信者の電子メール プロバイダーによって拒否されたため、メッセージを配信できませんでした。
    メッセージは次の組織に拒否されました。BL2FFO11FD039.mail.protection.outlook.com。
    管理者向けの診断情報:
    生成サーバー: xxxx.com
    [email protected] BL2FFO11FD039.mail.protection.outlook.com #<BL2FFO11FD039.mail.protection.outlook.com #5.7.0 smtp;550 5.7.0 Relay Access Denied> #SMTP#
    元のメッセージ ヘッダー:
    Received: from na01-by2-obe.outbound.protection.outlook.com (207.46.163.241)
     by exch.xxxx.com (192.168.10.32) with Microsoft SMTP Server (TLS)
     id 14.3.210.2; Sun, 19 Oct 2014 22:36:47 -0700
    Received: from BN1AFFO11FD049.protection.gbl (10.58.52.31) by
     BN1AFFO11HUB044.protection.gbl (10.58.52.155) with Microsoft SMTP Server
     (TLS) id 15.0.1049.20; Mon, 20 Oct 2014 05:36:44 +0000
    Received: from mgcserv4.magsaysay.com.ph (203.167.92.249) by
     BN1AFFO11FD049.mail.protection.outlook.com (10.58.53.64) with Microsoft SMTP
     Server id 15.0.1049.20 via Frontend Transport; Mon, 20 Oct 2014 05:36:43
     +0000
    Received: from Crystal ([203.167.92.232])          by
     mgcserv4.magsaysay.com.ph (Lotus Domino Release 8.5.3)          with ESMTP id
     2014102013364607-10992 ;          Mon, 20 Oct 2014 13:36:46 +0800 
    X-TM-IMSS-Message-ID: <[email protected]>
    Received: from na01-bl2-obe.outbound.protection.outlook.com ([65.55.169.54])
     by magsaysay.com.ph ([203.167.92.232]) with ESMTP (TREND IMSS SMTP Service
     7.0; TLS: TLSv1/SSLv3,256bits,AES256-SHA) id 26975997000186d5 ; Mon, 20 Oct
     2014 13:40:58 +0800
    Received: from BL2FFO11FD041.protection.gbl (10.173.160.33) by
     BL2FFO11HUB022.protection.gbl (10.173.161.46) with Microsoft SMTP Server
     (TLS) id 15.0.1049.20; Mon, 20 Oct 2014 05:36:36 +0000
    Received: from mail.xxxx.com (216.81.51.170) by
     BL2FFO11FD041.mail.protection.outlook.com (10.173.161.137) with Microsoft
     SMTP Server (TLS) id 15.0.1039.16 via Frontend Transport; Mon, 20 Oct 2014
     05:36:36 +0000
    Received: from na01-by2-obe.outbound.protection.outlook.com (207.46.163.236)
     by exch.xxxx.com (192.168.10.32) with Microsoft SMTP Server (TLS)
     id 14.3.210.2; Sun, 19 Oct 2014 22:36:28 -0700
    Received: from BY2FFO11FD056.protection.gbl (10.1.14.33) by
     BY2FFO11HUB055.protection.gbl (10.1.14.244) with Microsoft SMTP Server (TLS)
     id 15.0.1039.16; Mon, 20 Oct 2014 05:36:15 +0000
    Received: from mailgate.zzz.com (14.16.28.51) by
     BY2FFO11FD056.mail.protection.outlook.com (10.1.15.193) with Microsoft SMTP
     Server id 15.0.1049.20 via Frontend Transport; Mon, 20 Oct 2014 05:36:13
     +0000
    X-AuditID: c0a81e07-b7f5e6d000000b4e-4d-54449f4b6588
    Received: from UNER2.zzz.com (unr2.zzz.com
     [192.168.30.13])      by mailgate.zzz.com (Symantec Messaging Gateway) with
     SMTP id CA.40.02894.B4F94445; Mon, 20 Oct 2014 13:36:11 +0800 (HKT)
    Received: from UN2.zzz.com ([::1]) by UNR2.zzz.com
     ([::1]) with mapi id 14.01.0438.000; Mon, 20 Oct 2014 13:36:11 +0800
    From: Yukihiro <[email protected]>
    To: Simonu <[email protected]>, Charles
            <[email protected]>
    CC: Miln <[email protected]>, FSA
            <[email protected]>
    Subject: Re: unia s maual / MV Kett Iand
    Thread-Topic: unaa sh ml / MVlettsland
    Thread-Index: Ac/sEV9D2LsdkU5fRkW0Rd1v4PsvSQAFlzIA
    Date: Mon, 20 Oct 2014 05:36:10 +0000
    Message-ID: <D06AC01C.21F27%[email protected]>
    References: <[email protected]>
    In-Reply-To: <[email protected]>
    Accept-Language: en-US
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator:
    user-agent: Microsoft-MacOutlook/14.4.2.140509
    x-originating-ip: [192.168.30.123]
    MIME-Version: 1.0
    X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJIsWRmVeSWpSXmKPExsVyYIUcr673fJcQg8bHChbzDrexW/R3vGG2
            OPK31GLjrinMDiwePbO6WAIYo7hsUlJzMstSi/TtErgy/my9w1Zw2LJi74lOxgbGd+ZdjJwc
            EgImEq27r7NA2GISF+6tZ+ti5OIQErjIKHF27jdmCGcCo8SpVw3MIFVsAtoS21rusILYIgKR
            En8nzgKzmQXiJL7sPAc2SVjAWOLni0tsEDUmEvNOdzNC2EYSp55dZgKxWQRUJa5unwBm8wro
            SVzdtgNsvpBAhETH9lawOZxA808+PwxmMwJd9/3UGiaIXeISlyYvYoO4WkBiyZ7zzBC2qMTL
            x//A7hEFmtnc9YYRIq4kcfbZAaA5HEC9wRJ3mzgg1gpKnJz5hGUCo9gsJFNnIVTNQlIFEdaU
            WL9LH6JaUWJK90N2CFtDonXOXCjbWuJq40IWZDULGDlWMQrlJmbmGOqV5mXqJhZnJuol5+du
            YoREJ/sOxg9NlocYBTgYlXh4pzi5hAixJpYVV+YeYpTgYFYS4f2XARTiTUmsrEotyo8vKs1J
            LT7EyMTBKdXAKPV7/zEX5dgtO6cd8N8764+UCO+vDPaVj5LWF051+GIx3/pf/dHiA0Gn+Lia
            by2Se/tyVqhMYGzs1CpNAcut2bfuLIhUOqbbIDv7buL74s/XWGIu27vcYoi+dJ9BSzA9WNnH
            h1NVbn+SgEDAhsL6Cyvs48Ja+1InV76xt515//fJOSLapX/uKbEUZyQaajEXFScCAFed/I2s
            AgAA
    Return-Path: [email protected]
    X-EOPAttributedMessage: 2
    X-Forefront-Antispam-Report-Untrusted: CIP:14.1.28.51;CTRY:HK;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(428002)(189002)(66654002)(199003)(252514010)(76176999)(21056001)(71186001)(31966008)(106466001)(81156004)(77096002)(95666004)(54356999)(105586002)(4396001)(50986999)(15975445006)(86362001)(83506001)(107046002)(84326002)(19617315012)(36756003)(85852003)(53416004)(92726001)(15974865002)(19580395003)(19580405001)(44976005)(101416001)(16236675004)(92566001)(87836001)(85306004)(99396003)(2656002)(46102003)(120916001)(15202345003)(20776003)(30436002)(512874002);DIR:INB;SFP:;SCL:1;SRVR:BY2FFO11HUB055;H:mailgate.zzzz.com;FPR:;MLV:sfv;PTR:014168051.static.ctinets.com;MX:1;A:0;LANG:en;
    X-Exchange-Antispam-Report-Test: UriScan:;UriScan:;UriScan:;
    Received-SPF: None (protection.outlook.com: zzz.com does not designate
     permitted sender hosts)
    Authentication-Results: spf=none (sender IP is 203.167.92.249)
     [email protected]; 
    X-Auto-Response-Suppress: DR, OOF, AutoReply
    X-Matching-Connectors: 130582569966280204;(42405700-fa69-4020-a9c4-08d0e394d333);()
    X-Forefront-Antispam-Report-Untrusted: CIP:216.81.51.170;CTRY:CA;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(10009020)(428002)(199003)(66654002)(252514010)(189002)(81156004)(106466001)(76176999)(54356999)(36756003)(77096002)(101416001)(53416004)(50986999)(105586002)(95666004)(31966008)(46102003)(20776003)(30436002)(19580395003)(4396001)(44976005)(19580405001)(16236675004)(6806004)(21056001)(71186001)(15974865002)(15202345003)(99396003)(84326002)(120916001)(15975445006)(83506001)(92726001)(92566001)(85852003)(86362001)(2656002)(87936001)(85306004)(107046002)(512874002)(19617315012);DIR:OUT;SFP:1101;SCL:1;SRVR:BL2FFO11HUB022;H:mail.xxx.com;FPR:;MLV:sfv;PTR:216.81.51.170.epikip.net;A:0;MX:1;LANG:en;
    X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BL2FFO11HUB022;UriScan:;
    X-Forefront-PRVS: 03706074BC
    X-MIMETrack: Itemize by SMTP Server on mgcserv4/mgc(Release 8.5.3|September 15, 2011) at
     10/20/2014 01:36:46 PM,
            Serialize by Router on mgcserv4/mgc(Release 8.5.3|September 15, 2011) at 10/20/2014
     01:36:47 PM,
            Serialize complete at 10/20/2014 01:36:47 PM
    X-TNEFEvaluated: 1
    Content-Type: multipart/alternative;
            boundary="_000_D06AC01C21F27hzzzcom_"
    Content-Language: ja-JP
    X-Forefront-Antispam-Report: CIP:203.167.92.249;CTRY:PH;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(428002)(252514010)(189002)(66654002)(199003)(76176999)(54356999)(86362001)(15974865002)(50986999)(85852003)(92566001)(92726001)(19617315012)(512874002)(46102003)(85306004)(97736003)(99396003)(120916001)(33186001)(53416004)(44976005)(105586002)(19580405001)(106466001)(16236675004)(77096002)(81156004)(19580395003)(95666004)(31966008)(71186001)(107046002)(21056001)(101416001)(15202345003)(84676001)(68736004)(30436002)(87836001)(2656002)(20776003)(4396001)(6806004)(84326002)(83506001)(15975445006)(36756003)(72026002);DIR:INB;SFP:;SCL:1;SRVR:BN1AFFO11HUB044;H:mgcserv4.magsaysay.com.ph;FPR:;MLV:sfv;PTR:ErrorRetry;MX:1;A:0;LANG:en;
    X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1AFFO11HUB044;

    Hi Shiloh,
    According to your description, my understanding is that you send a message to external user(@xxx.com) fail. 
    Before going further, I'd like to ask the following question to narrow down the issue:
    1. Could you send message to any other external user except xxx.com? like google.com,outlook.com.
    2. Try to disable or bypass Transport Scanning in Forefront Protection 2010 and check if any helps.
    You can refer to the following article to disable or bypass FPE:
    http://social.technet.microsoft.com/wiki/contents/articles/407.how-to-disable-or-bypass-transport-scanning-in-forefront-protection-2010-for-exchange-server-fpe.aspx
    Best regards,
    Niko Cheng
    TechNet Community Support

  • "Message Queued for submission" performance counter high for Exchange Server 2010 Database

    Hi,
    We are receiving SCOM Alert as "Mail Submission service is experiencing issue: Messages Queued for Submission-sustained for 15 mins-RED (>25)".
    After checking the "Messages queued for Submission" counter on the repective server it was found that the value is 66 but when we check the queue viewer we dont observe any messages stuck in Submission queue.
    Would like to know what aspects can be checked here, in order to troubleshoot the issue?
    The counter shows 0 value in perfmon for all other mailbox databases.
    Thanks & Regards.

    Hi,
    This is a known issue with Exchange Server 2007 and Exchange Server 2010.  We do not recommend that you use this counter for health alerts.
    I recommend you refer to the following article:
    http://support.microsoft.com/kb/2921142/en-us
    It is caused by the MailSubmission service submits a message for delivery multiple times, the counter is incremented two times but decremented only one time. This situation can leave the counter with a positive value even though there
    is no message in the queue. When you restart the service, the counter is reset. 
    Here is an similar thread for your reference:
    http://social.technet.microsoft.com/Forums/en-US/c9b485a5-ef0e-4b9a-851e-28c4a4c0606a/msexchangeis-mailbox-messages-queued-for-submission-keeps-increasing?forum=exchangesvradminlegacy
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Customize the Response Message for Resource Scheduling - Sent by Microsoft Exchange Server 2010

    We have a room mailbox and when one books it the organzier gets response with the following and the very botoom:
    Sent by Microsoft Exchange Server 2010
    I want to remove it as I dont want anybody to know what mail server we are running?  thankx

    Hi,
    As what Andy says, it is by default and there is no method to remove it.
    Sorry for any inconvenience.
    Regards,
    Winnie Liang
    TechNet Community Support

  • SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

    Hello,
    We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
    2010 cannot be installed".
    Here is the end of 'ExchangeSetup.log' showing various error messages:
    [11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
    [11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
    [11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
    [11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
    [11/29/2014 23:00:07.0522] [2] Unexpected Error
    [11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
    [11/29/2014 23:00:07.0523] [1] Executing:
    if ($server -eq $null)
    new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
    [11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
    [11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
    [11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
    [11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
    [11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
    [11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
    [11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    [11/29/2014 23:00:07.0609] [1] [ERROR] The following error was generated when "$error.Clear();
    if ($server -eq $null)
    new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
    " was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
    [11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
    [11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
    [11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
    [11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
    [11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    [11/29/2014 23:00:07.0633] [0] End of Setup
    [11/29/2014 23:00:07.0633] [0] **********************************************
    [11/29/2014 23:39:03.0429] [0] **********************************************
    [11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
    [11/29/2014 23:39:03.0435] [0] **********************************************
    [11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
    [11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
    [11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
    [11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
    [11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
    [11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
    [11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
    [11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
    [11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
    [11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
    [11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
    [11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
    [11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
    [11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
    [11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
    [11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
    [11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
    [11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
    [11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
    [11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
    [11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
    [11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
    [11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
    [11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
    [11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
    [11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
    [11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
    [11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
    [11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
    [11/29/2014 23:39:13.0920] [0] Applying default role selection state
    [11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
    [11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
    [11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
    [11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
    [11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
    [11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
    [11/29/2014 23:39:26.0117] [0] End of Setup
    [11/29/2014 23:39:26.0117] [0] **********************************************
    I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
    I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
    Thanks,
    Voon

    Thank you Larry and Al for your replies.
    I used the 'official' migration
    guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
    as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
    I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
    the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
    I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

  • Receive email delay one hour using Mac Mail client (Mountain Lion) connect Exchange Server 2010

    Hi all,
    My boss use iPhone, iPad, MacBook Air (Mac Mail client), MacPro (Mac Mail client) connect Exchange Serve 2010 to receive emails. All clients are okay except MacBook Air, the Mac Mail client cannot receive the latest emails from Exchange Server, but it can receive (sync) the emails after one hour. The other clients can receive the latest email after Exchange Server receive new emails immediately.
    In this period, the MacBook Air can receive the other IMAP, POP3 and webmail from ISP normally. I tried to set 5 mins to check emails or manual check email from Exchange Server. However, the latest email still delay one hour.......... .
    I dumped a screenshot for Mac Mail setting for Exchange Server and a Log file.
    could anyone help me to solve this issue?
    Thanks

    I am not sure what the user has the check for new messages set for but mail does arrive as short as 2 minutes.  It does however arrive on his iphone immediately first.

  • Exchange Server 2010 - OWA, ECP, EWS not working

    Hello,
    I am evaluating exchange server 2010. I was able to install it, but now the admin websites will not render in IIS.  OWA, ECP, etc. I especially want Outlook Anywhere to work.  I can admin through the windows admin interface so that's not a concern.
     I want users to access their email through the web as well.  I checked permissions but could have them wrong. Any help is appreciated.
    Thanks
    John Grace

    There are about twenty different types of 403 error. To see which one is happening here, you'd need to look at the IIS log files, and get the status subcode, which is the number after the 403 in the logged line.
    The most common, though, is 403.4, which means 'SSL Required'.  What happens if you go to
    https://servername (i.e. https instead of http).
    Another one is 403.6, which means that IIS has been configured to only allow access to a certain range of IP address, and the one you're trying to access it from isn't one of them.
    OWA For SmartPhone

  • Exchange Server 2010: Incoming mail not delivered

    I have an Exchange Server 2010 Standard with all recent patches and updates. 
    -It has been in service for 3 years without any issues. 
    -There is plenty of hard drive space for the logs and the data (over 100GB in each)
    -The current size of the mail database is 150GB
    -There is no registry entry in place limiting the size of the database ([url="http://technet.microsoft.com/en-us/library/bb232092.aspx"]Database Size Limit in GB as outlined here[/url]
    Starting a few days ago, incoming mail is reaching the server but not being delivered to user mailboxes. Internal mail works fine when this happens. Looking at the Queue Viewer doesn't show anything abnormal. The Submission Queue shows nothing.  
    It is only after I reboot the Exchange Server that the Submission queue will show all the messages waiting to be delivered and they will all be delivered successfully after the reboot. The event logs do not show any error messages.
    The server will continue to run fine for a few hours and then the problem starts all over again.
    What could be causing this?

    Any 3rd party antivirus/anti-spam software installed on the server? If so, disable and test.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Problems installing Mailbox role on Exchange Server 2010 SP3

    I am in the process of installing Exchange Server 2010 SP3 on a Windows Server 2012 server in order to migrate our existing Exchange 2003 server. Everything went well with the installation process until I went to add the Mailbox server role, which is giving
    me the following error (from the log file):
    [05/03/2013 21:58:09.0090] [1] Executing: 
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
    [05/03/2013 21:58:09.0105] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'TAM-FS2.tacomaartmuseum.org', Preferred Global Catalog: 'TAM-FS2.tacomaartmuseum.org', Preferred Domain
    Controllers: '{ TAM-FS2.tacomaartmuseum.org }'
    [05/03/2013 21:58:09.0105] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
    [05/03/2013 21:58:09.0276] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" 
    [05/03/2013 21:58:09.0344] [2] Process standard output: 
    [05/03/2013 21:58:09.0344] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
    [05/03/2013 21:58:09.0347] [2] [ERROR] Unexpected Error
    [05/03/2013 21:58:09.0347] [2] [ERROR] Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0350] [2] Ending processing Start-SetupProcess
    [05/03/2013 21:58:09.0350] [1] The following 1 error(s) occurred during task execution:
    [05/03/2013 21:58:09.0350] [1] 0.  ErrorRecord: Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0350] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0351] [1] [ERROR] The following error was generated when "$error.Clear(); 
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 87.".
    [05/03/2013 21:58:09.0351] [1] [ERROR] Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0351] [1] [ERROR-REFERENCE] Id=MailboxComponent___13A8A6B7DE0A4fe3BEB5CB1D86105DA3 Component=EXCHANGE14:\Current\Release\PIM Storage\Content Indexing
    [05/03/2013 21:58:09.0351] [1] Setup is stopping now because of one or more critical errors.
    [05/03/2013 21:58:09.0351] [1] Finished executing component tasks.
    [05/03/2013 21:58:09.0393] [1] Ending processing Install-MailboxRole
    I've searched all over but can't seem to find any reference to "exit code 87" - does anyone have any ideas?
    Thanks,
    Matt

    Error 87 -with these details below - and a fix. The situation that got me here by the way was an incomplete install that was uninstalled, then installed again.
    [02/24/2014 06:49:06.0967] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'xxxxxxxxxxxxxxx', Preferred Global Catalog: 'xxxxxxxxxxxxxxxxxxxxxxxx', Preferred Domain Controllers:
    '{ xxxxxxxxxxxxxxxxxxxxxxx }'
    [02/24/2014 06:49:06.0967] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
    [02/24/2014 06:49:06.0967] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man"
    [02/24/2014 06:49:07.0592] [2] Process standard output:
    [02/24/2014 06:49:07.0592] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
    [02/24/2014 06:49:07.0592] [2] [ERROR] Unexpected Error
    [02/24/2014 06:49:07.0592] [2] [ERROR] Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0592] [2] Ending processing Start-SetupProcess
    [02/24/2014 06:49:07.0592] [1] The following 1 error(s) occurred during task execution:
    [02/24/2014 06:49:07.0592] [1] 0.  ErrorRecord: Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0592] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0608] [1] [ERROR] The following error was generated when "$error.Clear();
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 87.".
    [02/24/2014 06:49:07.0608] [1] [ERROR] Process execution failed with exit code 87.
    I found I could fix this by removing the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Microsoft-Exchange-Troubleshooters/Operational
    and everything underneath it.
    My guess is that wevtutil didn't like adding an event log where it already existed but was slightly different in setup (no idea how, exactly).
    After 24 hours I'll try post again - giving things time to make sure they are actually working.

  • Exchange Server 2010 Installation

    I am getting the following error while installing Exchange Server 2010 on Server 2008 R2. Following is the log file:
    Summary: 3 item(s). 1 succeeded, 1 failed.
    Elapsed time: 00:00:02
    Preparing Setup
    Completed
    Elapsed Time: 00:00:00
    Mailbox Role
    Failed
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Error:
    The following error was generated when "$error.Clear(); if ([Environment]::OSVersion.Version.Major -ge 6) { $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe"; $reg= join-path (join-path $env:SystemRoot system32) reg.exe; $servicecmd = join-path
    (join-path $env:SystemRoot system32) sc.exe; if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"})) { if ((get-service wsbexchange).Status -eq "Running") { Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    } Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange"; } Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg"
    -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /t REG_SZ /d `"CExchangeHelper Class`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f"; Start-SetupProcess
    -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows
    nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery
    /t REG_DWORD /d 1 /f"; Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for
    Windows Server Backup`""; Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`""; }"
    was run: "Process execution failed with exit code 1.".
    Process execution failed with exit code 1.
    Elapsed Time: 00:00:02
    Finalizing Setup
    Cancelled

    Hi,
    Please make sure the account has required permissions: Schema Admins, Domain Admins, Enterprise Admins, and Organization Management.
    And please check if you have meet the prerequisites for Exchange 2010 installation.
    Exchange 2010 Prerequisites
    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.141).aspx
    In addition to the prerequisites, we also need to prepare AD and domain for Exchange 2010.
    Prepare Active Directory and Domains
    http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
    To narrow down the issue, I recommend you check the setup log to see if there is any clues.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange Server 2010 - DAG - Physical and Virtual

    Hi All,
    we are trying to configure Exchange Server 2010 SP1 DAG with TWO Servers, we are getting the error sector size on log file header was mismatch
    1) Physical Server -  when we check the sector size on log file - 512 bytes   (RAID5)
    2) Virtual Server  -  when we check the sector size on log file - 4096 bytes
    is there any workaround to solve this issue or do i need to re-install the physical server with 4096 sector size..
    When i check the Volume details on both machine
    1)
    Bytes Per Sector  :               512
    Bytes Per Physical Sector :       <Not Supported>
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024
    2)
    Bytes Per Sector  :               512
    Bytes Per Physical Sector :  4096
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024
    MCITP

    Hi Jared,
    I've got a question regarding your answer.
    We have an existing Exchange 2010 DAG configuration with 3 mailbox servers in NL and 3 in the UK.
    2 for normal databases at each site and 1 for Archive databases at each site.
    The current Mailbox servers for the Archive databases are Hyper V 2008 R2 based VM's with a passthrough for storing the databases.
    We now want add 1 new Mailbox server for storing archive databases at each site and add them to the DAG.
    Can we use Windows 2012 Hyper-V hosts and create the new VM's with 4k sectorsize vhdx files for the new mailbox servers ?
    Regards
    Misha Verhoeven 

Maybe you are looking for