Exchange Server 2013: Deploying High Availability and Site Resilience

Dear All,
I'm planning to Deploying High Availability and Site Resilience.
I have two data center and I have one exchange server on each site (multi-role).
I want to deploy Database Availability Group.
Is it possible? any idea?
in addition, all clients is connected to their email to their own site. dose it has any affected to Outlook users?
KH
[email protected]

Hi MAS,
Currently, I have only mailbox server and only database for each site.
+ Site1: I has DB1 and all users in site1 will access to their own site. (MBX1) subnet 192.168.1.0/24
+ Site2: I has DB2 and all users in site2 will access to their own site. (MBX2) subnet 192.168.2.0/24
But the email for incoming and outgoing with external will go to Site1.
In Planning,
I want to implement DAG to provide HA on database level below:
Is it possible to do that? dose it has any affected to current Outlook users?
BR,
KH
[email protected]

Similar Messages

Exchange server 2013 CAS High Availability

Dear All,
Next weekend i need to build Exchange CAS 2013 HighAvailbility can somebody help me please.
we don't have any load balancers we may use windows NLB (or) is there any way to build without load balancers and Windows NLB.
If possible i need step by step guide deploying cas 2013 HA.How do i redirect users to different cas server i need to have this control if one fails.
Thanks & Regards, Santosh Chowdary Vasireddy System Administrator Prolifcs DHFLVC Silicon Towers, 5th Floor, Survey #14, Kondapur, Hyderabad – 500 032. Work +91 40 3999 1999 Ex.1656 l Cell +91 9849277255 l [email protected] A Global
Provider of IBM, Microsoft and Testing Solutions Award Winner for Technical Excellence, BPM, SOA, Portal and Governance

There are a few options for load balancing.
DNS Round Robin is one of the way to go without any load balancing solution.
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx
The article above talks about each option and their advantages and disadvantages.
To enable round robin for Windows Server
Click Start, click All Programs, click Administrative Tools, and then click DNS.
Expand DNS, right-click the DNS server you want to configure, and then click Properties.
Click the Advanced tab, select Enable round robin and Enable netmask ordering, and then click OK.
Picked up from : http://technet.microsoft.com/en-us/library/gg398251.aspx
The link below is the way Microsoft has configured Load balancing and entire exchange architecture.
http://blogs.technet.com/b/exchange/archive/2014/04/21/the-preferred-architecture.aspx
Please be aware that, all the above needs careful planning before implementing. There are advantages as well as downsides to each of them.

Exchange Server 2013 deployment on VMware Fault Tolerance

Hi People,
Instead of using the DAG feature on the Exchange Server 2013, so what is the caveats in deploying the Exchange Server 2013 stand alone and then implementing the Vmware FT or at least HA to give the availability at the Hypervisor level ?

Hey AlbertWT,
With Exchange 2010, try not to think of entire servers as being active or passive. Instead, think of database copies as being active or passive. Your Mailbox role virtual machine can contain both active and passive copies of databases within your DAG.
Think of a scenario where you have three virtual machines running the Exchange 2010 Mailbox role and you have a total of three databases. You would have an active copy of each database and then presumably two passive copies as well. That there is only one active database on a Mailbox server at a time, and if that server fails there are two other copies that can come online automatically.
In the case of vSphere HA, if you lose a host that's running a Mailbox server, that active database would automatically be brought up on one of the two surviving Mailbox servers. vSphere HA would then automatically restart that failed virtual machine on another host and you'd quickly be back to having three Exchange Mailbox servers online.
Does that help clarify things for you?
Matt
http://www.thelowercasew.com

Exchange Server 2013 Mailbox - High CPU Usage

Hi,
We are having an issue with our Exchange 2013 Mailbox Server.
The process Microsoft.Exchange.Store.Worker consumes most of the CPU utilization.
Have anyone encountered this issue? How were you able to resolve it?
Thanks

Hi,
According to your description, your database is not active. And to understand more about the issue, I’d like to confirm if there is some user experience slow connection or other performance issue.
However, since in Exchange 2013 single Store Worker Process is only responsible for one database, we can firstly confirm if the specific mailbox database causes the high CPU:
http://msexchangeteam.in/how-to-identify-which-microsoft-exchange-store-worker-process-is-owned-by-mailbox-database-in-exchange-server-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.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange server 2013 supported mailbox databases and public folder databases

I want to know about Exchange server 2013 SP1 Standard and Enterprise version support how many Mailbox databases and Public folder Databases? Total Mailbox and Public folder databases supported information.
I Know as below but not clear:
1) Exchange server 2013 SP1 Sandard edition support 5 Databases, It's include Public folder databases, total=5 or 5 mailbox databases+5 public folder databases=10 databases
2) Exchange server 2013 SP1 Enterprise edition support 100 Databases, It's include Public folder databases, total=100 or 100 mailbox databases+100 public folder databases=200 databases
kindly let me know. Thanks.
Babu

Hi Babu,
Please check this link too.
http://blogs.technet.com/b/exchange/archive/2013/06/04/per-server-database-limits-explained.aspxhttp://blogs.technet.com/b/exchange/archive/2013/06/04/per-server-database-limits-explained.aspx
Thanks & Regards S.Nithyanandham

Exchange Server 2013 restarts frequently after Cumulative Update 3 is installed

Hi All,
In our Environment Exchange Server 2013 CU3 is installed and restarts every alternate days.Below are the details
Event Id : 6008
The previous system shutdown at 03:13:44 on ‎12-‎06-‎2014 was unexpected.
Evend Id : 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xfffffa800e9a8080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061214-30108-01.
Event 41, Kernal Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Can somebody help me through this because it was causing severe to our organization and restarts frequently as well.

Hello,
Try following solutions:
http://support.microsoft.com/kb/2883203/en-us
http://itsalwaysmyproblem.com/2013/08/27/exchange-2013-and-bugcheck-0x000000ef/
Also installing CU5 may be helpful.
Hope it helps,
Adam
www.codetwo.com
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.

