Configuration Manager Current Branch 2103 向けロールアップ リリース (KB10036164)

皆さん、こんにちは。

今回は、Microsoft Endpoint Configuration Manager (MECM, SCCM, Configuration Manager) Current Branch 2103 向けの更新プログラム (ロールアップ) について紹介したいと思います。

Configuration Manager CB 2103 向けのロールアップは初めてのリリースです。時期的には、CB 2107 のリリースされる頃ですね。

ロールアップのため、複数の問題事象を修正した修正プログラムとなります。

<ロールアップ (修正プログラム) の詳細>

KB10036164 (https://aka.ms/KB10036164)

  • Deployment of an operating system image may fail under the following conditions:
    • The image is deployed using standalone media, such as a USB drive.
    • The computer restarts between two Install Application task sequence steps.
    • The first Install Application task sequence step does not have the Continue on error option enabled.

When this issue occurs, errors resembling the following are recorded in the smsts.log.

	App install failed.
	...
	Install application action failed: '{*application_name*}'. Error Code 0x80004005
	Sending error status message
	The client GUID must be set in an environment variable.
	GetClientIDs() failed. 80004005
	GetClientIDs (sClientIdentity, sClientGUID_Ext), HRESULT=80004005
	Non fatal error 0x80004005 in sending task sequence execution status message to Management Point
	Install application action cannot continue. ContinueOnErrorFlag is set to false.
	Install Static Applications failed, hr=0x80004005
	Process completed with exit code 2147500037
	Failed to run the action: Install Application. Error -2147467259
  • Applications don’t upgrade as expected under the following conditions:
    • App1 is deployed and installed for User1.
    • The deployment of App2 supersedes App1, and the option Automatically upgrade any superseded versions of this application is enabled.
    • User2 logs in to the same computer. When these conditions occur, App2 doesn’t automatically replace App1 as expected.
  • The Install Package task sequence step repeats indefinitely under the following conditions:
    • Packages defined with the Set Dynamic Variables task are used as part of the Install Package task sequence step.
    • The same program is called more than once, and that program returns a pending reboot exit code of 3010.
    • The computer is rebooted after the second run of the program that returns the 3010 exit code.
  • The Import-CMQuery PowerShell cmdlet fails with a MOF compilation error after updating to Configuration Manager version 2103.
  • Selecting the Task Sequences node after selecting the References tab in deployment details causes the console to terminate unexpectedly.
  • Content for Microsoft updates fails to download if an Alternate Content Provider (ACP) is in use, and the client switches to a different network during the download process. An error resembling the following is recorded in the ctm.log file.
    CTM job {GUID} encountered error 0x80070057 during download ('Sccm Client is IBCM')- The error is non retriable.
    CTM encountered error processing reply from DTS. Code 0x80004004
    
  • Client installation from a cloud management gateway (CMG) fails if the client is unable to contact the internal management point. The ccmsetup.log file contains an error resembling the following.
    Failed to correctly receive a WEBDAV HTTPS request.. (StatusCode at WinHttpQueryHeaders: 405)
    
  • Applications do not appear as expected in Software Center if there is a single quotation mark in the Keywords field of the application’s properties. The cidownloader.log and cistore.log files contain errors resembling the following.
    m_spCIStore->StoreCI(spIEnum), HRESULT=87d00215
    CCIStore::GetCIEx - Requested CI ModelName ScopeId_{GUID}/Application_{GUID}, Version 25 not found in [Store] (0x87d00215).
    
  • Task sequences that run with the Run as high performance power plan option enabled due not revert to the previously defined power plan when complete.
  • If a required scheduled task sequence attempts to run during an in-place upgrade, and the client is in provisioning mode, the scheduled task sequence and the upgrade fail. This happens because the scheduled task sequence fails when the client is in provisioning mode, then cleans up the task sequence environment. This, in turn, causes the in-place upgrade to fail. The smsts.log contains errors resembling the following.
    Install Software failed to run command line, hr=0x80070002
    Process completed with exit code 2147942402
    Failed to run the action: Collect Post-Upgrade Computer Data. Error -2147024894
    Management Point name must be set in an environment variable
    
  • The Apply Operating System task fails if you set the option Logical drive letter stored in a variable under the Destination field to the variable _OSDDetectedWinDrive. The variable incorrectly adds a backslash character to the drive letter, causing later operations to fail. Errors resembling the following are recorded in the smsts.log file.
    Set command line: "OSDApplyOS.exe" /image:PRI00001,1 /target:C:\ /runfromnet:False
    ...
    CDisk::IsLocalHardDrive(volume), HRESULT=80070057
    The drive letter 125 does not correspond to a local hard drive.
    The requested target could not be resolved to a valid volume on this computer. Check your task sequence to ensure this drive is correct and that it is being created
    The parameter is incorrect. (Error: 80070057; Source: Windows)
    Process completed with exit code 2147942487
    Failed to run the action: Apply Operating System. Error -2147024809
    ...
    The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed. Error 0x80004004
    Failed to run the last action: Apply Operating System. Result -2147024809. Execution of task sequence failed.
    
  • The deployment of an operating system using boot media over a cloud management gateway may fail if the management point is configured for Internet-only communication. Errors resembling the following are recorded in the TSMBootstrap.log file.
    Error. Status code 500 - (CMGConnector_InternalServerError) returned
    RequestMPKeyInformation: Send() failed.
    MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80004005
    Failed to get information for MP
    
  • The SMS Executive Service (smsexec.exe) terminates unexpectedly under either of the following conditions.
    • If a request timeout occurs during the Azure Active Directory group discovery process.
    • During rule processing if an automatic deployment rule (ADR) contains fewer than two rule actions.
  • A task sequence may fail to complete if the content location lookup returns 0x8000000a (E_PENDING). The CcmMessaging.log and smsts.log contain errors resembling the following.
     CCMMessaging: 
     _TranslateAddress(msgHeader, &bLocalEndpoint, sTargetEndpoint), HRESULT=8000000a
     CForwarder_Base::Send failed (0x8000000a).
    
     smsts:
     CAppMgmtSDK::GetEvaluationState <applicationID> = DownloadFailed
     Installation job completed with exit code 0x00000000
     Execution status received: 24 (Application download failed )
     App install failed.
     ...
     Install application action failed: 'Application name'. Error Code 0x80004005

※ このロールアップには、KB9603111 および KB9833643 が含まれます。

<修正プログラムのインストール>

対象環境の Configuration Manager コンソールには、下記のように、KB10036164 が表示されます。上記に記載されている不具合を修正するプログラムなので、早期にアップデートすることをお勧めいたします。

シェアする

  • このエントリーをはてなブックマークに追加

フォローする