Z

Zep

Member

Last active 3 months ago

  1. 5 months ago
    Tue May 1 19:50:04 2018

    @clonedeploy On second thought, you wouldn't need all the images on the shares, just the images you want, as long as you've correctly grouped everything it should be fine, CloneDeploy would be unaware of what images are where, it's up to you to make sure the the image is available on the proper shares.

    To your last post, there isn't really a concept of a main in a cluster group, the primary distribution point is the main regardless of whether it's in the group or not. It would be used for info, but the transfer would not come across the primary if not in the group. Each task checks how many tasks are already connected to a share and picks the share with the lowest amount of tasks to connect to. If all the shares have even utilization a random one is picked. So it's not exactly round robin, but similar.

    Thanks for the information!

    So i set up a cluster group, but when I create a boot usb it gives an error for on demand tasks.

    This is because by default it set the distribution point to [server IP] instead of the actual IP address.

    WIll I have to set the distribution points on both slave and master to them selfs ?

    Thanks!

  2. Tue May 1 16:33:30 2018

    @clonedeploy All the shares? Yes.

    Oh cool!

    Thanks!.

    Just want to be clear,

    If I have 4 desktops all in a cluster group. 1 machine will be the main and the other the slaves.

    the cluster group will allow me to round robin between all the servers.

    Is this correct ?

  3. Tue May 1 16:29:43 2018

    @clonedeploy Yes. You just need to setup a cluster group

    do all of the machines have to have all the images ?

  4. Tue May 1 16:06:09 2018
    Z Zep started the conversation rotate between distribution points.

    Hello,

    Is it possible to round robin between distribution points ?

    I image over 100+ pcs at a time and multicast is disabled. I can only setup multiple SMB shares.

    thanks!

  5. 7 months ago
    Fri Feb 23 19:16:59 2018

    I had this issue awhile ago when using multiple USBs for the same server.

    I just raised the queue in the distribution point settings to 40 to resolve it.

  6. 8 months ago
    Mon Feb 12 17:54:06 2018
    Z Zep posted in Secure Boot Hurdles.

    Have a paid for version.

    I wouldnt mind paying you 20$ a month if you update and support he software.

  7. Thu Feb 1 20:20:07 2018
    Z Zep started the conversation Multicast clobber mode.

    Hey I was looking around digging through some settings and I was wondering if it was possible to add multicast clobber mode in any way.

    thanks!

  8. 11 months ago
    Tue Nov 7 18:37:56 2017

    @clonedeploy That's not the correct location. That's the original schema stating it was uploaded from /dev/sda. It doesn't have anything to do with where it deploys to.

    looked over your answer again. figured it out.

    Thank you!

  9. Tue Nov 7 16:48:31 2017

    as well... the schema is set to /dev/sda

  10. Tue Nov 7 16:46:15 2017
    ** Looking For Active Task For ec:b1:d7:3b:79:e6.2UA53222GQ.F703E280-359E-11E5-9178-ECB1D73B79E6 **
     
    {"computerId":"false","task":"ond","taskId":null}
     
    ...... This Computer Was Not Found
     
    ** Looking For Active Task For ec:b1:d7:3b:79:e6 **
     
    {"computerId":"false","task":"ond","taskId":null}
     
    ...... This Computer Was Not Found
     
    No Active Web Tasks Were Found For This Computer. Starting Clobber Imaging.
     
    ** Displaying Boot Arguments **
     
    BOOT_IMAGE=/kernels/4.13.2x64 root=/dev/ram0 rw ramdisk_size=156000 task=clobber image_profile_id=5 consoleblank=0 web=http://10.40.47.248/clonedeploy/api/ClientImaging/ USER_TOKEN=4718ec9b-f69f-4f66-a67b-4cbe533b7023 MAC: ec:b1:d7:3b:79:e6
    Linux client_console.localdomain 4.13.2 #1 SMP Mon Sep 18 12:18:16 EDT 2017 x86_64 GNU/Linux
     
    Boot Image Version: 1008
     
    ** Using Clobber Mode **
     
    image_name=ICT-9-22-2107 profile_id=5 server_ip=10.40.47.248 pre_scripts="" post_scripts="" file_copy=False sysprep_tags="" task_completed_action="Reboot" osx_target_volume="" munki_repo_url="" change_computer_name=true fix_bootloader=true partition_method=dynamic dp_id="1" computer_id=-103703
     
    ...... Success
     
    ** Checking Current Queue **
     
    ...... Complete
     
    ** Mounting SMB Share **
     
    ...... Connecting To Clonedeploy
     
    ...... Success
     
    ** Looking For Hard Drive(s) **
     
    ...... Displaying Available Devices
    RO RA SSZ BSZ StartSec Size Device
    rw 256 512 1024 0 159744000 /dev/ram0
    rw 256 512 4096 0 256060514304 /dev/sda
    rw 256 512 4096 2048 256059465728 /dev/sda1
    rw 256 2048 2048 0 70260736 /dev/sdb
    Disk /dev/ram0: 152.4 MiB, 159744000 bytes, 312000 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
     
     
    Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x25fb7c98
     
    Device Boot Start End Sectors Size Id Type
    /dev/sda1 * 2048 500118191 500116144 238.5G 7 HPFS/NTFS/exFAT
     
     
    Disk /dev/sdb: 67 MiB, 70260736 bytes, 34307 sectors
    Units: sectors of 1 * 2048 = 2048 bytes
    Sector size (logical/physical): 2048 bytes / 2048 bytes
    I/O size (minimum/optimal): 2048 bytes / 2048 bytes
     
    ...... Found Drive(s)
     
    ...... Drive(s): /dev/sdb /dev/sda
     
    ** Processing /dev/sdb **
     
    Get hd_schema: profileId=5&clientHdNumber=0&newHdSize=281042944&schemaHds=&clientLbs=2048
     
    {"BootPartition":null,"Guid":null,"IsValid":"false","Message":"The Logical Block Size Of This Hard Drive 2048 Does Not Match The Original Image 512","PartitionType":null,"PhysicalPartitionCount":0,"PhysicalPartitions":null,"SchemaHdNumber":0,"UsesLvm":null}
     
    ...... The Logical Block Size Of This Hard Drive 2048 Does Not Match The Original Image 512
     
    ** Processing /dev/sda **
     
    Get hd_schema: profileId=5&clientHdNumber=1&newHdSize=256060514304&schemaHds=&clientLbs=512
     
    {"BootPartition":null,"Guid":null,"IsValid":"false","Message":"No Active Hard Drive Images Were Found To Deploy.","PartitionType":null,"PhysicalPartitionCount":0,"PhysicalPartitions":null,"SchemaHdNumber":-1,"UsesLvm":null}
     
    ...... No Active Hard Drive Images Were Found To Deploy.
     
    ** Closing Active Task **
View more