Last active 3 weeks ago
I'm using CloneDeploy 1.3.3 running on Windows Server 2008 using the Mac Imaging Environment and I'm experiencing significant lag when imaging more than a couple of MacBook air's. I'm not sure if this is related, but when attempting to multicast I found that no devices were able to boot up to CloneDeploy at all. Any ideas why it might be running so slow? I should also note that I am Imaging Sierra to High Sierra which I was able to successfully pull off in my testing.
I work for an educational institute and I would like to separate my faculty clients from my student clients. I can easy extract faculty clients using a smart group since they all start with the same three letters denoting our school district. However the student devices are named after the students name and then include the asset tag. Since every student name is different I cannot exactly set criteria to search for all of them. Is there a way that I can create a smart group based on words that are not contained in the client name?
Like "Does not contain NPS".
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.
@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.
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.
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
Awesome Thanks! What script has the bless command? Or if you used a different command what is it?
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
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.