部署任务序列Deploy a task sequence

适用范围:Configuration Manager (Current Branch)Applies to: Configuration Manager (current branch)

创建任务序列并分发引用的内容后,将其部署到设备集合。After you create a task sequence, and distribute the referenced content, deploy it to a device collection. 使用此操作可以在设备上运行任务序列。This action allows the task sequence to run on a device. 经过部署的任务序列可以自动运行,也可以在由设备的用户安装时运行。A deployed task sequence can run automatically, or when installed by a user of the device.

警告

你可以管理高风险任务序列部署的行为。You can manage the behavior for high-risk task sequence deployments. 高风险部署是自动安装、可能产生意外结果的部署。A high-risk deployment is a deployment that is automatically installed and has the potential to cause unwanted results. 例如,部署目的为“必需”且部署 OS 的任务序列被认为是高风险部署。For example, a task sequence that has a purpose of Required that deploys an OS is considered a high-risk deployment. 有关详细信息,请参阅用于管理高风险部署的设置For more information, see Settings to manage high-risk deployments.

过程Process

使用以下过程将任务序列部署到集合中的计算机。Use the following procedure to deploy a task sequence to the computers in a collection.

备注

任务序列部署的状态消息显示在主站点上的“消息”窗口中,但不会显示在管理中心站点上。The status messages for the task sequence deployment are displayed in the message window on a primary site, but they aren't displayed on a central administration site.

  1. 在 Configuration Manager 控制台中,转到“软件库”工作区,展开“操作系统”,然后选择“任务序列”节点。In the Configuration Manager console, go to the Software Library workspace, expand Operating Systems, and then select the Task Sequences node.

  2. 在“任务序列”列表中,选择要部署的任务序列。In the Task Sequence list, select the task sequence that you want to deploy.

  3. 在功能区的“主页”选项卡上,在“部署”组中,选择“部署”。On the Home tab of the ribbon, in the Deployment group, select Deploy.

    备注

    如果“部署”不可用,则任务序列会有无效的引用。If Deploy isn't available, the task sequence has a reference that's not valid. 纠正该引用,然后再次尝试部署任务序列。Correct the reference and then try to deploy the task sequence again.

  4. 在“常规”页面上,指定以下信息。On the General page, specify the following information.

    • 任务序列:指定要部署的任务序列。Task sequence: Specify the task sequence to deploy. 默认情况下,此框显示所选的任务序列。By default, this box displays the selected task sequence.

    • 集合:选择包含要运行任务序列的计算机的集合。Collection: Select the collection that contains the computers to run the task sequence.

      不要部署将 OS 安装到不适合的集合(例如所有数据中心服务器集合)的任务序列。Don't deploy a task sequence that installs an OS to inappropriate collections, such as a collection of all your data center servers. 请确保所选集合仅包含要运行任务序列的那些计算机。Be sure that the selected collection contains only those computers that you want to run the task sequence.

      有关高风险部署的详细信息,请参阅高风险部署For more information about high-risk deployments, see High-risk deployments.

    • 使用与此集合关联的默认分发点组:将任务序列内容存储在集合默认分发点组上。Use default distribution point groups associated to this collection: Store the task sequence content on the collection's default distribution point group. 如果未将所选集合与分发点组关联,则此选项为灰色。If you haven't associated the selected collection with a distribution point group, this option is grayed out.

    • 为依赖关系自动分发内容:如果任何引用的内容具有依赖项,则该站点也会将从属内容发送到分发点。Automatically distribute content for dependencies: If any referenced content has dependencies, then the site also sends dependent content to distribution points.

    • 此任务序列的预下载内容:有关详细信息,请参阅配置预缓存内容Pre-download content for this task sequence: For more information, see Configure pre-cache content.

    • 选择部署模板:为任务序列保存和指定部署模板。Select Deployment Template: Save and specify a deployment template for a task sequence.

      重要

      某些项目未保存在模板中。Some items aren't saved in the template. 确保在运行部署向导时应用以下各项:Make sure you apply the following items when you run the deployment wizard:

      • 软件安装Software Installation
      • 计划Scheduling
      • 预下载内容Pre-download content
    • 备注(可选) :指定描述此任务序列部署的其他信息。Comments (optional): Specify additional information that describes this deployment of the task sequence.

  5. 在“部署设置”页上,指定以下信息:On the Deployment Settings page, specify the following information:

    • 目的:从下拉列表中,选择下列选项之一:Purpose: From the drop-down list, choose one of the following options:

      • 可用:用户会在软件中心看到该任务序列,并可根据需要进行安装。Available: The user sees the task sequence in Software Center and can install it on demand.

      • 必需:Configuration Manager 将自动根据配置计划自动运行任务序列。Required: Configuration Manager automatically runs the task sequence according to the configured schedule. 如果任务序列未隐藏,则用户仍可以跟踪其部署状态。If the task sequence isn't hidden, a user can still track its deployment status. 在截止时间之前,用户还可通过软件中心安装任务序列。They can also use Software Center to install the task sequence before the deadline.

      备注

      如果多个用户登录设备,软件中心内可能无法显示包和任务序列部署。If multiple users are signed into the device, package and task sequence deployments may not appear in Software Center.

    • 可用于以下项目:指定任务序列是否可用于以下任一类型:Make available to the following: Specify whether the task sequence is available to one of the following types:

      • 仅 Configuration Manager 客户端Only Configuration Manager clients
      • Configuration Manager 客户端、媒体和 PXEConfiguration Manager clients, media, and PXE
      • 仅媒体和 PXEOnly media and PXE
      • 仅媒体和 PXE(隐藏)Only media and PXE (hidden)

      重要

      将“仅媒体和 PXE (隐藏)”设置用于自动化任务序列部署。Use the Only media and PXE (hidden) setting for automated task sequence deployments. 要让计算机在无用户干预的情况下自动启动到该部署,请选择“允许无人参与的操作系统部署”,并将 SMSTSPreferredAdvertID 变量设置为媒体的一部分。To have the computer automatically boot to the deployment with no user interaction, select Allow unattended operating system deployment and set the SMSTSPreferredAdvertID variable as part of the media. 有关任务序列变量的详细信息,请参阅任务序列变量For more information about task sequence variables, see Task sequence variables.

    • 发送唤醒数据包:如果部署为“必需”并选择此选项,则在客户端运行部署前,该站点会将唤醒数据包发送到计算机。Send wake-up packets: If the deployment is Required and you select this option, the site sends a wake-up packet to computers before the client runs the deployment. 此数据包可在到达安装截止时间时将计算机从休眠中唤醒。This packet wakes the computer from sleep at the installation deadline time. 使用此选项前,必须针对“LAN 唤醒”配置计算机和网络。Before using this option, computers and networks must be configured for Wake On LAN. 有关详细信息,请参阅计划如何唤醒客户端For more information, see Plan how to wake up clients.

    • 允许客户端使用按流量计费的 Internet 连接在安装截止时间之后下载内容,这可能会导致附加成本:此选项仅适用于所需部署。Allow clients on a metered Internet connection to download content after the installation deadline, which might incur additional costs: This option is only available for Required deployments. 如果你的自定义任务序列安装应用程序但不部署 OS,则可以指定是否允许客户端在安装截止日期之后下载内容(如果客户端使用按流量计费的 Internet 连接)。When you have a custom task sequence that installs an application but doesn't deploy an OS, you can specify whether to allow clients to download content after an installation deadline when they use metered internet connections. Internet 提供商有时根据你在按流量计费的 Internet 连接上使用的数据量计费。Internet providers sometimes charge by the amount of data that you use when you're on a metered internet connection.

      备注

      虽然使用按流量计费的 Internet 连接可能对不部署 OS 的任务序列有效,但不支持这种连接。While using a metered internet connection might work for task sequences that don't deploy an OS, it's not supported.

  6. 在“计划”页上,指定以下信息:On the Scheduling page, specify the following information:

    重要

    Windows PE 客户端从 PXE 或启动媒体启动时,客户端不会评估部署计划。When a Windows PE client starts from PXE or boot media, the client doesn't evaluate deployment schedules. 这些计划包括启动、过期,和截止时间。These schedules include start, expire, and deadline times. 仅部署从完整的 Windows OS 启动的客户端部署中的计划。Only configure schedules in deployments to clients that start from the full Windows OS. 请考虑使用其他方法(例如维护窗口)来控制部署到从 Windows PE 启动的客户端的活动任务序列。Consider using other methods, such as maintenance windows, to control active task sequences deployed to clients that start from Windows PE.

    • 计划此部署将在何时变为可用:指定任务序列可以在目标计算机上运行的日期和时间。Schedule when this deployment will become available: Specify the date and time when the task sequence is available to run on the destination computer. 选择“UTC”选项后,任务序列可同时用于多台计算机。When you select the UTC option, the task sequence is available for multiple computers at the same time. 否则,根据每台计算机的本地时间,部署可以在不同时间使用。Otherwise the deployment is available at different times, according to the local time on each computer.

      如果启动时间早于所需时间,则客户端会在启动时间下载任务序列内容。If the start time is earlier than the required time, the client downloads the task sequence content at the start time.

    • 计划此部署将在何时过期:指定任务序列在目标计算机上过期的日期和时间。Schedule when this deployment will expire: Specify the date and time when the task sequence expires on the destination computer. 选择“UTC”选项后,任务序列会同时在多台目标计算机上过期。When you select the UTC option, the task sequence expires on multiple destination computers at the same time. 否则,根据每台计算机的本地时间,部署会在不同时间过期。Otherwise the deployment expires at different times, according to the local time on each computer.

    • 分配计划:对于“必需”部署,请指定客户端何时运行任务序列。Assignment schedule: For a Required deployment, specify when the client runs the task sequence. 你可以添加多个计划。You can add multiple schedules. 分配计划可以具有以下配置之一:The assignment schedule can have one of the following configurations:

      • 特定日期和时间A specific date and time
      • 每月、每周,或自定义的定期模式Monthly, weekly, or custom recurrence pattern
      • 尽快As soon as possible
      • 登录或注销事件Log on or log off events

      备注

      如果为必需部署计划一个启动时间,该时间要早于任务序列可用的日期和时间,Configuration Manager 会在指定的启动时间内下载内容。If you schedule a start time for a required deployment that's earlier than the date and time when the task sequence is available, the Configuration Manager client downloads the content at the assigned start time. 即使计划在以后提供任务序列,也会发生此行为。This behavior occurs even though you scheduled the task sequence to be available at a later time.

    • 重新运行行为:指定重新运行任务序列的时间。Rerun behavior: Specify when the task sequence reruns. 选择下列选项之一:Select one of the following options:

      • 从不重新运行已部署的程序:如果客户端之前已运行了任务序列,则它不会重新运行。Never rerun deployed program: If the client has previously run the task sequence, it doesn't rerun. 即使任务序列最初失败或者任务序列文件已更改,此任务序列也不会重新运行。The task sequence doesn't rerun even if it originally failed or the task sequence files have changed.

      • 始终重新运行程序:计划部署时,任务序列始终在客户端上重新运行。Always rerun program: The task sequence always reruns on the client when the deployment is scheduled. 即使已成功运行,任务序列也将重新运行。It reruns even if the task sequence has already run successfully. 如果使用在其中例行更新任务序列的定期部署,则此设置非常有用。This setting is useful when you use recurring deployments in which the task sequence is routinely updated.

        重要

        默认情况下选择此选项。This option is selected by default. 但是,在分配必需部署之前没有任何影响。However, it has no effect until you assign a required deployment. 用户始终可以重新运行可用的部署。A user can always rerun available deployments.

      • 如果上次尝试失败则重新运行:只有在以前未成功运行的情况下,才在计划部署时重新运行任务序列。Rerun if failed previous attempt: The task sequence reruns when the deployment is scheduled, only if it previously failed to run. 此设置对必需部署非常有用。This setting is useful for a required deployment. 如果上次运行尝试失败,它会根据分配计划自动尝试重新运行。If the last attempt to run was unsuccessful, it automatically tries to rerun according to the assignment schedule.

      • 如果上次尝试成功则重新运行:仅当它上次在客户端成功运行时才重新运行任务序列。Rerun if succeeded on previous attempt: The task sequence reruns only if it previously ran successfully on the client. 如果你使用在其中例行更新任务序列的定期部署,并且每个更新都要求成功安装以前的更新,则此设置很有用。This setting is useful when you use recurring deployments in which the task sequence is routinely updated, and each update requires that the previous update is installed successfully.

      备注

      用户可以重新运行可用的任务序列部署。A user can rerun an available task sequence deployment. 在生产环境中部署可用的任务序列之前,首先测试如果用户多次重新运行任务序列会发生什么情况。Before you deploy an available task sequence in a production environment, first test what happens if a user reruns the task sequence multiple times.

  7. 在“用户体验” 页上,指定下列信息:On the User Experience page, specify the following information:

    • 允许用户独立于分配运行程序:指定用户是否可以在分配计划以外运行所需的部署。Allow user to run the program independently of assignments: Specify whether a user can run a required deployment outside of the assignment schedule. 对于可用部署,始终启用此选项。This option is always enabled for available deployments.

    • 显示任务序列进度:指定 Configuration Manager 客户端是否显示任务序列的进度。Show Task Sequence progress: Specify whether the Configuration Manager client displays the progress of the task sequence.

    • 软件安装:指定在计划的时间之后是否允许用户在已配置的维护时段之外安装软件。Software installation: Specify whether the user is allowed to install software outside a configured maintenance window after the scheduled time.

    • 系统重启(如果要求完成安装) :指定是否允许用户在晚于分配时间的已配置维护时段之外安装软件后重启计算机。System restart (if required to complete the installation): Specify whether the user is allowed to restart the computer after a software installation outside a configured maintenance window after the assignment time.

    • Windows Embedded 设备的写入筛选器处理:此设置控制通过写入筛选器启用的 Windows Embedded 设备的安装行为。Write filter handling for Windows Embedded devices: This setting controls the installation behavior on Windows Embedded devices that are enabled with a write filter. 选择此选项可在安装截止时间或维护时段提交更改。Choose the option to commit changes at the installation deadline or during a maintenance window. 选择此选项后需要重启,然后所作更改才能保留在设备上。When you select this option, a restart is required and the changes persist on the device. 否则,应用程序将安装到临时覆盖,并稍后提交。Otherwise, the application is installed to the temporary overlay, and committed later. 将任务序列部署到 Windows Embedded 设备时,确保设备是配置了维护时段的集合的成员。When you deploy a task sequence to a Windows Embedded device, make sure the device is a member of a collection that has a configured maintenance window.

    • 允许任务序列针对 Internet 上的客户端运行:指定是否允许在基于 Internet 的客户端上运行任务序列。Allow task sequence to run for client on the Internet: Specify whether the task sequence is allowed to run on an internet-based client.

      在通过云管理网关 (CMG) 将 Windows 10 就地升级任务序列部署到基于 Internet 的客户端时,支持此设置。This setting is supported for deployments of a Windows 10 in-place upgrade task sequence to internet-based clients through the cloud management gateway (CMG). 有关详细信息,请参阅通过 CMG 部署 Windows 10 就地升级For more information, see Deploy Windows 10 in-place upgrade via CMG.

      自版本 2006 起,可以将包含启动映像的任务序列部署到通过 CMG 通信的设备上。Starting in version 2006, you can deploy a task sequence with a boot image to a device that communicates through the CMG. 用户需要从软件中心启动任务序列。The user needs to start the task sequence from Software Center.

      备注

      当已建立 Azure Active Directory (Azure AD) 联接的客户端运行 OS 部署任务序列时,新 OS 中的客户端不会自动建立 Azure AD 联接。When an Azure Active Directory (Azure AD)-joined client runs an OS deployment task sequence, the client in the new OS won't automatically join Azure AD. 即使没有建立 Azure AD 联接,客户端仍是受管理的。Even though it's not Azure AD-joined, the client is still managed.

      在已建立 Azure AD 联接或使用基于令牌的身份验证的基于 Internet 的客户端上运行 OS 部署任务序列时,需要在安装 Windows 和 ConfigMgr 步骤中指定 CCMHOSTNAME 属性。When you run an OS deployment task sequence on an internet-based client, that's either Azure AD-joined or uses token-based authentication, you need to specify the CCMHOSTNAME property in the Setup Windows and ConfigMgr step.

      在版本 2002 及更低版本中,需要启动介质的操作无法与此设置相配合。In version 2002 and earlier, operations that require a boot media aren't supported with this setting. 请将此选项仅用于一般软件安装或在标准 OS 中运行操作的基于通用脚本的任务序列。Use this option only for generic software installations or script-based task sequences that run operations in the standard OS.

      备注

      对于所有基于 Internet 的任务序列方案,请从软件中心启动任务序列。For all internet-based task sequence scenarios, start the task sequence from Software Center. 这些方案不支持 Windows PE、PXE 或任务序列介质。They don't support Windows PE, PXE, or task sequence media.

  8. 在“警报”页上,为此任务序列部署指定所需的警报设置。On the Alerts page, specify the alert settings that you want for this task sequence deployment.

  9. 在“分发点” 页上,指定下列信息:On the Distribution Points page, specify the following information:

    • 部署选项:有关详细信息,请参阅部署选项Deployment options: For more information, see Deployment options.

    • 在没有本地分发点可用的情况下使用远程分发点:指定客户端是否可以使用来自相邻边界组的分发点来下载任务序列所需的内容。When no local distribution point is available, use a remote distribution point: Specify whether clients can use distribution points from a neighbor boundary group to download the content that's required by the task sequence.

    • 允许客户端使用默认站点边界组分发点:指定在无法从当前或相邻边界组中的分发点获得内容时,客户端是否应从站点默认边界组中的分发点下载内容。Allow clients to use distribution points from the default site boundary group: Specify if clients should download content from a distribution point in the site default boundary group, when it isn't available from a distribution point in the current or neighbor boundary groups.

      备注

      从版本 1810 开始,当设备运行任务序列并且需要获取内容时,它可以使用类似于 Configuration Manager 客户端的边界组行为。Starting in version 1810, when a device runs a task sequence and needs to acquire content, it uses boundary group behaviors similar to the Configuration Manager client. 有关更多详细信息,请参阅对边界组的任务序列支持For more information, see Task sequence support for boundary groups.

  10. 若要保存这些设置以便再次使用,请在“摘要”选项卡上选择“另存为模板” 。To save these settings to use again, on the Summary tab select Save As Template. 为模板提供名称,然后选择要保存的设置。Supply a name for the template and select the settings to save.

  11. 完成向导。Complete the wizard.

部署选项Deployment options

这些选项位于任务序列部署的“分发点”选项卡上。These options are on the Distribution Points tab of the task sequence deployment. 它们是动态的,基于任务序列的部署和属性中的其他选择。They're dynamic based upon other selections in the deployment and attributes of the task sequence. 你可能不会总是看到所有选项。You may not always see all options.

备注

如果使用多播部署 OS,则在需要时或者在运行任务序列之前将内容下载到计算机。When you use multicast to deploy an OS, download the content to the computers either as needed or before the task sequence runs.

  • 运行中任务序列需要时,从本地下载内容:指定客户端在任务序列需要内容时从分发点下载内容。Download content locally when needed by the running task sequence: Specify that clients download content from the distribution point as it's needed by the task sequence. 客户端启动任务序列。The client starts the task sequence. 当任务序列中的步骤需要内容时,会在步骤运行之前下载它。When a step in the task sequence requires content, it's downloaded before the step runs.

  • 启动任务序列之前本地下载所有内容:指定客户端在运行任务序列之前从分发点下载所有内容。Download all content locally before starting task sequence: Specify that clients download all the content from the distribution point before the task sequence runs. 如果指定任务序列可用于 PXE 和启动媒体部署,则“部署设置”页不会显示此选项。If you make the task sequence available to PXE and boot media deployments on the Deployment Settings page, this option isn't shown.

  • 需要时通过运行任务序列从分发点直接访问内容:指定客户端从分发点运行内容。Access content directly from a distribution point when needed by the running task sequence: Specify that clients run the content from the distribution point. 只有当与任务序列关联的所有包都能够使用分发点上的包共享时才可以使用此选项。This option is only available when you enable all packages associated with the task sequence to use a package share on the distribution point. 要使内容能够使用包共享,请参阅每个包的“属性”中的“数据访问”选项卡。To enable content to use a package share, see the Data Access tab in the Properties for each package.

重要

为了最大限度地确保安全,请选择“运行中任务序列需要时,从本地下载内容”或“启动任务序列之前本地下载所有内容”选项 。For greatest security, select the options to Download content locally when needed by the running task sequence or Download all content locally before starting task sequence. 选择其中任何一个选项后,Configuration Manager 会对包进行哈希处理,便于确保包的完整性。When you select either of these options, Configuration Manager hashes the package, so that it can ensure package integrity. 选择“需要时通过运行任务序列从分发点直接访问内容”选项后,Configuration Manager 不会在运行指定的程序之前验证包哈希。When you select the option to Access content directly from a distribution point when needed by the running task sequence, Configuration Manager doesn't verify the package hash prior to running the specified program. 由于站点无法确保包完整性,因此具有管理权限的用户可能会改变或篡改包内容。Because the site can't ensure package integrity, it's possible for users with administrative rights to alter or tamper with package contents.

示例 1:一个部署选项Example 1: One deployment option

部署可擦除磁盘及应用图像的 OS 部署任务序列。You deploy an OS deployment task sequence that wipes the disk and applies an image. 在“部署设置”页上,使其可用于包含媒体和 PXE 的选项:On the Deployment Settings page, you make it available to an option that includes media and PXE:

部署任务序列,使其可用于以下任务

在“分发点”页上,只有一个部署选项:On the Distribution Points page, there's only one deployment option:

  • 运行中任务序列需要时,从本地下载内容Download content locally when needed by the running task sequence

部署任务序列,一个部署选项

“启动任务序列前从本地下载所有内容”选项不可用,因为部署可用于媒体和 PXE。The option to Download all content locally before starting task sequence isn't available because the deployment is made available to media and PXE.

“需要时通过运行任务序列从分发点直接访问内容”选项不可用。The option to Access content directly from a distribution point when needed by the running task sequence isn't available. 并非所有引用内容都使用包共享。Not all of the referenced content uses a package share.

示例 2:两个部署选项Example 2: Two deployment options

部署可擦除磁盘及应用图像的 OS 部署任务序列。You deploy an OS deployment task sequence that wipes the disk and applies an image. 在“部署设置”页上,可使用“仅限 Configuration Manager 客户端” 。On the Deployment Settings page, you make it available to Only Configuration Manager clients. 在“分发点”页上,有两个可用的部署选项:On the Distribution Points page, there are two deployment options available:

  • 运行中任务序列需要时,从本地下载内容Download content locally when needed by the running task sequence
  • 启动任务序列之前在本地下载所有内容Download all content locally before starting task sequence

部署任务序列,两个部署选项

“需要时通过运行任务序列从分发点直接访问内容”选项不可用。The option to Access content directly from a distribution point when needed by the running task sequence isn't available. 并非所有引用内容都使用包共享。Not all of the referenced content uses a package share.

示例 3:三个部署选项Example 3: Three deployment options

你拥有几个包含管理脚本和相关内容的包。You have several packages with administrative scripts and associated content. 在包属性的“数据访问”选项卡上,将它们全部配置为“将此包中的内容复制到分发点上的包共享” 。On the Data Access tab of the package properties, you configure all of them to Copy the content in this package to a package share on distribution points.

你将为这些脚本包创建一个任务序列(该任务序列仅具有几个“安装包”步骤),然后对其进行部署。You create a task sequence that only has several Install Package steps for these script packages, and the deploy it. 在“部署设置”页上,唯一可使用的选项是“仅限 Configuration Manager 客户端” 。On the Deployment Settings page, the only option is to make available to Only Configuration Manager clients. 此选项是唯一可用的选项。This option is the only available. 任务序列不适用于 OS 部署,因为它没有与之关联的启动图像。The task sequence isn't for OS deployment, because it doesn't have a boot image associated with it. 在“分发点”页上,有三个可用的部署选项:On the Distribution Points page, there are three deployment options available:

  • 运行中任务序列需要时,从本地下载内容Download content locally when needed by the running task sequence
  • 启动任务序列之前在本地下载所有内容Download all content locally before starting task sequence
  • 需要时通过运行任务序列从分发点直接访问内容Access content directly from a distribution point when needed by the running task sequence

部署任务序列,三个部署选项

通过 CMG 部署 Windows 10 就地升级Deploy Windows 10 in-place upgrade via CMG

Windows 10 就地升级任务序列支持部署到通过云管理网关 (CMG) 托管的 Internet 客户端。The Windows 10 in-place upgrade task sequence supports deployment to internet-based clients managed through the cloud management gateway (CMG). 此功能可让远程用户更轻松地升级到 Windows 10,无需连接 Intranet。This ability allows remote users to more easily upgrade to Windows 10 without needing to connect to the intranet.

确保就地升级任务序列引用的所有内容均分发到内容已启用的 CMG。Make sure all of the content referenced by the in-place upgrade task sequence is distributed to a content-enabled CMG. (启用 CMG 设置:允许 CMG 充当云分发点,并提供 Azure 存储中的内容。)你还可使用云分发点(Enable the CMG setting: Allow CMG to function as a cloud distribution point and serve content from Azure storage.) You can also use a cloud distribution point. 否则设备无法运行任务序列。Otherwise devices can't run the task sequence.

在部署升级任务序列时,请使用以下设置:When you deploy an upgrade task sequence, use the following settings:

  • 部署“用户体验”选项卡上的“允许任务序列针对 Internet 上的客户端运行”。Allow task sequence to run for client on the Internet, on the User Experience tab of the deployment.

  • 在部署的“分发点”选项卡上选择以下选项之一:Choose one of the following options on the Distribution Points tab of the deployment:

    • 运行中任务序列需要时,从本地下载内容。Download content locally when needed by the running task sequence. 从版本 1910 开始,任务序列引擎可以按需从启用内容的 CMG 或云分发点下载包。Starting in version 1910, the task sequence engine can download packages on-demand from a content-enabled CMG or a cloud distribution point. 此更改为基于 Internet 的设备的 Windows 10 就地升级部署提供了更大的灵活性。This change provides additional flexibility with your Windows 10 in-place upgrade deployments to internet-based devices.

    • 启动任务序列之前在本地下载所有内容。Download all content locally before starting task sequence. 在 Configuration Manager 版本 1906 及更低版本中,其他选项(例如“运行任务序列时,如需要则在本地下载内容”)不适用于此方案。In Configuration Manager version 1906 and earlier, other options such as Download content locally when needed by the running task sequence don't work in this scenario. 任务序列引擎无法从云源下载内容。The task sequence engine can't download content from a cloud source. 启动任务序列之前,Configuration Manager 客户端必须从云资源下载内容。The Configuration Manager client must download the content from the cloud source before starting the task sequence. 为满足你的要求,必要时仍可在 1910 版本中使用此选项。You can still use this option in version 1910 if needed to meet your requirements.

  • (可选)部署“常规”选项卡上的“此任务序列的预下载内容”。(Optional) Pre-download content for this task sequence, on the General tab of the deployment. 有关详细信息,请参阅配置预缓存内容For more information, see Configure pre-cache content.

