Released: October 2018 Quarterly Exchange Updates


The latest cumulative update for Exchange Server 2016 is now available on the download center. There is no release for Exchange Server 2013 or Exchange Server 2010 as these products are both in the extended support phase of lifecycle. The cumulative update released today includes fixes to customer reported issues, all previously reported security/quality issues and updated functionality.

Updated Pre-requisite requirements

.NET Framework 4.7.2 Support

.NET Framework 4.7.2 is now supported with Exchange Server 2016 Cumulative Update 11. .NET Framework 4.7.2 will be required on Exchange Server 2016 with the Cumulative Update released in June, 2019.

We have validated .NET Framework 4.7.2 on the previously released Exchange Server 2013 Cumulative Update 21 and are announcing .NET Framework support with Exchange Server 2013 Cumulative Update 21 as well.

.NET Framework 4.7.2 will be required on the forthcoming Exchange Server 2019. Windows Server 2019, which is also required for Exchange Server 2019, installs .NET Framework 4.7.2 by default.

Changes to Visual C++ Version Dependencies

With today’s release we are updating the Visual C++ runtime version dependencies on Exchange Server 2016. Effective with Cumulative Update 11, all Exchange Server 2016 roles (Management Tools, Mailbox, Edge) will require installation of Visual C++ 2012 runtime. This is a change from Cumulative Update 10 where Visual C++ 2013 was incorrectly listed as being required on all roles. Visual C++ 2013 runtime, in addition to Visual C++ 2012, is required on the Mailbox role only.

Versions of Exchange setup before Cumulative Update 11 silently installed Visual C++ 2010 and 2012 components. Exchange setup has been changed in Cumulative Update 11 and later to enforce the Visual C++ runtime requirements using setup pre-requisite rules. When installing Cumulative Update 11 or later for the first time on an existing server, setup will detect the presence of the previously installed instances of Visual C++ placed there by Exchange setup and will not indicate that the Visual C++ 2012 runtime needs to be installed.

However, when setup performs the first upgrade of a server to Cumulative Update 11 or later, it will remove the versions of the Visual C++ binaries placed there by Exchange setup previously. This removal is necessary to change setup behavior, correct the condition which caused us to issue an advisory to install MS11-025 and ensure that future Visual C++ updates are applied by Windows Update and Microsoft Update.

Important: To avoid a setup failure, it is necessary to install the Visual C++ 2012 runtime before installing Cumulative Update 11 or later for the first time on an existing server. The setup pre-requisite rule works as expected when using Cumulative Update 11 or later to install a new server using the Cumulative Update 11 or later package.

Note: Exchange Server 2019, when released, will include the Visual C++ pre-requisite rules enforced by setup.

Release Details

KB articles that describe the fixes in each release are available as follows:

The updates released today do not include new updates to Active Directory Schema. If upgrading from an older Exchange version or installing a new server, Active Directory updates may still be required. These updates will apply automatically during setup if the logged on user has the required permissions. If the Exchange Administrator lacks permissions to update Active Directory Schema, a Schema Admin must execute SETUP /PrepareSchema prior to the first Exchange Server installation or upgrade.

Cumulative Update 11 does require an Administrator to execute SETUP /PrepareAD to ensure RBAC roles are current before applying the cumulative update released today.

Adjustment to Cumulative Update Release Schedule

Due to the delay associated with Cumulative Update 11, there will not be a cumulative update released in December 2018. Our next planned set of quarterly updates will occur in March 2019 and will include Exchange Server 2016 Cumulative Update 12 and Exchange Server 2019 Cumulative Update 1.

Additional Information

Microsoft recommends all customers test the deployment of any update in their lab environment to determine the proper installation process for your production environment. For information on extending the schema and configuring Active Directory, please review the appropriate TechNet documentation.

Also, to prevent installation issues you should ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed. To verify the policy settings, run the Get-ExecutionPolicy cmdlet from PowerShell on the machine being upgraded. If the policies are NOT set to Unrestricted you should use the resolution steps in KB981474 to adjust the settings.

Reminder: Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the currently supported cumulative update for the product version in use, e.g., 2013 Cumulative Update 21, 2016 Cumulative Update 10 or 9.

For the latest information on Exchange Server and product announcements please see What's New in Exchange Server 2016 and Exchange Server 2016 Release Notes. You can also find updated information on Exchange Server 2013 in What’s New in Exchange Server 2013, Release Notes and product documentation available on TechNet.

