Operating System Installation and Software Distribution for Windows 7

Similar documents
IT Lifecycle Management Client- and Software Management Business-Processes

Outline SSS Microsoft Windows Server 2008 Hyper-V Virtualization

Course 6291A: Updating Your Technology Knowledge of Microsoft Windows XP to Windows 7 Beta

(Exam ): Configuring

Data Sheets RMS infinity

Windows 7, Enterprise Desktop Support Technician

Windows 7, Enterprise Desktop Support Technician Course 50331: 5 days; Instructor-led

Course Description. Course Audience. Course Outline. Course Page - Page 1 of 12

Administering and Maintaining Windows 7 Course 50292C; 5 Days, Instructor-led

Installing and Upgrading to Windows 7

Course Outline. ttttttt

Planning and Managing Windows 7 Desktop Deployments & Environments Version 7

50331D Windows 7, Enterprise Desktop Support Technician (Windows 10 Curriculum)

Simplify Your Windows Server Migration

Module 3: Resolve Software Failure This module explains how to fix problems with applications that have problems after being installed.

HP Client Automation software Starter and Standard Editions

ICT Professional Optional Programmes

Planning and Managing Windows 7 Desktop Deployments and Environments

Compliance series Guide to meeting requirements of USGCB

MS Planning and Managing Windows 7 Desktop Deployment and Environments

RayManageSoft. infinity. The new generation of Application Lifecycle Management

HEAT DSM Release Overview. Andreas Fuchs Product Management November 16th, 2015

How to Prepare for the Upgrade to Microsoft Dynamics CRM 2013 (On-premises)

"Charting the Course to Your Success!" MOC D Windows 7 Enterprise Desktop Support Technician Course Summary

MS MCITP: Windows 7 Enterprise Desktop Support Technician Boot Camp

Backup Exec System Recovery Management Solution 2010 FAQ

Device Lifecycle Management

Planning and Managing Windows 7 Desktop Deployments and Environments

Planning and Managing Windows 7 Desktop Deployments and Environments

Kaseya IT Automation Framework

Streamlining Patch Testing and Deployment

Top 10 Reasons to Virtualize VMware Zimbra Collaboration Server with VMware vsphere. white PAPER

NE-6294A Planning and Managing Windows 7 Desktop Deployments and Environments

HP Client Manager 6.1

Operating System Migration

eguide: Designing a Continuous Response Architecture 5 Steps For Windows Server 2003 End of Life Success

Maintaining Microsoft SCCM Health with Absolute DDS

inforouter V8.0 Server & Client Requirements

IT Asset Management. Introduction to an effective IT management with Spider Asset

Table Of Contents. - Microsoft Windows - WINDOWS XP - IMPLEMENTING & SUPPORTING MICROSOFT WINDOWS XP PROFESSIONAL...10

Implementing and Supporting Microsoft Windows XP Professional

Data Sheet: Endpoint Security Symantec Endpoint Protection The next generation of antivirus technology from Symantec

System Management. What are my options for deploying System Management on remote computers?

Planning and Administering Windows Server 2008 Servers

Business Value of Microsoft System Center 2012 Configuration Manager

MS 50292: Administering and Maintaining Windows 7

Data Sheet: Backup & Recovery Symantec Backup Exec System Recovery Windows Small Business Server Edition

Symantec Backup Exec System Recovery

HP Client Manager 6.2

Solution Recipe: Improve PC Security and Reliability with Intel Virtualization Technology

SSM6437 DESIGNING A WINDOWS SERVER 2008 APPLICATIONS INFRASTRUCTURE

Table of Contents Release Notes 2013/04/08. Introduction in OS Deployment Manager. in Security Manager Known issues

Accelerating Microsoft Windows 7 migrations with Citrix XenApp

BEST PRACTICES. Systems Management.

THE COMPLETE VIEWER FOR MS PROJECT. Deployment White Paper

Sage CRM Technical Specification

F. Hoffmann-La Roche AG chooses enteo NetInstall to manage software packaging and distribution

ManageEngine Desktop Central Training

Installing and Configuring Windows 7 Client

Configuring Windows Server 2008 Active Directory

Business Virtualization

Data Sheet: Backup & Recovery Symantec Backup Exec System Recovery The Gold Standard in Complete Windows System Recovery

Windows 7 Upgrade Risk Mitigation Planning: Ensuring Windows 7 Upgrade Success

Chapter 5: Operating Systems Part 1

EMA Product Brief: Desktop Virtualization with Quest

Cursuri Certificare Microsoft

Configuring and Administering Windows 7

White paper. Rapidly Deliver Microsoft Offi ce 2007 with Citrix XenApp

A+ Guide to Software: Managing, Maintaining, and Troubleshooting, 5e. Chapter 3 Installing Windows

Microsoft Windows 7. Administration. Instant Reference. William Panek WILEY. Wiley Publishing, Inc.

