Outline the deployment experience


Deployment requires downtime for users’ devices and must be monitored efficiently. As your organization's process manager, you’ll explain how your team might ensure updates are communicated in the best way, how updates can be applied across devices in a timely manner, and how deployment is monitored.

Inform users in a timely manner

Having the right approach to communication will help your organization ensure its users are ready for Windows feature updates, so these can be rolled out seamlessly. Updates provide continuous innovation and improvements to the product, in the same way that users’ personal devices, such as smartphones, receive updates. Ideally, users should feel excited about the update and its value, while understanding the importance of keeping devices secure. You explain that there are several measures that your team can employ to achieve this. For example by:

  • Sending organization-wide overview emails about the update and how it will be deployed
  • Sending personalized emails to users with specific details about the update
  • Setting an opt-out deadline for employees who need to remain on the current version for a little longer, due to a business need
  • Providing the ability to voluntarily update at users’ convenience (Configuration Manager only)
  • Informing users of an install date where the update could, or will, be deployed to all devices

You can combine all of these measures and match them with its deployment timeline, to ensure all users are informed and covered by the update in a timely manner. For example:

Communication timeline

As the process manager, you highlight that having an open and easy to understand communication process for updates will ensure that users see this as work that’s undertaken regularly. Over time, it will help familiarize them with the update process.

Communicate the benefits of the update

Your organization's users will have varied technical ability and IT experience. Depending on their role, users will also vary in where and when they use their devices and applications. You explain that the organization’s communications about updates should be appropriate for users. Your team can prepare a communication package and trial it with pilot users to see how effective the message lands. Pilot users tend to be more technically savvy, so less technically capable individuals should also be included to help understand how effective the message really is.

Details about benefits, along with when, and how the update will be rolled out, should be clear and easy to understand from communications. User notification about the update can correlate with the deployment rings. For example, each time deployment moves to the next deployment ring, an accompanying communication can be sent to users, to guide, and inform them about the update. This way, there would be staggered communication that’s in line with the deployment processes. You explain that the team might share emails like this:

Informative email about the update

You suggest that communications, such as emails, should point to resources and places where users can find more information, help, and support on the update. This way, users will have a good understanding of the update, and know how to get support if they need it.

Monitor deployment

Monitor the deployment process. Monitoring will help identify issues during deployment and fix them when they occur. Your team can use Desktop Analytics to monitor the deployment process when deploying to devices.

Desktop Analytics will show deployment progress. For example, your team can use it to see how many devices have been deployed to successfully and how many have issues needing further attention. This information is used to find patterns of issues across devices. For example, problems with disk space availability, or a device that might have failed while downloading the update. Desktop Analytics gives your team a better idea of issues across deployment devices, so they can quickly fix them.

Deployment status in Desktop Analytics

Desktop Analytics also gives a health status overview of deployment devices. You can review this on an ongoing basis to help better understand and learn how to prevent and resolve issues in the future. For example, the organization will see the percentage of devices with crashes before and after the update. This helps you understand whether the stability of applications has decreased or increased in the newly deployed version of Windows, and helps improve for future deployments.

Health status factors in Desktop Analytics