Author: clonedeploy

CloneDeploy 1.3.0 Beta 1 Released

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.

Samba Vulnerability 5-24-2017

If you installed CloneDeploy on Linux you should probably patch Samba.  There is a new vulnerability that effects all versions over the last 7 years.  As long as you didn’t open your smb share up to the internet(who would do that?) you should have little to worry about, but I would still patch anyway.  Since we are on the topic, I’m guessing you know about WCry.  Since CloneDeploy uses SMB shares to transfer images, make sure your Windows OS is patched to fix the SMB vulnerability in Windows also.

CloneDeploy Proxy DHCP 2.0.0 Released

  • Complete code rewrite – more efficient now
  • Fixes bug where the proxy server would not respond to requests forwarded by an ip helper / relay
  • Added support for DHCP relays that use option 82
  • Works properly on Linux with Mono now
  • Added option to generate Apple NBI list string without the need for CloneDeploy Server
  • Added support for WinPE – Needed for next CloneDeploy release
  • Added integration with CloneDeploy to check for reservations stored in the CloneDeploy Web Interface – In next CloneDeploy release
  • Grab the new version from the Downloads page

And now for some CloneDeploy 1.2.0 news:

  • WinPE support is approximately 75% done
  • A utility to easily create the WinPE imaging environment for use with CloneDeploy has been finished
  • CloneDeploy Proxy DHCP has been updated to support WinPE
  • Bug fixes and feature requests are under way
  • Anticipated release date is late September – early October

CloneDeploy Patch 1.1.1 Released 6-27-16

  • Fixes a bug when using the Linux imaging environment where the minimum hard drive size required for the image is calculated incorrectly when using a File based image with LVM
  • Fixes a bug when using the Linux imaging environment where LVM partitions do not deploy if the volume group or logical volume contains a dash(-) in the name
  • Fixes a bug when using the Linux imaging environment where the On Demand image list is blank if you upgraded from a previous version
  • Fixes a bug when using the macOS imaging environment where images could not be uploaded because the SMB share was connected as the read only user
  • Fixes a bug when using the macOS imaging environment where the wrong logical block size may be used when creating the partitions
  • Fixes a bug in the WebUI where the Approve Image option is available when it should not be

CloneDeploy 1.1.0 Released 6-18-16

As usual I was hoping to get more into this release, but I felt it was time to release what was done.  Click here for the changelog.

Important: This is currently only for new installations.  I hope to have an upgrade pack as well as upgrade documentation available later this week.  DO NOT attempt to upgrade until those are available.