Welcome to Desktop Deployment Essentials. Our new series to help you prepare for
your shift to Windows 10 and Office 365 ProPlus. So by now we've covered steps 1
through 6 in our Modern Desktop Deployment wheel and in the next few
minutes, we'll walk you through step 7 as we explore the servicing models for both
Windows 10 and Office 365 ProPlus. Now both windows 10 office 365 ProPlus
introduced new servicing options, support models and update timelines. These
changes simplify the process for staying current on the latest features along
with these updates, are new configuration options to enable servicing plans that
meet your needs updates fall into two main categories:
Feature Updates and then Quality Updates which contain
cumulative security reliability and bug fixes. In terms of cadence both Windows (10)
and Office (365 ProPlus) deliver semi-annual channels, which deliver new features twice per
year around March and September, while quality and security updates occur
monthly. Additionally unique to Office 365 apps, we deliver monthly channel
updates that are fully-supported and contain both new features and quality
updates. Okay, let's pause for a second because you might be thinking are
these updates going to be compatible, will I need to keep retraining my users and
what are the risks? So let's break this down and explain some of the advantages
of the new approach. First we've moved away from the model of the past that
would introduce huge waves of change every three or so years to now more
incremental smaller ripples of change with feature updates twice per year now
with technology trends moving so fast and rapidly evolving security threats
this keeps you current. Some of the security related updates for example
can't just be delivered to be a monthly security patches they may require
low-level changes to the platform like with virtualization-based security.
Second delivering quality and security updates is a cumulative package corrects
many of the issues from the past. It used to be lead pick-and-choose sometimes
from up to a dozen updates or more each month for both Windows and Office. As you
can imagine this creates nearly an impossible set of test matrices for
support. Also if you install a one or two year old version of Windows or Office
it might take hours or even days to apply all the updates delivered since
that version was released. So now you're always just one update away from being
current. With cumulate updates and we've reduced the number of
monthly updates that you'll need to deploy. Each update builds upon updates
from previous months and contains all the fixes that you need to get current.
This is especially helpful if a PC has been turned off for several months because
it's in storage. Another advantage is that before we roll out these updates
for broad deployment, we first release builds by insider programs for Office
and Windows and this allows us to gather telemetry and feedback ahead of us
releasing these updates broadly. Now the Insider Programs are open to everyone so
you can get ahead of understanding the updates. By the time that we release
updates, we'll receive telemetry from millions of configurations so that when we
do release updates, quality is now inherently more
predictable and one more thing because Office 365 ProPlus and Insider builds
reflect monthly channel updates. If you are using semi annual channel for Office
to deliver feature updates twice a year aligned to Windows you can now validate
these builds early as well using the semi-annual channel targeted releases.
We've also thought through how to make to the deployment of updates seamless.
System Center Configuration Manager current branch is updated frequently to
support the roll out of these updates to both Windows and Office and any new
related capabilities. Now let's shift gears to how you're going to roll out these
updates for any release you recommend 3 different deployment phases for IT
validation (usually IT or internal insiders), piloting and broad production deployment. Once you're up and running on
Windows 10 and Office 365 ProPlus, you'll use monthly servicing to stay current
with critical security and quality updates then you'll move to semi annual
servicing for new features. Let's start with monthly updating. The service model
is designed so you can choose to limit the roll out of new features to just
twice per year and if needed you can even skip a semi-annual update and
continue receiving quality and security updates. As I mentioned the cumulative
nature of monthly updates means that each increases in size per month. Using a
technology called Express Updates in Windows and binary delta compression in
Office we can reduce the size of the download significantly in both
approaches the update engines compare what's on the PC and finds only the
differentials needed to update what's there. Windows Update for business and
Windows Server Update Services have supported these Express Updates for a
long time, but now we've also added that support to
System Center Configuration Manager so it can also use Express Updates. Binary
Delta Compression in Office is only used if you're updating
from the most recent version of Office 365 ProPlus so to use this approach you
need to be updated from the previous build and can't skip (monthly) updates. Windows and
Office update channels can be managed by a Configuration Manager using standard
approval and targeting process. Additionally you can use policy settings
in Office and Windows to enforce update channels used as well as related
settings. So those are your considerations for monthly updates, but
now let's move on to the larger semi-annual updates. As we covered in
device and app readiness, you'll want to begin your preparation for these larger
updates using the same readiness tools that we set up in step one of the
deployment wheel. Now if you missed that episode you can check it out at the link
shown (aka.ms/ddev1) as for tooling you can use policy settings with Windows Update for
Business, software update management via ConfigMgr, WSUS or update policies
set by Intune and if you are concerned about network bandwidth check out
episode 2 in our Essential Series (aka.ms/ddev2) on Directory and Network Readiness to learn
about your options to reduce network traffic via Delivery Optimization or
other Peer to Peer caching technologies. Now while installing the
larger feature updates via a standard software update management routines is a
supported option, many organizations are going to opt to use upgrade task
sequences using System Center Configuration Manager or the Microsoft
Deployment Toolkit. This option also allows you to create custom checks prior
to installing the feature update and allows you to perform custom tasks after
the installation is completed. Post update checks might include temporarily
suspending services if needed during the update driver installation and
replacement, application upgrades or Taskbar and Start menu personalization
settings. If you're already using task sequences to migrate your Windows 7
machines to Windows 10 and are well-versed in those tools, this is
really a great place to start and provides the ultimate control. And while
you can use a single task sequence for the entire upgrade, it's often
common for organizations to use two task sequences one task sequence for making
sure that machines are ready for the upgrade, that also silently pre-stages all
the required setup files on target computers and another task sequence to
do the actual upgrade. This approach ensures that your user productivity is
less impacted and if you don't use upgrade task sequences, you can now run
custom actions or apply driver files during feature updates in the pre-
install phase before setup compatibility checks or in the pre-
commit phase before the upgrade is applied. So that was a run-through of
Windows as a Service and Office as a Service models and what you can do to stay up to date
next up on our deployment process wheel, we'll cover what you can do to get your
users ready for Windows 10 and Office 365 ProPlus with tips and resources for
user adoption and communication planning. To learn more don't forget to visit our
Modern Desktop Deployment Center and keep following our Desktop Deployment
Essentials series here on Microsoft Mechanics. Thanks for watching!
Không có nhận xét nào:
Đăng nhận xét