Data sheet
“Windows 7 supports
easier deployment –
Columbus enables this
while providing a smooth
migration process across
mixed Windows
versions.”
Just a couple of years after Windows Vista, a product not very well received
by its customers, Microsoft has finally delivered the real successor to XP:
Windows 7. Migration from Windows XP to Windows 7 however has more
challenges than earlier migrations from previous Windows versions. A
completely new process for the operating system’s installation is just one
of the issues to be overcome. To ensure optimum rollout and
administra-tion of Windows 7, to protect current investments and deliver a smooth
step-by-step transition, an appropriate system lifecycle management
so-lution is needed that can concurrently handle Windows 7, older Windows
versions, and a productive mixed-version environment.
Columbus – the ideal solution for
Win-dows 7 management
Windows PE 2 support – for increased
perfor-
mance and faster driver loading
64-bit support – for deploying the latest client and
server operating systems
Analysis tools – for efficient troubleshooting
One Windows PE version for all Windows versions
– unified management of all systems
Site-dependent adaptation of PE sources –
modu-
lar concept for large and complex environments Full integration with disk imaging – stage 200
computers in 4 hours
Excellent expandability – full scripting support
and adaptability to suit the environment
Investment protection – all existing Columbus
installations can be transferred
Many companies have postponed upgrading their exi-sting Windows XP environments due to the much publi-cized challenges of Windows Vista reported in the media. Windows 7’s many improvements have earned positive reception, but along with its improved features come
some significant changes in security, operating system up-grades and bare-metal installations, collaboration, legacy application compatibility and other such fundamental areas. To benefit from the more productive and stable en-vironment offered by Windows 7, every company will have to decide on the right approach and timing for migrating to Windows 7.
Operating System Installation and
Software Distribution for Windows 7
2
Legacy Hardware – the challenge
A significant migration problem is to decide which hardware makes the migration list and how to get that existing hard-ware online. Although the quality and number of available drivers for Windows 7 has been increased since Windows Vista, with Windows 7 sharing the same driver framework as Vista, there are still devices for which no driver is available. Particular hardware caught without drivers are multifunction printers, notebooks, mobile devices and other devices which have drivers embedded into control-panel style software.
For centrally-managed devices like multifunction printers, printer drivers may be available for multiple Windows versi-ons but the functionality provided for each Windows version may differ – printing to a spool directory or scanning to a user shared folder or mailbox, for instance, will require different permissions for Windows 7 than for legacy Windows XP and earlier clients.
Windows 7 – good planning is essential for successful migration
Besides checking off the requirements list and diving into installing Windows 7, the successful migration team will understand and address the many technical issues to be handled. Brainware earned significant experience working closely with early-adopter customer teams on many large-scale Windows Vista projects. Windows Vista was indeed a precursor to Windows 7 and our experience readily transferred to early Beta versions of Windows 7. More, as we worked together with large customers teams on migration preparations, we acquired extensive knowledge of this new operating system. Here we highlight some of the key lessons learned.
Critical step – the lab
An important factor prior to upgrading to Windows 7 is a comprehensive test of its new functionality in the target en-vironment and with the target software applications. It could happen for instance, that the automatic network detection feature of Windows 7 causes a network connection of a note-book to work correctly but only after the network type has been properly identified. End-users or administrators would get no notification of an improperly identified network – the network connection simply does not work.
More, the User Account Control (UAC) security feature, ad-ministrative access, and other security models updated with Windows 7 have to be thoroughly verified in the context of the applications to be used before setting out on installing Windows 7 everywhere.
Windows 7 is in fact an operating system with good back-wards compatibility features, but some of these features are disabled by default. Even with these compatibility features enabled, problems with older legacy applications may surface which will drive additional effort and cost of the migration project as some applications will require engineering of up-grades or workarounds.
The execution challenge:
Mixed Windows versions
One of the greatest execution challenges of any Win-dows 7 migration is that in most cases all systems will be migrated over time. The changeover to Windows 7 will likely be done over several phases and the migration will need to allow end-users to be productive in a mixed environment containing Windows 7, Windows XP, and even Windows 2000.
To reduce migration friction on the entire organization, existing capabilities such as operating system instal-lation, software distribution, security patching, client inventory, remote maintenance and other such similar SLA-bound services must persist for all Windows version clients. One key advantage to creating and operating a mixed version environment is that fall-back scenarios are facilitated, as in the case where certain critical systems must drop-back to older Windows versions in case of unexpected errors.
3
[Continued] ... good planning is essential for successful migration
Five important steps for migrating
to Windows 7
1. Hardware: Is existing hardware supported by
Win-dows 7? Does the performance meet the requirements for satisfactory Windows 7 operation? Will updated drivers lack certain features previously administered in Windows XP?
2. Software: Does existing software run under
Win-dows 7? Are updates necessary? Will macros, plug-ins and add-ons function with the new version of the soft-ware?
3. Training: Will users be prepared to handle Windows 7’s
improved user interface and different system behavior? Is the internal helpdesk ready to answer usability que-stions?
4. Rollout: Is there a tested step-by-step rollout process
plan which takes into account the additional load during this phase? Will more technical groups migrate first or will pilot groups be identified for rollout?
5. Parallel operation: Can Windows 7 be administered
with the same tools used for older Windows versions?
Does existing hardware meet the requirements?
Prior to upgrading to Windows 7, assuming the needed drivers mentioned above are available, hardware must be verified to ensure it is sufficiently stable and powerful. Although the actual requirements are lower compared to Windows Vista, hardware performance is considerably more critical compa-red to Windows XP. Newer clients, most designed for Vista and sold in the last three years, should have sufficient RAM and processor power to run Windows 7.
Usability and interface functionality built into Windows 7, such as automatic indexing, will consume a good deal of available performance. Power management is much more advanced, and will aggressively try to use ACPI functionality to save power and extend notebook battery life – besides being more noticeable to users, any instability in ACPI and ACPI-dependent system firmware, such as AHCI and IRRT, will be quickly exposed.
Identify such marginal hardware quickly with comprehensive inventory scans, and keep close track of models needing re-placement or firmware upgrades.
Does the migration timing meet requirements?
Finally, determine if it is the right time for a Windows 7 migra-tion. Windows 7 probably makes more sense if using Office 2007 or planning to migrate to the announced Office 2010, or to finally satisfy upgrading the aging infrastructure which was supposed to be upgraded to Vista over the last three years. If however those tried and true legacy applications are perfor-ming, it should be possible to plan any migration backwards from Microsoft’s anticipated Windows XP support end-of-lifeand continue working with the existing Windows versions for some time. The most optimal approach is to time the migration to Windows 7 together with new hardware and adoption of major productivity suites such as Microsoft Office 2010.
4
Rollout preparations
When preparing a rollout of Windows 7, proper end-user and helpdesk training is critical to acceptance. The modified user inter-face, the new security functionality and the likely updated behavior of new Windows 7 compatible applications will generate many questions. End-users and helpdesk staff must be trained to prevent hundreds of hours of internal support, and prevent general dissatisfaction backlash surrounding the new Windows 7 platform.
Windows PE
When discussing Windows 7 and Windows Vista installa-tion, “Windows PE” will come up. The Windows Preinstall Environment (Windows PE) is a minimized, bootable ver-sion of Windows which is required in the starting phase of the system installation. Windows PE is updated regularly. The preparation of the target system to be installed is done within Windows PE. This deployment environment is considerably more flexible and faster, but requires that drivers be integrated for Windows 7 and also for Win-dows PE. To help reduce some added driver management effort, Columbus uses the driver collections created for Windows PE to also facilitate the installation of older Win-dows versions, and drive imaging and system diagnostic functionality.
On the technical level, bear in mind that Windows 7 is more active than Windows XP and will drive increased configuration requirements and network load for the rollout. The timeframe and volume of the rollouts have to be planned carefully to make sure that other users will not be impacted in their daily work, and to fundamentally drive a smoother migration pro-cess. We recommend spreading the migration over some time and in controlled groups, performing the actual installations outside normal business hours or to rotate migration groups through a “staging lab” in which network configurations and load can be constrained.
Since Brainware has already acquired much experience with the deployment of Windows Vista and Windows 7, we are pleased to help in planning an optimum process for any situ-ation.
Full Windows 7 support required
In order to distribute Windows 7 efficiently throughout the network, the support of some new technologies is required. With Windows Image Management (WIM) at the core of pro-visioning the Windows 7 operating system, the only Microsoft supported environment is Windows PE. This mini operating system is used in the first stage of the installation process to identify hardware via PnP, allow for unattended options du-ring deployment, allow for repair and imaging functionality. Beyond getting Windows 7 installed and running, post-install services like system configuration, software distribution, inventory and security patch management must be fully sup-ported for this new operating system.
Industry leader in Windows 7 segment
Active in the early stages of Windows 7 Beta and in close coo-peration with its customers, Brainware has mastered the new Windows 7 functionality to offer more: Columbus exploits many Windows 7 features, and even extends some provided by default from Microsoft.
5
[Continued] ... Rollout preparations
Full Windows PE and Imaging support
An important benefit to customers is that Windows PE and imaging driven from Windows PE can be fully leveraged. The integration of new drivers and utilities in existing Windows PE boot images is a substantial effort which has been completely modularized and leveraged within Columbus. Moreover, sup-port for 32-bit as well as 64-bit versions of the Windows 7 and generally of Microsoft’s 6.1 version operating systems is indis-pensable. The installation and management of 64-bit systems is particularly evidenced by Microsoft’s release of Windows 2008R2 in the 64-bit only version.
Columbus protects packaging investments
Regarding software distribution, existing software packages can be pushed to Windows 7 clients as well as all older Win-dows operating systems. If the packaged software itself is compatible with Windows 7, the package investment is protected because the Columbus software package does not need to be modified.“Up to 80% of existing Columbus
packages can usually be reused
under Windows 7. Around 15%
may need upgrading to newer
versions, and 5% could require
re-engineering.”
6
No point solutions
The optimum integration of Windows 7 support with sup-port for older Windows versions is not achieved with a point solution, but with an integrated suite. Customers migrating to use Windows 7 will find the corresponding support also in all other modules of Brainware Columbus – from bare-metal operating system installation through the lifecycle chain up to asset, license and contract management.
Standardize management to reduce effort and cost
Though mixed Windows version clients break from the ideal standardized end-user system, the unified management ap-proach delivered by Columbus provides the benefits of stan-dardization even in a heterogeneous environment as clients, regardless of actual configuration, are all managed the same way. This management standardization capability is core to save cost, realize efficient deployments, carry out regular maintenance of user systems, and deliver services to end-users regardless of the Microsoft client or server operating system under real-world conditions.There are however two key limitations to be aware of with Microsoft’s Solution Accelerator. The first limitation is that Microsoft’s Solution Accelerator only supports Windows Vista and Windows 7 environments, and does not support older Windows versions or mixed version environments. The second limitation is that substantial commitment is required to a number of additional Microsoft products to deliver services like software distribution, inventory, patch management, remote maintenance and others to the user base during migration.
Integrated solution for mixed operation
As mentioned above, most migration scenarios will require the use of a comprehensive solution to cover all real-world environments and requirements. Without such a solution migration planning and execution is prohibitive. With Colum-bus, Brainware offers exactly such a comprehensive approach with full integration of Windows 7 support into its matured support capabilities for older Windows versions. The sum of these integrated capabilities offered by Columbus results in a solution that goes further than Microsoft’s support for Win-dows 7 migration alone.
Extended use of pre-Windows 7 tools
Apart from remote maintenance, additionally integrated tools include capabilities for system analysis and robust disk imaging in the Windows PE environment. These enhanced ca-pabilities can simply be administered and modified using the mechanisms of Columbus, allowing for example to adapt dri-vers and utilities in Windows 7’s Windows PE environment.
Maintain one Windows PE
For customers who need to use Windows 7 as well as older Windows versions over a longer period and manage mixed operating system deployments, having to manage just one Windows PE environment is very beneficial. Using multiple Windows PE environments to suit various Windows version drives higher maintenance efforts and chances for errors. Columbus enabled the use of only the latest Windows PE ver-sion to reduce the administration requirement and avoid this substantial cost overhead altogether.
Window 7 support alone is not enough
With Windows Vista and Windows 7 Microsoft improved operating system installation. The Microsoft Solution Accelerator for Business Desktop Deployment features supplementing tools which support imaging and distribution.
© 1989-2009 Brainware Solutions AG - All rights reserved Brainware Solutions AG Sumpfstrasse 15 CH – 6300 Zug Tel. +41 41 748 22 00 Fax +41 41 748 22 01 www.brainware.ch [email protected] Columbus-Brainware GmbH An der Bleiche 12 DE – 60437 Frankfurt/Main Tel. +49 800 748 22 00 Fax +49 800 748 22 00 www.columbus-brainware.de [email protected] Partner
About Brainware
Brainware is a leading provider of lifecycle and system ma-nagement solutions in Microsoft Windows based IT envi-ronments for servicing large and small firms globally. Its flagship “Columbus” management tool suite coupled with its workflow web-based solution, automates time consuming administrative efforts, improves overall reliability through automation, and substantially reduces the overall cost of IT management.
Brainware is delivering industry-leading customer support and term-project services in close cooperation with its part-ners throughout all aspects of the systems lifecycle manage-ment landscape.