Note: Documentation may not be fully available at the time this post is published.

The Exchange Team

Comments (48)

  1. Terry says:

    Any news about support for Server 2019 in Exchange 2016?

    1. @Terry, there are no current plans to add support for Windows Server 2019 on Exchange Server 2016.

  2. Stephen Hudson says:

    So we have Exchange 2016 Mailbox servers currently at CU10.
    Prior to upgrading to CU11 we must: –
    1. Install C++ 2010 (MFC) Update, CU11 will fail the prerequisite check if not installed
    2. Install C++ 2012 runtime (even though it is listed as having been silently installed by Exchange 2016 CU10), CU11 will check for ‘C++ 2012 runtime’, and remove older C++ 2012 components
    3. Ensure that C++ 2013 runtime is installed (it is, because it has always been a prerequisite of the Exchange 2016 Mailbox role)
    Once the above is satisfied Exchange 2016 can be upgraded to CU11; correct?

    1. Andy says:

      I have been quite confused by the VC++ caveats between this and the MS11-025 bulletin. We are running 2016 CU10 and VC++ 2010 was not installed at all. And now this article says to install the VC++ 2012 update, however the CU11 update page we need to install VC++ 2013, which is listed as a prereq. Like WTF, some clarity would be nice.

      1. @Andy, if you aren’t running Cumulative Update 11 or later, install MS11-025. Before installing Cumulative Update 11 or later, install VC++ 2012 from the link above (You only need to do this once per server or admin workstation the first time you install anything released after September 2018). Install VC++ 2013 from the link above on Mailbox role. Install Cumulative Update 11 or later.

    2. @Stephen, your descriptions/interpretations are not accurate, but the steps you outline will work.

    3. Andrew says:

      It certainly isn’t particularly easy to follow. I’ve been supporting our exchange environment for over 15 years and I had to read through that at least three times, plus the comments, to get what I hope is a workable approach to this.

      I have exchange 2016 cu5 on windows server 2016. I looked at the links for VC++2012 and VC++2013 and they don’t mention windows server 2016

      Also, when I look at what I have installed, there are already a bunch of VC++ versions on there. Does windows server 2016 come with these already?

      This list is from WMIC “product get name” and is a little different from the display in programs and features

      Microsoft Visual C++ 2005 Redistributable
      Microsoft Visual C++ 2005 Redistributable (x64)
      Microsoft Visual C++ 2008 Redistributable – x64 9.0.30729.6161
      Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.4148
      Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.6161
      Microsoft Visual C++ 2010 x64 Redistributable – 10.0.40219
      Microsoft Visual C++ 2010 x86 Redistributable – 10.0.40219
      Microsoft Visual C++ 2012 x86 Additional Runtime – 11.0.51106
      Microsoft Visual C++ 2012 x86 Minimum Runtime – 11.0.51106
      Microsoft Visual C++ 2012 x64 Additional Runtime – 11.0.60610
      Microsoft Visual C++ 2013 x64 Additional Runtime – 12.0.40660
      Microsoft Visual C++ 2013 x86 Minimum Runtime – 12.0.40660
      Microsoft Visual C++ 2012 x64 Minimum Runtime – 11.0.60610
      Microsoft Visual C++ 2013 x86 Additional Runtime – 12.0.40660
      Microsoft Visual C++ 2013 x64 Minimum Runtime – 12.0.40660

      thanks
      andrew

  3. Gregor says:

    Hmmm

    [Owa] An internal server error occurred. The unhandled exception was: System.Globalization.CultureNotFoundException: Culture is not supported.
    Parameter name: culture
    4096 (0x1000) is an invalid culture identifier.
    at System.Globalization.CultureInfo.InitializeFromCultureId(Int32 culture, Boolean useUserOverride)
    at Microsoft.Exchange.Net.ClientCultures.GetCultureInfoInstance(Int32 lcid)
    at Microsoft.Exchange.Net.ClientCultures.GetBrowserDefaultCulture(HttpRequestBase httpRequest)
    at Microsoft.Exchange.Clients.Owa.Core.OwaPage.InitializeCulture()
    at ASP.auth_errorfe_aspx.__BuildControlTree(auth_errorfe_aspx __ctrl)
    at ASP.auth_errorfe_aspx.FrameworkInitialize()
    at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    at System.Web.UI.Page.ProcessRequest()
    at System.Web.UI.Page.ProcessRequest(HttpContext context)
    at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    This is when I try owa from Android.

    1. @Gregor, this normally points to a problem with globalization of the OS with an inappropriately named resource file/folder. CultureID 4096 (0x1000) is being used to track the addition of many new locale identifiers. I would suggest you work with support to understand what is wrong with the OS installation.

      1. Gregor says:

        This is standard Android 8 install with locale English (Slovenia).

        OS is 2016 With latest CU.

        BTW, is Exchange 2016 supported on Server 2019?
        Maybe I could try there :)

        1. Gregor says:

          Meh.
          Tested on new Server 2019 with Exchange 2019 same result.

          1. Gregor says:

            Well this one is resolved with released version of Exchange 2019.
            Finally but been waiting 2 years + to get it resolved.

  4. does IPv6 have to be enabled to install CU11?
    I try to install a new server in the existing 2016 infrastructure (all other servers Cu10) and decided to immediately install Cu11, setup writes a bunch of errors during Prerequisites Analysis (Either Active Directory doesn’t exist, or it can’t be contacted. and much more – account check, AD upgrade check), but Cu10 setup on the same system does not find any errors

    2012 r2, IPv6 disabled via
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters
    “DisabledComponents”=dword:ff
    and the same configuration on DC’s.
    In test environment with default IPv6 settings (but IPv6 binding removed from network adapter) CU11 setup does not found any problem during readiness check

    1. @Dave, Exchange does not explicitly require IPv6. The errors you are encountering indicate the Exchange Server cannot contact a domain controller. This is normally due to wrong credentials being used, e.g. logging on as the local admin, or an underlying networking issue, e.g. DNS, IPsec Policy or IP routing.

      1. as I wrote above on the same server under the same user CU10 is installed without any problems and errors.

        1. Jorge says:

          Having the same issue. CU11 reports multiple errors in readiness checks. One error states “The mailbox server role isn’t on this computer”. When it clearly has mailbox role installed I have installed C++ 2010 update, C++ 2012, and C++ 2013.

          1. jorge says:

            I was able to install CU 11 by installing the update on an exchange server located in the same site as the DC holding the schema master. Once the DCs replicated the changes, i was able to install CU 11 on the other exchange 2016 serves located in other sites.

        2. Anonymous says:
          (The content was deleted per user request)
        3. seem to have found the cause: in event log
          ExSetupUI.exe 3516 Get Servers for mydomain.com TopologyClientTcpEndpoint (localhost) 3 System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0230759. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout) — End of inner exception stack trace —

          it is obvious that no Exchange.Directory.TopologyService on the server – as this is a fresh installation!

          After clean install of CU10 and attempt to upgrade to CU11 finally got a sane error that need to update the AD from the same site where the schema master located.

  5. Rick Parrent says:

    Hey Exchange Team-

    Is there any word on Autodiscover services supporting TLS 1.2? Ever since I shut of TLS 1.0, I get SSL errors every time I test on exRCA.com

    1. @Rick, we are aware that this site needs to be updated to support TLS 1.2. Unfortunately, I don’t have a timeframe that I can share for this work to be completed.

  6. Troy says:

    When upgrading from CU10 to CU11 do we need to run setup.exe /PrepareAllDomains after running setup.exe /PrepareAD if we are in a multi-domain environment?

    Are there any details about what changes in RBAC with CU11?

    1. @Troy, no need to prepare your domains with this update.

    2. @Troy, the RBAC changes in this update do not change any existing policies, definitions or capabilities. These changes were made to support co-existence with the forth coming Exchange Server 2019 which will be delivered later this year.

  7. Bob says:

    When installing CU11 on my Edge server I get this during the install:

    Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.

    1. @Bob, per above, you need to install VC++ 2012 before applying the cumulative update. You are hitting the setup error referenced.

  8. EinmalIM says:

    Any plans to speed up the setup time?

    CPU usage is between 0 and 5% most of the time. Very seldom it reaches 10%. This is on Xeon E5620 8 cores + HT.

    Some parallel / multi threaded setup actions would be nice.

    After 40 minutest I am still at step 10/18 9%

    1. @EinmalIM, thank you for your feedback. We are aware of the lengthy times required to install a cumulative update. We are working to improve this. This will be incremental work and should improve over time. Thank you for your patience.

  9. EinmalIM says:

    Any plans to speed up the setup time?

    CPU usage is between 0 and 5% most of the time. Very seldom it reaches 10%. This is on Xeon E5620 8 cores + HT.

    Some parallel / multi threaded setup actions would be nice.

    After 40 minutes I am still at step 10/18 9%

  10. FieroVin says:

    Installed C++ 2012 and 2013 runtimes before attempting setup but it’s not happy. :(

    Any help?

    Error:
    The following error was generated when “$error.Clear();
    $auditLogMbxName = “SystemMailbox{8cc370d3-822a-4ab8-a926-bb94bd0641a9}”;
    $auditLogMbxLastName = “SystemMailbox 8cc370d3-822a-4ab8-a926-bb94bd0641a9”;
    Write-ExchangeSetupLog -Info (“Retrieving users with LastName=$auditLogMbxLastName.”);
    $auditLogUser = @(Get-User -Filter {LastName -eq $auditLogMbxLastName} -IgnoreDefaultScope -ResultSize 1);
    if ($auditLogUser.Length -eq 0)
    {
    Write-ExchangeSetupLog -Info (“Retrieving audit log users with LastName=$auditLogMbxLastName.”);
    $auditLogUser = @(Get-User -AuditLog -Filter {LastName -eq $auditLogMbxLastName} -IgnoreDefaultScope -ResultSize 1);
    }

    if ($auditLogUser.Length -eq 0)
    {
    Write-ExchangeSetupLog -Info (“Installing user account with Name=$auditLogMbxName and LastName=$auditLogMbxLastName.”);
    Install-UserAccount -Name $auditLogMbxName -LastName $auditLogMbxLastName;
    }
    else
    {
    Write-ExchangeSetupLog -Info (“Audit log user $auditLogMbxName already exists.”);
    }
    ” was run: “Microsoft.Exchange.Data.Directory.ADConstraintViolationException: An Active Directory Constraint Violation error occurred on NCGADC2.ncga.state.nc.us. Additional information: The operation failed because UPN value provided for addition/modification is not unique forest-wide.
    Active directory response: 000021C8: AtrErr: DSID-03200BD2, #1:
    0: 000021C8: DSID-03200BD2, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 90290 (userPrincipalName)
    —> System.DirectoryServices.Protocols.DirectoryOperationException: A value in the request is invalid.
    at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
    at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
    at Microsoft.Exchange.Data.Directory.GuardedDirectoryExecution.Execute[T](String bucketName, Func`1 action, Int64& concurrency)
    at Microsoft.Exchange.Data.Directory.PooledLdapConnection.GuardedSendRequest(String forestName, GuardedDirectoryExecution guardedDirectoryExecution, DirectoryRequest request, TimeSpan timeout, Func`3 sendRequestDelegate, Int64& concurrency)
    at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IADLogContext logContext, Boolean shouldLogLastFilter)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    — End of inner exception stack trace —
    at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer, String callerFilePath, Int32 callerFileLine, String memberName)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
    at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave, String callerFilePath, Int32 callerFileLine, String memberName)
    at Microsoft.Exchange.Management.Deployment.InstallUserAccount.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.b__91_1()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)”.

    1. SvenC says:

      Sounds like the system mailbox is existing elsewhere already?
      SystemMailbox{8cc370d3-822a-4ab8-a926-bb94bd0641a9}

      From exception details: The operation failed because UPN value provided for addition/modification is not unique forest-wide.

      1. elMario says:

        We receive the same error.

        What should the next step be?

        1. FieroVin says:

          FYI, In our case, we found that the account referenced in the error SystemMailbox{8cc370d3-822a-4ab8-a926-bb94bd0641a9} had been moved from the default User container to a “service accounts” OU, once we moved the account back to the default container setup completed.

    2. elMario says:

      Have you found a fix for this error?

      1. FieroVin says:

        I have a case open with Premier Support, so far we have not found a solution. They did check for a duplicate of that system mailbox account and could not find one.

      2. FieroVin says:

        @elMario

        Have you made any progress? We have not yet had any success.

  11. TDR says:

    It sucks that the VC++2012 dependency is not checked and flagged by the installer and its sucks even more that there is zero mention of the VC++2012 requirement on the KB article for CU11.

    So many like me will end up with broken servers giving cryptic messages and have to search the internet to find the cause.

    1. @TDR – This was called out in the original blog post. It was even bolded to call attention to it. Your assumption that the installer does not check is not accurate. The installer does check but when it runs the first time the binaries are installed from the previous cumulative update so the check passes. The fact that when you run setup a second time and the pre-req shows is proof that the installer checks and that the versions previously installed by setup have now been removed and replaced by a pre-req check.

      1. TDR says:

        So what happened to me was my Edge server install crashed out half way through with an error telling me to reboot. Not unusual with CU updates – they sometimes fail and you have to rerun them from where they left off.

        However due to the VC++2012 issue – when I tried to rerun the CU, the installer just stops. No on screen error, except a cryptic message in the setup logs about some specific DLL dependencies. I had to spend quite some time and the System Internals tools to work out it was looking for VC++2012. I found this article subsequently.

        So if that information is needed here, I would have thought it’s pretty obviously needed on the KB article. Not every person tasked with installing this is going to think to check a specific blog. Installing CUs is often frustrating enough as it is – you need to update the KB please.

        AND the CU installer really should detect and display a user friendly error message for such a dependency error without just dying.

        1. TDR says:

          Error that caused initial install fail:

          [10/16/2018 22:07:23.0758] [2] Beginning processing install-MsiPackage
          [10/16/2018 22:07:23.0773] [2] ProductCode is ‘c3f10d8c-bd70-4516-b2b4-bf6901980741’.
          [10/16/2018 22:07:23.0773] [2] PackagePath was set to ‘C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI’; changing to full path ‘C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI’.
          [10/16/2018 22:07:23.0789] [2] ProductCode is ‘c3f10d8c-bd70-4516-b2b4-bf6901980741’.
          [10/16/2018 22:07:23.0805] [2] Installing MSI package ‘C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI’.
          [10/16/2018 22:07:23.0805] [2] No updates directory was specified for the msi installation.
          [10/16/2018 22:07:23.0805] [2] Installing a new product. Package: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI. Property values: ALLUSERS=1 REBOOT=ReallySuppress
          [10/16/2018 22:07:24.0102] [2] [ERROR] Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ‘.
          [10/16/2018 22:07:24.0102] [2] [ERROR] Fatal error during installation
          [10/16/2018 22:07:24.0102] [2] [ERROR] Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ‘.
          [10/16/2018 22:07:24.0102] [2] [ERROR] Fatal error during installation
          [10/16/2018 22:07:24.0102] [2] [ERROR] Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ‘.
          [10/16/2018 22:07:24.0102] [2] [ERROR] Fatal error during installation
          [10/16/2018 22:07:24.0106] [2] Ending processing install-MsiPackage
          [10/16/2018 22:07:24.0106] [1] The following 1 error(s) occurred during task execution:
          [10/16/2018 22:07:24.0106] [1] 0. ErrorRecord: Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ‘.
          [10/16/2018 22:07:24.0106] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ‘. —> System.ComponentModel.Win32Exception: Fatal error during installation
          — 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.Deployment.InstallMsi.InstallPackageFile(String packagePath)
          at Microsoft.Exchange.Management.Deployment.InstallMsi.InternalProcessRecord()
          at Microsoft.Exchange.Configuration.Tasks.Task.b__91_1()
          at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
          [10/16/2018 22:07:24.0106] [1] [ERROR] The following error was generated when “$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + “TransportRoles\agents\Hygiene\ASDat.MSI”) `
          -LogFile ($RoleSetupLoggingPath + “\InstallASDat.msilog”) `
          -PropertyValues (“ALLUSERS=1″) `
          -UpdatesDir $RoleUpdatesDir
          ” was run: “Microsoft.Exchange.Configuration.Tasks.TaskException: Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ‘. —> System.ComponentModel.Win32Exception: Fatal error during installation
          — 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.Deployment.InstallMsi.InstallPackageFile(String packagePath)
          at Microsoft.Exchange.Management.Deployment.InstallMsi.InternalProcessRecord()
          at Microsoft.Exchange.Configuration.Tasks.Task.b__91_1()
          at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)”.
          [10/16/2018 22:07:24.0106] [1] [ERROR] Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ‘.
          [10/16/2018 22:07:24.0106] [1] [ERROR] Fatal error during installation
          [10/16/2018 22:07:24.0106] [1] [ERROR-REFERENCE] Id=TransportCommonComponent___3f4a70ff37b549999a228ec24821d0dc Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
          [10/16/2018 22:07:24.0106] [1] Setup is stopping now because of one or more critical errors.
          [10/16/2018 22:07:24.0106] [1] Finished executing component tasks.
          [10/16/2018 22:07:24.0184] [1] Ending processing Install-GatewayRole
          [10/16/2018 22:07:56.0902] [0] CurrentResult setupbase.maincore:396: 0
          [10/16/2018 22:07:56.0918] [0] End of Setup

        2. TDR says:

          Error received subsequently trying to run CU11 setup until VC++2012 installed:

          [10/16/2018 22:16:55.0731] [0] **********************************************
          [10/16/2018 22:16:55.0747] [0] Starting Microsoft Exchange Server 2016 Setup
          [10/16/2018 22:16:55.0747] [0] **********************************************
          [10/16/2018 22:16:55.0747] [0] Local time zone: (UTC+00:00) Dublin, Edinburgh, Lisbon, London.
          [10/16/2018 22:16:55.0747] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
          [10/16/2018 22:16:55.0747] [0] Setup version: 15.1.1591.10.
          [10/16/2018 22:16:55.0747] [0] Logged on user: TDRMAIL\admin.
          [10/16/2018 22:16:55.0778] [0] Command Line Parameter Name=’sourcedir’, Value=’E:\’.
          [10/16/2018 22:16:55.0778] [0] Command Line Parameter Name=’mode’, Value=’Install’.
          [10/16/2018 22:16:55.0778] [0] RuntimeAssembly was started with the following command: ‘/sourcedir:E: /mode:Install’.
          [10/16/2018 22:16:55.0934] [0] The following roles are installed: GatewayRole AdminToolsRole
          [10/16/2018 22:16:56.0153] [0] [ERROR] Exception has been thrown by the target of an invocation.
          [10/16/2018 22:16:56.0153] [0] [ERROR] Could not load file or assembly ‘Microsoft.Exchange.CabUtility.dll’ or one of its dependencies. The specified module could not be found.
          [10/16/2018 22:16:56.0153] [0] Unable to load assembly from file C:\Program Files\Microsoft\Exchange Server\V15\bin\Microsoft.Exchange.Setup.GUI.dll using setup arguments /sourcedir:E:./mode:Install, source directory is E:\, target directory is C:\Windows\Temp\ExchangeSetup and Exchange is installed True.

  12. Anonymous says:

    +++ TDR comment!
    I’ve spent a load of hours trying to bring the EX16CU10 back to life… likely I did it on my lab but imagine doing this for your client…

    Microsoft, great job with CU11!
    oh! and great job with Win10 1809 too!

    1. robk says:

      This does not surprise me at all. How else is Microsoft going to shove their ‘Cloud’ solution down your throat? by making sure they spent less and less time delivering good solid on-premises product and forcing everyone to go and join the ‘Dark Side’. Like telling us that Exchange 2019 will only ‘work’ on Windows 2019 that has not been released yet and has been pulled form the shelf for the time being… MS can’t fix the powershell -Verbose switch for like 4 years now and you want them to deliver a good working CU??? Every CU so far released for Exchange 2016 always had some issues like Get-Help not working and so on…..Pretty sad…

      1. RyanB says:

        Loved the shoving the cloud solution down the throat comment, couldn’t agree more!

  13. Andrew says:

    I have exchange 2016 cu5 on windows server 2016. I looked at the links for VC++2012 and VC++2013 and they don’t mention windows server 2016

    Also, when I look at what I have installed, there are already a bunch of VC++ versions on there. Does windows server 2016 come with these already?

    This list is from WMIC “product get name” and is a little different from the display in programs and features

    Microsoft Visual C++ 2005 Redistributable
    Microsoft Visual C++ 2005 Redistributable (x64)
    Microsoft Visual C++ 2008 Redistributable – x64 9.0.30729.6161
    Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.4148
    Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.6161
    Microsoft Visual C++ 2010 x64 Redistributable – 10.0.40219
    Microsoft Visual C++ 2010 x86 Redistributable – 10.0.40219
    Microsoft Visual C++ 2012 x86 Additional Runtime – 11.0.51106
    Microsoft Visual C++ 2012 x86 Minimum Runtime – 11.0.51106
    Microsoft Visual C++ 2012 x64 Additional Runtime – 11.0.60610
    Microsoft Visual C++ 2013 x64 Additional Runtime – 12.0.40660
    Microsoft Visual C++ 2013 x86 Minimum Runtime – 12.0.40660
    Microsoft Visual C++ 2012 x64 Minimum Runtime – 11.0.60610
    Microsoft Visual C++ 2013 x86 Additional Runtime – 12.0.40660
    Microsoft Visual C++ 2013 x64 Minimum Runtime – 12.0.40660

    thanks
    andrew

  14. Sebastian says:

    Hi Guys,

    tried to install CU11 on my CU10 Test enviroment (2Ex2010, 1 Edge, 1 PF2010). Installed all VC++ 2010/2012/2013 (x86/64). I`m at the end of my knowledge. It looks like i have no rights (but i`m the exchangeadmin, check this more than twice). Errors like:
    [REQUIRED] The Mailbox server role isn’t installed on this computer.
    Failed [Rule:UnifiedMessagingRoleNotInstalled] [Message:The Mailbox server role isn’t installed on this computer.]
    Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UnifiedMessagingRoleNotInstalled.aspx
    Failed [Rule:BridgeheadRoleNotInstalled] [Message:The Mailbox server role isn’t installed on this computer.]
    Failed [Rule:GlobalUpdateRequired] [Message:Global updates need to be made to Active Directory, and this user account isn’t a member of the ‘Enterprise Admins’ group.]
    Failed [Rule:GlobalServerInstall] [Message:You must be a member of the ‘Organization Management’ role group or a member of the ‘Enterprise Admins’ group to continue.]
    Failed [Rule:DelegatedCafeFirstInstall] [Message:You must use an account that’s a member of the Organization Management role group to install the first Client Access server role in the topology.]
    Failed [Rule:DelegatedFrontendTransportFirstInstall] [Message:You must use an account that’s a member of the Organization Management role group to install the first Client Access server role in the topology.]
    Failed [Rule:DelegatedMailboxFirstInstall] [Message:You must use an account that’s a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.]
    Failed [Rule:DelegatedClientAccessFirstInstall] [Message:You must use an account that’s a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.]
    Failed [Rule:DelegatedUnifiedMessagingFirstInstall] [Message:You must use an account that’s a member of the Organization Management role group to install the first Mailbox server role in the topology.]
    Failed [Rule:AdInitErrorRule] [Message:Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter on a computer in the domain testmedia and site ham, and wait for replication to complete. See the Exchange setup log for more information on this error.]
    Failed [Rule:ForestLevelNotWin2003Native] [Message:The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2016, the forest functional level must be at least Windows Server 2003 native.]
    Failed [Rule:MailboxRoleNotInstalled] [Message:The Mailbox server role isn’t installed on this computer.]
    Failed [Rule:CannotAccessAD] [Message:Either Active Directory doesn’t exist, or it can’t be contacted.]

    Rebooted 10 times both 2016 Servers, tried with different Admin Accounts, tried via GUI or cmd or powershell.

    Please provide and exact reuqirements sheet with version numbers etc.

    1. Sebastian says:

      Sorry, Tipo: (2Ex2016CU10, 1 Edge 2016CU10, 1 PF2010)

      1. Sebastian says:

        Testserver1:
        Microsoft Visual C++ 2012 x86 Minimum Runtime – 11.0.61030
        Microsoft Visual C++ 2012 x86 Additional Runtime – 11.0.61030
        Microsoft Visual C++ 2012 Redistributable (x64) – 11.0.61030
        Microsoft Visual C++ 2013 Redistributable (x64) – 12.0.40660
        Microsoft Visual C++ 2013 x86 Minimum Runtime – 12.0.40660
        Microsoft Visual C++ 2012 Redistributable (x86) – 11.0.61030
        Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.4148
        Microsoft Visual C++ 2013 Redistributable (x86) – 12.0.40660
        Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.6161
        Microsoft Visual C++ 2013 x86 Additional Runtime – 12.0.40660

        Testserver2 (is deinstalled a little bit):
        Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.4148
        Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.6161
        Microsoft Visual C++ 2012 Redistributable (x64) – 11.0.61030
        Microsoft Visual C++ 2013 Redistributable (x64) – 12.0.40660

Skip to main content