Deploying 2x Exchange Server 2013 CAS server email traffic high availability during patching & reboot

Hi people,
What is the best way to utilize VMware technology to host 2x the Exchange Server 2013 CAS role VM in my production VM to ensure that the email traffic is not halted during server patching ?
Previously in Exchange Server 2007 I am using Windows NLB (IGMP Multicast) on my ESXi 4.1, now with ESXi 5.1 and 2013 I wonder if there is any better way to make sure that the server failover does not disrupt the mail flow between the Smarthost and the CAS server role.
Thanks

Hey AlbertWT,
Can you clarify exactly what you mean when you say "server patching?" Do you mean patching at the ESXi host level or something within the guest?
As you probably know Exchange 2013 CAS no longer needs NLB or even a hardware load balancer. Due to changes in the architecture, even simple DNS round robin is "enough" to load balance the CAS role. NLB has its own set of headaches which you are probably all too familiar with so getting rid of that can help remove a lot of complexity from the situation.
If you can clarify what you mean by "server patching" and "server failover" in your post I think that would be helpful for me to give you a more definitive answer.
Matt
http://www.thelowercasew.com

Exchange Server 2013 migration and high avalability

Hello,
We are using Office 365 online and will be migrating onto an in-house Exchange Server 2013 on a new Windows Server box.
I have two questions:
1. What is the best way to migrate everything from the Office 365 to the in house server? Do I setup a hybrid environment and then move the mailboxes and then remove the hybrid environment?
2. What is the best way to setup high availability for the in-house Exchange server? I found out that in order to setup Exchange 2013 as high availability it needs to run on Windows server 2012 STD or Windows server 2008 Enterprise.
Please let me know and provide links to step by step instructions if possible.
Thank you, Karel
Thank you. Karel Grulich, MCSE, SBS

Hi Karel,
Thank you for your question.
In addition Ed’s suggestion, moving mailbox form Exchange online to Exchange on premise could be refer to the following link:
https://technet.microsoft.com/en-us/library/jj906432(v=exchg.150).aspx
Exchange 2013 high availability could be referred by the following link:
https://technet.microsoft.com/en-us/library/dd638137(v=exchg.150).aspx
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

Exchange server 2013 CAS server high availability

Hi
I have exchange server 2010 sp3(2 MB, 2Hub/Cas) servers.
Planning to migrate to exchange server 2013.( 2 cas servers and 2 mbx servers).
I dont want to go all traffic single so i am keeping the role separate..
In exchange 2010 i achieved hub/CAS high availability through NLB.
In exchange 2013 how to acheive this...
Please share your suggestions with document if possible...

Here ya go:
http://technet.microsoft.com/en-us/library/jj898588(v=exchg.150).aspx
Load balancing
and
http://technet.microsoft.com/en-us/office/dn756394
Even though it says 2010, it applies to 2013 vendors as well.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Deploying Windows Server 2012 and Exchange Server 2013

Hi All,
Our Clinet is planning to implement Exchange Server 2013 as an email solution. There is no Active Directory Domain exists in the environment. So, we have planned to configure a Windows Server 2012 R2 Standard as a Domain Controller and Exchange
Server 2013 Standard would be installed on another Windows Server 2012 R2 Standard.
The setup would be for 250 users. Please guide me about the Cost of OS + Exchnage and CAL for 250 Users.
Warm Regards,
Prosenjit Sen
Thanks & Regards, Prosenjit Sen.

Another option would be to consider signing up for Office 365 instead of setting up the hardware and software for such a small number of users. It will take a long time for the cost of the hardware, maintenance, and support to be less costly than Office
365, if it would ever be less expensive. There is a lot of maintenance required for Exchange, so unless your client already has someone experienced in configuring and maintaining Exchange, there is a lot of expense in bringing someone up to speed to
perform those functions capably.
Just a suggestion. I do not work for Microsoft and I have no financial incentive to propose an Office 365 environment. I just know that if I were running my own business, I would have to be convinced that my business required its own internal
mail system when there are so many fully functional and capable mail systems available via subscription.
. : | : . : | : . tim

Exchange Server 2013 and Remote Access VPN on a single server running Windows Server 2012?

Just by way of background, I have been installing and administering network servers, e-mail systems, VPN servers, and the like for many years. However, my involvement with Exchange and Windows Server has been mostly on the forensics and data recovery
level, or as a (sophisticated) user. I have never tried to deploy either from scratch before. My deployment experiences have been mostly with Linux in recent years, and with small private or personal "servers" running such cutting edge
software as Windows XP back when it was new. And even NetWare once.
When a client asked me if I could set up a server for his business, running Exchange Server (since they really want Outlook with all of its bells and whistles to work, particularly calendars) and providing VPN access for a shared file store, I figured it
could not be too difficult given that its a small business, with only a few users, and nothing sophisticated in the way of requirements. For reasons that don't bear explaining here, he was not willing to use a vendor hosting Exchange services or cloud
storage. There is no internal network behind the server; it is intended to be a stand-alone server, hanging off a static IP address on the Internet, providing the entirely mobile work-force of about 10 people with Exchange-hosted e-mail for their computers
and phones, a secure file store, and not much else. If Exchange didn't need it, I would not need to install Active Directory, for example. We have no direct need for its services.
So I did the research and it appears, more by implication than outright assertion, that I should be able to run Windows Server 2012 with Exchange Server 2013 on a server that also hosts Remote Access (VPN only) and does nothing else. And it appears
I ought to be able to do it without virtualizing any of it. However, I have spent the last three or four days fighting one mysterious issue after another. I had Remote Access VPN working and fairly stable very quickly (although it takes a very
long time to become available after the server boots), and it has mostly remained reliable throughout although at times while installing Exchange it seems to have dropped out on me. But I've always been able to get it back after scrounging through the
logs to find out what is bothering it. I have occasionally, for a few minutes at a time, had Exchange Server willing to do everything it should do (although not always everything at the same time). At one point I even received a number of e-mails
on my BlackBerry that had been sent to my test account on the Exchange Server, and was able to send an e-mail from my BlackBerry to an outside account.
But then Exchange Server just stopped. There are messages stuck in the queues, among other issues, but the Exchange Administration Center refuses now to display anything (after I enter my Administrator password, I just get a blank screen, whether on
the server or remotely).
So, I am trying to avoid bothering all of you any more than I have to, but let me just begin with the basic question posed in the title: Can I run Exchange Server (and therefore Active Directory and all of its components) and Remote Access (VPN only) on
a single Windows Server 2012 server? And if so, do I have to run virtual machines (which will require adding more memory to the server, since I did not plan for it when I purchased it)? If it can be done, can anyone provide any pointers on what
the pitfalls are that may be causing my problems? I am happy to provide whatever additional information anyone might like to help figure it out.
Thanks!

