System Center 2019 UR2

Ein neues Update Rollup für System Center 2019 ist verfügbar: System Center 2019 UR2

Folgende Produkte erhalten damit ein Update:

  • Data Protection Manager
  • Operations Manager
  • Orchestrator
  • Service Manager
  • Virtual Machine Manager

Details: https://support.microsoft.com/en-us/help/4569535/update-rollup-2-for-system-center-2019

Nachfolgend wieder detaillierter die für diesen Blog relevanten Produkte SCSM und SCO aufgeführt. Neue Funktionen gibt es, wie leider immer in den letzten URs, nicht. Dafür aber einige wichtige Bug Fixes, die auch Benutzern das Leben leichter machen.

Für System Center Service Manager SCSM (Zitat, Details hier: https://support.microsoft.com/en-in/help/4558753/update-rollup-2-for-system-center-service-manager-2019 ):

  • Whenever a customer deletes service offering category, it will check if there are SO’s on that category and prevent the category deletion. It will show an alert on console to delete the SO if they want to delete the category.
  • Surface devices imported by SCCM connector will not be marked as virtual machines.
  • End user will still be able to update his other requests even if he is removed as an affected user from one of his requests through Self Service Portal.
  • Users will be able to scroll properly on all standard forms under work items tab.
  • Made enhancements to the start-up time of the SDK service.
  • When a user opens manual activity from any IR/CR and execute custom task, it will execute without any error.
  • Each Portal Trace log now shows thread ID, Process ID, Date and Time in UTC.
  • Service Manager supports SCCM from 1806 to 2002. However, it is recommended to follow the steps in “After the Installation”.
  • Enables support for the MSOLEDBSQL driver so that users can move from SQL Native Client. Manual steps are required to use the MSOLEDBSQL driver together with SQL Server Analysis Server (SSAS). See the next section “Steps to change provider in SQL Server Analysis Server”.

Korrekturen für System Center Orchestrator SCO (Zitat, Details hier: https://support.microsoft.com/en-in/help/4569536/update-rollup-2-for-system-center-2019-orchestrator)

  • Map Published Data activity fails when the source data contains special XML characters.
  • GP Encrypt and Decrypt file activities fail when using new GnuPG versions.
  • Web Service throws InvalidOperationException when Runbook Parameter ID is in upper case.
  • SCO Audit trail does not log any information even when auditing has been enabled.
  • Improvement: Data encryption in the DB now supports AES_256 Encryption algorithm.

Tags

Starten Sie jetzt Ihren Weg zu Azure!

Los geht's

top