Blog Alert
When a new post is published, we'll deliver it to your inbox.

Enter your email address

Search The Blog
Categories
Archives
<   November 2009   >
MonTueWedThuFriSatSun
      1
2345678
9101112131415
16171819202122
23242526272829
30      
Recommended Links
Contact
To learn more, please contact:

Gartner
Office: + 1 203 964 0096
sitefeedback@gartner.com
help@gartner.com

Contact Us Form
Worldwide General Contacts
03 November, 2006 10:00 AM EST
The Windows Update Effect
Posted By: Steve Kleynhans, Research VP

As Microsoft approaches the finish line with both Windows Vista and Office 2007, most testers continue to note that there are minor holes in the products. With previous releases, Microsoft may have been forced to hold back a release for these types of problems. However, the world is somewhat different this time around. Microsoft has a huge safety net it can fall back on: Windows Update.

Windows Update (and now Microsoft Update) has proven to be a boon to both consumers and Microsoft. After some rough spots in the early days, Windows Update has become a pretty solid and reliable vehicle. Although it can still be somewhat intrusive, it has greatly simplified the process of getting patches and other fixes. With Vista and Office 2007, Microsoft can release the product to manufacturing in a complete form, but continue to embellish it with new device drivers, minor enhancements and fixes right through the actual consumer release. The good news is that this ensures that the product will continue to get more polished. The downside is that organizations must factor these changes into their testing processes.

Looking ahead, Windows Update may also have a significant impact on another well-established tradition - waiting for Service Pack 1. With the ability to slip fixes into the product, the need for large, cumbersome, fear-inducing service packs have somewhat diminished. There is a significant likelihood that the first service pack for Vista may, in fact, be quite a ways off in future.
Take this into account when developing your implementation plans.