An old thread but I ran into this issue and thought I share my solution since I ran into the same issue. Configuring VPN removes the HTTPS 443 binding on the Default Site in IIS for some strange reason; just go and editing the bindings, add HTTPS and things
should be back to normal.

New Deployment of Exchange Server 2013.

Hello All,
Good Day !!
We are planning to install Exchange 2013 Mailbox and Client Access on single server ( Windows Server 2012 Standard).
Currently Active Directory roles runs on windows server 2008R2 Sp1.
Its a new deployment for exchange as currently we are using Godaddy email server ( Can we migrate all our emails from Go daddy to our exchange Server).
Also confirm current active directory will support the installation and deployment of Exchange Server 2013.
How much HDD, RAM and CPU cores are required to support exchange Server Mailbox and Client Access roles( Users are 30 ).
How many Static IP's and SSl certificates are required for exchange.
Atlast as i said its new deployment please suggest if anything else is missing from my end.

Hello,
I recommend using professional cheat-sheet articles for Exchange 2013 sizing:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part1.html
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part2.html
The server's requirements depend on many factors ie. number of emails received/sent, mailboxes sizes etc.
In addition your AD environment's level supports Exchange 2013 deployment. You will need only prepare your schema and forest for Exchange installation. You will need also at least one public IP address and SSL certificate for that 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.

Exchange Server 2013 and Office 365 Integration

If we are using Exchange Server 2013 on premise, can we have 2 of our users integrated with Office 365 so that they can utilize their Exchange Server email account with the apps and features of Office 365?

Hi,
You can deploy a hybrid environment using Exchange 2013 CU2 or later version with Office 365.
Could you please tell me what do you mean by "we have 2 of our users integrated with Office 365 so that they can utilize their Exchange Server email account with the apps and features of Office 365"?
Here is my understanding: You create these two mailboxes on Exchange 2013, but you need to allow for redirection from the on-premises OWA environment to the Office 365 OWA. If that is your case, you need to specify a target URL for your organization(for
example, www.outlook.com/contoso.com). If I have misunderstood your concern, please let me know.
For more information, here is an article for your reference.
Plan an Exchange Online hybrid deployment in Office 365
http://technet.microsoft.com/en-us/library/hh852414.aspx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Trying to install Exchange Server 2013 and receive this error.

Hello,
I have a computer running Windows Server 2012 R2 Standard. I have completed all the prerequisites to install Exchange Server 2013. It all was going good until the install started. Then I received the below error. Does anyone have any suggestions? I am new
to Exchange Server so would thank and appreciate any help I could get to resolve this issue.
Thank You,
Stan
Error:
The following error was generated when "$error.Clear();
initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
" was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:A7D2016C83F003458132789EEB127B84:CN=Exchange Servers\0ADEL:16cd035a-6201-492f-b85f-1e28cc9f9ee0,CN=Deleted Objects,DC=MULTIAXCNC,DC=local on
the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MULTIAXCNC,DC=local points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Here is the error I am getting and the last setup log I can find. Any help how to get past the error would be helpful.
Thank You,
Stan
Error
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.AddAccessRuleCryptographicException: Could not grant Network Service access to the certificate with thumbprint 845C42A131A8A73487400A91491182FB95B81612
because a cryptographic exception was thrown. ---> System.Security.Cryptography.CryptographicException: Access is denied.
   at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.CAPIAddAccessRule(X509Certificate2 certificate, AccessRule rule)
   at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.AddAccessRule(X509Certificate2 certificate, AccessRule rule)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ManageExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services, String websiteName, Boolean requireSsl, ITopologyConfigurationSession dataSession, Server server,
