| Using PC Cloning Technology To Speed Networked PC Deployments |
|
|
|
| Saturday, 29 November 2008 | ||||
Halaman 1 dari 2 Once, the deployment and configuration of new PCs was one of the most time consuming tasks of a reseller or systems integrator. However, a new method with some new technology now makes a different approach to disk cloning possible and the time it takes to configure a new PC can be reduced from hours to minutes. Disk cloning lets you take a snapshot image of a source computer's hard drive and transfer that image to another computer. This snapshot is not just a copy of files and directories, but a detailed copy or image of everything on the drive, including OS file formatting, FAT tables, drive partition information, and so on. This image of the drive can be transferred to another computer, making its drive contents an exact replica of the original computer. In the following sections, we'll quickly describe how and why the process works. (The Fig shows each of the major components of a network disk cloning system.) The imaging application is a program that creates an image file and uploads it to the network server. Put simply, an image file is a file that contains a "picture" or "image" of one or more hard-drive partition(s) of a "source" PC. Any fully installed and configured PC may be used as a source machine from which to create an image file. If the source PC has been configured with applications and data files in addition to the operating system, then the image file will include both the operating system and its associated applications and data files. When uploading an image file from the source machine onto the server, the imaging software first prompts the user for a filename and target folder (directory) where the image file will be stored. Typically this will be the folder on the network server or shared device where the master library of images is stored. The imaging software then displays the partition table of the source PC, allowing the user to select the desired partition(s) to be included in the image. The imaging software is also invoked during the download process. When downloading an image file, the imaging software searches the database for the Alias/Name of the PC being configured. If the specified Alias/Name is not found, the agent automatically brings up a menu that allows the user to assign or randomly select an Alias/Name. Once the Alias/Name is selected, the imaging software determines which image is to be downloaded and whether or not to image the target machine as a Sender or Receiver. The first PC to come up as "live" during an image broadcast session will be assigned as a Sender and all subsequent PCs will become Receivers. Senders receive the image from the server, write the image to the designated partitions, and resend the image to all Receivers. Receivers simply write the image to the designated partitions. The imaging software's final function is to reboot the now cloned PC. The client configuration agent can run manually or it can be included in the image file, installed as part of the cloning process by the Imaging Software to run as a service following the boot sequence. This client configuration agent requires the use of a source file, which is placed on the hard drive by the imaging software during the imaging process. The source file contains specific configuration information such as IP address and computer name, which is unique to that PC. If this source file is found, the configuration agent makes changes to the registry as specified by the source file. If the source file is not found, the client configuration agent prompts the user for the required information. When its task is completed, providing no errors have been logged in the error log file, the client configuration agent deletes the source file, its own executable, and the error log file. Optionally, the client configuration agent updates the status for the specific PC being configured in the Name/Alias object in the status database. The client configuration agent displays critical error and informational messages on the screen while it is running, regardless of the mode. Other errors and messages are written in a .LOG file at the root of the partition containing the system root directory. Configuration Database/Status Database The configuration database is a set of data files on the server that contain specific configuration information for each PC to be configured. It stores configuration values such as IP Address, Computer Name, and other configuration values, which are unique for each target machine. The configuration database also functions as a status database providing reportable status information to the disk cloning console on each individual PC while the PCs are being cloned and configured. The configuration database is created and managed using the disk cloning management console. The management console provides the interface where the vast majority of the user interaction will be performed. Its initial function is to allow the user to create a configuration SET. A configuration SET defines a group of machines to be configured and includes Names/Aliases and configuration values for each PC in the configuration set. Each Name/Alias within the "Set" contains the IP Addresses, Computer Names, Domain Names, Product Names, Product Numbers, and related information that may be required by the Client configuration agent when actually performing the client configuration task for the target PC. The Management Console displays the current status of each Name/Alias in a given SET while the download and configuration processes are running. This allows the user to quickly view the progress of each PC as it is being imaged and configured. Partition/Disk Image Files The Imaging Software creates the image files and contains a snapshot or picture of one or more partitions of the source machine's disk drive. Typically, these files are compressed and stored on a network file server and become part of a library of image files, which the imaging software can use to install and configure a target PC at any time. Image Files also provide a convenient way to re-image a PC in the event of a major failure as part of a disaster recovery strategy within an IS department. The following sequence of operations outlines the steps an integrator might perform in order to use disk cloning technology to fully deploy systems within an organization. Step One: Create An Image File A source PC should be configured to contain the desired Operating System, Applications, and any associated Data File, if required. The Client Configuration Agent should also be installed on the source PC along with the Security ID generation (SIDgen) tools for NT if the image will be used to install and configure NT machines. This PC is then rebooted, using a bootable DOS floppy. A network connection is established with a drive letter mapped to the folder (directory) on the server where the image file will be stored. The Imaging Software is then used to create an image file of the source PC's hard drive partition(s). |
||||