Released: June 2021 Quarterly Exchange Updates

Published Jun 29 2021 08:03 AM 97.2K Views

Today we are announcing the availability of quarterly Cumulative Updates (CUs) for Exchange Server 2016 and Exchange Server 2019. These CUs include fixes for customer reported issues, all previously released security updates, and a new security feature.

A full list of fixes is contained in the KB article for each CU, but we wanted to highlight the new security feature.

Exchange Server AMSI Integration

As mentioned in our recent blog post, the June 2021 CUs include new Exchange Server integration with AMSI (Antimalware Scan Interface). AMSI exists in Windows Server 2016 and Windows Server 2019, and the new integration is available in Exchange 2016 and Exchange 2019 when running on either of those operating systems. For Exchange 2016, AMSI integration is available only when running on Windows Server 2016. It is not available for Exchange 2016 running on Windows Server 2012 or Windows Server 2012 R2.

AMSI integration in Exchange Server provides the ability for an AMSI-capable antivirus/antimalware solution to scan content in HTTP requests sent to Exchange Server and block a malicious request before it is handled by Exchange Server. The scan is performed in real-time by any AMSI-capable antivirus/antimalware solution that runs on the Exchange server as the server begins to process the request. This provides automatic mitigation and protection that compliments the existing antimalware protection in Exchange Server to help make your Exchange servers more secure.

Because we know that some of our customers modify the web.config file on their Exchange Server, we wanted to let you know that installation of the June 2021 CUs will add a new section in the web.config of every HTTP service under <Modules>. The entry will be called "HttpRequestFilteringModule" and it must be present for AMSI integration to work.

Release Details

The KB articles that describe the fixes in each release and product downloads are as follows:

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.

These updates contain schema and directory changes and so require you prepare Active Directory (AD) and all domains. You can find more information on that process here. Schema changes can be tracked here. For best practices for successful installation, please see this document.

If updating from an older version of the CU, please see Exchange Update Wizard for detailed steps to follow.

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 these resolution steps to adjust the settings.

If you plan to install the update with the unattended install option using either PowerShell or a command prompt, make sure you specify either the full path to the setup.exe file or use a “.” in front of the command if you are running it directly from the folder containing the update. If you do not, Exchange Setup may indicate that it completed successfully when it did not. Read more here.

Note: Customers in Exchange hybrid deployments and those using Exchange Online Archiving with an on-premises Exchange deployment are required to deploy a supported CU for the product version in use.

For the latest information on the Exchange Server and product announcements please see What's New in Exchange Server and Exchange Server Release Notes.

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

The Exchange Server team