List`1 warningList, Boolean allowConfirmation, Boolean forceNetworkService)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Setup Log Below
# Default Install steps for ClientAccessRole.
# Programmatically generated on 7/5/2014 10:58:24 PM.
# Variable Declarations
$RoleAllRoles = 'BridgeheadRole,GatewayRole,ClientAccessRole,MailboxRole,UnifiedMessagingRole,FrontendTransportRole,AdminToolsRole,MonitoringRole,CentralAdminRole,CentralAdminDatabaseRole,CentralAdminFrontEndRole,LanguagePacksRole,CafeRole,FfoWebServiceRole,OSPRole'
$RoleBinPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Bin'
$RoleCustomerFeedbackEnabled = $True
$RoleDatacenterPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Datacenter'
$RoleDatacenterServiceEndpointABCHContactService = '<ServiceEndpoint><Url>http://pvt-contacts.msn.com/abservice/abservice.asmx</Url></ServiceEndpoint>'
$RoleDatacenterServiceEndpointDomainPartnerManageDelegation = '<ServiceEndpoint><Url>https://domains.live.com/service/managedelegation.asmx</Url></ServiceEndpoint>'
$RoleDatacenterServiceEndpointDomainPartnerManageDelegation2 = '<ServiceEndpoint><Url>https://domains.live.com/service/managedelegation2.asmx</Url></ServiceEndpoint>'
$RoleDatacenterServiceEndpointLiveFederationMetadata = '<ServiceEndpoint><Url>https://nexus.passport.com/FederationMetadata/2006-12/FederationMetadata.xml</Url></ServiceEndpoint>'
$RoleDatacenterServiceEndpointLiveGetUserRealm = '<ServiceEndpoint><Url>https://login.live.com/GetUserRealm.srf</Url></ServiceEndpoint>'
$RoleDatacenterServiceEndpointLiveServiceLogin2 = '<ServiceEndpoint><Url>https://login.live.com/RST2.srf</Url></ServiceEndpoint>'
$RoleDatacenterServiceEndpointMsoFederationMetadata = '<ServiceEndpoint><Url>https://nexus.microsoftonline-p.com/FederationMetadata/2006-12/FederationMetadata.xml</Url></ServiceEndpoint>'
$RoleDomainController = 'MULTIAX2012.MULTIAXCNC.local'
$RoleExternalCASServerDomain = $null
$RoleFqdnOrName = 'MULTIAX2012.MULTIAXCNC.local'
$RoleInstallationMode = 'Install'
$RoleInstallPath = 'C:\Program Files\Microsoft\Exchange Server\V15\'
$RoleInvocationID = '20140705-2258240578829153548'
$RoleIsAdminToolsRoleInstalled = $True
$RoleIsBridgeheadRoleInstalled = $True
$RoleIsDatacenter = $False
$RoleIsDatacenterDedicated = $False
$RoleIsFfo = $False
$RoleIsPartnerHosted = $False
$RoleLanguagePacksPath = 'C:\Exchange\'
$RoleLoggedOnUser = 'MULTIAXCNC\Administrator'
$RoleLoggingPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Logging'
$RoleNetBIOSName = 'MULTIAX2012'
$RoleNoSelfSignedCertificates = $False
$RolePreviousVersion = $null
$RoleProductPlatform = 'amd64'
$RoleRoleName = 'ClientAccessRole'
$RoleRoles = 'BridgeheadRole,AdminToolsRole'
$RoleSetupLoggingPath = 'C:\ExchangeSetupLogs'
$RoleTargetVersion = '15.00.0913.022'
$RoleUpdatesDir = $null
# Component tasks
# Tasks for 'All Roles Common First' component
# [ID = AllRolesCommonFirst___3e69ba31a53e4c29a2d6bffcf78cc614, Wt = 5, isFatal = True] "Starting the WMI service."
7/5/2014 10:58:24 PM:
          if (Get-Service winmgmt* | ?{ $_.Name -ieq "winmgmt" })
            Set-Service winmgmt -StartupType Automatic
            Start-SetupService -ServiceName winmgmt
# [ID = AllRolesCommonFirst___56139ce4432346ecb7936afae4c3a9cc, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
7/5/2014 10:58:24 PM:
          & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoleName.Replace('Role','')
# [ID = AllRolesCommonFirst___edc23bc11a4e4119a6a4ee802ff1ea49, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
7/5/2014 10:58:24 PM:
          if ($RoleRoles)
            & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoles.Replace('Role','').Split(',')
# [ID = AllRolesCommonFirst___62f13a063b2846a5ab20765bb7a3fc51, Wt = 5, isFatal = True] "Starting the Remote Registry service."
7/5/2014 10:58:25 PM:Start-SetupService -ServiceName RemoteRegistry
# [ID = AllRolesCommonFirst___00573a17b6e34c26842a6646830d57fa, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
7/5/2014 10:58:25 PM:Set-LocalPermissions
# [ID = AllRolesCommonFirst___77668249568048d3812fb7cdba08c58b, Wt = 1, isFatal = False] "Creating the Exchange server configuration object in Active Directory."
7/5/2014 10:59:35 PM:
          $mofFilePath = ($RoleInstallPath + "bin\Exchange.MOF");
          $mflFilePath = ($RoleInstallPath + "bin\en\Exchange.MFL");
          compile-moffile -MofFilePath:$mofFilePath;
          compile-moffile -MofFilePath:$mflFilePath;
# [ID = AllRolesCommonFirst___f557448f44964e5eaa5dba792a3c4f09, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
7/5/2014 10:59:35 PM:
           Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeRPCByPortRule)
# [ID = AllRolesCommonFirst___84a0f0e2c2f44db2b537e9696c26fc3e, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
7/5/2014 10:59:35 PM:
           Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeRPCEPMapByPortRule)
# Tasks for 'ClientAccess Permissions Configuration' component
# [ID = ClientAccessLocalPermissionsComponent___6246589bb8494a3580c22c26e18451d1, Wt = 1, isFatal = True] "Setting folder or registry permissions for the Mailbox role: Client Access service. "
7/5/2014 10:59:35 PM:Set-LocalPermissions -Feature:"ClientAccess"
# Tasks for 'Exchange 2003 Registry Configuration' component
# [ID = LegacyRegistryMarkersComponent___7d6dadc1069b42ac93eadd1143c04a1a, Wt = 1, isFatal = True] "Installing/Removing registry values used by Exchange 2003 components"
7/5/2014 11:00:01 PM:set-ExsetdataRegistryMarkers
# Tasks for 'Client Access Perf Counters' component
# [ID = ClientAccessPerfCountersComponent___deb99c54869843b68426390615283ab7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:01 PM:new-PerfCounters -DefinitionFileName OwaInstallSingleCounters.xml
# [ID = ClientAccessPerfCountersComponent___ca78563ec1f1468982d1a2e59c6001bd, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:15 PM:new-PerfCounters -DefinitionFileName EcpPerfCounters.xml
# [ID = ClientAccessPerfCountersComponent___e69a559428fb42029ca3261e795b216d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:21 PM:new-PerfCounters -DefinitionFileName RwsPerfCounters.xml
# [ID = ClientAccessPerfCountersComponent___c335490f948a4b16b5e2d2ce5f1eb9e7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:26 PM:new-PerfCounters -DefinitionFileName InfoworkerAvailabilityPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___5af856aa00ae485ca206c5cdd13e9128, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:31 PM:new-PerfCounters -DefinitionFileName InfoworkerSharingPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___86121d1b951e43fb934f1f1d573362eb, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:35 PM:new-PerfCounters -DefinitionFileName ThrottlingPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___ea5896b92c494834b1a93c4620fcaef4, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:42 PM:new-PerfCounters -DefinitionFileName MiddleTierStoragePerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___dab6f03bdf5141efb7b017c3009fb9e6, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:48 PM:new-PerfCounters -DefinitionFileName ActiveManagerClientPerfmon.xml
# [ID = ClientAccessPerfCountersComponent___5471455db0ef4610bf68fe7ad9417e19, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:53 PM:new-PerfCounters -DefinitionFileName RmsPerfCounters.xml
# [ID = ClientAccessPerfCountersComponent___81ad52cb2950483196b52371b4d992c8, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:00:58 PM:new-PerfCounters -DefinitionFileName InfoworkerMailTipsPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___072bf6737f1c42a0a8847ce35cf8a0c7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:01:03 PM:new-PerfCounters -DefinitionFileName InfoworkerUserPhotosPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___50b64611f7444bb49d50e00c206d2c13, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:01:08 PM:new-PerfCounters -DefinitionFileName AirSyncCounters.xml
# [ID = ClientAccessPerfCountersComponent___f2620ff8c3754396a8ea7d77257e2895, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:01:14 PM:new-PerfCounters -DefinitionFileName ClientAccessRulesPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___4ef0f16c017840a583ace9f062300207, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:01:19 PM:new-PerfCounters -DefinitionFileName Imap4Counters.xml
# [ID = ClientAccessPerfCountersComponent___135fb06dadd9403a83ceebb290638efe, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:01:24 PM:new-PerfCounters -DefinitionFileName Pop3Counters.xml
# [ID = ClientAccessPerfCountersComponent___312e8d44e92b45e0809f9d3d5dc2cfc0, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:01:29 PM:new-PerfCounters -DefinitionFileName WsPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___3c333497697041cb854190ec31c17b18, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:01:48 PM:new-PerfCounters -DefinitionFileName UMClientAccessCounters.xml
# [ID = ClientAccessPerfCountersComponent___ba015b97cc0b4beba7b25b6cb297fcac, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:01:54 PM:new-PerfCounters -DefinitionFileName AutodiscoverPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___3daffea50d5a4318aab4aa737e508146, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:01:59 PM:new-PerfCounters -DefinitionFileName OAuthCounters.xml
# [ID = ClientAccessPerfCountersComponent___c71073d7f1ab4c119af83efb513b3a9d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:04 PM:new-PerfCounters -DefinitionFileName InfoWorkerMessageTrackingPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___abdaf0bf21f4473b88819ee85cada219, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:10 PM:new-PerfCounters -DefinitionFileName RpcClientAccessPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___9f160f3e42984edfa25b62424ebc05b5, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:15 PM:new-PerfCounters -DefinitionFileName RpcClientAccessServerPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___e55cb179521a4dacbeaa588c6948cf14, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:15 PM:new-PerfCounters -DefinitionFileName AddressBookServicePerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___064a7856cf7c4b0399c85cf4f3bc2f1c, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:20 PM:new-PerfCounters -DefinitionFileName RpcEntryPointsPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___42325F33-A961-41FE-B6B5-5CFB3AA9820A, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:22 PM:new-PerfCounters -DefinitionFileName MapiHttpEmsmdbPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___4C04D747-3B5C-400A-980F-45504324EF42, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:28 PM:new-PerfCounters -DefinitionFileName MapiHttpNspiPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___5ab36fffacd04975bb1bc681a214bf71, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:33 PM:new-PerfCounters -DefinitionFileName ThrottlingServiceClientPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___6ca23933132d44b39d6586cb3f9f8f21, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:39 PM:new-PerfCounters -DefinitionFileName MSExchMailboxReplicationServicePerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___6602c41b35254405bed412fab7d527fe, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:44 PM:new-PerfCounters -DefinitionFileName MSExchMailboxReplicationServicePerMdbPerformanceCounters.xml -FileMappingSize 2097152
# [ID = ClientAccessPerfCountersComponent___74e45a45ea8c449092a10929ae24ba4b, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:50 PM:new-PerfCounters -DefinitionFileName MlbPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___a3bcb686add64cf296c8616d387d0323, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:02:55 PM:new-PerfCounters -DefinitionFileName MlbMultiInstancePerformanceCounters.xml -FileMappingSize 2097152
# [ID = ClientAccessPerfCountersComponent___c00c15c4ef6f479b9f5deb852d8eda7d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:03:01 PM:new-PerfCounters -DefinitionFileName ProvisioningPerfCounters.xml
# [ID = ClientAccessPerfCountersComponent___fe1a2a7c828f4b57abc2e50dc09baddf, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:03:06 PM:new-PerfCounters -DefinitionFileName GalsyncPerfCounters.xml
# [ID = ClientAccessPerfCountersComponent___35D14CB8B01949818832943A391D77B9, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:03:11 PM:new-PerfCounters -DefinitionFileName BackSyncPerfCounters.xml
# [ID = ClientAccessPerfCountersComponent___e69599d235234effb6d2740f3c52f7e1, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:03:11 PM:new-PerfCounters -DefinitionFileName AdminAuditPerfCounters.xml
# [ID = ClientAccessPerfCountersComponent___09bd11b57f6445e890391a507262cf32, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:03:16 PM:new-PerfCounters -DefinitionFileName InfoworkerMultiMailboxSearchPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___324687361E1C473A834C22A66104679f, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:03:16 PM:new-PerfCounters -DefinitionFileName ProvisioningCachePerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___98C36FFEC7944065889DB24067CFD3EE, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:03:21 PM:new-PerfCounters -DefinitionFileName OABRequestHandlerPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___1F5A7B68C95B42568E02FAA15A05EF17, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:03:26 PM:new-PerfCounters -DefinitionFileName DlpPolicyTipsPerformanceCounters.xml
# [ID = ClientAccessPerfCountersComponent___995DEA7A1AC5467C89939F5F8CE5F2AF, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
7/5/2014 11:03:31 PM:new-PerfCounters -DefinitionFileName ConfigurationCachePerformanceCounters.xml
# Tasks for 'Client Access Configuration' component
# [ID = ClientAccessComponent___d5119205104847bcb275cb63b65160b6, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
7/5/2014 11:03:35 PM:
          $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\Owa\Bin\Microsoft.Exchange.Clients.Owa.dll");
          $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
          precompile-ManagedBinary -BinaryName $fullPath -AppBase $appBase;
# [ID = ClientAccessComponent___954344d74d8849e9ae7123b91761ed9d, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
7/5/2014 11:03:57 PM:
          $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\Sync\Bin\Microsoft.Exchange.AirSyncHandler.dll");
          $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
          precompile-ManagedBinary -BinaryName $fullPath -AppBase $appBase;
# [ID = ClientAccessComponent___6632d6c1d5054563942db4f180976238, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
7/5/2014 11:04:01 PM:
          $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\AutoDiscover\Bin\Microsoft.Exchange.AutoDiscover.dll");
          $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
          precompile-ManagedBinary -BinaryName $fullPath -AppBase $appBase;
# [ID = ClientAccessComponent___390b4ffddd484dcb9edc01dd725e020a, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
7/5/2014 11:04:07 PM:
          $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\exchweb\ews\bin\Microsoft.Exchange.Services.dll");
          $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
          precompile-ManagedBinary -BinaryName $fullPath -AppBase $appBase;
# [ID = ClientAccessComponent___178a10624c88445093855c4ede7e9b9c, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:42 PM:
          . "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
          Set-NtlmLoopbackCheck $false
# [ID = ClientAccessComponent___14a6761e144e428b93c62249acc814fe, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:42 PM:install-ClientAccessIisWebServiceExtensions
# [ID = ClientAccessComponent___28fdfe8bec984e809cdeef6d4d59bf4e, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:43 PM:
        if (get-service MSExchangeServiceHost* | where {$_.name -eq "MSExchangeServiceHost"})
            restart-service MSExchangeServiceHost
# [ID = ClientAccessComponent___7816256880dc4be0baf5b005b2af8cd3, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:45 PM:
        if (get-service MSExchangeProtectedServiceHost* | where {$_.name -eq "MSExchangeProtectedServiceHost"})
            restart-service MSExchangeProtectedServiceHost
# [ID = ClientAccessComponent___e95499b43bd1484dbc03098fb1b4e592, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:45 PM:set-ExchangeServerRole -Identity $RoleFqdnOrName -IsClientAccessServer:$true -DomainController $RoleDomainController
# [ID = ClientAccessComponent___f4c48e196e374cf3af269b1cea0602c8, Wt = 1, isFatal = True] "Installing/Removing the WebReady Document Viewing service."
7/5/2014 11:04:45 PM:Install-TranscodingServiceEx
# [ID = ClientAccessComponent___f50fd59d231140eb9b2405bbed2b93d4, Wt = 1, isFatal = False] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:45 PM:
          if ($RoleIsDatacenter -eq $false)
            uninstall-FBAService
# [ID = ClientAccessComponent___9fad9d51b3ec4ecdad567ab58e470be7, Wt = 1, isFatal = False] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:45 PM:
          if ($RoleIsDatacenter -eq $false)
            stop-setupservice -ServiceName MSExchangeFBA
# [ID = ClientAccessComponent___1c7a7da2ab9d41bb8db75522ad28b9db, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:45 PM:
          $tpath = "$env:SystemRoot\system32\inetsrv\microsoft.web.administration.dll";
          add-type -Path $tpath;
          $sm = new-object Microsoft.Web.Administration.ServerManager;
          if ($sm.Sites["Exchange Back End"] -eq $null)
            $ppath = "$env:SystemDrive\inetpub\wwwroot";
            $s = $sm.Sites.Add("Exchange Back End","http", "*:81:", $ppath);
            $s.ServerAutoStart = $true;
            $sb =$s.Bindings;
            $b = $sb.Add("*:444:","https");
            $sm.CommitChanges();
# [ID = ClientAccessComponent___a5f211d837784aea931b9ba55c39996d, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:45 PM:
          Get-ExchangeServer $RoleFqdnOrName | Add-AdPermission -User "S-1-5-20" -ExtendedRights "Exchange Web Services Token Serialization";
# [ID = ClientAccessComponent__SetInstallPathInMrsAppConfig, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:45 PM:
          Set-InstallPathInAppConfig -ConfigFileRelativePath "Bin" -ConfigFileName "MsExchangeMailboxReplication.exe.config"
# [ID = ClientAccessComponent___765cc444ba07411aa81d58397b0401fd, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:45 PM:
          if (!(get-service MSExchangeMailboxReplication* | where {$_.name -eq "MSExchangeMailboxReplication"}))
            install-MailboxReplicationService
# [ID = ClientAccessComponent___151b722e327b42a69411df32afdbbcbb, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:46 PM:
           Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeMailboxReplicationFirewallRule)
# [ID = ClientAccessComponent___7d69bb94f08245589e49eb569c6d5f4f, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:46 PM:
          if (!(get-service MSExchangeMigrationWorkflow* | where {$_.name -eq "MSExchangeMigrationWorkflow"}))
            install-MigrationWorkflowService
# [ID = ClientAccessComponent___95f051d9dc5941c4b6014181b6e5ce93, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:
           Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeABRPCFirewallRule)
# [ID = ClientAccessComponent___959c2d6566984da6b8e0e3235c1c11c2, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:
           Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangePOPBeByPortRule)
# [ID = ClientAccessComponent___29864e7462374fdb84fc75eec931d8e4, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:
          Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeIMAP4BeFirewallRule)
# [ID = ClientAccessComponent___052e1b794d0641ada4d6d417061af2a8, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:
           Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeOWAByPortRule)
# [ID = ClientAccessComponent___975efd8911fd41cca8b17462535d710e, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:
           Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeMailboxReplicationByPort)
# [ID = ClientAccessComponent___023036e43f004bda9f4f4e0b1e0d233f, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:
          Install-ResourceHealthActiveFlags
# [ID = ClientAccessComponent___3a51c2876e2c4643bc892d2665754228, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\PushNotifications\" -ConfigFileName web.config
# [ID = ClientAccessComponent___FCC16AC1FFED43518F8292DBE770C621, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\mapi\emsmdb\" -ConfigFileName web.config
# [ID = ClientAccessComponent___E9C71786D02E40CBB1403E2E1A4B0758, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\mapi\nspi\" -ConfigFileName web.config
# [ID = ClientAccessComponent___abcab6b91ac844848c58b4ee66fcbea6, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:
            ."$RoleInstallPath\Scripts\Install-OutlookServiceVirtualDirectory.ps1";
# [ID = ClientAccessComponent___9D94915F-B12D-4579-93EE-36B6DF42CF4A, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:47 PM:
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          $MapiClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi");
          $MapiMailboxClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi\emsmdb");
          $clrConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeMapiMailboxAppPool_CLRConfig.config");
          Start-SetupProcess -Name "$CommandAppCmd" -args "add apppool /name:MSExchangeMapiMailboxAppPool /autostart:true /managedRuntimeVersion:v4.0 /queueLength:65535 /CLRConfigFile:`"$clrConfigFilePath`" /managedRuntimeLoader:`"`"
