Hallo Applikationsverantwortliche,

es ist soweit, die Juni-Updates für Exchange Server wurden veröffentlicht. Mit dabei sind die CUs für Exchange 2013 und Exchange 2016 sowie ein UR für Exchange Server 2010.

 

.NET Framework 4.7.1

Wie bereits angekündigt ist .Net Framework 4.7.1 nun Pflicht für die Installation von Exchange Server 2013 CU 21 und Exchange Server 2016 CU 10.

VC++ 2013 runtime library is required

The Exchange Server updates released today require the VC++ 2013 runtime library installed on the server. The VC++ runtime library is required to provide current and future security updates for a third party component shipped with Exchange Server. The component provides WebReady Document Viewing in Exchange Server 2010 and 2013 and Data Loss Prevention in Exchange Server 2013 and 2016. Setup will enforce the installation of the pre-requisite on Exchange Server 2013 and 2016 when a cumulative update is applied. Exchange Server 2010 Update Rollup 22 and later will force the installation of the VC++ runtime before the update can be applied. Future security updates for all versions of Exchange Server will force installation of the runtime package if not already installed. Customers who use Windows Update to patch or update their servers, will need to ensure that the VC++ 2013 runtime package is applied before running Windows Update. Update Rollup 22 and future security updates for all versions of Exchange server will fail to install manually or via Windows Update if the runtime library is not installed.

 

Exchange Server 2010

Mit der Veröffentlichung von Exchange Server 2010 SP3 Update Rollup wird nun auch Windows Server 2016 Domänencontroller unterstützt. Somit wird nicht nur die Betriebssystemversion von AD-DCs unter Server 2016 unterstützt, sondern tatsächlich auch FFL und DFL 2016.

Die eingesetzten Windows Server 2016 müssen mindestens das Juni 2018-Update installiert haben, um als DCs für Exchange 2010 verwendet werden zu können.

Active Directory Schema

Keines der März-Updates enthält Aktualisierungen für das Schema seit den September-Updates 2017.

Exchange Server 2016 CU10 – behobenen Probleme

  • 4056609 Event ID 4999 and mailbox transport delivery service won’t start with Exchange Server 2016 CU7 installed
  • 4133605 Cmdlets to create or modify a remote shared mailbox in an on-premises Exchange environment
  • 4133620 „HTTP 500 due to ADReferralException“ error when a user tries to view detail properties of mailboxes in a child domain in Exchange Server
  • 4095974 „System.InvalidOperationException“ occurs when the „Enable-MailPublicFolder“ cmdlet is run against a public folder in Exchange Server
  • 4095973 Set-ServerComponentState cmdlet does not honor the write scope defined in the RBAC management scope in Exchange Server
  • 4095993 HTTP 500 error when an administrator tries to manage regional settings in ECP on Windows Server 2016
  • 4294209 Cannot clear the “Maximum message size” check box for Send messages or Receive messages in EAC in Exchange Server 2016
  • 4294208 „TooManyObjectsOpenedException“ error when you run the „Get-PublicFolderMailboxDiagnostics“ cmdlet in Exchange Server
  • 4294212 Cannot send VBScript-created messages in the Outlook 2016 client
  • 4294211 Cannot run “Set-CalendarProcessing” cmdlets after you apply CU8 or CU9 for Exchange Server 2016
  • 4294210 Cannot edit an email attachment in OWA in an Exchange Server 2016 environment
  • 4294204 Changing „IsOutOfService“ to „False“ in an earlier Exchange Server version does not immediately update in a later Exchange Server environment
  • 4092041 Description of the security update for Microsoft Exchange Server 2013 and 2016: May 8, 2018

Exchange Server 2013 CU21 – behobene Probleme

  • 4133605 Cmdlets to create or modify a remote shared mailbox in an on-premises Exchange environment
  • 4133604 User can’t log on to a POP/IMAP account by using NTLM authentication in Exchange Server 2013
  • 4133618 Unexpected error occurs when running the Get-DatabaseAvailabilityGroupNetwork cmdlet in Exchange Server 2013
  • 4133620 “HTTP 500 due to ADReferralException” when a user tries to view detail properties of mailboxes in a child domain in Exchange Server
  • 4058473 An Office 365 primary mailbox user cannot be assigned full access permissions for an on-premises mailbox in Exchange Server
  • 4094167 The MSExchangeRPC service crashes with a System.NullReferenceException exception in Exchange Server 2013
  • 4095974 “System.InvalidOperationException” occurs when the „Enable-MailPublicFolder“ cmdlet is run against a public folder in Exchange Server
  • 4092041 Description of the security update for Microsoft Exchange Server 2013 and 2016: May 8, 2018
  • 4294205 POP3 services intermittently stop in an Exchange Server 2013 environment
  • 4294204 Changing „IsOutOfService“ to „False“ in an earlier Exchange Server version does not immediately update in a later Exchange Server environment

Exchange Server 2010 UR22 – behobene Probleme

  • 4295751 EWS impersonation not working when accessing resource mailboxes in a different site in Exchange Server 2010 SP3

 

Viel Erfolg beim Updaten!

 

Andi