部署軟體更新Deploy software updates

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

軟體更新部署階段是部署軟體更新的程序。The software update deployment phase is the process of deploying software updates. 無論您部署軟體更新的方式為何,站台都會:No matter how you deploy software updates, the site:

  • 將更新新增至軟體更新群組Adds the updates to a software update group
  • 將更新內容發佈至發佈點Distributes the update content to distribution points
  • 將更新群組部署至用戶端Deploys the update group to clients

在您建立部署之後,站台會將相關聯的軟體更新原則傳送至目標用戶端。After you create the deployment, the site sends an associated software update policy to targeted clients. 用戶端會從內容來源將軟體更新內容檔案下載到其本機快取。The clients download the software update content files from a content source to their local cache. 網際網路上的用戶端一律會從 Microsoft Update 雲端服務下載內容。Clients on the internet always download content from the Microsoft Update cloud service. 接著,這些軟體更新便可供用戶端安裝。The software updates are then available for installation by the client.

提示

若發佈點不可用,內部網路上的用戶端可以從 Microsoft Update 下載軟體更新。If a distribution point isn't available, clients on the intranet can also download software updates from Microsoft Update.

注意

軟體更新和其他部署類型不同,全都會下載至用戶端快取。Unlike other deployment types, software updates are all downloaded to the client cache. 無論用戶端上快取大小上限的設定為何。This is regardless of the maximum cache size setting on the client. 如需用戶端快取設定的詳細資訊,請參閱設定 Configuration Manager 用戶端的用戶端快取For more information about the client cache setting, see Configure the client cache for Configuration Manager clients.

如果您設定必要的軟體更新部署,就會在排程期限自動安裝軟體更新。If you configure a required software update deployment, the software updates are automatically installed at the scheduled deadline. 或者,用戶端電腦上的使用者可以在期限前排程或起始軟體更新安裝。Alternatively, the user on the client computer can schedule or initiate the software update installation prior to the deadline. 在嘗試安裝後,用戶端電腦會將狀態訊息傳回網站伺服器,回報軟體更新安裝是否成功。After the attempted installation, client computers send state messages back to the site server to report whether the software update installation was successful. 如需軟體更新部署的詳細資訊,請參閱 Software update deployment workflowsFor more information about software update deployments, see Software update deployment workflows.

軟體更新的部署共有三種主要案例:There are three main scenarios for deploying software updates:

通常,您一開始會手動部署軟體更新以建立用戶端的基準,然後使用自動部署或階段式部署來管理用戶端上的軟體更新。Typically, you start by manually deploying software updates to create a baseline for your clients, and then you manage software updates on clients by using an automatic or phased deployment.

注意

使用階段式部署時,您無法使用自動部署規則。You can't use an automatic deployment rule with a phased deployment.

手動部署軟體更新Manually deploy software updates

在 Configuration Manager 主控台中選取軟體更新,並手動開始部署程序。Select software updates in the Configuration Manager console and manually start the deployment process. 您通常會使用這種部署方法來:You typically use this method of deployment to:

  • 在建立管理每月部署的自動部署規則之前,以所需的軟體更新將用戶端更新為最新狀態Get clients up-to-date with required software updates before you create automatic deployment rules that manage monthly deployments

  • 部署頻外軟體更新Deploy out-of-band software updates

以下清單提供手動部署軟體更新的一般工作流程:The following list provides the general workflow for manual deployment of software updates:

  1. 篩選使用特定需求的軟體更新。Filter for software updates that use specific requirements. 例如,提供可擷取超過 50 個用戶端所需之所有安全性或重要軟體更新的準則。For example, provide criteria that retrieves all security or critical software updates that are required on more than 50 clients.

  2. 建立含有軟體更新的軟體更新群組。Create a software update group that contains the software updates.

  3. 在軟體更新群組中下載軟體更新的內容。Download the content for the software updates in the software update group.

  4. 手動部署軟體更新群組。Manually deploy the software update group.

如需詳細資訊和詳細步驟,請參閱手動部署軟體更新For more information and detailed steps, see Manually deploy software updates.

