ABOUT

CloneDeploy 1.3.0 Beta 1 Released 8-28-2017

The first beta for CloneDeploy 1.3.0 is now available.  I typically don’t like betas, but this version calls for a lot of testing before it can be considered stable.  Hopefully the community can step up and provide feedback in order to get this moved to stable as soon as possible.  The beta is fully featured, but there are many bugs to be worked out.  Major changes include:

  • Major code rewrite – Front and back end are now two totally separate web applications
  • Multiple CloneDeploy servers can now be clustered together to provide separation of Image Server, Tftp Server, Multicast Server, and Front End.  All the services can be load balanced across the servers.
  • ProxyDHCP has been updated to allow load balancing / failover of Tftp servers
  • Complete API
  • MacOS Sierra support
  • Complete client iso / usb generation from within the web ui.  No need for external tools.
  • Distribution points can now point directly to other shares.  No need to mount them on the server.
  • Computer registration now uses a unique identifier, meaning you can register a usb nic multiple times to different computers

Sadly, a replication service, to sync all images across the servers did not make it in.  That will be top priority for 1.4.0.  There are still some styling fixes to apply to the front end that I am aware of.  I expect many bugs to be found, but they should all be simple fixes once found.  Please post your findings in the 1.3.0 Forum beta channel.  You can grab the beta at the downloads page.

 

 

What Is CloneDeploy?

CloneDeploy is a free open source solution for computer cloning / imaging. It is an alternative for other solutions such as Symantec Ghost Solution Suite, Acronis Snap Deploy, Windows Deployment Services, DeployStudio, etc. It supports imaging Windows XP through Windows 10, Linux, and OS X, using both Unicast and Multicast technologies.

Features.

  • Multiple Imaging Environments for greater compatibility
  • MBR and GPT
  • Legacy BIOS and EFI
  • Full LVM Support
  • Full Extended/Logical Partition support
  • NTFS, FAT, ext2, ext3,ext4, hfs plus, xfs
  • Cloning to smaller drives
  • Automatic computer renaming
  • Client booting from USB/ISO/PXE/NetBoot
  • Simple Web Interface
  • Completely automated imaging
  • Custom scripting
  • Multicast
  • Can be installed on Windows, Linux, and FreeNAS
  • Bare Metal Restores

Is It For Me?

CloneDeploy was created to be used primarily in schools or small businesses. It can be used to image 1000’s of computers (probably not all at once). It should be used with an existing infrastructure. Meaning, a network with managed routers / switches, DHCP server, etc. CloneDeploy is intended to be installed on a server that is always running to ensure imaging is readily available.

How Does It Work?

CloneDeploy is a managed solution consisting of two parts. A server side component and a client side component. The server side is installed on Windows or Linux and the UI can be accessed from any web capable device within your network.  There are 3 different clients in order provide greater flexibility / compatibility.  One based on WinPE, one on Embedded Linux, and one on Mac OS X.  Imaging is achieved through your network with the use of PXE booting and WOL or you can use the standalone client iso for CD booting or USB booting. To achieve the best results all of your clients are added to CloneDeploy, then you simply search for the computer you wish to deploy and start the task. The client will automatically turn on and begin to image. Imaging can be accomplished without ever being present at the physical machine’s location.

What it is NOT.

  • CloneDeploy is NOT a backup solution and should never be used as such.  It is only intended to provide imaging capabilities for generic images that do not contain irreplaceable data.
  • CloneDeploy is NOT an unattended installation of Windows.  CloneDeploy is a cloning program.  It creates an image of an existing machine that can then be deployed to other machines.  Yes, it could be thought of as unattended because it is totally automated, but there is a difference.
Comments are closed.