Last active 6 days ago

  1. 4 weeks ago
    Tue May 22 16:46:40 2018

    Sorry to take so long to respond to this thread. I've been busy with some other stuff. I think I figured out why imaging Sierra to High Sierra does not properly set the boot drive. If I run the command while booted into Clone Deploy (1.3.3) I get an error "Setting startup disk not allowed while System Integrity Protection (SIP) is enabled.

    It looks like this command can only be used from the recovery partition. I can disable it before uploading an image and this fixes the issue with the ? boot folder. i.e. systemsetup is able to set the startup disk. However this leaves the device without SIP enabled which may or may not be detrimental to the final deployment (I'm sure Apple would view it as detrimental).

    Of course it can be reenabled from the recovery partition. However I find it easier to leave it enabled and select Macintosh HD from the Startup Manager. Curiously enough this only happens when imaging from HFS+ to APFS (Sierra to High Sierra), but I bet that has something to do with the update to firmware since the setting carries over to the target machine.

  2. Tue May 22 12:23:14 2018
    M MunkiMan posted in MacOS Error on deploy.

    @rnguyen I ran into similar issues with imaging iMacs before upgrading to CD 1.3.3. I basically had to deconstruct core storage using diskutil cs createVolume fusing the SSD and HDD. I have also found that sometimes it's necessary to copy the schema from a working image (non core storage) I did this on the server itself not in the web interface.

    On another note: I have been imaging successfully from Sierra to High Sierra with only one small issue. They image fine, but do not bless the boot drive properly resulting in a ? folder on next boot up. You then have to select the Macintosh HD from the Mac Startup Manager and bless the drive after booting up. But that little hassle is worth it since a CD image takes about 10 to 15 minutes (20G base) compared to 30-45 to upgrade the way Apple wants you to.

  3. 4 months ago
    Wed Jan 31 16:11:35 2018
    M MunkiMan posted in Copy Files/Drivers and run scripts.

    Sorry I just figured it out. I did not realize at first that the file I had put into the share point was actually a zip file of the one that I was trying to copy to the image. After that everything worked perfectly.

  4. Wed Jan 31 15:45:53 2018
    M MunkiMan posted in Copy Files/Drivers and run scripts.

    I've been trying to get this to work with the Mac imaging environment. I don't seem to have the option to choose the destination partition. It's locked as /Volumes/Macintosh HD/. Everything else is as outlined in your documentation and this forum entry. The only thing I can think of is the context of the file. Are there restrictions such as spaces / or \? Thanks

  5. 5 months ago
    Wed Jan 10 20:09:17 2018


  6. Wed Jan 10 19:11:21 2018

    Awesome Thanks! What script has the bless command? Or if you used a different command what is it?

  7. Wed Jan 10 15:03:12 2018

    In CloneDeploy 1.2.0 there was a section for editing core scripts in the Global > Imaging Scripts setting. I cannot seem to find that in my deployment of 1.3.3. I just want to make sure I'm not missing some crucial piece of the server setup. There have been a few quirks in upgrading as you know. So if there is a different location or specialized account (although I'm logged in as an admin). Thanks

  8. Fri Jan 5 19:10:44 2018

    Of course I tested again today with two devices that imaged just fine from 10.12 to 10.13 with no issue. Here's the log for the first device I tested where on reboot I had a ? folder however once choosing the volume Macintosh HD it booted just fine.

  9. Wed Jan 3 14:41:27 2018

    Update on imaging from Sierra to High Sierra. After upgrading to CloneDeploy 1.3.3 and working though a couple of hick-ups getting the NetBoot service working I have been able to image Sierra to High Sierra successfully. I did not have to use the extracted firmware package as chronicled in the link you provided above. Initially when imaging I received a warning from CloneDeploy (thank you for putting that bit of code in) that imaging hfsf+ to apfs could result in an unbootable drive. The result, however has been a perfectly bootable drive. The only issue is that the volume does not get blessed at the end of imaging so initial boot will be a question mark folder. This is reminiscent of when you first added Mac support and PXE booting obviously did not have access to the mac command line and could not bless the drive. So my question is this: Is it possible to add a post script to be run at the end of the Mac imaging to bless the drive? If so where would I add this in CloneDeploy? Thanks for all the hard work, and hanging in there bucking the Apple Juggernaut.

  10. Fri Dec 29 15:20:02 2017

    That worked adding that to the config file. I can now boot into apple netboot, however after the upgrade to 1.3.3 I cannot upload an image. I get an error that mounting the smb share failed. After changing the user passwords in both the web interface and on the server I went through your SMB troubleshooting documentation. Everything looks good until I get to step 6 booting into the console. When I attempt to mount the share with user cd_share_rw and the password that I reset and verified I receive a message that mounting the share failed and permission was denied. Are there certain characters I should avoid when creating this password?

View more