further simplifying servicing models€¦ · packaging technology 7 sp1 2008 r2 sp1 change to...
TRANSCRIPT
Further simplifying servicing models for Windows 7 SP1, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2
Artyom SinitsynSecurity Program Manager CEE & CIS
2
Scanning for
new updates
indexes all
existing
updates
Installing limited
distribution releases
must index all newer
fixes
3
4
Typical Windows 7 PC:
Selectively Patched
Windows 7 Test Lab PC:
Fully Patched
What customers
are running
What we
are testing
Y
YY
Individual updates add complexity and cost, increase fragmentation, and reduce quality
Windows 7 has had 4,000+ updates since SP1 released. Over 600 of
those updates were never widely distributed 5
Systems with a fragmented set of updates are less reliable
6
HOW?
• Align with Windows 10 Servicing Model
• Minimize disruption to business
Benefits for Customers
Consistent Servicing
Experience
Servicing experience across OS platforms is more consistent and simplified.
Fewer updates to manage
Improve Update quality
Improve OS reliability
Eliminating update fragmentation will ensure customers are in the same
configuration we test, and customers will have all updates proactively
Easy to get current Only 1 update needed to get current
7
WHAT?
8
9
10
Client OS Server OS Comments
XP 2003 R2 Out of scope. In CSA, very few fixes
Vista 2008 Out of scope. Technically challenging due to old
packaging technology
7 SP1 2008 R2 SP1 Change to rollup package
8 2012 Change to rollup package (Windows 8 is in CSA)
8.1 2012 R2 Change to rollup package
10 2016 Out of scope. Already provided in rollup package
The scope of the change is Windows 7 SP1, Windows Server 2008 R2 SP1, Windows Server
2012, Windows 8.1, and Windows Server 2012 R2.
Increasing our update quality, ecosystem reliability, and reducing support costs with Two rollups a month
12
New optional Rollup on 3rd Tuesday (PST)
13
14
15
Security1
Security2
Security3
9B
Non
Security
9C
3rd Tue2nd Tue
16
Security1
Security2
Security3
9B
Non
Security
9C
3rd Tue2nd Tue
10B
2nd Tue
10B’
2nd Tue
Security Security
Non
Security
New Security update of the month
Includes Preview rollup of last month.
17
Security1
Security2
Security3
9B
Non
Security
9C
3rd Tue2nd Tue
10B 10C
3rd Tue2nd Tue
10B’
2nd Tue
Security Security
Non
Security
Security
Non
Security
Non
Security
Monthly Rollup of the month
New Non-Security update of the
month
18
Security1
Security2
Security3
9B
Non
Security
9C
3rd Tue2nd Tue
10B 10C
3rd Tue2nd Tue
10B’
2nd Tue
Security Security
Non
Security
Security
Non
Security
Non
Security
11B
2nd Tue
11B’
2nd Tue
Security Security
Security
Non
Security
Non
Security
New Security update of the month
Includes Preview rollup of last month.
19
Security1
Security2
Security3
9B
Non
Security
9C
3rd Tue2nd Tue
10B 10C
3rd Tue2nd Tue
10B’
2nd Tue
Security Security
Non
Security
Security
Non
Security
Non
Security
11B 11C
3rd Tue2nd Tue
11B’
2nd Tue
Security Security
Security
Non
Security
Non
Security
Security
Security
Non
Security
Non
Security
Non
Security
Monthly Rollup of the month
New Non-Security update of the
month
20
Security1
Security2
Security3
9B
Non
Security
9C
3rd Tue2nd Tue
10B 10C
3rd Tue2nd Tue
10B’
2nd Tue
Security Security
Non
Security
Security
Non
Security
Non
Security
11B 11C
3rd Tue2nd Tue
11B’
2nd Tue
Security Security
Security
Non
Security
Non
Security
Security
Security
Non
Security
Non
Security
Non
Security
12B
2nd Tue
12B’
2nd Tue
Security Security
Security
Security
Non
Security
Non
Security
Non
Security
21
Security1
Security2
Security3
9B
Non
Security
9C
3rd Tue2nd Tue
10B 10C
3rd Tue2nd Tue
10B’
2nd Tue
Security Security
Non
Security
Security
Non
Security
Non
Security
11B 11C
3rd Tue2nd Tue
11B’
2nd Tue
Security Security
Security
Non
Security
Non
Security
Security
Security
Non
Security
Non
Security
Non
Security
12B
2nd Tue
12B’
2nd Tue
Security Security
Security
Security
Non
Security
Non
Security
Non
Security
12C
Security
Security
Security
Non
Security
Non
Security
Non
Security
Non
Security
3rd Tue
22
Security1
Security2
Security3
9B
Non
Security
9C
3rd Tue2nd Tue
10B 10C
3rd Tue2nd Tue
10B’
2nd Tue
Security Security
Non
Security
Security
Non
Security
Non
Security
11B 11C
3rd Tue2nd Tue
11B’
2nd Tue
Security Security
Security
Non
Security
Non
Security
Security
Security
Non
Security
Non
Security
Non
Security
12B 12C
3rd Tue2nd Tue
12B’
2nd Tue
Security Security Security
Security
Security
Non
Security
Non
Security
Non
Security
Security
Security
Non
Security
Non
Security
Non
Security
Non
Security
23
Release Type Example of Package Title
Target Users Distribution Channel
B Security Only Update
[October, 2016] Security Only Quality Update for [OS] (KBxxxxxxx)
• For Enterprise users• Rollup that includes
only the security patches for that month
• WSUS• Microsoft Update
Catalog
B’ Monthly Rollup [October, 2016] Security Monthly Quality Rollup for [OS] (KBzzzzzzz)
• For all users• Rollup that includes
Security update + non-security updates
• Windows Update• WSUS• Microsoft Update
Catalog
Release Type Example of Package Title
Target Users Distribution Channel
C Monthly RollupPreview
[October, 2016] Preview of Monthly Quality Rollup for[OS] (KBnnnnnnn)
• For all users• Rollup that includes
fixes of B' + new non-security fixes
• Optional distribution
• Windows Update• WSUS• Microsoft Update
Catalog
26
27
evolution monthly rollup
Proactively include previous content
1. Security GDRs
2. Non-Security GDRs
3. Hotfixes by area
Continue shipping
Continue shipping all* previous fixes and new fixes each month. Only 1 update required to get
current
New fixes are rolled up together into a single
package
Create the rollup Month over month additions
Previous month’s fixes are also included.
Example: September package would also include all new fixes
and all August fixes
PHASE
CO
NT
EN
T I
N T
HE R
OLLU
P
Including older fixes
28
31
32
33
34
35
http://technet.microsoft.com/library/cc708456(v=WS.10).aspx
36
User Impact Details Mitigation
Download and install
size
On Windows 7 the additive rollup will grow to be at
least 500MB
• Space required to install may be over 3GB
• WU/WSUS customers can use Express to
minimize download size. SCCM doesn’t support
Express
• Component Based Servicing (CBS) will only
install changed components
SCCM is investigating
Express support
Any issues with
security fixes also
impact non-security
payload
The non-sec payload will also include the security
rollup so if a customer has an issue with a security
fix they may also be unable to use the non-security
payload until the issue is resolved
CSS escalation processes
(critsit). WSD will need to
respond quickly like we do
on Win10
38
Disk space taken on Win7 SP1
A-1 Clean install SP1 9.24GB
A-2 Install all GDRs 26.2GB
A-3 Run cleanup 17.8GB
B-1 Clean + Convenience Rollup 12.1GB
B-2 Run cleanup 12.1GB
Note: Less disk space taken for installation of Convenience Rollup
39
40
41
42
What are we going to do tomorrow, Brain?
https://blogs.technet.microsoft.com/securityrus/2016/09/26/windowsrollup/
https://blogs.technet.microsoft.com/securityrus/2016/09/29/windowsrollupwebcast/
https://blogs.technet.microsoft.com/windowsitpro/2016/08/15/further-simplifying-servicing-model-for-windows-7-and-windows-8-1/
https://blogs.msdn.microsoft.com/dotnet/2016/08/15/introducing-the-net-framework-monthly-rollup/
43
