Win7 OS Development / Deployment
Deployment of Microsoft (MS) Windows 7 Operating System or Win7 OS as it is commonly known, throughout an organization can be organized into three phases – 1) Win7 OS image design, 2) application deployment/functionality testing/remediation and 3) end-user image deployment. While planning will be ongoing on each phase simultaneously end-user image deployment will require the base image(s) and some level of application testing. MS has expanded and enhanced the toolkits available to the organization for creating and managing Win7 OS. Two of the most useful for this task are the Microsoft Deployment Toolkit (MDT) and System Center Configuration Manager (SCCM).
Image design – (4 wks. to 3 mos.) this is the most critical phase as it is the driver for all of the following stages. The image design is centered around the preferences of the organization and how they desire to deploy – the ‘thick’ vs. ‘thin’ approach. The ‘thick’ approach is an attempt towards a single – one size fits all image. The approach attempts to include all drivers, applications, software updates and image customizations in an attempt to deploy a single image to all users or as is commonly called ‘all-in-one’. The main issue there will be the size of the image and how it is to be delivered. The other end of the spectrum is the ‘thin’ approach which delivers the standard OS image, required drivers and maybe a few standard applications. Some will refer to this as the ‘hybrid’ design as the image contains organizational required applications with the OS deployment. The idea with thin image is minimalist which is critical when deploying via the organizational WAN. The organizational software inventory is the common driver in both of these approaches and is probably the weighting factor in what direction an organization takes. Creation and management of the image are most easily accomplished with the MS MDT tool even if the organization utilizes the MS SCCM for application management throughout the organization. For organizations that require multiple images due to customizations such as screen savers and need to manage multiple language packs or install applications that cannot be distributed utilizing SCCM, using Group Policy or custom scripts will help the organization manage this process. If the organization does not have Win7 SME’s in house MS Consulting Services or other 3rd party consulting services can be engaged to ensure this phase is completed to the requirements of the organization.
Application testing – (time dependent on # of applications) will be a critical and time consuming activity depending on how the organization decides to approach the issue – in-house testing or contract to an outside service organization. No matter which approach the organization takes to solve the issue it will take considerable organizational resources to accomplish. There are two parts to this phase – application deployment testing and application functionality testing. Deployment testing will need to be done via the methodology the organization utilizes to deploy applications to the end user. If the organization has an internal deployment package team, remediation for most deployment packages can be accomplished relatively quickly. Some might require assistance from the SW developer or an outside consulting service. Application functionality testing is the second piece of the puzzle and must be done on a Win7 platform. While most applications can be functional tested on a virtual platform some will need to be tested on physical machines which represent the user’s actual physical environment. Monitoring of the progress of this process will be a driver for deployment.
Deployment – (time dependent on deployment methodology) methodology will be driven by many factors including the organizations end-user support system design, tolerance for end-user interaction with the OS deployment process and deployment time horizon. Deployment methods are either High-touch, Lite-touch or Zero-touch and will be driven mainly by the number of OS clients to deploy. An organization with client computers over 500 or more Zero-touch with push automation is the recommended and logical method for OS distribution. It does however require the most up-front prep work and will require the organizations to have resources who are SME’s in MS tools as well as networking and deployment methodology. Image design and application testing are the precursor phases for deployment. The organization will need to decide how they desire to manage the deployment process e.g. by site or user group. Either method is dependent on managing and monitoring the application testing process as individual end-user deployment is of course dependent on all of the applications being available for deployment. For a large deployment the development of an automated tool to match Win7 compatible applications against user inventory is highly recommended.