Last active [hidden]

  1. last week
    Fri Aug 10 12:43:27 2018
    clonedeploy posted in Upgrade broke computer naming.

    @TB_Admin you are correct. Someone else has requested this functionality also. I have already implemented in the next version, to keep registration disabled and still prompt for a name. It should be available in the next month or so.

  2. Fri Aug 10 12:41:43 2018

    Search function does not work but I am running Version 1.3.0 and it appears you have addressed this in a patch I read in another thread.

    Yes this was addressed in a later patch.

    Another is that when adding host, most occasions I check how many are added and they are not there (Maybe its a browser bug as I am using Chrome)

    Not sure about this one, I would patch to latest version

    2 features missing which would I found useful (which CWDS had) is that when I have ticked my hosts and click "add selected computers" there was a popup at the top which confirmed "19 hosts added to group" - I would like this to return.

    You want to the know the number of hosts added?, I can add this.

    Also when searching for hosts I only get to see in the table - "NAME" - "MAC" and most of the remaining screen space is just blank.

    You should also see image and image profile

    Is it possible/or could it be made possible so that these fields have useful info in when adding hosts (like CWDS it used to show what group the device is already in) so I can easily ID devices that are not in any groups.

    I'm not sure what other useful info there is, there should already be name, mac, image, and image profile, you can do groups, because computers can be in many groups, I supposed I could add something that shows if they are in any groups

  3. Fri Aug 10 12:26:24 2018
    clonedeploy posted in Reset Password.

    This wouldn't be a password issue. Are there any errors in your apache error log?

  4. Thu Aug 9 17:52:46 2018
    clonedeploy posted in Upgrade broke computer naming.

    Registration needs to be enabled to get the name prompt.

  5. Thu Aug 9 17:02:37 2018
    clonedeploy posted in Increase Imaging Speed?.

    Increasing the queue would probably make things worse. If you are imaging multiple machines at the same time you should probably be multicasting.

    The best solution is to using clustering. Setup multiple SMB shares, they can be new one's or use an existing file server. Then you setup CloneDeploy to pull images from all of the available distribution points. Each client will automatically pick the smb share with the least connections. This way your CloneDeploy server isn't doing any heavy lifting, it just a web interface and tftp server.

  6. Thu Aug 9 16:53:05 2018
    clonedeploy posted in Increase Imaging Speed?.

    Sounds like your CloneDeploy server has a bottleneck. Probably the hard drive. Are you using SSD's or raid array in your server? Most people install CloneDeploy on a spare PC where the specs aren't that great. That's why the default queue size for the distribution point is set to 2.

  7. Thu Aug 9 01:59:01 2018
    clonedeploy posted in Upgrade broke computer naming.

    can you post a screenshot of your admin settings->security page?

  8. Wed Aug 8 17:56:02 2018

    I don't think there is much you can do. You definitely don't want to make CloneDeploy public facing. It doesn't have enough hardening for that. If you want to get creative you could probably make some type of script that dumps the database every so often and uploads it to some type of cloud storage, then the other server could import the db every so often.

  9. Wed Aug 8 17:20:40 2018

    Are these sites interconnected in any way?

  10. Wed Aug 8 17:19:30 2018
    clonedeploy posted in Deploy seems fine, then fails.

    Attachments should be fixed, just moved to a new vps and hadn't updated my php settings yet.

    Few things going on. First it's an efi image so you should be uploading from an efi boot loader, not sure if it's related to your issue or not. Second the issue is happening when trying to expand the filesystem on deployment. In your image profile deploy options try setting Don't Expand Volumes.

View more