We incorporated the new updation for delivering the upgrade and configuring an update tempo for users into our deployment planning. Our Aim and methods were to:
Roll out the upgrade in Phases: Configuration Manager helped us easily manage this phased rollout in order that one group of users would receive the upgrade first, then another group, and so on. This way, if one user group experiences issues, we could quickly adjust our deployment methods for subsequent one.
Mitigate network impact from the upgrade: Considering the dimensions of the initial upgrade package, we would have liked to limit the impact on our internal network bandwidth. Phasing the rollout minimized this impact.
Limit traffic through the web firewall: People used Configuration Manager to deliver the upgrade package to the local disks . This limited the quantity of traffic that went through our firewall.
When update channels arrived within the Office 2016 time-frame , we were ready to place some groups of users on a slower, Semi-annual Channel update schedule. The advantage of using the Semi-annual Channel update is that it gives us longer to validate the compatibility of line-of-business applications with the updated features before installing them on user’s systems. On the opposite hand, people that want the newest features as soon as possible, like staff who got to show customers the newest innovations, are on the Monthly Channel, and receive monthly feature updates.
Ensure user readiness: With the faster pace of feature release and innovation in Office 365, we wanted to alert our users to the new functionality and help them quickly rise up to hurry . We used several strategies for this, including in-app notifications, a SharePoint site with information on new features, and Yammer.
Create effective support/listening channels. With the rapid deployment of latest features, we wanted a dynamic view of Office client health. we would have liked effective listening channels, in order that we could quickly learn of issues and adjust our approach as needed . A community of early adopters gave us feedback.
Help improve the software before release. CSEO plays a primary role within the “First and Best” program at Microsoft, where we deploy pre-release products to our employees. With Office 365 ProPlus, we learned about deployment and adoption, and helped the merchandise team address issues before the general public release.
The upgrade process
To Install the upgrade process, we used Configuration Manager, which supports both mandatory and user-initiated installations. We gave our users the choice to initiate the upgrade at their convenience from Configuration Manager Software Center—it was up to them to make a decision when to put in it. We also set an enforcement date on which Configuration Manager pushed out a compulsory upgrade to the systems that had not yet been upgraded. We communicated with our users before time about these options and dates.
To upgrade Office clients, we used the subsequent approaches:
For Office clients on the company network: we used Configuration Manager to deliver the upgrade package to our worldwide network of Distribution Point servers. Clients then downloaded the package from the closest server. Different sets of customer received the download package. The Configuration Manager feature “peer caching” also allowed designated clients that met specific criteria to be set as “super peers.” With the peer-caching feature enabled, these specific clients share their local Configuration Manager cache to other clients to scale back overall server and infrastructure traffic.
For new installations of Windows 10: we used our Windows Deployment Services servers to deliver the upgrade as a part of the Windows 10 image. Now we use Windows Autopilot to run upgrades using Intune. We use Autopilot to line up and pre-configure new devices, getting them ready for productive use. additionally , we use Windows Autopilot to reset, repurpose and recover devices.
Users started the upgrade to Office 365 ProPlus with one click. As soon as a replacement app was installed, it had been available to use even while the remainder of the upgrade was ongoing . If a user attempted to start out the app before it had finished installing, its installation was prioritized to li the app to open within the shortest time. on the average , the entire upgrade took but half-hour .
Comments
Post a Comment