Pushing the Button on Vista

OK. Your organization has made a decision to move to Windows Vista. Youve weighed the good against the bad, youve tested the new operating system with your existing apps, and youve navigated the complex licensing landscape to determine how much a migration it will cost over time.

Now, you just have to deploy Vista to your users. Simple, right?

Wrong.

eWEEK Labs recently put Vista deployment to the test, using Microsofts own latest and greatest, System Center Configuration Manager 2007. We tested Beta 2 of SCCM at Blade Network Technologies, using dozens of servers and laptops.

Click here to read Labs review of SCCM 2007 Beta 2.

Microsofts SCCM 2007 is filled with tools and surrounded by best-practice guides to make field deployment of Vista a reality. Yet, despite having almost twice the number of developers—59 compared to the 39 who worked on SCCM 2007s precursor, SMS 2003—and nearly double the lines of code, deployment procedures are still complex and fragile.

When it comes of deploying Windows Vista, its hardly groundbreaking to recommend that IT managers deploy the OS in a centralized depot and then send systems out to their new homes.

Vistas hardware requirements alone mean that most organizations will likely deploy the OS during the regular hardware refresh cycle. There are a couple of scenarios, however, in which field deployment of Vista will likely happen sooner than later: laptop deployments and upgrades within IT.

In many organizations, laptop systems refresh on a faster schedule than desktop systems do. In addition, laptop users are more likely than desktop users to be in remote locations without convenient access to a central depot. For these systems, the new ability of SCCM 2007 to create standalone upgrade media will likely be welcome: a DVD or USB stick can be created using new wizards in SCCM 2007 and then sent to remote workers for an in-place upgrade.

Click here to read how to put USB drive protection in place.

IT organizations seem likely to be among the first groups of users that will get Vista. And for these users—whether they are in desk-side support, a call center or IT engineering—in-place upgrades will likely make the most sense. This is especially true if users in these groups will be making component changes, such as memory or graphics cards upgrades, that are necessary to get the full Vista "experience," as Microsoft calls the Windows Aero Glass interface.

Deploying to the IT department is clearly one of the best ways to become familiar with the OS deployment tools now included in SCCM 2007. Based on our tests with SCCM 2007 Beta 2, this type of deployment will give IT staff a training ground to work out inventory collection quirks.

Many of the Microsoft management platforms improved (inventory) and new (task sequencing) features have a significant learning curve, even for administrators experienced with SMS.

Next Page: Are we there yet?