Vista Service Pack 1 shipped on 18 March, two weeks ago. The specific deferred-deployment organisations that have been waiting for SP1 are now moving forward. The cumulative deployment trajectory will be visible across the year.
This is a shorter post — the structural issues were treated at the Vista RTM and the eleven-month retrospect. The SP1 release is incremental.
What is in SP1
The release includes substantial reliability and performance work plus specific cumulative bug fixes. Specific properties:
Reliability fixes. The cumulative bug-fix volume is substantial; specific deferred deployment organisations will benefit from the cumulative work.
Performance improvements. Specific perceived-performance improvements; specific I/O optimisations; specific cumulative refinement. The user-experience differential between Vista RTM and Vista SP1 is meaningful.
Compatibility shims. Specific older applications that did not work under Vista RTM may work under SP1. The cumulative compatibility surface is broader.
Specific architectural refinement. No major new features; substantial polish across existing infrastructure.
The release is exactly the kind of cumulative work that earlier service-pack work has been. The cumulative effect on enterprise-deployment readiness is meaningful.
What is happening at organisations
Three observations from the past two weeks.
Specific deferred-deployment organisations are accelerating. Specific organisations with planned post-SP1 deployment are now beginning the cumulative deployment work. The cumulative deployment percentage across major UK operators will increase substantially through 2008.
Specific testing infrastructure is operational. Specific organisations have continued application-compatibility testing through 2007; specific cumulative test results will inform deployment timing per organisation.
Specific user-communication preparation is in progress. Specific organisations are preparing user training, specific communication ahead of deployment, specific support-load planning.
The cumulative discipline is operationally rational. Specific deployment over 6-12 months following SP1 release is the expected pattern.
What I am doing at Gala Coral
Specific deployment planning for Gala Coral is now operational.
Specific application-compatibility testing produced specific results. Most line-of-business applications are operationally compatible; specific exceptions have been identified and addressed.
Specific user-experience training is being prepared. Specific user-facing changes — UAC, the new interface, IE 7 protected mode — are being explained ahead of deployment.
Specific deployment plan is for phased rollout from May through early 2009. Less critical hosts first; more critical hosts later. The cumulative discipline matters.
Specific monitoring during deployment. The cumulative impact on operational metrics will be visible; specific issues will be addressable through standard incident-response.
What I am paying attention to
Three things over the next 12 months.
Specific cumulative deployment percentage. Specific tracking metric. The cumulative deployment trajectory will inform structural assessments.
Specific Vista-targeted exploitation. 70% probability of meaningful incidents. As the deployment grows, specific targeting will follow; specific cumulative effect on incident rates will be visible.
Specific Microsoft response cadence to Vista SP1 issues. 85% probability of acceptable response. Microsoft has been credible in similar releases; specific response will inform structural confidence.
A small reflection
Vista SP1 represents the cumulative-completion point that earlier Windows service packs have represented for earlier Windows releases. The cumulative trajectory toward broader deployment now begins; specific subsequent observation will be informative.
For my own continued writing: continued tracking of the deployment trajectory. The cumulative archive informs structural understanding.
More in time.