皆さん、こんにちは。
今回は、Microsoft Endpoint Configuration Manager (MECM, SCCM, Configuration Manager) Current Branch 2107 向けの初めてのロールアップ リリースについてお伝えします。このロールアップは、early update ring (PowerShell のスクリプトを実行して早期に CB 2107 を適用した方) だけではなく、通常の方法で CB 2107 へアップグレードされた方も対象です。
<修正プログラムの詳細>
KB11121541 (https://aka.ms/KB11121541)
- After upgrading to version 2107, one or more applications in a task sequence fail with an error resembling the following in the
smsts.log
.Install Static Applications failed, hr=0x87d00267
- Offline Servicing for Windows Server 2022 operating system image fails to detect updates as applicable.
- The Installation Status tab in Software Center hangs without loading completely. When this issue occurs, errors resembling the following are repeated in the
scclient.log
.Getting all instances of CCM_Application Getting all instances of CCM_Program Getting all instances of CCM_SoftwareUpdate
- The CMTrace log file viewer does not display all characters at the beginning of a line.
- Syntax highlighting for PowerShell ignores the back quote escape character (`) when escaping double quotation marks.
- The site server may stop processing state messages, resulting in a backlog of files, due to a primary key constraint violation. Errors resembling the following are recorded in the
statesys.log
file.SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 2627 at record 100 for TopicType 500, StateID 1: "Violation of PRIMARY KEY constraint 'SR_MissingMessageRanges_PK'. Cannot insert duplicate key in object 'dbo.SR_MissingMessageRanges'. The duplicate key value is (123456, 112233).", Line 0 in procedure ""
- A console extension may fail to import with an error resembling the following recorded in the
AdminUI.ExtensionInstaller.log
file.Return code indicates unhandled case. Result: Exception of type 'System.OutOfMemoryException' was thrown.
- The Configuration Manager console generates an exception when selecting View Collection from the Collections tab in the Devices node. The exception contains information resembling the following.
The requested object information could not be retrieved. Refresh the Configuration Manager console to verify that another administrator has not moved or deleted the object, or that the role-based administration security scopes or security roles for the object or current user have not changed. ConfigMgr Error Object: instance of __ExtendedStatus { Operation = "GetObject"; ParameterInfo = "SMS_DeviceCollectionMember.SiteID=\"{Site_ID}\""; ProviderName = "WinMgmt"; }; Error Code: NotFound
- The Configuration Manager client is blocked from sending endpoint analytics sensor events to the management point. This happens when there are backlogs in the CCM_SensorMessageQueue in WMI. Errors resembling the following are recorded in the
SensorEndpoint.log
file.Invoke SensorWmiProvider succeeded. QueryTraceW returned=234 for SensorFramework-Live-Etw... Failed to get the next message to send. 0x80041032
- The Configuration Manager console terminates unexpectedly if a Reporting Services Point is installed while the SQL Server Reporting Services (SSRS) service is stopped. The
AdminUI.log
file contains errors resembling the following.System.ArgumentException Version string portion was too short or too long.
- The Configuration Manager Support Center Client Tools application terminates unexpectedly on a Windows 11 computer selecting different deployments.
- The Cloud Management Gateway Azure Storage Account can now be configured to use TLS 1.2 through the Configuration Manager console. For more information, see Enforce TLS 1.2.
- Improvements to the Data Warehouse synchronization process are included to prevent the SQL Server TempDB from filling up.
- Endpoint analytics sensor data now includes the system SKU and processor name, and Microsoft Surface Model information, for Windows 11 hardware readiness.
- The cloud service configuration file (.csfg) is not updated after deploying a cloud management gateway. Errors resembling the following are recorded in the
CloudMgr.log
file.ERROR: TaskManager: Task [UpdateServiceConfigurationTask: Service {ID}] has failed. Exception Hyak.Common.CloudException, ChangeDeploymentConfigurationOperationFailed: The Change Deployment Configuration operation failed for the domain '{ID}' in the deployment slot 'Production' with the name '{ID}-deployment': 'The specified configuration settings for Settings are invalid. Verify that the service configuration file is a valid XML file, and that role instance counts are specified as positive integers.'..~~
- Incremental collection updates don’t work when the WQL statements contain custom properties.
- In some scenarios the maximum client policy size is incorrectly limited to 16MB instead of 32MB. This results in errors resembling the following in the
smsts.log
file.Request was successful. dwBodyLength <= m_nMaxReplySize, HRESULT=80004005 reply message body length is too long (18291682, 16777216)
- The BitLocker recovery key is only escrowed for the first user on a computer instead of all users that log on.
- Clients fail to download content from a peer cache source under the following conditions:
- The content is deleted from a distribution point but remains in the peer cache.
- The client is on a low bandwidth connection that causes the BITS download job to take over 24 hours to complete.
- The device collection is unexpectedly empty when selected from the device graph on the Windows 10 dashboard.
- The list of BitLocker recovery keys is blank for Azure Active Directory-joined devices.
※ このロールアップに、KB10503003 の内容も含まれます。
<既知の問題>
Azure Monitor 機能の Log Analytics コネクタが Configuration Manager バージョン 2107 から削除されました。 ただし、管理者が OMS コネクタを表示および削除できるページは存在しますが、機能しません。
Configuration Manager を Azure Monitor に接続する – Azure Monitor | Microsoft Docs
<ロールアップのインストール>
対象環境の Configuration Manager コンソールには、下記のように、KB11121541 が表示されます。上記に記載されている不具合を修正するプログラムなので、早期にアップデートすることをお勧めいたします。