Module BITadd (BIT Active Directory Design)

Table of Contents. Introduction. Audience. At Course Completion. Prerequisites. Microsoft Certified Professional Exams

Northwestern University Dell Kace Patch Management

Sage CRM Technical Specification

Course 50322B: Configuring and Administering Windows 7

Course 6292A: Installing and Configuring Windows 7 Client. About this Course. Audience Profile

Designing a Windows Server 2008 Applications Infrastructure

Augmenting VMware View Horizon (VDI) with Micro Focus Client Management

Reducing the Cost and Complexity of Business Continuity and Disaster Recovery for

Installing and Configuring Windows 7 Client

IT & Asset Management Training Workshops

Course 6437A: Designing a Windows Server 2008 Applications Infrastructure

Windows 7, Enterprise Desktop Support Technician

Workstation Management

Convergence of Desktop Security and Management: System Center 2012 Endpoint Protection and System Center 2012 Configuration Manager

Optimos Enterprise Helpdesk Automation Solution Case Study

Effective Use of Individual User Profiles with Software Distribution

Only Athena provides complete command over these common enterprise mobility needs.

Administering Windows-based HP Thin Clients with System Center 2012 R2 Configuration Manager SP1

Virtual Patching: a Proven Cost Savings Strategy

Transcription:

Data sheet Operating System Installation and Software Distribution for Windows 7 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 administration of Windows 7, to protect current investments and deliver a smooth step-by-step transition, an appropriate system lifecycle management solution is needed that can concurrently handle Windows 7, older Windows versions, and a productive mixed-version environment. Windows 7 supports easier deployment Columbus enables this while providing a smooth migration process across mixed Windows versions. Many companies have postponed upgrading their existing Windows XP environments due to the much publicized challenges of Windows Vista reported in the media. Windows 7 s many improvements have earned positive reception, but along with its improved features come Columbus the ideal solution for Windows 7 management Windows PE 2 support for increased performance 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 modular 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 some significant changes in security, operating system upgrades and bare-metal installations, collaboration, legacy application compatibility and other such fundamental areas. To benefit from the more productive and stable environment offered by Windows 7, every company will have to decide on the right approach and timing for migrating to Windows 7.

2 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 earlyadopter 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 environment 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 notebook 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, administrative 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 backwards 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 upgrades or workarounds. The execution challenge: Mixed Windows versions One of the greatest execution challenges of any Windows 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 installation, 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. Legacy Hardware the challenge A significant migration problem is to decide which hardware makes the migration list and how to get that existing hardware 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 versions 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.

3 [Continued]... good planning is essential for successful migration 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 compared 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 replacement or firmware upgrades. Does the migration timing meet requirements? Finally, determine if it is the right time for a Windows 7 migration. 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 performing, it should be possible to plan any migration backwards from Microsoft s anticipated Windows XP support end-of-life Five important steps for migrating to Windows 7 1. Hardware: Is existing hardware supported by Windows 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 Windows 7? Are updates necessary? Will macros, plug-ins and add-ons function with the new version of the software? 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 questions? 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? and 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 interface, 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. 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 process. 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. Windows PE 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 situation. 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 provisioning 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 during 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 supported for this new operating system. When discussing Windows 7 and Windows Vista installation, Windows PE will come up. The Windows Preinstall Environment (Windows PE) is a minimized, bootable version 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 Windows 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 Windows versions, and drive imaging and system diagnostic functionality. Industry leader in Windows 7 segment Active in the early stages of Windows 7 Beta and in close cooperation 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, support for 32-bit as well as 64-bit versions of the Windows 7 and generally of Microsoft s 6.1 version operating systems is indispensable. The installation and management of 64-bit systems is particularly evidenced by Microsoft s release of Windows 2008R2 in the 64-bit only version. 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. Columbus protects packaging investments Regarding software distribution, existing software packages can be pushed to Windows 7 clients as well as all older Windows 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.

6 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. 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. No point solutions The optimum integration of Windows 7 support with support 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. 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 Columbus, 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 Windows 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 capabilities can simply be administered and modified using the mechanisms of Columbus, allowing for example to adapt drivers 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 version to reduce the administration requirement and avoid this substantial cost overhead altogether. Standardize management to reduce effort and cost Though mixed Windows version clients break from the ideal standardized end-user system, the unified management approach delivered by Columbus provides the benefits of standardization 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 end-user systems, and deliver services to endusers regardless of the Microsoft client or server operating system under real-world conditions.

About Brainware Brainware is a leading provider of lifecycle and system management solutions in Microsoft Windows based IT environments 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 partners throughout all aspects of the systems lifecycle management landscape. Brainware Solutions AG Sumpfstrasse 15 CH 6300 Zug Tel. +41 41 748 22 00 Fax +41 41 748 22 01 www.brainware.ch info@brainware.ch 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 info@columbus-brainware.de Partner 1989-2009 Brainware Solutions AG - All rights reserved