注意

  • 從 2020 年 4 月 21 日開始,「Office 365 專業增強版」會重新命名為「Microsoft 365 Apps 企業版」 。Starting on April 21, 2020, Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. 如需詳細資訊,請參閱 Office 365 專業增強版的名稱變更 (部分機器翻譯)。For more information, see Name change for Office 365 ProPlus. 在主控台正在進行更新時,您在 Configuration Manager 主控台與輔助文件中可能仍會看到提及舊名稱。You may still see references to the old name in the Configuration Manager console and supporting documentation while the console is being updated.
  • 手動部署 Microsoft 365 Apps 用戶端更新時,請在 [軟體程式庫] 工作區之 [Office 365 用戶端管理] 下方的 [Office 365 更新] 節點中加以尋找。When manually deploying Microsoft 365 Apps client updates, find them in the Office 365 Updates node under Office 365 Client Management of the Software Library workspace.

自動部署軟體更新Automatically deploy software updates

使用自動部署規則 (ADR) 來設定自動軟體更新部署。Configure automatic software updates deployment by using an automatic deployment rule (ADR). 這種部署方式是每月軟體更新 (一般稱為「週二修補程式日」) 和管理定義更新的常見方式。This method of deployment is common for monthly software updates (typically known as "Patch Tuesday") and for managing definition updates. 您可以定義 ADR 的準則以自動化部署程序。You define the criteria for an ADR to automate the deployment process. 以下清單提供自動部署軟體更新的一般工作流程:The following list provides the general workflow to automatically deploy software updates:

  1. 建立指定部署設定的 ADR。Create an ADR that specifies deployment settings.

  2. 站台會將軟體更新新增至軟體更新群組。The site adds the software updates to a software update group.

  3. 站台會將軟體更新群組部署至目標集合中的用戶端。The site deploys the software update group to the clients in the target collection.

首先,判斷您的自動軟體更新部署策略。First, determine your automatic software update deployment strategy. 例如,建立 ADR,以便一開始以測試用戶端集合為目標。For example, create the ADR to initially target a collection of test clients. 在您確認測試群組已成功安裝軟體更新之後,將新的部署新增至規則。After you verify the test group successfully installed the software updates, add a new deployment to the rule. 您也可以將現有部署中的目標集合變更為包含更多用戶端的集合。You could also change the targeted collection in the existing deployment to one that includes a larger set of clients. 決定要使用的策略時,請考量下列行為:Consider the following behaviors when deciding upon the strategy to use:

  • 您能夠修改 ADR 所建立之軟體更新物件的內容。You're able to modify the properties of the software update objects that the ADR creates.

  • 當您將軟體更新新增至目標集合時,ADR 會自動將它們部署到用戶端。The ADR automatically deploys software updates to clients when you add them to the target collection.

  • 當您或 ADR 將新的軟體更新新增至軟體更新群組時,站台會自動將它們部署到目標集合中的用戶端。When you or the ADR adds new software updates to the software update group, the site automatically deploys them to the clients in the target collection.

  • 隨時啟用或停用 ADR 的部署。Enable or disable deployments at any time for the ADR.

建立 ADR 之後,請將其他部署新增至規則中。After you create an ADR, add additional deployments to the rule. 此動作可協助您管理將不同更新部署到不同集合的複雜性。This action helps you manage the complexity of deploying different updates to different collections. 每個新部署都會有完整的功能和部署監視體驗。Each new deployment has the full range of functionality and deployment monitoring experience.

您新增的每個新部署:Each new deployment that you add:

  • 使用 ADR 第一次執行時所建立的相同更新群組和套件Uses the same update group and package, which the ADR creates when it first runs
  • 能夠以不同集合為目標Can target a different collection
  • 支援獨特的部署內容,包括:Supports unique deployment properties including:
    • 啟用時間Activation time
    • 期限Deadline
    • 使用者經驗User experience
    • 分隔每個部署的警示Separate alerts for each deployment

如需詳細資訊和詳細步驟,請參閱自動部署軟體更新For more information and detailed steps, see Automatically deploy software updates

分階段進行部署軟體更新Deploy software updates in phases

從 1810 版開始,您可以建立軟體更新的階段式部署。Starting in version 1810, create phased deployments for software updates. 階段式部署可讓您根據可自訂的準則與群組,以組織協調且循序的軟體推出。Phased deployments allow you to orchestrate a coordinated, sequenced rollout of software based on customizable criteria and groups.

如需詳細資訊,請參閱建立階段式部署For more information, see Create phased deployments.