AUTOMATED DEPLOYMENT OF WINDOWS 7 6
Automateddeployment of windows 7
AutomatedDeployment of Windows 7
Mostof the businesses have shifted from the use of old operating systemsand started using windows 7. It is because of the resultant benefitsof the use of this operating system. The approaches and tools for thedeployment of windows seven that makes sense for an enterprisedepends on the extent on how the enterprise has allied itself withthe Microsoft. Enterprises have received significant economicadvantages out of the use of windows 7. Various factors need to beconsidered before making an automated deployment of windows 7. Thedocument focuses to the factors considered as well as the process ofmaking an automated deployment of windows seven in an enterprise(Finnet al., 2011).
Variousfactors need to be assessed before the deployment of windows seven inan enterprise. The first step is to consider the ability of theavailable hardware to use windows 7. The best way in assessing is theuse of the MAP toolkit 7.0. It is also termed as the Microsoftassessment and also planning. It main role is the creation of theinventory of the hardware. The inventory includes the operatingsystem of the hardware, drivers and also the software (Hashimi& Hashimi, 2006).
Thesecond step is the consideration of the compatibility of theapplications with the windows 7. The assessment is done by the freetool offered by Microsoft that enables one to validate thecompatibility of the applications to windows 7. The toolkit isreferred to as the ACT. The third step in the deployment of windowsseven is the determination of the operating system images to use. Theenterprise has to determine on whether to use a thin image or a thickimage. In the thin image method applications are installed afterwardswhile on the thick image method applications and the operating systemare installed together. Another method is a hybrid method where theoperating system is installed together with the core applicationsthat are of importance to the users (Finnet al, 2011).
Thefourth step is to determine the tool to be applied in the imagedeployment. There are several tools that are present for any imagethe enterprise chooses. The tools apply in the management, creationas well as deployment of the image to windows 7. Some of the toolsthat are owned by Microsoft include WAIK (Windows AutomatedInstallation Kit), WDS (Windows Deployment Service) and the MDT(Microsoft Deployment Toolkit) (Hashimi& Hashimi, 2006).
Thebest method of making the automated deployment of windows seven isthe use of MDT 2010. It is because there is no additionalinfrastructure that is needed than the available server. The use ofMDT 2010 is also cost effective to the enterprise. It is becausethere are fewer support calls and the configuration is consistent.The investment in the infrastructure is also insignificant. The MDT2010 has several benefits associated with it there are fewerproblems mainly because the configurations are reliable in all thecomputers. The deployment is also easier because the MDT 2010 usesdevice drivers, handles apps and installation updates. There is alsostreamlined maintenance because of the ease in the deployment ofapplications, device drivers and updates (Finnet al, 2011).
Theautomated deployment of windows seven entails the following steps.The first step is the enterprise assessment of its readiness to makethe deployment. The enterprise can make the use of the MicrosoftAssessment and also planning toolkit. The second step is to determinethe compatibility of the application with windows 7. The enterprisecan make the use of ACT in the determination. It enables theenterprise to remediate and also triage the apps that have problemsin compacting. Preparation of infrastructure for the deploymentprocess is the third step. The file server needs to be created forthe MDT 2010. The enterprise can also choose to use the WindowsDeployment Services of the Windows Server 2008. The easiest way inthe network deployment is initializing client computers using theservices of deployment offered by windows (Hashimi& Hashimi, 2006).
Thefourth step in the deployment is the installation of the MDT 2010together with the essential components. They get installed on theserver file together with Windows AIK and other components needed bythe server. The enterprise also needs to establish a deploymentshare. It then gets incorporated with OS, device drivers, apps andalso updates. The enterprise also needs to put into place a tasksequence that is capable of installing windows 7. There is a need tocreate and also customize the configuration that is required fordeployment in the case of MDT 2010. There are instructions that areconsidered for the installation of windows seven task sequences (Finnet al., 2011).
Theenterprise also has to create boot images. The media needs to beestablished for the deployment share. The images are also required tobe copied to a device that is portable. It may be a DVD, UDF or a USBflash drive. Windows seven is then deployed to each and everycomputer in the enterprise. The final step is to activate the windows7. It can get activated with Microsoft on the occasion that theenterprise does not make the use of the KMS (Hashimi& Hashimi, 2006).
Theautomated deployment of windows seven is of great benefits to anyenterprise. The enterprise achieves efficiency in its operationsleading to success. However, there are various limitations associatedwith deployment of windows 7. It needs limited interactions at theinitial stages of the installation. With the growth of theenterprise, they can later involve the MDT 2010 that offers almostzero-touch experience. It only makes the use of the WindowsDeployment Services and the configuration of the database.
Finn,A., Gibson, D., & Van, S. K. (2011). MasteringWindows 7 deployment.Indianapolis, Ind: Wiley.
Hashimi,S. Y., & Hashimi, S. I. (2006). Deploying.NET applications: Learning MSBuild and ClickOnce.Berkeley, Calif: Apress.