/processModel.identityType:LocalSystem /managedPipelineMode:Integrated /recycling.periodicRestart.time:00:00:00 /processModel.idleTimeout:00:00:00 /processModel.pingingEnabled:false /failure.rapidFailProtection:false" -IgnoreExitCode @(183);
          Start-SetupProcess -Name "$CommandAppCmd" -args "add vdir /app.name:`"Exchange Back End/`" /path:`"/mapi`" /physicalPath:`"$MapiClientAccessPath`"" -IgnoreExitCode @(183);
          Start-SetupProcess -Name "$CommandAppCmd" -args "add app /site.name:`"Exchange Back End`" /physicalPath:`"$MapiMailboxClientAccessPath`" /applicationPool:MSExchangeMapiMailboxAppPool /path:`"/mapi/emsmdb`""
-IgnoreExitCode @(183);
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/access /sslFlags:Ssl /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/anonymousAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/basicAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/clientCertificateMappingAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/digestAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/iisClientCertificateMappingAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/windowsAuthentication /enabled:true /commit:apphost";
# [ID = ClientAccessComponent___B551AAAC-0F36-428B-B1BB-3B9AFDC9EAEF, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:50 PM:
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          $MapiClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi");
          $MapiAddressBookClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi\nspi");
          $clrConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeMapiAddressBookAppPool_CLRConfig.config");
          Start-SetupProcess -Name "$CommandAppCmd" -args "add apppool /name:MSExchangeMapiAddressBookAppPool /autostart:true /managedRuntimeVersion:v4.0 /queueLength:65535 /CLRConfigFile:`"$clrConfigFilePath`" /managedRuntimeLoader:`"`"
