Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Saturday, June 19, 2010

Disk duplication

The Microsoft policy concerning disk duplication of Windows XP installations
fogproject.org
kbox
Dell KACE

K-image

The K2000 K-image format is file based so that images can be easily edited, eliminating the need to rebuild images. Its single instancing technology minimizes the time, bandwidth and storage required to capture and archive disk images. Efficient state management allows for lightning-fast reimaging of systems by bypassing redundant file transfers and only applying changes to the original image. The agentless feature of other K2000 components extends to disk imaging. Administrators have the ability to execute fully automated bare metal system build-outs.

Pre and Post Installation Tasks

A vast amount of work needs to be performed both before and after the deployment of an image. Performing this work manually negates the benefits achieved by partially automating the deployment process. The K2000 Deployment Appliance supports pre and post installation tasks to be included as part of the image deployment process. By utilizing pre and post installation tasks, administrators can fully automate systems deployment and work with thin images—key components of systems deployment best practices. K2000 pre installation tasks include disk, RAID and BIOS configuration while post installation tasks include sysprep automation, domain joining, service packs, and application and script deployment.

Change the SID and computer name of a cloned virtual machine

======================
Acronis SnapDeploy can deploy Win7 & 2008 images. Paid product 
drbl-winroll.org claims to work with Win7.
Can also be used in tandem with Clonezilla to do massive cloning across network.
---------------------------
For XP, Vista and Win 7.
MDT is prolly alot easier in my opinion, no hardware dependence, only 1 image per OS...
Injects drivers just before the image starts, automates all syspreping when creating the image.
Put it this way, to create a new image, I boot a computer into a PXE environment (usually a virtual), let it install the OS, Software, patches, registry tweaks etc, sysprep, reboot, capture the image, upload image to the server.
That entire task, I have hit F12, and clicked the OS i want the image based on and hit next, and walked away.
The put a image on a computer, I hit F12 into sysprep, choose the OS Image I want to use, type in computer name, hit next, walk away, and it'll image, inject drivers, boot into mini-setup, join to the domain with the right name, install any specific software for that lab (based on computer name).
This is in an education environment, a whole new lab can be up and running without having to worry about creating a whole new image for a new set of hardware, all i need to do is pull the drivers into MDT, it takes care of the rest, so a room can be unpacked and setup in roughly 1 hour.

No comments: