定义就绪情况条件Define readiness criteria

确定角色和人员Figure out roles and personnel

规划和管理部署涉及各种不同的活动和最适合每个角色的角色。Planning and managing a deployment involves a variety of distinct activities and roles best suited to each. 在你计划的情况下,需要查明你需要哪些角色才能执行部署以及应填写这些角色。As you plan, it's worth figuring out which roles you'll need to carry out the deployment and who should fill them. 不同角色在部署的各个阶段处于活动状态。Different roles are active at various phases of a deployment. 某些角色可能由同一个人填写,具体取决于组织的规模和复杂程度。Depending on the size and complexity of your organization, some of the roles could be filled by the same person. 但是,最好拥有一个已建立的 流程管理器,该管理器将监督部署的所有任务。However, it's best to have an established process manager, who will oversee all of the tasks for the deployment.

Process managerProcess manager

进程管理器领导更新部署过程并拥有推动该过程的权限(如有必要)。The process manager leads the update deployment process and has the authority to push the process forward--or halt it if necessary. 他们还具有整理这些活动的责任:They also have responsibilities in organizing these activities:

兼容性工作流Compatibility workstream 部署Deployment 功能和现代化Capability and modernization
分配应用程序优先级Assigning application priority 查看基础结构要求Reviewing infrastructure requirements 确定基础架构更改Determining infrastructure changes
应用程序评估Application assessment 根据要求验证基础结构Validating infrastructure against requirements 确定配置更改Determining configuration changes
设备评估Device assessment 创建基础结构更新计划Creating infrastructure update plan 创建功能方案Create capability proposal

它是流程管理器的角色,可收集有关补救措施的报告、升级失败,并确定你的环境是否已准备好进行试点部署和广泛的部署。It's the process manager's role to collect reports on remediation efforts, escalate failures, and to decide whether your environment is ready for pilot deployment and then broad deployment.

此表草拟了其他角色的一个视图,以及它们的责任、相关技能和部署阶段,这些阶段需要他们:This table sketches out one view of the other roles, with their responsibilities, relevant skills, and the deployment phases where they are needed:

角色Role 交给Responsibilities 熟练Skills 活动阶段Active phases
Process managerProcess manager 端到端管理流程;确保输入和输出是捕获的;确保活动进度Manages the process end to end; ensures inputs and outputs are captures; ensures that activities progress IT 服务管理IT Service Management 规划、准备、试点部署、广泛部署Plan, prepare, pilot deployment, broad deployment
应用程序所有者Application owner 定义应用程序测试计划;分配用户验收测试人员;验证应用程序Define application test plan; assign user acceptance testers; certify the application 了解关键和重要应用程序Knowledge of critical and important applications 规划、准备、试点项目部署Plan, prepare, pilot deployment
应用程序开发人员Application developer 确保开发应用以与当前 Windows 版本保持兼容Ensure apps are developed to stay compatible with current Windows versions 应用程序开发;应用程序修正Application development; application remediation 规划、准备Plan, prepare
最终用户计算End-user computing 通常是一个包含基础结构工程师或部署工程师的组,这些工程师确保升级工具与 Windows 兼容Typically a group including infrastructure engineers or deployment engineers who ensure upgrade tools are compatible with Windows 裸机部署;基础结构管理;应用程序交付;更新管理Bare-metal deployment; infrastructure management; application delivery; update management 规划、准备、试点部署、广泛部署Plan, prepare, pilot deployment, broad deployment
操作Operations 确保支持适用于当前的 Windows 版本。Ensure that support is available for current Windows version. 提供部署后支持,包括用户通信和回退。Provide post-deployment support, including user communication and rollbacks. 平台安全Platform security 准备、试点部署、广泛部署Prepare, pilot deployment, broad deployment
安全性Security 查看和批准安全基准和工具Review and approve the security baseline and tools 平台安全Platform security 准备、试点部署Prepare, pilot deployment
利益干系人Stakeholders 表示受更新影响的组,例如,财务负责人、最终用户服务或更改管理Represent groups affected by updates, for example, heads of finance, end-user services, or change management 业务部门或部门的关键决策人Key decision maker for a business unit or department 规划、试点项目部署、广泛部署Plan, pilot deployment, broad deployment

设置分级应用的标准Set criteria for rating apps

