Migrate Exchange 2003-2013 and AD 2000-2012

We are in the process of migrating from Exchange 2003 to Exchange 2013. We currently have 4 Domain Controllers in Windows Server 2000. Two of them host also Exchange Server 2003 in an A-P mode configuration.
The double hop migration to 2010 was not possible as it requiered a minimal functional level of Windows Server 2003. This lead us to consider the double hop migration to 2007 first, even though it is not the recomended path. We have more
than 400 mailboxes with a size than often passes 1TB.
Is this scenario possible and may be the risks? Do you think using a third party tool to pass data to Exchange 2013 would be a safer solution?
Looking forward to your ideas.
Thank you,
Megi

Hi,
As far as I know, same with the Exchange server migration, we cannot also directly migrate AD 2000 to AD 2012. Thus, I recommend you directly upgrade to AD 2008 and then migrate Exchange 2003 to 2007 to 2013.
Here are more references you can refer to :
Exchange 2000/2003 to Exchange 2007 migration guidelines:
http://blogs.technet.com/b/mbaher/archive/2008/06/04/migrating-exchange-2000-2003-to-exchange-2007-guidelines.aspx
Step-by-Step Exchange 2007 to 2013 Migration:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Thanks,
Angela Shi
TechNet Community Support

Similar Messages

  • Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

    I wasn't prepared for this task, and it was thrown at me to do...  Eyes are bleeding from planning reading and planning, would LOVE any input from you guys.  First time posting, here and have heard great things about these forums.  The Company
    I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
    Scenario:
    Old Domain/Server: (To be decommissioned)
    Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
    Exchange 2003 SP2 (6.5.7638.1)
    Server is a domain controller and exchange server.
    Migrating to:
    Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
    VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality 
    VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
    VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
    These are probably not ideal conditions, but I have to work with what I'm given.
    Host server (2012 R2) is in work group mode.  Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2.  I had intended starting at a lower functionality level and raising
    it later, but.... ya I forgot to change it.  If needed I can spool up a new DC with a lower functional level.
    DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain.  The concern is migrating the mailboxes from Exchange 2003 on the old domain to
    Exchange 2013 on the new domain.  The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
    I had some ideas, but I'm not sure if they will work.  This is something I have never done before (Senior Engineer Quit).
    My thoughts:
    - Establish a two way trust relationship between the two domains.
    - Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
    - Create the users on the new domain
    - Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013 
    - Link Exchange accounts to the correct user accounts on the new DC.
    Can this be done cleanly? Am I going about this the correct way?  Any feedback would be GREATLY appreciated.
    Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

    Hi,
    Base on my experience, your idea is feasible.
    However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link: 
    http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
    After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
    Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
    Exchange 2010/2007 to 2013 Migration and Co-existence Guide
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Migrate Exchange 2003 Public folders and OAB to Office365?

    Hi guys,
    I am trying to migrate exchange 2003 public folders to office 365. I have read various documentation however they were either out of date or half-solutions.
    The company stored OAB's in each public folder as well, how do I go about migrating these lists into office 365? Will it just "work" if I migrate the public folders across?
    Thanks,
    Alex

    Hi,
    If you are migrating from inhouse 2003 to office 365, then the best options for you are-
    1. Either you can go for the manaul process. You can create PST files and can upload them to mailboxes through office 365 account.
    Kindly refer the below mentioned link for the same 
    http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx 
    2. Or you can go for any 3rd party tool using the same you can migrate your public folders to office 365. This is required when you need to avoid the risks associated and need to keep your environment up and running even while migration process. Respond
    back for third party tool suggestions.

  • Migrate Exchange 2003 to Office 365

    Dear all,
    We are going to migrate Exchange 2003 to Office 365. Because of the large number of mailboxes and mail databases, we decide to build hybrid to support coexistence during the migration period.
    According to "Exchange Server Deployment Assistant" I found that we can build more Exchange 2010 for that requirement
    http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-BwAIAAAAQAAAAAEAiFIAAAA~
    I just wonder that after deploying the Exchange 2010, can we move directly the mailboxes from Exchange 2003 to Office 365 or we need to move to Exchange 2010 first (as a "buffer") before moving to Office 365
    Thanks a lot !!!

    Hello,
    The main goal of a staged migration is to migrate Exchange on-premises servers when:
    1. You have more than 2000 mailboxes.
    2. You plan to migrate over a few weeks and months rather than in a single batch.
    3. You want to migrate to the Cloud completely and remove your on-premises Exchange deployment.
    Hybrid scenarios are useful when you do not want to remove your on-premises deployment. In some cases there is no technical possibility, it is not cost-effective etc. to move a whole organization to Office 365. In these situations you may decide that moving
    only some mailboxes to Office 365 is a good option and create a hybrid deployment.
    You need to consider all pros and cons, especially when Exchange 2003 has gone out of support lifecycle and then choose the better option for your organization.
    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.

  • Not able to install Exchange Server 2013 on Windows Server 2012

    I got an error while installing exchange server 2013 on windows server 2012 : "The registry key "SOFTWARE\Microsoft\Exchange Server\v15\Pickup" does not exist under "HKEY_LOCAL_MACHINE " any related solutions highly appreciated
    thanks :

    Hello,
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    I'm marking the reply as answer as there has been no update for a couple of days.
    If you come back to find it doesn't work for you, please reply to us and unmark the answer.
    Cara Chen
    TechNet Community Support

  • Exchange Server 2013 In Windows Server 2012 - unable to logon EXchange Administrator Center (EAC)

    Hi All,
    I Just installed Exchange Server 2013 in Windows Server 2012 and trying to connect Dynamics CRM 2013 (DNS).
    The Installations Success full but unable to load the EAC page by using the following URL
    https://servername:port/owa/auth/logon.aspx
    I have cross checked in Exchange/owa/auth folder don't have the "logon.aspx" file 
    But the auth folder have the "logoff.aspx" 
    I installed many time freshly in separate WS-2012 but it not contains that logon.aspx 
    I want access the Exchange Administrator Center 
    Please Help me to solve it 
    IIS Exchange (Missing of logon.aspx)
    SRKD0808

    Hi All,
    I sorted out this problem 
    Actually we have to run these 2 commands in Domain Control, But what i did  I just run this
    1) setup /PrepareSchema /IAcceptExchangeServerLicenseTerms
    Command in Domain Control we don't need to run the 2nd command, Because I already try to installed exchange 2013 very first time it success and after some modifications
    it gone.
    That time it will ask you to provide Organization name, Once you give that it will create the Organization name in Domain control and it will save the settings when
    you install first time 
    Because of this reason It is failing to run these 2 command
    Finally what i did I just revert back my Domain control snapshot & Exchange server as well 
    Then i started freshly Installation in DC and Exchange server 2013 successfully installed 
    URL http://servername/ecp/default.aspx
    Whole Process will be here 
     Exchange Server 2013 Step by Step Installation In Windows Server 2012
    SRKD0808

  • Migrate exchange 2003 to exchange online from EAC.

    Hi,
    I have to migrate my local exchange 2003 to my new exchange online from office365.
    I have to make a Cuteover migrate (complete migrate .... sorry for my english). I understand i have to use a batch to import my on-premise exchange to exchange 365. My question is : does the batch do a "cut-paste" or a "copy-paste" of
    my local data to online data ? do i will lost all local user mailbox data(mail contact calendar) ?
    Thanks you
    Julien

    Hi, first of all let me tell that the process from the ECP will create a single batch job for cutover migration, secondly, the process will consist of migrating Exchange mailboxes, contacts and Distribution Groups but the source content will remain as is
    not a cut/paste operation.
    If you want more info about the process I recommend you to read the following:
    http://technet.microsoft.com/en-us/library/jj874016(v=exchg.150).aspx
    Alberto Pascual MVP-MCSA-MCITP-MCTS-MCP-O365MS-MCC http://blogs.itpro.es/guruxp

  • How to configure workflow manager 1.0 ? Scenario "sharepoint 2013 and sql server 2012 workflow manager in one server" .

    i have sharepoint 2013 and sql server 2012 in one server . how to configure workflow manager 1.0 on the same server ?

    Please follow below technet article :
    http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
    Installing and Configuring Workflow Manager 1.0 (Step by Step)
    Note: The steps in this article apply to SharePoint Server 2013.
    The SharePoint 2013 Workflow platform is not supported in SharePoint Foundation 2013.
    If my contribution helps you, please click Mark As Answer on that post and
    Vote as Helpful
    Thanks, ShankarSingh(MCP)

  • Installing BAM with Biztalk Server 2013 and SQL server 2012

    Hello All,
    I have to work on BAM with BizTalk Server 2013 and SQL server 2012 , is BAM already comes with BizTalk server installation ?
    Will I needs to explicitly install that ? from where I can get the installer for BAM ?
    What else I will needs to work on BAM ?
    Note : I want to handle Exceptions in BAM ....how to do that ?
    Thanks,
    Nitin.
    Thanks and Regards, Nilesh Thakur.

    Hi,
    BAM is available with BizTalk, all you need is to select it and install .
    Refer the
    Installation Guide available on MSDN or follow the blog: http://sandroaspbiztalkblog.wordpress.com/2013/05/05/biztalk-2013-installation-and-configuration-important-considerations-before-set-up-the-server-part-1/
    Maheshkumar S Tiwari|User
    Page|Blog|BizTalk
    Server : Scheduling Orchestration using Trigger Message

  • Unity 8.0 and Migrating Exchange 2003 to 2010

    In the coming months I hope to be upgrading from Exchange 2003 (sp2) to Exchange 2010 (sp3) running on Windows Server 2012.  I currently have Unity 8.0(3.1) running on Server 2003.  We hope to be upgrading to Exchange 2013 at the end of the year if that is supported.
    Before I contact my Cisco partner about this upgrade I would like to know what to expect.  Any advice and suggestions would be appreciated.
    Thanks!
    Nick

    The integration is completely different than with legacy Unity.  High-level: Unity leverages MAPI integration and is completely dependent upon AD and Exchange to function properly.  Hence, the schema extensions, Permissions Wizard (and associated permissions), and etc.  Unity Connection leverages web-based APIs for integration.  Specifically it uses WebDav for Exch 2003 and EWS for Exchange 2007/2010.  It is a dual message store synchronization architecture, which means that 1) it can function independently without AD and/or Exchange integration and 2) no schema extensions and 3) less complicated permissions requirements.  With Unity Connection, the users have a mailbox on the server and then a copy of that message is synchronized into the user's corporate Exchange mailbox.  You get MWI synchronization between phone and email and etc (hence, you get Unified Messaging).  Another nice thing is that you can handle requirements for voicemail only scenarios locally on Unity Connection without having to create dummy or "resource" AD/Exchange accounts in the corporate systems.  You can read up more on this integration here and hit me back up if you have questions.  I'll be glad to help if I can.
    http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg010.html
    As for the fax part, OK - that's a problem in your scenario.  Personally, I've never been a big fan of using Unity for that (and don't) but then again, I don't really like "fax" anyway.  Personal opinions aside, I'll go with relay of facts.  Unity Connection supports integration with 3rd-party fax systems.  You can take a look at that here:
    http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg080.pdf
    In terms of Unity though, the reality is that it's days are (and have been) numbered.  See below:
    http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps5745/ps6509/end_of_life_notice_c51-681593.html
    Hailey
    Please rate helpful posts!

  • 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.

  • Migrating exchange 2003 to 2010 while everyone is running SMTP, POP3 and IMAP on the old exchange 2003

    Hi all
    We have a legacy Exchange 2003 running with more than 800 users and with a very mixed configuration for client access. Most of users are running POP3/SMTP on the Exchange, some are running IMAP/SMTP and some are running MAPI access. 
    Please note that THERE IS NO WAY that we move all users to MAPI access before the installation (due to deadlines).
    We plan to install a new Exchange 2010, starting with a CAS/HUB server. We do not need to migrate users automatically, and we can proceed later to move them individually to the new Exchange 2010 infrastructure in a non-transparent way. 
    More importantly, we need to maintain that everyone receives their e-mail and all communication through the exchange 2003 continues uninterrupted. 
    My question is can we install the new CAS/HUB server, while maintaining the old exchange server running with it's old name and create new names for the CAS/HUB server. In such a configuration, will all the Exchange 2003 services continue to run as usual
    (POP3/IMAP/SMTP/MAPI)?

    In addition, you may also spend some times at below mentioned helpful resources to check the prerequisites before moving all mailboxes from exchange 2003 to 2010 :
    http://exchangeserverpro.com/wp-content/uploads/2011/02/Exchange-Server-2003-to-2010-Migration-Guide-V1.3-Planning-Chapter.pdf
    http://technet.microsoft.com/en-us/library/dd638130(v=exchg.141).aspx
    https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/
    Moreover, to avoid any interruption  during the completion of migration process, you can also take a look at this application(http://www.exchangemigrationtool.com/) that could be a good alternate approach
    for you.

  • 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

  • Copy to my calendar missing after migration Exchange 2010-2013

    Hi there,
    We have migrated our Exchangeserver from Exchange 2003 too 2010 and then too 2013.
    In Outlook 2007 (with Exchange 2003 and later 2010) we had a button in the 'New appointment window' called 'Copy to my Calander' When we made an appointment in a Public Calander.
    After migrating to Exchange 2013 the button is missing, but we're still using the Public folder (Calander).
    Is there a solution for this?

    Hi,
    I'm marking the reply as answer as there has been no update for a couple of days.
    If you come back to find it doesn't work for you, please reply to us and unmark the answer.
    Best Regards,
    Steve Fan
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • Exchange Server 2013 and RADIUS server(freeRADIUS2)

    I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
    I am using Windows Server 2012, I already installed Exchange
    Server 2013 on it and everything works as intended.
    But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS
    server which is not on my Windows Server 2012. I have to use their RADIUS server ( freeRADIUS2 ), the RADIUS server from
    the company where I am doing my internship.
    I already did the checklist that is on http://technet.microsoft.com/en-us/library/cc772591.aspx. I configured the NPS as
    a RADIUS proxy, because that's what I need.
    So after doing everything that is on that checklist, my question is:
    Is it possible that the Exchange Server 2013 will use my NPS which is now configured as a NPS RADIUS proxy to authenticate my mailbox users that I have on my Exchange Server 2013?

    thanks for such a quick response.
    Just a small question about the link that you put. Does member server mean other server other than domain controller?
    Regards,
    Yes, Also the server on which you are installing Exchange should have exchange installed.
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Maybe you are looking for