Changing The Image Storage Location

If you want to change where images are saved, there are two components that need updated.  The SMB share on the server and the Distribution Point in the Web Interface.  This process also varies depending on if you will be storing the images on the local CloneDeploy Server or somewhere else like a NAS, SAN, File Server, etc.  I will outline the process for each.

I.  Alternate Storage Location On Local Server

  1. Disable the existing share located at program files\clonedeploy\cd_dp
  2. Create a new directory at your desired location with a name of your choice.  I will use c:\myshare for this example.
  3. Inside that directory create two more directories – images and resources
  4. You should now have a directory structure that includes c:\myshare\images and c:\myshare\resources
  5. Create a new share at the base c:\myshare directory
  6. Give the share a name of your choice
  7. When CloneDeploy was installed 2 local user accounts were created cd_share_ro and cd_share_rw – Add the users to the share permissions, giving cd_share_ro read access and cd_share_rw change access.  If you want to create your own accounts instead of the pre-installed accounts feel free to do so.  If you need to use a domain account be sure to use an account with the least permissions possible, never use an admin account.  Update the security permissions to match.  cd_share_rw modify and cd_share_ro read and execute
  8. Next the CloneDeploy Web Application also needs permission to write to this directory.  Add the user IIS_IUSRS to the security permissions of the c:\myshare directory with Modify permissions.
  9. Test your share from another machine using those 2 accounts
  10. Open the CloneDeploy Web Interface and go to Admin -> Distribution Points
  11. Select View on the primary distribution point
  12. Update the following fields to reflect any changes you made share name, domain, read write username, read write password, read only username, read only password it is possible that none of those fields need changed.
  13. Update the physical path to your shared directory, in this example it would be c:\myshare
  14. Click Update Distribution Point


I.  Alternate Storage Location On Remote Server

There are really only two ways to do this each has it’s pros and cons.

A.  Block Level (iSCSI , Fibre Channel)

This is the easiest as far as CloneDeploy configuration.  Just mount the block device to your CloneDeploy server and follow the previous guide for Alternate Storage On Local Server.  In this scenario CloneDeploy will still remain as the SMB server for your clients.

B.  File Level (SMB)

In this scenario the client computers must be able to directly reach the SMB server, it cannot be “proxied” through the CloneDeploy server.  If your network configuration does not allow this, you cannot use this option.

  1. Create a new SMB share on your file server and inside of that directory create 2 more directories, images and resources. Also create two users that have access to that share.  A read only user and a read write user.  The client computers will use these users.
  2. Create a third user that the CloneDeploy server will use to access the share.  It needs to have read / write access.  I will refer to this user as CloneDeployServerUser for the rest of this guide.
  3. Open the CloneDeploy Web Interface and go to Admin -> Distribution Points
  4. Select View on the primary distribution point
  5. Change the Server Ip to the ip of your file server
  6. Change the Share Name to the share you created
  7. Change the Domain to your domain if using domain users, if they are local users Workgroup should work
  8. Update the Read Only and Read Write users and passwords to match those from step 1
  9. Change the Physical Path to the UNC path for your share.  Something like \\\myshare
  10. Leave the Uses Backend Storage box unchecked.  This is not needed and will be removed in the next release.
  11. Click Update Distribution Point
  12. Create a new user on your CloneDeploy Server that exactly matches the CloneDeployServerUser name and password
  13. Create a new IIS Application Pool named CloneDeploy. Change the identity of the Application Pool to use a custom account. Enter in the credentials for the CloneDeployServerUser
  14. Assign that Application Pool to the CloneDeploy Web Application. Restart IIS.
  15. Add the user IIS AppPool\CloneDeploy to the security permissions with Modify permissions to program files\clonedeploy\web and program files\clonedeploy\tftpboot
  16. Good Luck.


in Additional Help
Comments are closed.