This paper will describe the factors, which must be considered when planning and designing a system image. Evaluating the previous work is an important part of developing segmentation methods for the image analysis techniques. A system image refers to an actual duplicate of drivers. By evasion, a system image contains the drivers required for windows to run. It also encompasses computers’ system settings, programs, and windows files. The user can make use of system image in restoring the stuff of the computer if the hard disk or even the computer constantly stops working. The computer formulates a whole restoration when it is restored. The user cannot select specific files to restore. All of the system settings, current programs, and files are substituted with contents of system image. However, this variety of backup contains the user’s personal data. It is recommended that, the backing up of files is regularly done using Windows Backup in order restore specific files and folders as it is required. When the user sets up Windows Backup, windows chooses the files back up while it leaves out some. On the other hand, the user can select the things that require to be backed up and whether the user requiresto include a system image (Kamau, 2012).
Windows SIM is a tool that is used to open Windows images, create report files, and manage allocation shares and design sets. Windows SIM (Windows SIM) generates and administrates unattended Windows Setup report folders in a graphical user interface (GUI). Windows SIM itself cannot transform windows image system. It only used to design an answer folder. The produced answer file is useful as it is used during window installation and Windows Setup to apply settings. Windows SIM do not make any settings change in a Windows image file. Windows SIM is responsible for enabling the user to design an answer file that is used in times of Windows Setup. The user is able to view all the mechanism available inside a Windows image. The user is able to add gear settings to the answer file. The user has the potential to determine the times to apply mechanism settings by affixing it to a specific setting pass. Once the component configurations are attached to an unattended answer folder, the user now adopts the full powers to view and customize all available settings regarding any component.
DISM (Deployment Image Servicing and Management) is a tool that is employed to unlock windows images, design answer files, and administer allocation shares and settings sets. It as well runs updates, language packs and drivers to the windows image. Deployment Image Servicing and Management are accessible in all setting up of Windows 7. The user can make use of DISM to repair a Windows image and when preparing a Windows PE image. The user can as well use it to activate or deactivate Windows features allocated in an image. DISM is also useful when upgrading a Windows image to obtain a different edition, add and/or remove, and catalog packages. If the user targets for offline based servicing regarding unattended answer folder, DISM is an important tool which will ensure it completely and satisfactorily done (Kamau, 2012). It is possible to service an image hosted by 64-bit host to a 32-bit image and as well service an image hasted by 32-bit to a 64-bit image.
ImageX is a tool that is used to captures, design, adjust, and relate Windows image
It is a command based line tool which facilitates original equipment manufacturers (OEMs) and corporations to confine, to adjust, and to assert file-based disk images that are necessary for faster deployment. ImageX tool works together Windows image files for replication to a network. It can as well work together with various technologies that make use of Window image files like Operating System Feature Deployment Pack, Windows Deployment Services (Windows DS), Windows Setup, and the System Management Server (SMS). If the user intends to change the location of a Windows image to another computer, the user must run sysprep even if the other computer has similar hardware settings. The sysprep /generalize is a command tool that eliminates special data from Windows installation, and enables the user to salvage that image on another computer. Once the user boot the Windows image the next time, the specialized settings pass runs. When these configurations pass runs, various components have procedures that have to be processed when the user boot a Windows image based on another computer. All methods of transferring a Windows image to another computer be it through hard disk duplication, imaging, or other method, it have to be organized with the sysprep /generalize command. Copying or moving a Windows image to another computer without conducting a run sysprep /generalize is not at all supported.
Windows Pre-installation Environment (Windows PE) 2.0 is a minimal Win32 operating system. It has limited functions that are built based on Windows Vista kernel. Some of the functions include preparing the computer for the purpose of Windows installation, copying disk images hosted from a network data provider as well as initiating Windows Setup. There are several tools that are used to design and set Windows PE environments and are located in the window AIK. Windows PE is not build as the basic operating system for a computer. However, it is instead applied as individual pre-installation settings and as a fundamental constituent of various setups. It is also used for recovery technologies like Windows Deployment Services (Windows DS), Systems Management Server (SMS), Setup for Windows Vista, Deployment Feature Pack, Operating System (OS) and Windows Recovery Environment (Windows RE) (Kamau, 2012).
USMT 4.0 is a tool that is used to transfer user information to window 7 from a prior version of Windows. USMT is mounted as a main part of Windows AIK in %Program%/Windows AIK/Tools/USMT directory. (USMT) 4.0 (Windows® User State Migration Tool) is scriptable instruction based line tool. It offers a professional customizable user profile transfer knowhow for computer professionals. There are to components in USMT that includes LoadState and ScanState. They are available in form of modifiable sets of .xml files, MigUser.xml, MigApp.xml, and MigDocs.xml. Additionally, the user can build custom .xml files in order to buttress their transfer requirements. The user can also design a Config.xml specification and settings file to prevent from the transfer.
Sysprep (System Preparation) tool is a modern technology that computer users can use combined various deployment tools in order to mount Microsoft Windows operating systems. It is advisable as the process invites minimal intervention by a technician or an administrator. Sysprep is basically used all through large-scale rollouts. This cuts the cost and time to have a technician or an administrator to interactively fix the operating system for the user’s computer (Kamau, 2012).
The following steps creating and executing a reference image;
- Build the answer file that will automate the fixation of Windows 7.
- Authenticate and save the settings.
- Constitute a reference fixation.
- Design the bootable Windows PE optical disk of UFD. It should hold the ImageX Windows AIK tool.
- Confine the fixation using network share.
- Arrange the image as of a network share.
The three best practices that should be implemented when creating a system image are;
- Always make sure you have a back-up image copied to a DVD. Or in other words copy the image to a DVD.
- Create a system repair Disc.
- create a back up
- Click on the start button go to getting started and then, select back up files.
- Click on create a computer system image hyperlink.
- Make a decision on the position you will save the image. The following choices are favorable; burn to various DVD’s, external drive, or even store on a network location.