你的环境中的某些应用是核心业务活动的基础。Some apps in your environment are fundamental to your core business activities. 其他应用帮助工作人员执行其角色,但对您的业务运营不重要。Other apps help workers perform their roles, but aren’t critical to your business operations. 在你开始清点和评估你的环境中的应用之前,你应该建立一些用于对你的应用进行分类的条件,然后确定每个应用的优先级。Before you start inventorying and assessing the apps in your environment, you should establish some criteria for categorizing your apps, and then determine a priority for each. 此过程将帮助你了解如何最佳地部署更新以及如何解决可能出现的任何问题。This process will help you understand how best to deploy updates and how to resolve any issues that could arise.

在 "准备" 阶段中,你将立即对组织中的每个应用应用你定义的条件。In the Prepare phase, you'll apply the criteria you define now to every app in your organization.

下面是建议的分类方案:Here's a suggested classification scheme:

分类Classification 定义Definition
极热Critical 处理核心业务活动和进程的最重要的应用程序。The most vital applications that handle core business activities and processes. 如果这些应用程序不可用,则业务部门或业务部门无法正常工作。If these applications were not available, the business, or a business unit, couldn't function at all.
重要提示Important 个人教职员工成员需要支持其工作效率的应用程序。Applications that individual staff members need to support their productivity. 此处的停机时间将影响单个用户,但对企业的影响最小。Downtime here would affect individual users, but would only have a minimal impact on the business.
不重要Not important 如果这些应用尚不可用,则不会对业务产生任何影响。There is no impact on the business if these apps are not available for a while.

对应用程序进行分类后,应根据优先级和严重程度同意每个分类对组织的含义。Once you have classified your applications, you should agree what each classification means to the organization in terms of priority and severity. 此活动将帮助确保你可以对相应的紧迫级别的问题进行会审。This activity will help ensure that you can triage problems with the right level of urgency. 你应该为每个应用分配一个基于时间的优先级。You should assign each app a time-based priority.

下面是优先级分级系统的示例。你的组织可能会有所不同详细信息:Here's an example priority rating system; the specifics could vary for your organization:

优先级Priority 定义Definition
raid-11 必须尽快调查和解决所标识的任何问题或风险。Any issues or risks identified must be investigated and resolved as soon as possible.
ppls-22 开始在两个工作日内调查风险和问题,并 在当前 部署周期内对其进行修复。Start investigating risks and issues within two business days and fix them during the current deployment cycle.
三维空间3 开始在10个工作日内调查风险和问题。Start investigating risks and issues within 10 business days. 无需在当前部署周期内全部修复。You don’t have to fix them all within the current deployment cycle. 但是,所有问题必须在下一个部署周期结束时修复。However, all issues must be fixed by the end of the next deployment cycle.
4 开始在20个工作日内调查风险和问题。Start investigating risks and issues within 20 business days. 你可以在当前或将来的开发周期中修复它们。You can fix them in the current or any future development cycle.

与优先级不同,但也是截然不同的,这是严重程度的概念。Related to priority, but distinct, is the concept of severity. 你还应根据你对应用的问题的感觉会影响部署周期来定义严重级别。You should define a severity ranking as well, based on how you feel a problem with an app should affect the deployment cycle.

下面是一个示例:Here's an example:

严重性Severity 作用Effect
raid-11 工作中断或收入损失Work stoppage or loss of revenue
ppls-22 业务单元的工作效率损失Productivity loss for a business unit
三维空间3 单个用户的工作效率损失Productivity loss for individual users
4 对用户的影响最小Minimal impact on users

示例:大型金融公司Example: a large financial corporation

使用建议的方案,金融公司可能会对其应用进行分类,如下所示:Using the suggested scheme, a financial corporation might classify their apps like this:

应用App 分类Classification
点数处理应用Credit processing app 极热Critical
Frontline 客户服务应用Frontline customer service app 极热Critical
PDF 查看器PDF viewer 重要提示Important
图像处理应用程序Image-processing app 不重要Not important

此外,它们可能将此分类与严重级别和优先级排名结合起来,如下所示:Further, they might combine this classification with severity and priority rankings like this:

分类Classification 严重性Severity 优先级Priority 响应Response
极热Critical 1 或 21 or 2 1 或 21 or 2 对于1,停止部署,直到解决。对于2,请停止针对受影响的设备或用户的部署。For 1, stop deployment until resolved; for 2, stop deployment for affected devices or users only.
重要提示Important 3或43 or 4 3或43 or 4 对于3,请继续部署(即使针对受影响的设备),前提是存在解决方法指南。For 3, continue deployment, even for affected devices, as long as there is workaround guidance.
不重要Not important 4 4 继续部署所有设备。Continue deployment for all devices.