备注

从软件中心启动任务序列。Start the task sequence from Software Center. 此方案不支持 Windows PE、PXE 或任务序列媒体。This scenario doesn't support Windows PE, PXE, or task sequence media.

高风险部署High-risk deployments

部署高风险部署(例如 OS)时,“选择集合”窗口将仅显示满足在站点属性中配置的部署验证设置的自定义集合。When you deploy a high-risk deployment, such as an OS, the Select Collection window displays only the custom collections that meet the deployment verification settings that are configured in the site's properties. 高风险部署始终局限于自定义集合、你所创建的集合和内置“未知计算机”集合。High-risk deployments are always limited to custom collections, collections that you create, and the built-in Unknown Computers collection. 创建高风险部署时,无法选择“所有系统”等内置集合。When you create a high-risk deployment, you can't select a built-in collection such as All Systems. 若要查看所含客户端少于配置的最大大小的全部自定义集合,请禁用“隐藏成员数大于站点最低大小配置的集合”选项。To see all custom collections that contain fewer clients than the configured maximum size, disable the option to Hide collections with a member count greater than the site's minimum size configuration. 有关详细信息,请参阅用于管理高风险部署的设置For more information, see Settings to manage high-risk deployments.

部署验证设置基于集合的当前成员身份。The deployment verification settings are based on the current membership of the collection. 部署任务序列后,Configuration Manager 不重新评估高风险部署设置的集合成员身份。After you deploy the task sequence, Configuration Manager doesn't reevaluate the collection membership for the high-risk deployment settings.