/processModel.identityType:LocalSystem /managedPipelineMode:Integrated /recycling.periodicRestart.time:00:00:00 /processModel.idleTimeout:00:00:00 /processModel.pingingEnabled:false /failure.rapidFailProtection:false" -IgnoreExitCode @(183);
          Start-SetupProcess -Name "$CommandAppCmd" -args "add vdir /app.name:`"Exchange Back End/`" /path:`"/mapi`" /physicalPath:`"$MapiClientAccessPath`"" -IgnoreExitCode @(183);
          Start-SetupProcess -Name "$CommandAppCmd" -args "add app /site.name:`"Exchange Back End`" /physicalPath:`"$MapiAddressBookClientAccessPath`" /applicationPool:MSExchangeMapiAddressBookAppPool /path:`"/mapi/nspi`""
-IgnoreExitCode @(183);
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/access /sslFlags:Ssl /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/anonymousAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/basicAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/clientCertificateMappingAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/digestAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/iisClientCertificateMappingAuthentication /enabled:false /commit:apphost";
          Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/windowsAuthentication /enabled:true /commit:apphost";
# [ID = ClientAccessComponent___178FD1A31B5949A0B4A819E39311B1FD, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:52 PM:
            $ExchangeLabsRegKey = 'HKLM:\SOFTWARE\Microsoft\ExchangeLabs'
            $E4eCertificateDistinguishedNameRegValueName = 'E4eCertificateDistinguishedName'
            if ($RoleDatacenterE4eCertificateDistinguishedName -ne $null)
                New-ItemProperty -path "$ExchangeLabsRegKey" -Name $E4eCertificateDistinguishedNameRegValueName -Value $RoleDatacenterE4eCertificateDistinguishedName -Force
                Write-ExchangeSetupLog -Info "Wrote registry key: $ExchangeLabsRegKey\$E4eCertificateDistinguishedNameRegValueName. value: $RoleDatacenterE4eCertificateDistinguishedName"
            else
                Write-ExchangeSetupLog -Info "Could not write registry key: $ExchangeLabsRegKey\$E4eCertificateDistinguishedNameRegValueName. Value is null."
            $E4eServiceUrlRegValueName = 'E4eServiceUrl'
            if ($RoleDatacenterE4eServiceUrl -ne $null)
                New-ItemProperty -path "$ExchangeLabsRegKey" -Name $E4eServiceUrlRegValueName -Value $RoleDatacenterE4eServiceUrl -Force
                Write-ExchangeSetupLog -Info "Wrote registry key: $ExchangeLabsRegKey\$E4eServiceUrlRegValueName. value: $RoleDatacenterE4eServiceUrl"
            else
                Write-ExchangeSetupLog -Info "Could not write registry key: $ExchangeLabsRegKey\$E4eServiceUrlRegValueName. Value is null."
