佈建模式Provisioning mode

適用於: Configuration Manager (最新分支)Applies to: Configuration Manager (current branch)

在 OS 部署工作順序期間,Configuration Manager 會將用戶端置於佈建模式中。During an OS deployment task sequence, Configuration Manager places the client in provisioning mode. (作業系統部署工作順序包含就地升級至 Windows 10。)在此狀態下,用戶端不會處理來自站台的原則。(An OS deployment task sequence includes in-place upgrade to Windows 10.) In this state, the client doesn't process policy from the site. 此行為可讓工作順序執行,而不需擔負在用戶端上執行其他部署的風險。This behavior allows the task sequence to run without risk of additional deployments running on the client. 當工作順序完成時,不論成功還是處理失敗,它都會結束用戶端佈建模式。When the task sequence completes, either success or handled failure, it exits client provisioning mode.

如果工作順序意外失敗,則用戶端會保持於佈建模式中。If the task sequence unexpectedly fails, the client can be left in provisioning mode. 例如,如果在工作順序處理中間重新啟動裝置,它便無法復原。For example, if the device restarts in the middle of task sequence processing, and it's unable to recover. 系統管理員必須手動找出並修正處於此狀態的用戶端。An administrator must manually identify and fix clients in this state.

手動移除佈建模式Manually remove provisioning mode

如果用戶端留在佈建模式中,請使用此手動程序讓用戶端返回正常作業。If a client is left in provisioning mode, use this manual process to return the client to normal operation.

Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false

重要

此 WMI 方法所進行變更的其中之一是設定登錄值,但它也會進行其他變更。One of the changes made by this WMI method is setting a registry value, but it makes other changes as well. 只變更登錄值不能讓用戶端完全退出佈建模式。Just changing the registry value doesn't fully take the client out of provisioning mode. 如果您手動編輯登錄,用戶端可能會出現非預期的行為。If you manually edit the registry, the client may exhibit unexpected behaviors.

用戶端佈建模式逾時Client provisioning mode timeout

從 1902 版開始,工作順序會在將用戶端置於佈建模式時,設定時間戳記。Starting in version 1902, the task sequence sets a timestamp when it puts the client in provisioning mode. 每隔 60 分鐘,處於佈建模式之用戶端會檢查自時間戳記以來的持續時間。Every 60 minutes, a client in provisioning mode checks the duration of time since the timestamp. 如果它處於佈建模式的時間已超過 48 小時,用戶端會自動結束佈建模式,並重新啟動其程序。If it's been in provisioning mode for more than 48 hours, the client automatically exits provisioning mode and restarts its process.

佈建模式的逾時值預設為 48 小時。48 hours is the default provisioning mode timeout value. 您可以調整裝置上的這個計時器,方法是在下列登錄機碼中設定 ProvisioningMaxMinutes 值:HKLM\Software\Microsoft\CCM\CcmExecYou can adjust this timer on a device by setting the ProvisioningMaxMinutes value in the following registry key: HKLM\Software\Microsoft\CCM\CcmExec. 如果此值不存在或為 0,則用戶端會使用預設的 48 小時。If this value doesn't exist or is 0, the client uses the default 48 hours.

時間戳記 ProvisioningEnabledTime 位於下列登錄機碼中:HKLM\Software\Microsoft\CCM\CcmExecThe timestamp ProvisioningEnabledTime is located in the following registry key: HKLM\Software\Microsoft\CCM\CcmExec. 時間戳記的值提供電腦上次進入佈建模式的時間。The timestamp has a value of the last time the machine entered provisioning mode. 該值的格式為 Epoch (Unix 時間戳記) 及 UTC。The format is epoch (Unix timestamp) and is in UTC.

當您使用下列命令,手動讓電腦進入佈建模式,此時間戳記也會重設成目前的時間:This timestamp is also reset to the current time when you manually place the machine in provisioning mode by using the following command:

Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $true

程序流程圖Process flow diagrams

這些圖表會顯示工作順序和用戶端的程序流程。These diagrams show the process flow for the task sequence and the client.

工作順序Task sequence

下圖顯示工作順序設定佈建模式的方式:The following diagram shows how the task sequence sets provisioning mode:

工作順序設定佈建模式的流程圖

用戶端補救Client remediation

下圖顯示用戶端結束佈建模式的方式:The following diagram shows how the client exits provisioning mode:

用戶端結束佈建模式的流程圖

請參閱See also

varnameSetup Windows and ConfigMgr

升級作業系統Upgrade Operating System