81 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-2459826%22%20slang%3D%22en-US%22%3EReleased%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2459826%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20availability%20of%20quarterly%20Cumulative%20Updates%20(CUs)%20for%20Exchange%20Server%202016%20and%20Exchange%20Server%202019.%20These%20CUs%20include%20fixes%20for%20customer%20reported%20issues%2C%20all%20previously%20released%20security%20updates%2C%20and%20a%20new%20security%20feature.%3C%2FP%3E%0A%3CP%3EA%20full%20list%20of%20fixes%20is%20contained%20in%20the%20KB%20article%20for%20each%20CU%2C%20but%20we%20wanted%20to%20highlight%20the%20new%20security%20feature.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--438181770%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%20id%3D%22toc-hId--434550120%22%3E%3CFONT%20size%3D%225%22%3EExchange%20Server%20AMSI%20Integration%3C%2FFONT%3E%3C%2FH2%3E%0A%3CP%3EAs%20mentioned%20in%20our%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fnews-about-the-june-2021-cumulative-update-for-exchange-server%2Fba-p%2F2437578%22%20target%3D%22_blank%22%3Erecent%20blog%20post%3C%2FA%3E%2C%20the%20June%202021%20CUs%20include%20new%20Exchange%20Server%20integration%20with%20AMSI%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwin32%2Famsi%2Fantimalware-scan-interface-portal%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAntimalware%20Scan%20Interface%3C%2FA%3E).%20AMSI%20exists%20in%20Windows%20Server%202016%20and%20Windows%20Server%202019%2C%20and%20the%20new%20integration%20is%20available%20in%20Exchange%202016%20and%20Exchange%202019%20when%20running%20on%20either%20of%20those%20operating%20systems.%20For%20Exchange%202016%2C%20AMSI%20integration%20is%20available%20only%20when%20running%20on%20Windows%20Server%202016.%20It%20is%20not%20available%20for%20Exchange%202016%20running%20on%20Windows%20Server%202012%20or%20Windows%20Server%202012%20R2.%3C%2FP%3E%0A%3CP%3EAMSI%20integration%20in%20Exchange%20Server%20provides%20the%20ability%20for%20an%20AMSI-capable%20antivirus%2Fantimalware%20solution%20to%20scan%20content%20in%20HTTP%20requests%20sent%20to%20Exchange%20Server%20and%20block%20a%20malicious%20request%20before%20it%20is%20handled%20by%20Exchange%20Server.%20The%20scan%20is%20performed%20in%20real-time%20by%20any%20AMSI-capable%20antivirus%2Fantimalware%20solution%20that%20runs%20on%20the%20Exchange%20server%20as%20the%20server%20begins%20to%20process%20the%20request.%20This%20provides%20automatic%20mitigation%20and%20protection%20that%20compliments%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FExchange%2Fantispam-and-antimalware%2Fantimalware-protection%2Fantimalware-protection%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Eexisting%20antimalware%20protection%20in%20Exchange%20Server%3C%2FA%3E%20to%20help%20make%20your%20Exchange%20servers%20more%20secure.%3C%2FP%3E%0A%3CP%3EBecause%20we%20know%20that%20some%20of%20our%20customers%20modify%20the%20web.config%20file%20on%20their%20Exchange%20Server%2C%20we%20wanted%20to%20let%20you%20know%20that%20installation%20of%20the%20June%202021%20CUs%20will%20add%20a%20new%20section%20in%20the%20web.config%20of%20every%20HTTP%20service%20under%20%3CMODULES%3E.%20The%20entry%20will%20be%20called%20%22HttpRequestFilteringModule%22%20and%20it%20must%20be%20present%20for%20AMSI%20integration%20to%20work.%3C%2FMODULES%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%226%22%3ERelease%20Details%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EThe%20KB%20articles%20that%20describe%20the%20fixes%20in%20each%20release%20and%20product%20downloads%20are%20as%20follows%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EExchange%20Server%202019%20Cumulative%20Update%2010%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F5003612%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EKB5003612%3C%2FA%3E)%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2FLicensing%2Fservicecenter%2Fdefault.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EVLSC%20Download%3C%2FA%3E%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3FfamilyID%3Daa0d4c7c-526f-4a1a-924c-b534839f0001%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EDownload%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202016%20Cumulative%20Update%2021%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F5003611%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EKB5003611%3C%2FA%3E)%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3FfamilyID%3D88e4107e-a9a6-4847-959d-98e6e5d46f4a%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EDownload%3C%2FA%3E%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3FfamilyID%3D34d3b97f-2e82-481a-a0ab-70d6cfcfdbbe%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EUM%20Lang%20Packs%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EAdditional%20Information%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EMicrosoft%20recommends%20all%20customers%20test%20the%20deployment%20of%20any%20update%20in%20their%20lab%20environment%20to%20determine%20the%20proper%20installation%20process%20for%20your%20production%20environment.%3C%2FP%3E%0A%3CP%3EThese%20updates%20contain%20schema%20and%20directory%20changes%20and%20so%20require%20you%20prepare%20Active%20Directory%20(AD)%20and%20all%20domains.%20You%20can%20find%20more%20information%20on%20that%20process%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%20Schema%20changes%20can%20be%20tracked%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fplan-and-deploy%2Factive-directory%2Fad-schema-changes%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%20For%20best%20practices%20for%20successful%20installation%2C%20please%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fplan-and-deploy%2Finstall-cumulative-updates%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethis%20document%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3EIf%20updating%20from%20an%20older%20version%20of%20the%20CU%2C%20please%20see%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fexchangeupdatewizard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Update%20Wizard%3C%2FA%3E%20for%20detailed%20steps%20to%20follow.%3C%2FP%3E%0A%3CP%3EAlso%2C%20to%20prevent%20installation%20issues%20you%20should%20ensure%20that%20the%20Windows%20PowerShell%20Script%20Execution%20Policy%20is%20set%20to%26nbsp%3B%3CSTRONG%3EUnrestricted%3C%2FSTRONG%3E%26nbsp%3Bon%20the%20server%20being%20upgraded%20or%20installed.%20To%20verify%20the%20policy%20settings%2C%20run%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fmicrosoft.powershell.security%2Fget-executionpolicy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EGet-ExecutionPolicy%3C%2FA%3E%26nbsp%3Bcmdlet%20from%20PowerShell%20on%20the%20machine%20being%20upgraded.%20If%20the%20policies%20are%20NOT%20set%20to%20Unrestricted%20you%20should%20use%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Fplan-and-deploy%2Fdeployment-ref%2Fms-exch-setupreadiness-powershellexecutionpolicycheckset%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethese%20resolution%20steps%3C%2FA%3E%26nbsp%3Bto%20adjust%20the%20settings.%3C%2FP%3E%0A%3CP%3EIf%20you%20plan%20to%20install%20the%20update%20with%20the%20unattended%20install%20option%20using%20either%20PowerShell%20or%20a%20command%20prompt%2C%20make%20sure%20you%20specify%20either%20the%20full%20path%20to%20the%20setup.exe%20file%20or%20use%20a%20%E2%80%9C.%E2%80%9D%20in%20front%20of%20the%20command%20if%20you%20are%20running%20it%20directly%20from%20the%20folder%20containing%20the%20update.%20If%20you%20do%20not%2C%20Exchange%20Setup%20may%20indicate%20that%20it%20completed%20successfully%20when%20it%20did%20not.%20Read%20more%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Ftroubleshoot%2Fsetup%2Fex2019-setup-does-not-run-correctly-started-powershell%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%20class%3D%22note%22%3ENote%3A%20Customers%20in%20Exchange%20hybrid%20deployments%20and%20those%20using%20Exchange%20Online%20Archiving%20with%20an%20on-premises%20Exchange%20deployment%20are%20required%20to%20deploy%20a%20supported%20CU%20for%20the%20product%20version%20in%20use.%3C%2FP%3E%0A%3CP%3EFor%20the%20latest%20information%20on%20the%20Exchange%20Server%20and%20product%20announcements%20please%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fnew-features%2Fnew-features%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWhat's%20New%20in%20Exchange%20Server%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Frelease-notes%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Server%20Release%20Notes%3C%2FA%3E.%3C%2FP%3E%0A%3CP%20class%3D%22note%22%3ENote%3A%20Documentation%20may%20not%20be%20fully%20available%20at%20the%20time%20this%20post%20is%20published.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Server%20team%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2459826%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20availability%20of%20quarterly%20Cumulative%20Updates%20(CUs)%20for%20Exchange%20Server%202016%20and%20Exchange%20Server%202019.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2459826%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202019%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESetup%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2498591%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2498591%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20not%20mentioned%20in%20this%20blog%20post%2C%20but%20it%20was%20previously%20announced%20that%20this%20would%20be%20the%20final%20CU%20for%20Exchange%202016%2C%20I%20believe.%20That%20is%20what%20we%20have%20in%20our%20planning%2C%20but%20I%20thought%20I'd%20ask%20to%20confirm%20if%20this%20is%20still%20the%20case.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2501589%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2501589%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F782460%22%20target%3D%22_blank%22%3E%40kevlyn%3C%2FA%3E%2C%20the%20answer%20is%20that%20it%20is%20the%20last%20CU%2C%20unless%20someone%20higher%20up%20at%20Microsoft%20says%20it's%20not.%20Then%2C%20it%20might%20or%20might%20not%20be%2C%20depending%20on%20the%20phase%20of%20the%20moon%20and%20what%20that%20manager%20had%20for%20lunch.%20Stay%20tuned.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2502763%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2502763%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20an%20O365%20Hybrid-Setup%20with%20Exchange%202016%20CU18%20and%20Exchange%202019%20CU9%20on%20premises%20in%20coexistence.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%20I%20tried%20to%20install%20either%20CU10%20or%20CU21%2C%20but%20neither%20succeeded.%20Setup%20fails%20while%20accessing%20adminsdholder%20object%20in%20AD%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5B06%2F30%2F2021%2016%3A04%3A08.0020%5D%20%5B2%5D%20Used%20domain%20controller%20DC1.mydomain.local%20to%20read%20object%20CN%3DDelegated%20Setup%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Dmydomain%2CDC%3Dlocal.%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0035%5D%20%5B2%5D%20Used%20domain%20controller%20DC1.mydomain.local%20to%20read%20object%20DC%3Dmydomain%2CDC%3Dlocal.%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0098%5D%20%5B2%5D%20Used%20domain%20controller%20DC1.mydomain.local%20to%20read%20object%20CN%3DAdminSDHolder%2CCN%3DSystem%2CDC%3Dmydomain%2CDC%3Dlocal.%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0113%5D%20%5B2%5D%20%5BERROR%5D%20Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0113%5D%20%5B2%5D%20%5BWARNING%5D%20An%20unexpected%20error%20has%20occurred%20and%20a%20Watson%20dump%20is%20being%20generated%3A%20Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0301%5D%20%5B1%5D%20The%20following%201%20error(s)%20occurred%20during%20task%20execution%3A%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0301%5D%20%5B1%5D%200.%20ErrorRecord%3A%20Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0301%5D%20%5B1%5D%200.%20ErrorRecord%3A%20System.NullReferenceException%3A%20Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Tasks.SetupTaskBase.LogReadObject(ADRawEntry%20obj)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.InternalProcessRecord()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.%3CPROCESSRECORD%3Eb__91_1()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String%20funcName%2C%20Action%20func%2C%20Boolean%20terminatePipelineIfFailed)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage%20taskStage%2C%20Action%20initFunc%2C%20Action%20mainFunc%2C%20Action%20completeFunc)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()%3CBR%20%2F%3Eat%20System.Management.Automation.CommandProcessor.ProcessRecord()%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0301%5D%20%5B1%5D%20%5BERROR%5D%20The%20following%20error%20was%20generated%20when%20%22%24error.Clear()%3B%3CBR%20%2F%3E%24createTenantRoot%20%3D%20(%24RoleIsDatacenter%20-or%20%24RoleIsPartnerHosted)%3B%3CBR%20%2F%3E%24createMsoSyncRoot%20%3D%20%24RoleIsDatacenter%3B%3C%2FPROCESSRECORD%3E%3C%2FP%3E%3CP%3E%23%24RoleDatacenterIsManagementForest%20is%20set%20only%20in%20Datacenter%20deployment%3B%20interpret%20its%20absense%20as%20%24false%3CBR%20%2F%3E%5Bbool%5D%24isManagementForest%20%3D%20(%24RoleDatacenterIsManagementForest%20-eq%20%24true)%3B%3C%2FP%3E%3CP%3Eif%20(%24RolePrepareAllDomains)%3CBR%20%2F%3E%7B%3CBR%20%2F%3Einitialize-DomainPermissions%20-AllDomains%3A%24true%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%3CBR%20%2F%3E%7D%3CBR%20%2F%3Eelseif%20(%24RoleDomain%20-ne%20%24null)%3CBR%20%2F%3E%7B%3CBR%20%2F%3Einitialize-DomainPermissions%20-Domain%20%24RoleDomain%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%3CBR%20%2F%3E%7D%3CBR%20%2F%3Eelse%3CBR%20%2F%3E%7B%3CBR%20%2F%3Einitialize-DomainPermissions%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%3CBR%20%2F%3E%7D%3CBR%20%2F%3E%22%20was%20run%3A%20%22System.NullReferenceException%3A%20Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Tasks.SetupTaskBase.LogReadObject(ADRawEntry%20obj)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.InternalProcessRecord()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.%3CPROCESSRECORD%3Eb__91_1()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String%20funcName%2C%20Action%20func%2C%20Boolean%20terminatePipelineIfFailed)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage%20taskStage%2C%20Action%20initFunc%2C%20Action%20mainFunc%2C%20Action%20completeFunc)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()%3CBR%20%2F%3Eat%20System.Management.Automation.CommandProcessor.ProcessRecord()%22.%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0301%5D%20%5B1%5D%20%5BERROR%5D%20Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0301%5D%20%5B1%5D%20%5BERROR-REFERENCE%5D%20Id%3DDomainGlobalConfig___27a706ffe123425f9ee60cb02b930e81%20Component%3DEXCHANGE14%3A%5CCurrent%5CRelease%5CShared%5CDatacenter%5CSetup%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0301%5D%20%5B1%5D%20Setup%20is%20stopping%20now%20because%20of%20one%20or%20more%20critical%20errors.%3CBR%20%2F%3E%5B06%2F30%2F2021%2016%3A04%3A08.0301%5D%20%5B1%5D%20Finished%20executing%20component%20tasks.%3C%2FPROCESSRECORD%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDomain-%20and%20Forest%20level%20was%20W2012R2%2C%20I%20raised%20it%20to%20W2016.%20Permissions%20for%20the%20admin%20user%20is%20also%20fine%2C%20I%20also%20tried%20with%20the%20built-in%20Admin.%20PrepareSchema%20succeeded%20already.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2502850%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2502850%22%20slang%3D%22en-US%22%3E%3CP%3Eok%2C%20I%20try%20it%20again%3B-)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wanted%20to%20install%20Exchange%202019%20CU10%20in%20a%20mixed%20environment%3A%20Exchange%202016%20CU18%20and%20Exchange%202019%20CU9%20on%20premises%2C%20hybrid%20setup%20with%20O365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESetup%20fails%20while%20performing%20%2Fpreparead%2C%20the%20log%20states%20an%20error%20while%20reading%20from%20the%20AD%20AdminSdHolder%20object%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22ErrorRecord%3A%20Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20error%20when%20I%20perform%20Exchange%202016%20CU21%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20performed%20CU9%20with%20%2Fpreparead%20switch%20again%2C%20no%20issues%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20I%20cross%20checked%20CU21%20in%20another%20forest%20(pure%20Exchange%202016%20environment)%3A%20it%20succeeds%2C%20no%20problems%20at%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20no%20clue%20at%20the%20moment...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2502513%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2502513%22%20slang%3D%22en-US%22%3E%3CP%3Edoublepost%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2502815%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2502815%22%20slang%3D%22en-US%22%3E%3CP%3EOk%2C%20tried%20to%20post%20my%20error%20here%2C%20but%20it%20is%20not%20published...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Esorry%20original%20post%20was%20published%20with%20a%20large%20delay%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2504621%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2504621%22%20slang%3D%22en-US%22%3E%3CP%3EI%20got%20exactly%20the%20same%20failure%20with%202019%20CU10.%3CBR%20%2F%3EWas%20CU10%20tested%20before%20it%20was%20release%3F%3CBR%20%2F%3ECmdlet%20failed.%20Cmdlet%20Remove-ServiceEndpoint%2C%20parameters%20-DomainController%20%22xxxx%22%20-Identity%20%22Windows%20Live%20Calendar%22.%3CBR%20%2F%3ECmdlet%20failed.%20Cmdlet%20initialize-DomainPermissions%2C%20parameters%20-CreateTenantRoot%20%22False%22%20-CreateMsoSyncRoot%20%22False%22%20-IsManagementForest%20%22False%22.%3CBR%20%2F%3ECmdlet%20failed.%20Cmdlet%20Install-ExchangeOrganization%2C%20parameters%20-DomainController%20%22xxxx%22%20-OrganizationName%20%22x%22%20-PrepareSchema%20%22True%22%20-PrepareOrganization%20%22True%22%20-Industry%20%22NotSpecified%22%20-ActiveDirectorySplitPermissions%20%24null%20-PrepareDomain%20%22True%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2505852%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2505852%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20failure%20here%2C%20Exchange%202016%20CU%2020%20-%26gt%3B%20CU%2021.%3C%2FP%3E%3CP%3EFix%20it%20pls%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2506233%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2506233%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%20all%20the%20AD%20update%20work%20from%20a%20DC%20first%20the%20update%20exchange%20and%20it%20worked%20fine%20I%20did%20all%20from%20command%20line%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2506569%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2506569%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20any%20way%20to%20monitor%20%2F%20verify%20Exchange%20%26lt%3B-%26gt%3B%20AMSI%20Integration%3F%3C%2FP%3E%3CP%3EI%20deployed%202019%20CU10%20without%20issues%20and%20made%20sure%20WDAV%20is%20running%2C%20I%20do%20notice%20an%20increased%20cpu%20load%20and%20antimalware%20scanning%20process%20is%20consuming%20resources%20constantly.%3C%2FP%3E%3CP%3ECouldn%C2%B4t%20find%20any%20log%20or%20event%20enteries%20so%20far%20though.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2507887%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2507887%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1093017%22%20target%3D%22_blank%22%3E%40justsomeadmin%3C%2FA%3E%26nbsp%3BFair%20question%3B%20we%20are%20working%20on%20a%20blog%20post%20related%20to%20this.%26nbsp%3BNote%20that%20there%20will%20be%20nothing%20to%20see%2C%20unless%20we%20(Microsoft)%20ship%20signatures%20to%20Defender%20to%20actually%20block%20something.%26nbsp%3BIf%20you%20speak%20of%203rd%20party%20solution%20that%20is%20AMSI%20compatible%2C%20then%20those%20signatures%20would%20be%20shipped%20by%20the%203rd%20party%20(totally%20out%20of%20our%20hands).%20But%20I%20get%20it%3B%20right%20now%20it%20is%20a%20bit%20of%20a%20black%20box%2C%20so%20a%20few%20people%20are%20pulling%20together%20some%20guidance%20around%20it%20all.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2507919%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2507919%22%20slang%3D%22en-US%22%3E%3CP%3Emy%20Exchange%202016%20farm%20is%20now%20on%20CU20%2C%20but%20I%20still%20can%20not%20update%20to%20CU21%20or%20CU10%20for%20the%20Exchange%202019%20servers%20(%2FPrepareAD%20fails).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20it%20also%20from%20a%20DC%20-%20same%20error%2C%20the%20procedure%20fails%20after%20walking%20through%20AdminSDHolder%20in%20AD%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUntil%20now%20I%20never%20had%20problems%20with%20any%20CU.%20Exchange%20Hybrid%20went%20live%20in%202021%2F03.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2508026%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2508026%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1092195%22%20target%3D%22_blank%22%3E%40MI5-Agent%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1092854%22%20target%3D%22_blank%22%3E%40Hnny0%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F550920%22%20target%3D%22_blank%22%3E%40GrahamJB%3C%2FA%3E%26nbsp%3B%3A%20At%20this%20time%2C%20we%20are%20not%20aware%20of%20systemic%20problems%20related%20to%20this%3B%20yes%2C%20those%20CUs%20have%20been%20tested%20as%20all%20other%20CUs%20(I%20know%20it%20was%20more%20of%20a%20hypothetical%20question).%26nbsp%3BWe%20suspect%20some%20non-standard%20AD%20permissions%20change%20is%20causing%20this%20but%20so%20far%2C%20we%20have%20not%20figured%20what%20it%20is.%3C%2FP%3E%0A%3CP%3ECould%20one%20of%20you%20open%20a%20support%20ticket%20with%20on-prem%20support%3F%20If%20you%20do%2C%20please%20PM%20me%20the%20ticket%20number.%3C%2FP%3E%0A%3CP%3EI'll%20post%20here%20if%20we%20figure%20out%20anything%20else%20on%20our%20end%2C%20but%20so%20far%20-%20we%20do%20not%20have%20have%20a%20repro%20of%20this%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2508035%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2508035%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1092195%22%20target%3D%22_blank%22%3E%40MI5-Agent%3C%2FA%3E%26nbsp%3B%20was%20the%20DC%20you%20tied%20it%20from%20the%20Schema%20master%20I%20do%20all%20my%20AD%20updates%20from%20the%20Schema%20master%20with%20on%20issues%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2508361%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2508361%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20installer%20cannot%20run%20on%20our%20schema%20master%20as%20it%20appears%20to%20need%20to%20have%20the%20prerequisites%20for%20exchange%20installed%20on%20the%20schema%20master%20(setup%20requires%20.Net%20Framework%204.8)%2C%20even%20when%20running%20with%20only%3A%3CBR%20%2F%3ESetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FPrepareSchema%3CBR%20%2F%3EWhy%20would%20that%20be%20a%20prereq%20for%20the%20schema%20upgrade%3F%3C%2FP%3E%3CP%3EWhy%20would%20anybody%20assume%20that%20dotnet%20must%20be%20installed%20at%20all%20on%20an%20AD%20schema%20master%20if%20you%20have%20an%20option%20not%20to%3F%3F%3CBR%20%2F%3EIs%20there%20a%20way%20to%20disable%20the%20pre-req%20check%20when%20just%20updating%20AD%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5BThis%20is%20an%20on-prem%20only%20setup%20upgraded%20over%20the%20years%20from%20SBS%202003%5D%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2508647%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2508647%22%20slang%3D%22en-US%22%3E%3CP%3EI%20gave%20again%20full%20access%20for%20a%20group%20containing%20EX-Servers%2C%20Org-Admin%2C%20Adminuser%20etc.%20to%20my%20AD%2C%20I%20also%20removed%20orphaned%20delegates.%20I%20also%20blocked%20some%20GPOs%20to%20the%20DCs%2C%20thus%20only%20the%20default%20GPOs%20are%20active%20-%20no%20success.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20believe%20that%20this%20is%20a%20problem%20with%20rights%20to%20the%20directoy%2C%20i%20presume%20it%20has%20something%20to%20do%20with%20the%20Exchange%20hybrid%20setup.%20I%20could%20install%20CU21%20in%20another%20onprem%20Exchange%20organisation%20without%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20I%20will%20open%20a%20ticket%20with%20MS%20later%20on%20when%20there%20is%20some%20time%20for%20it%2C%20running%20with%20CU20%2FCU9%20is%20fine%20for%20the%20next%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2509074%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2509074%22%20slang%3D%22en-US%22%3E%3CP%3EI%20ran%20the%20following%20on%20the%20exchange%20server%20and%20they%20succeeded%20on%20the%20exchange%202019%20server.%3C%2FP%3E%3CPRE%3ESetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FPrepareSchema%3C%2FPRE%3E%3CPRE%3ESetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FPrepareAD%20%2FOrganizationName%3Ax%3C%2FPRE%3E%3CP%3EThe%20following%20alternatives%20both%20fail%3A%3C%2FP%3E%3CPRE%3E%3CSPAN%20class%3D%22pl-c1%22%3ESetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FPrepareAllDomains%3C%2FSPAN%3E%3C%2FPRE%3E%3CPRE%3E%3CSPAN%20class%3D%22pl-c1%22%3ESetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FPrepareDomain%3Ax.local%3C%2FSPAN%3E%3C%2FPRE%3E%3CP%3Ewith%20the%20null%20reference%20error%20above%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2509075%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2509075%22%20slang%3D%22en-US%22%3E%3CP%3EBTW%20..%20has%20anybody%20tried%20following%20steps%20in%3A%3C%2FP%3E%3CP%3E%3CSPAN%3E%26gt%3BIf%20updating%20from%20an%20older%20version%20of%20the%20CU%2C%20please%20see%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fexchangeupdatewizard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Update%20Wizard%3C%2FA%3E%3CSPAN%3E%26nbsp%3Bfor%20detailed%20steps%20to%20follow.%3CBR%20%2F%3ECU10%20is%20not%20even%20listed%20!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2509571%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2509571%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%3A%3C%2FP%3E%3CP%3ESetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FPrepareAD%20%2FOrganizationName%3A%22First%20Organisation%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EResult%3A%3C%2FP%3E%3CP%3EExchange%20organization%20name%20cannot%20be%20specified.%20There%20already%20exists%20an%20Exchange%20organization%20with%20name%20'First%3CBR%20%2F%3EOrganization'.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2513085%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2513085%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHave%20applied%20the%20CU21%20to%20a%20system%20(2016)%20that%20had%20CU19.%20Having%20issues%20with%20client%20connectivity%20now.%20Is%20there%20any%20way%20of%20disabling%20AMSI%20for%20troubleshooting%20to%20ensure%20this%20isn't%20the%20cause%20of%20the%20issues%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2513819%22%20slang%3D%22en-US%22%3EBetreff%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2513819%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ESame%20%2FPrepareAD%20error%20as%20MSch%20and%20MI5-agent%20in%20hybrid%20configuration%20with%20on-prem%202016cu20%20on%20srv2016.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2515480%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2515480%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20found%20that%20after%20installing%20CU10%20on%20Exchange%202019%20it%20is%20no%20longer%20possible%20to%20edit%20Custom%20Attributes%20from%20the%20Exchange%20Admin%20Center.%20It%20looks%20to%20work%20without%20error%2C%20but%20then%20no%20change%20has%20been%20saved.%20The%20command%20logger%20shows%20the%20set-mailbox%20command%20is%20not%20actually%20run.%20Set-mailbox%20run%20directly%20from%20PowerShell%20works%20normally%20and%20does%20edit%20Custom%20Attributes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2515861%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2515861%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20same%20for%202016%26nbsp%3B%3CSPAN%3Eit%20is%20no%20longer%20possible%20to%20edit%20Custom%20Attributes%20from%20the%20Exchange%20Admin%20Center.%20But%20it%20gets%20picked%20up%20if%20you%20do%20it%20though%20AD%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2518297%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2518297%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20a%20general%20question%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20upgraded%20an%20Exchange%202016%20CU%2019%20server%20to%20CU%2021.%20Everything%20went%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20see%20the%20following%20service%3A%26nbsp%3BTracing%20Service%20for%20Search%20in%20Exchange%3C%2FP%3E%3CP%3EStartup%20type%3A%20Disabled%3C%2FP%3E%3CP%3EDescription%3A%26nbsp%3BThis%20service%20provides%20trace%20logs%20for%20search%20components%20in%20Exchange.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20service%20is%20not%20mentioned%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fdeployment-ref%2Fservices-overview%3Fview%3Dexchserver-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EOverview%20of%20Exchange%20services%20on%20Exchange%20servers%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20the%20purpose%20of%20this%20service%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2518694%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2518694%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20a%20reminder%20for%20all%20who%20use%20unattended%20setup.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3EIf%20you%20plan%20to%20install%20the%20update%20with%20the%20unattended%20install%20option%20using%20either%20PowerShell%20or%20a%20command%20prompt%2C%20make%20sure%20you%20%3CSTRONG%3Especify%20either%20the%20full%20path%20to%20the%20setup.exe%20file%20or%20use%20a%20%E2%80%9C.%E2%80%9D%20in%20front%20of%20the%20command%3C%2FSTRONG%3E%20if%20you%20are%20running%20it%20directly%20from%20the%20folder%20containing%20the%20update.%20If%20you%20do%20not%2C%20Exchange%20Setup%20may%20indicate%20that%20it%20completed%20successfully%20when%20it%20did%20not.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fsetup%2Fex2019-setup-does-not-run-correctly-started-powershell%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Server%202019%20setup%20does%20not%20run%20as%20expected%20if%20started%20from%20PowerShell%20using%20Setup.exe%20-%20Exchange%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20see%20it%20quite%20often%20that%20the%20unattended%20setup%20was%20called%20incorrectly%20and%20so%20PrepareAd%20or%20PrepareSchema%20doesn't%20run%20as%20expected.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2518737%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2518737%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3Emy%20lab%20environmente%3A%204%20Exchange%202016%20CU19.%3C%2FP%3E%3CP%3ESame%20problem%20with%20%2FPrepareAD%26nbsp%3B%3CSPAN%3Eas%20MSch%20and%20MI5-agent%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20opened%20a%20ticket%20to%20Microsoft%20Support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGiorgio%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2518738%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2518738%22%20slang%3D%22en-US%22%3E%3CP%3E%2FPrepareAD%20still%20fails.%20I%20installed%20the%20latest%20CU%20on%20all%20DCs%2C%20moved%20FSMO%20roles%20forth%20and%20back%2C%20tried%20Exchange%20setup%20from%20Exchange%20and%20DCs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENothing%20helped.%20%2FPrepareAD%20still%20fails%20after%2097~98%25%2C%20see%20my%20notes%20above.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20to%20say%2C%20that%20my%20organisation%20is%20in%20german%20as%20well%20(all%20Exchange%20servers%20and%20DCs)%2C%20though%20I%20tried%20%2Fpreparad%20also%20from%20an%20EN%20member%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22%E2%80%9C%20ausgef%C3%BChrt%20wurde%3A%20%E2%80%9ESystem.NullReferenceException%3A%20Der%20Objektverweis%20wurde%20nicht%20auf%20eine%20Objektinstanz%20festgelegt.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3Ebei%20Microsoft.Exchange.Management.Tasks.SetupTaskBase.LogReadObject(ADRawEntry%20obj)%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMaybe%20this%20specific%20problem%20is%20language%20related%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2518739%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2518739%22%20slang%3D%22en-US%22%3E%3CP%3E%40Giorgio%3A%20which%20language%20does%20your%20organisation%20use%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2518749%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2518749%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1092195%22%20target%3D%22_blank%22%3E%40MI5-Agent%3C%2FA%3E%26nbsp%3Byou%20can%20use%20the%20SetupAssist.ps1%20script%20to%20check%20a%20few%20well-known%20things.%20Have%20you%20tried%20this%3F%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmicrosoft.github.io%2FCSS-Exchange%2FSetup%2FSetupAssist%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ESetupAssist.ps1%20-%20Exchange%20Server%20Support%20Scripts%20(microsoft.github.io)%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2518768%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2518768%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1092195%22%20target%3D%22_blank%22%3E%40MI5-Agent%3C%2FA%3E%3C%2FP%3E%3CP%3EEnglish%20language%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2519234%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2519234%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F164282%22%20target%3D%22_blank%22%3E%40Lukas%20Sassl%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%5BPS%5D%20C%3A%5CScripts%26gt%3B.%5CSetupAssist.ps1%0AUser%20is%20an%20administrator.%0AWARNUNG%3A%20User%20is%20not%20a%20member%20of%20Domain%20Admins.%0AWARNUNG%3A%20User%20is%20not%20a%20member%20of%20Schema%20Admins.%20-%20Only%20required%20if%20doing%20a%20Schema%20Update%0AWARNUNG%3A%20User%20is%20not%20a%20member%20of%20Enterprise%20Admins.%20-%20Only%20required%20if%20doing%20a%20Schema%20Update%20or%20PrepareAD%20or%20PrepareDomain%0AWARNUNG%3A%20User%20is%20not%20a%20member%20of%20Organization%20Management.%0AWARNUNG%3A%20ExecutionPolicy%20is%20RemoteSigned%0ANo%20installer%20packages%20missing.%0ADownload%20Visual%20C%2B%2B%202012%20Redistributable%20Package%20and%20install%3A%20https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D30679%0ANo%20other%20PowerShell%20instances%20were%20detected.%0ANo%20reboot%20pending.%0AAll%20Critical%20Mailboxes%20have%20valid%20HomeMDB%20values%0AWARNUNG%3A%20Exchange%202019%20AD%20Level%20Failed.%20Mismatch%20detected.%0AWARNUNG%3A%20DN%20Value%3A%20'CN%3DStadt%20intern%2CCN%3DMicrosoft%20Exchange%2CCN%3DServices%2CCN%3DConfiguration%2CDC%3Dintern%2CDC%3Dde'%20-%20Version%3A%2016220%0AWARNUNG%3A%20DN%20Value%3A%20'CN%3Dms-Exch-Schema-Version-Pt%2CCN%3DSchema%2CCN%3DConfiguration%2CDC%3Dintern%2CDC%3Dde'%20-%20Version%3A%2017003%0AWARNUNG%3A%20DN%20Value%3A%20'CN%3DMicrosoft%20Exchange%20System%20Objects%2CDC%3Dintern%2CDC%3Dde'%20-%20Version%3A%2013240%0AWARNUNG%3A%20More%20Info%3A%20https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%3Fview%3Dexchserver-2019%0ASystem.Management.Automation.RuntimeException%3A%20Es%20ist%20nicht%20m%C3%B6glich%2C%20einen%20Index%20auf%20ein%20NULL-Array%20anzuwenden.%0A%20%20%20bei%20System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext%20funcContext%2C%20Exception%20exception)%0A%20%20%20bei%20System.Management.Automation.Interpreter.ActionCallInstruction%602.Run(InterpretedFrame%20frame)%0A%20%20%20bei%20System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame%20frame)%0A%20%20%20bei%20System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame%20frame)%0Abei%20Write-PrepareADInfo%2C%20C%3A%5CScripts%5CSetupAssist.ps1%3A%20Zeile%20236%0Abei%20Write-Mismatch%2C%20C%3A%5CScripts%5CSetupAssist.ps1%3A%20Zeile%20334%0Abei%20Test-ExchangeAdSetupObjects%2C%20C%3A%5CScripts%5CSetupAssist.ps1%3A%20Zeile%20452%0Abei%20MainUse%2C%20C%3A%5CScripts%5CSetupAssist.ps1%3A%20Zeile%201761%0Abei%20Main%2C%20C%3A%5CScripts%5CSetupAssist.ps1%3A%20Zeile%201814%0Abei%20%26lt%3BScriptBlock%26gt%3B%2C%20C%3A%5CScripts%5CSetupAssist.ps1%3A%20Zeile%201828%0Abei%20%26lt%3BScriptBlock%26gt%3B%2C%20%26lt%3BKeine%20Datei%26gt%3B%3A%20Zeile%201%0AWARNUNG%3A%20Ran%20into%20an%20issue%20with%20the%20script.%20If%20possible%20please%20email%20'ExToolsFeedback%40microsoft.com'%20of%20the%20issue%20that%20you%20are%20facing%3C%2FPRE%3E%3CP%3EThe%20script%20does%20not%20work%20properly.%3CBR%20%2F%3EUser%20is%20member%20of%20domain%20admin%20(intern%5Cadministrator).%3CBR%20%2F%3EUser%20is%20member%20of%20Schema%20Admin.%3CBR%20%2F%3EUser%20is%20a%20member%20of%20the%20Enterprise%20Admin.%3CBR%20%2F%3EUser%20is%20a%20member%20of%20Organization%20Management.%3CBR%20%2F%3EVisual%20C%2B%2B%202012%20Redistributable%20Package%20is%20installed%20and%20up-to-date.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2508250%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2508250%22%20slang%3D%22en-US%22%3E%3CP%3Every%20strange.%20The%20AD%20was%20setup%20in%202010%20with%20W2008R2%20-%20nothing%20special.%20Additionally%2C%20I%20am%20running%20Skype%20for%20Business%20on%20prem%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20tried%20else%3A%3C%2FP%3E%3CP%3E-%20from%20DC%20with%20and%20without%20schemamaster%20role%3C%2FP%3E%3CP%3E-%20i%20gave%20temporarily%20full%20access%20on%20AD%20for%20admin%20and%20Exchange-Servers%3C%2FP%3E%3CP%3E-%20disabled%20Windows%20FW-Rules%3C%2FP%3E%3CP%3E-%20%2Fpreparedomain%20instead%20of%20%2Fpreparead%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2509829%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2509829%22%20slang%3D%22en-US%22%3E%3CP%3EShare%20experience%3C%2FP%3E%3COL%3E%3CLI%3EDone%20upgraded%2015%20servers%20(Total%2030)%20Exchange%202016%20CU20%20to%2021%20on%20Hybrid%20coexistence%20mode.%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%3CUL%3E%3CLI%3Eso%20far%20no%20issue%3C%2FLI%3E%3CLI%3EPrepare%20schema%20required%3C%2FLI%3E%3CLI%3Ethen%20run%20AADC%20-%20refresh%20directory%20schema%20(optional)%3C%2FLI%3E%3CLI%3EDAG%20MA%20mode%3CBR%20%2F%3E%3CPRE%3EDAG%20MA%20Mode%0ASet-ServerComponentState%20TargetServer%20-Component%20HubTransport%20-State%20Draining%20-Requester%20Maintenance%0ARestart-Service%20MSExchangeTransport%0ASet-ServerComponentState%20TargetServer%20-Component%20UMCallRouter%20-State%20Draining%20-Requester%20Maintenance%0ACD%20%24ExScripts%0A.%5CStartDagServerMaintenance.ps1%20-ServerName%20TargetServer%20-MoveComment%20Maintenance%20-PauseClusterNode%0ASet-MailboxServer%20-Identity%20Server%20-DatabaseCopyAutoActivationPolicy%20Blocked%0ARedirect-Message%20-Server%20TargetServer%20-Target%20Server2.domain.local%0ASet-ServerComponentState%20TargetServer%20-Component%20ServerWideOffline%20-State%20Inactive%20-Requester%20Maintenance%0A%0AGet-ScheduledTask%20-TaskPath%20%5C%20%7C%20Stop-ScheduledTask%0AGet-ScheduledTask%20-TaskPath%20%5C%20%7C%20disable-ScheduledTask%0AGet-ScheduledTask%20-TaskPath%20%5C%0A%0AGet-ServerComponentState%20TargetServer%20%7C%20Format-Table%20Component%2CState%20-Autosize%0AGet-MailboxServer%20TargetServer%20%7C%20Format-List%20DatabaseCopyAutoActivationPolicy%0AGet-ClusterNode%20TargetServer%20%7C%20Format-List%0AGet-Queue%0A%0AGet-MpComputerStatus%20%7C%20ft%20RealTimeProtectionEnabled%0ASet-MpPreference%20-DisableRealtimeMonitoring%20%24True%0AGet-MpComputerStatus%20%7C%20ft%20RealTimeProtectionEnabled%0A%0A%0ASetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FMode%3AUpgrade%0A%0A%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%0ABring%20Service%20Back%20Online%0ASet-ServerComponentState%20TargetServer%20-Component%20ServerWideOffline%20-State%20Active%20-Requester%20Maintenance%0ASet-ServerComponentState%20TargetServer%20-Component%20UMCallRouter%20-State%20Active%20-Requester%20Maintenance%0ACD%20%24ExScripts%0A.%5CStopDagServerMaintenance.ps1%20-serverName%20TargetServer%0ASet-ServerComponentState%20TargetServer%20-Component%20HubTransport%20-State%20Active%20-Requester%20Maintenance%0ARestart-Service%20MSExchangeTransport%0AGet-ServerComponentState%20TargetServer%20%7C%20Format-Table%20Component%2CState%20-Autosize%0A%0AGet-ServerComponentState%20TargetServer%20%7C%20Format-Table%20Component%2CState%20-Autosize%0AGet-MailboxServer%20TargetServer%20%7C%20Format-List%20DatabaseCopyAutoActivationPolicy%0AGet-ClusterNode%20TargetServer%20%7C%20Format-List%0AGet-Queue%0A%0AGet-ScheduledTask%20-TaskPath%20%5C%20%7C%20enable-ScheduledTask%0AGet-ScheduledTask%20-TaskPath%20%5C%0ASet-MpPreference%20-DisableRealtimeMonitoring%20%24false%0AGet-MpComputerStatus%20%7C%20ft%20RealTimeProtectionEnabled%0A.%5CHealthChecker_21.06.29.1121.ps1%3C%2FPRE%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3EAMSI%20testing%20work%20-%20follow%20below%20steps%26nbsp%3B%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwin32%2Famsi%2Fhow-amsi-helps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwin32%2Famsi%2Fhow-amsi-helps%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AMSI_result.png%22%20style%3D%22width%3A%20806px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F293084i0EA4FB95F29A87F7%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22AMSI_result.png%22%20alt%3D%22AMSI_result.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2523171%22%20slang%3D%22de-DE%22%3ESubject%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2523171%22%20slang%3D%22de-DE%22%3E%3CP%3EUnfortunately%20the%20update%20doesn't%20work%20for%20us%20either.%20We%20want%20to%20update%20from%20CU20%20to%20CU21%3C%2FP%3E%3CPRE%3E%5B07.07.2021%2011%3A07%3A38.0002%5D%20%5B2%5D%20Die%20Active%20Directory-Sitzungseinstellungen%20f%C3%BCr%20'install-Container'%20lauten%3A%20Vollst%C3%A4ndige%20Gesamtstruktur%20anzeigen%3A%20'True'%2C%20Konfigurationsdom%C3%A4nencontroller%3A%20'AD01.domain.de'%2C%20Bevorzugter%20globaler%20Katalog%3A%20'AD01.domain.de'%2C%20Bevorzugte%20Dom%C3%A4nencontroller%3A%20'%7B%20AD01.domain.de%20%7D'%0A%5B07.07.2021%2011%3A07%3A38.0002%5D%20%5B2%5D%20User%20specified%20parameters%3A%20%20-Name%3A'UM%20AutoAttendant%20Container'%20-DomainController%3A'AD01.domain.de'%0A%5B07.07.2021%2011%3A07%3A38.0002%5D%20%5B2%5D%20Beginning%20processing%20install-Container%0A%5B07.07.2021%2011%3A07%3A38.0002%5D%20%5B2%5D%20Processing%20object%20%22UM%20AutoAttendant%20Container%22.%0A%5B07.07.2021%2011%3A07%3A38.0003%5D%20%5B2%5D%20Ending%20processing%20install-Container%0A%5B07.07.2021%2011%3A07%3A38.0005%5D%20%5B1%5D%20Processing%20component%20'CAFE%20Global%20AD%20Configuration'%20(Globale%20Clientzugriffseinstellungen%20werden%20konfiguriert.).%0A%5B07.07.2021%2011%3A07%3A38.0005%5D%20%5B1%5D%20Processing%20component%20'Domain-specific%20AD%20Configuration'%20(Dom%C3%A4nen%20f%C3%BCr%20Exchange%20werden%20konfiguriert.).%0A%5B07.07.2021%2011%3A07%3A38.0006%5D%20%5B1%5D%20Executing%3A%20%0A%20%20%20%20%20%20%20%20%20%20%24createTenantRoot%20%3D%20(%24RoleIsDatacenter%20-or%20%24RoleIsPartnerHosted)%3B%0A%20%20%20%20%20%20%20%20%20%20%24createMsoSyncRoot%20%3D%20%24RoleIsDatacenter%3B%0A%0A%20%20%20%20%20%20%20%20%20%20%23%24RoleDatacenterIsManagementForest%20is%20set%20only%20in%20Datacenter%20deployment%3B%20interpret%20its%20absense%20as%20%24false%0A%20%20%20%20%20%20%20%20%20%20%5Bbool%5D%24isManagementForest%20%3D%20(%24RoleDatacenterIsManagementForest%20-eq%20%24true)%3B%0A%0A%20%20%20%20%20%20%20%20%20%20if%20(%24RolePrepareAllDomains)%0A%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20initialize-DomainPermissions%20-AllDomains%3A%24true%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20elseif%20(%24RoleDomain%20-ne%20%24null)%0A%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20initialize-DomainPermissions%20-Domain%20%24RoleDomain%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20else%0A%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20initialize-DomainPermissions%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%0A%5B07.07.2021%2011%3A07%3A38.0009%5D%20%5B2%5D%20Die%20Active%20Directory-Sitzungseinstellungen%20f%C3%BCr%20'initialize-DomainPermissions'%20lauten%3A%20Vollst%C3%A4ndige%20Gesamtstruktur%20anzeigen%3A%20'True'%2C%20Konfigurationsdom%C3%A4nencontroller%3A%20'AD01.domain.de'%2C%20Bevorzugter%20globaler%20Katalog%3A%20'AD01.domain.de'%2C%20Bevorzugte%20Dom%C3%A4nencontroller%3A%20'%7B%20AD01.domain.de%20%7D'%0A%5B07.07.2021%2011%3A07%3A38.0010%5D%20%5B2%5D%20User%20specified%20parameters%3A%20%20-CreateTenantRoot%3A'False'%20-CreateMsoSyncRoot%3A'False'%20-IsManagementForest%3A'False'%0A%5B07.07.2021%2011%3A07%3A38.0010%5D%20%5B2%5D%20Beginning%20processing%20initialize-DomainPermissions%0A%5B07.07.2021%2011%3A07%3A38.0012%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20DC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0015%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DExchange%20Servers%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0015%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DExchange%20Servers%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0017%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DOrganization%20Management%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0017%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DOrganization%20Management%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0019%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DPublic%20Folder%20Management%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0019%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DPublic%20Folder%20Management%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0021%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DExchange%20Trusted%20Subsystem%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0021%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DExchange%20Trusted%20Subsystem%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0022%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DExchange%20Windows%20Permissions%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0022%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DExchange%20Windows%20Permissions%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0025%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DDom%C3%A4nen-Benutzer%2CCN%3DUsers%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0027%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DDelegated%20Setup%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0027%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DDelegated%20Setup%2COU%3DMicrosoft%20Exchange%20Security%20Groups%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0035%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20DC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0082%5D%20%5B2%5D%20Used%20domain%20controller%20AD01.domain.de%20to%20read%20object%20CN%3DAdminSDHolder%2CCN%3DSystem%2CDC%3Ddomain%2CDC%3Dde.%0A%5B07.07.2021%2011%3A07%3A38.0091%5D%20%5B2%5D%20%5BERROR%5D%20Der%20Objektverweis%20wurde%20nicht%20auf%20eine%20Objektinstanz%20festgelegt.%0A%5B07.07.2021%2011%3A07%3A38.0092%5D%20%5B2%5D%20%5BWARNING%5D%20An%20unexpected%20error%20has%20occurred%20and%20a%20Watson%20dump%20is%20being%20generated%3A%20Der%20Objektverweis%20wurde%20nicht%20auf%20eine%20Objektinstanz%20festgelegt.%0A%5B07.07.2021%2011%3A07%3A39.0174%5D%20%5B1%5D%20The%20following%201%20error(s)%20occurred%20during%20task%20execution%3A%0A%5B07.07.2021%2011%3A07%3A39.0174%5D%20%5B1%5D%200.%20%20ErrorRecord%3A%20Der%20Objektverweis%20wurde%20nicht%20auf%20eine%20Objektinstanz%20festgelegt.%0A%5B07.07.2021%2011%3A07%3A39.0174%5D%20%5B1%5D%200.%20%20ErrorRecord%3A%20System.NullReferenceException%3A%20Der%20Objektverweis%20wurde%20nicht%20auf%20eine%20Objektinstanz%20festgelegt.%0A%20%20%20bei%20Microsoft.Exchange.Management.Tasks.SetupTaskBase.LogReadObject(ADRawEntry%20obj)%0A%20%20%20bei%20Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.InternalProcessRecord()%0A%20%20%20bei%20Microsoft.Exchange.Configuration.Tasks.Task.%26lt%3BProcessRecord%26gt%3Bb__91_1()%0A%20%20%20bei%20Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String%20funcName%2C%20Action%20func%2C%20Boolean%20terminatePipelineIfFailed)%0A%20%20%20bei%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage%20taskStage%2C%20Action%20initFunc%2C%20Action%20mainFunc%2C%20Action%20completeFunc)%0A%20%20%20bei%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()%0A%20%20%20bei%20System.Management.Automation.CommandProcessor.ProcessRecord()%0A%5B07.07.2021%2011%3A07%3A39.0176%5D%20%5B1%5D%20%5BERROR%5D%20The%20following%20error%20was%20generated%20when%20%22%24error.Clear()%3B%20%0A%20%20%20%20%20%20%20%20%20%20%24createTenantRoot%20%3D%20(%24RoleIsDatacenter%20-or%20%24RoleIsPartnerHosted)%3B%0A%20%20%20%20%20%20%20%20%20%20%24createMsoSyncRoot%20%3D%20%24RoleIsDatacenter%3B%0A%0A%20%20%20%20%20%20%20%20%20%20%23%24RoleDatacenterIsManagementForest%20is%20set%20only%20in%20Datacenter%20deployment%3B%20interpret%20its%20absense%20as%20%24false%0A%20%20%20%20%20%20%20%20%20%20%5Bbool%5D%24isManagementForest%20%3D%20(%24RoleDatacenterIsManagementForest%20-eq%20%24true)%3B%0A%0A%20%20%20%20%20%20%20%20%20%20if%20(%24RolePrepareAllDomains)%0A%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20initialize-DomainPermissions%20-AllDomains%3A%24true%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20elseif%20(%24RoleDomain%20-ne%20%24null)%0A%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20initialize-DomainPermissions%20-Domain%20%24RoleDomain%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20else%0A%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20initialize-DomainPermissions%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%22%20was%20run%3A%20%22System.NullReferenceException%3A%20Der%20Objektverweis%20wurde%20nicht%20auf%20eine%20Objektinstanz%20festgelegt.%0A%20%20%20bei%20Microsoft.Exchange.Management.Tasks.SetupTaskBase.LogReadObject(ADRawEntry%20obj)%0A%20%20%20bei%20Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.InternalProcessRecord()%0A%20%20%20bei%20Microsoft.Exchange.Configuration.Tasks.Task.%26lt%3BProcessRecord%26gt%3Bb__91_1()%0A%20%20%20bei%20Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String%20funcName%2C%20Action%20func%2C%20Boolean%20terminatePipelineIfFailed)%0A%20%20%20bei%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage%20taskStage%2C%20Action%20initFunc%2C%20Action%20mainFunc%2C%20Action%20completeFunc)%0A%20%20%20bei%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()%0A%20%20%20bei%20System.Management.Automation.CommandProcessor.ProcessRecord()%22.%0A%5B07.07.2021%2011%3A07%3A39.0177%5D%20%5B1%5D%20%5BERROR%5D%20Der%20Objektverweis%20wurde%20nicht%20auf%20eine%20Objektinstanz%20festgelegt.%0A%5B07.07.2021%2011%3A07%3A39.0177%5D%20%5B1%5D%20%5BERROR-REFERENCE%5D%20Id%3DDomainGlobalConfig___27a706ffe123425f9ee60cb02b930e81%20Component%3DEXCHANGE14%3A%5CCurrent%5CRelease%5CShared%5CDatacenter%5CSetup%0A%5B07.07.2021%2011%3A07%3A39.0177%5D%20%5B1%5D%20Setup%20is%20stopping%20now%20because%20of%20one%20or%20more%20critical%20errors.%0A%5B07.07.2021%2011%3A07%3A39.0177%5D%20%5B1%5D%20Finished%20executing%20component%20tasks.%0A%5B07.07.2021%2011%3A07%3A39.0187%5D%20%5B1%5D%20Ending%20processing%20Install-ExchangeOrganization%0A%5B07.07.2021%2011%3A09%3A20.0967%5D%20%5B0%5D%20CurrentResult%20setupbase.maincore%3A396%3A%200%0A%5B07.07.2021%2011%3A09%3A20.0968%5D%20%5B0%5D%20End%20of%20Setup%0A%5B07.07.2021%2011%3A09%3A20.0968%5D%20%5B0%5D%20**********************************************%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2525156%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2525156%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20identical%20issue%20installing%20CU10%20on%20an%20up%20to%20date%20CU9%20Exchange%202019%20servers.%26nbsp%3B%20This%20is%20also%20in%20a%20hybrid%20environment.%26nbsp%3B%20I%20have%20tried%20all%20obvious%20fixes%20and%20NONE%20work.%26nbsp%3B%20Come%20on%20Microsoft...%20give%20us%20a%20fix%20please.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2513525%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2513525%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ecurrently%20I%20fail%20already%20in%20the%20preparation%20for%20the%20actual%20setup%3A%3CBR%20%2F%3ESchema%20was%20successfully%20updated%20from%20CU19%20to%20CU21%3CBR%20%2F%3ESetup.EXE%20%2FPrepareAD%20%2FIAcceptExchangeServerLicenseTerms%20keeps%20aborting%3A%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-60px%22%3EGUI%20Step%201%20from%2018%3A%3CBR%20%2F%3EDer%20folgende%20Fehler%20wurde%20generiert%2C%20als%20%E2%80%9E%24error.Clear()%3B%3CBR%20%2F%3E%24createTenantRoot%20%3D%20(%24RoleIsDatacenter%20-or%20%24RoleIsPartnerHosted)%3B%3CBR%20%2F%3E%24createMsoSyncRoot%20%3D%20%24RoleIsDatacenter%3B%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-60px%22%3E%23%24RoleDatacenterIsManagementForest%20is%20set%20only%20in%20Datacenter%20deployment%3B%20interpret%20its%20absense%20as%20%24false%3CBR%20%2F%3E%5Bbool%5D%24isManagementForest%20%3D%20(%24RoleDatacenterIsManagementForest%20-eq%20%24true)%3B%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-60px%22%3Eif%20(%24RolePrepareAllDomains)%3CBR%20%2F%3E%7B%3CBR%20%2F%3Einitialize-DomainPermissions%20-AllDomains%3A%24true%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%3CBR%20%2F%3E%7D%3CBR%20%2F%3Eelseif%20(%24RoleDomain%20-ne%20%24null)%3CBR%20%2F%3E%7B%3CBR%20%2F%3Einitialize-DomainPermissions%20-Domain%20%24RoleDomain%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%3CBR%20%2F%3E%7D%3CBR%20%2F%3Eelse%3CBR%20%2F%3E%7B%3CBR%20%2F%3Einitialize-DomainPermissions%20-CreateTenantRoot%3A%24createTenantRoot%20-CreateMsoSyncRoot%3A%24createMsoSyncRoot%20-IsManagementForest%3A%24isManagementForest%3B%3CBR%20%2F%3E%7D%3CBR%20%2F%3E%E2%80%9C%20ausgef%C3%BChrt%20wurde%3A%20%E2%80%9ESystem.NullReferenceException%3A%20Der%20Objektverweis%20wurde%20nicht%20auf%20eine%20Objektinstanz%20festgelegt.%3CBR%20%2F%3Ebei%20Microsoft.Exchange.Management.Tasks.SetupTaskBase.LogReadObject(ADRawEntry%20obj)%3CBR%20%2F%3Ebei%20Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.InternalProcessRecord()%3CBR%20%2F%3Ebei%20Microsoft.Exchange.Configuration.Tasks.Task.b__91_1()%3CBR%20%2F%3Ebei%20Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String%20funcName%2C%20Action%20func%2C%20Boolean%20terminatePipelineIfFailed)%3CBR%20%2F%3Ebei%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage%20taskStage%2C%20Action%20initFunc%2C%20Action%20mainFunc%2C%20Action%20completeFunc)%3CBR%20%2F%3Ebei%20Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()%3CBR%20%2F%3Ebei%20System.Management.Automation.CommandProcessor.ProcessRecord()%E2%80%9C.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20I%20had%20not%20installed%20the%20CU20%20so%20far%2C%20I%20have%20of%20course%20tried%20to%20make%20the%20preparations%20for%20the%20CU20%2C%20this%20works%20fine.%3CBR%20%2F%3ECurrently%20I%20do%20not%20know%20where%20to%20start.%20Permissions%20are%20almost%20impossible%20(upgrade%20from%20CU19%20to%20CU20%20has%20just%20worked).%3C%2FP%3E%3CP%3EDoes%20anyone%20have%20any%20ideas%3F%3C%2FP%3E%3CP%3EThanks%20%26amp%3B%20greetings%3C%2FP%3E%3CP%3EMario%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2529530%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2529530%22%20slang%3D%22en-US%22%3E%3CP%3EA%20little%20heads%20up%20-%20we%20have%20currently%20a%20ticket%20opened%20with%20MS%20as%20we%20see%20MSSyncAppPool%20crashing%20around%20every%20hour%20with%205011%20WAS%20error%2C%20right%20after%20installing%20CU21%20over%20Exchange%202016%20CU20.%20Still%20working%20on%20the%20root%20cause%20and%20solution%20with%20MS.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2531863%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2531863%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20across%20the%20exact%20same%20issue%20last%20night%2C%20and%20this%20thread%20seems%20to%20be%20the%20only%20place%20where%20people%20discuss%20this%20error.%20My%20org%20is%20also%20English%2C%20so%20probably%20we%20can%20rule%20out%20the%20language%20part.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1096374%22%20target%3D%22_blank%22%3E%40GioVin%3C%2FA%3E%3A%20How%20is%20your%20support%20ticket%20holding%3F%20Did%20you%20got%20any%20useful%20tips%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2533251%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20June%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2533251%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRIKE%3EI%20had%20the%20same%20%2FprepareAD%20error.%26nbsp%3B%20I%20was%20able%20to%20fix%20it%20by%20opening%20ADSI%20edit%20on%20my%20DC%20%26amp%3B%20migrating%20to%26nbsp%3BCN%3DConfiguration%2CDC%3D%3CDOMAIN%3E%2CDC%3D%3CCOM%3E%2CCN%3DServices%2CCN%3DMicrosoft%20Exchange%2CCN%3D%3CORGANIZATIONAME%3E%2CCN%3DHybrid%20Configuration%20%26amp%3B%20changing%20the%20security%20profile%20on%20the%20CN%3DHybrid%20Configuration.%26nbsp%3B%20Went%20to%20properties%20%26amp%3B%20gave%20network%20service%2C%20exchange%20%26amp%3B%20all%20other%20keys%20FULL%20access.%26nbsp%3B%20I%20then%20ran%20%2FprepareAD%20and%20it%20completed%20successfully.%26nbsp%3B%3C%2FORGANIZATIONAME%3E%3C%2FCOM%3E%3C%2FDOMAIN%3E%3C%2FSTRIKE%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Jun 29 2021 07:50 AM
Updated by:
www.000webhost.com