# [ID = ClientAccessComponent___240c7e5d07f941cfbe69a692dc33a31a, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:52 PM:
          ."$RoleInstallPath\Scripts\ConfigureCafeResponseHeaders.ps1";
          CreateCustomHeadersNodeForBackend 'autodiscover'
          CreateCustomHeadersNodeForBackend 'ecp'
          CreateCustomHeadersNodeForBackend 'ews'
          CreateCustomHeadersNodeForBackend 'oab'
          CreateCustomHeadersNodeForBackend 'owa'
          CreateCustomHeadersNodeForBackend 'powershell'
          CreateCustomHeadersNodeForBackend 'pushnotifications'
          CreateCustomHeadersNodeForBackend 'rpcproxy'
          CreateCustomHeadersNodeForBackend 'sync'
          CreateCustomHeadersNodeForBackend 'mapi\emsmdb'
          CreateCustomHeadersNodeForBackend 'mapi\nspi'
          CreateCustomHeadersNodeForBackend 'outlookservice'
# [ID = ClientAccessComponent___75f8c93d15314369983d33ec0742e189, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
7/5/2014 11:04:53 PM:
          New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
# Tasks for 'POP/IMAP Backend Configuration' component
# [ID = PopImapBeComponent___d91be94d83bb4dc28e1fbdf7d94ca60e, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:05 PM:
          if (!(get-service MSExchangeIMAP4BE* | where {$_.name -eq "MSExchangeIMAP4BE"}))
            install-Imap4BeService