例如,假设将“默认大小”设置为 100,将“最大大小”设置为 1000。For example, let's say you set Default size to 100 and the Maximum size to 1000. 创建高风险部署时,“选择集合”窗口仅显示包含的客户端少于 100 个的集合。When you create a high risk deployment, the Select Collection window only displays collections that contain fewer than 100 clients. 如果清除“隐藏成员数大于站点最低大小配置的集合”设置,则该窗口显示包含的客户端少于 1000 个的集合。If you clear the Hide collections with a member count greater than the site's minimum size configuration setting, the window displays collections that contain fewer than 1000 clients.

选择包含站点角色的集合时,以下行为适用:When you select a collection that contains a site role, the following behavior applies:

  • 如果集合包含站点系统服务器,而你将部署验证设置配置为阻止具有站点系统服务器的集合,则会出现错误。If the collection contains a site system server, and you configured the deployment verification settings to block collections with site system servers, then an error occurs. 你将无法继续创建部署。You can't continue creating the deployment.

  • 如果以下一项标准适用,“部署软件向导”将显示高风险警告。If one of the following criteria applies, then the Deploy Software Wizard displays a high-risk warning. 继续操作需要同意创建高风险部署。To continue, you need to agree to create a high-risk deployment. 站点会生成审核状态消息。The site generates an audit status message.

    • 如果集合包含站点系统服务器,而你将部署验证设置配置为对具有站点系统服务器的集合发出警告If the collection contains a site system server, and you configured the deployment verification settings to warn on collections with site system servers

    • 如果集合超过默认大小值If the collection exceeds the default size value

    • 如果集合包含服务器If the collection contains a server

另请参阅See also

管理任务序列来自动执行任务Manage task sequences to automate tasks