# [ID = PopImapBeComponent___e2debc6ecabf457eb6f278096ad5102c, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:06 PM:
          if (!(get-service MSExchangePOP3BE* | where {$_.name -eq "MSExchangePOP3BE"}))
            install-Pop3BeService
# [ID = PopImapBeComponent___7ee4dbb3fe884d26bb3e060ac68061ee, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:06 PM:
          $file = 'Microsoft.Exchange.Pop3Service.exe.config';
          $template = $file + '.template';
          $relPath = 'ClientAccess\PopImap';
          $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
          $fullFilePath = [System.IO.Path]::Combine($fullPath, $file);
          Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
          Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
          set-appconfigvalue -ConfigFileFullPath:$fullFilePath -Element:configuration/runtime/generatePublisherEvidence -Attribute:enabled -NewValue:false
# [ID = PopImapBeComponent___9b86c2af9f364990aa196cb6e69905b6, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:06 PM:
          $file = 'Microsoft.Exchange.Pop3.exe.config';
          $template = $file + '.template';
          $relPath = 'ClientAccess\PopImap';
          $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
          Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
          Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
# [ID = PopImapBeComponent___01c604c08fd6402e9de6b3c45e3431c8, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:06 PM:
          $file = 'Microsoft.Exchange.Imap4Service.exe.config';
          $template = $file + '.template';
          $relPath = 'ClientAccess\PopImap';
          $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
          $fullFilePath = [System.IO.Path]::Combine($fullPath, $file);
          Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
          Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
          set-appconfigvalue -ConfigFileFullPath:$fullFilePath -Element:configuration/runtime/generatePublisherEvidence -Attribute:enabled -NewValue:false
# [ID = PopImapBeComponent___2528980001a444fcb7097d123e879728, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:06 PM:
          $file = 'Microsoft.Exchange.Imap4.exe.config';
          $template = $file + '.template';
          $relPath = 'ClientAccess\PopImap';
          $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
          Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
          Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
# [ID = PopImapBeComponent___bbfdc492aaf748298977cb9b98e00029, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:07 PM:install-Imap4Container -Name:"IMAP4" -DomainController $RoleDomainController
# [ID = PopImapBeComponent___091c98cfe0f145189c0966717496795e, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:07 PM:install-Pop3Container -Name:"POP3" -DomainController $RoleDomainController
# [ID = PopImapBeComponent___42cb9f4ac2924c27b6ebf60b92a03628, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:07 PM:new-ImapSettings -DomainController $RoleDomainController -ExchangePath $RoleInstallPath
# [ID = PopImapBeComponent___181f5361a5df4e7ca009f21f26f8c0d5, Wt = 1, isFatal = True] "Configuring the server."
7/5/2014 11:05:07 PM:new-PopSettings -DomainController $RoleDomainController -ExchangePath $RoleInstallPath
# Tasks for 'ClientAccessExchangeCertificate' component
# [ID = ClientAccessExchangeCertificate___fb5e9028e669404d94dba90aace8c2f9, Wt = 1, isFatal = True] "Installing Client Access server certificates."
7/5/2014 11:05:07 PM:
          Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController

How to upgrade Exchange Server 2013 CU5 on my site?

My site have four Exchange servers . The four Exchange Servers are installed mailbox and cas roles. The
Dag achieved by the four servers. Please help me to upgrade exchange server 2013 cu5 on the four servers. how to do? Thanks.
北京老马

Hi Martin
Find the below information.
Upgrade Sequence for each Role:
==========================
You should upgrade your Exchange 2013 server roles in the following order:
Client Access
Mailbox
Edge
For DAG members
Upgrade only passive servers in the first phase.
Before you apply the service pack to a DAG member, move all active mailbox database copies off the server to be upgraded and configure the server to be blocked from activation.
Place server in DAG maintenance mode before applying the service pack to any DAG member,
Stop any scheduled tasks or other processes running on the DAG member or within that DAG that could adversely affect the DAG member being upgraded or the upgrade process
Good Luck !!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Exchange Server 2013: Deploying High Availability and Site Resilience

Similar Messages

Maybe you are looking for