You are not logged in.


[2017.09.08] DeployStudio build v1.7.8 (checksum, release note).
[2016.08.26] DeployStudio build v1.6.19 (release note).
[2013.02.23] DeployStudio last universal build v1.5.17 (release note).

#1 Re: Usage » High Sierra 10.13 Imaging Install School Manager DEP process theory » 2018-11-09 16:40:33

Many thanks for your time, detailed report and directions. This does explain why I could not install Mojave from my external USB boot drive with Mojave targeting the internal!
Also good to know we can still have some room for workarounds....
As far as firmware updates, usually they come with security updates, so I've just added a task to check for Apple's software updates within my second DS workflow (eg: after using startosinstall with HighSierra 10.13.6 - build 17G65 the OS is automatically updated to 17G3025 during my second workflow)
It would take one of those brand new MacBook air to see if macOS Mojave 10.14.1 Supplemental Update does change its firmware.
Interesting article here about firmware versions:

#2 Re: Usage » High Sierra 10.13 Imaging Install School Manager DEP process theory » 2018-11-06 17:30:59

Hello and many thanks again
Yes indeed, something must have changed in Mojave…

I am trying to replicate the result I achieve with a 10.13.6 High Sierra Netboot image from server and DeployStudio and your script
The same workflow works if I use an external USB drive with 10.13.6 High Sierra

If I use Mojave on the external drive, DS Runtime works but the script fails and I can’t find the right option to use startoinstall

I would rather use Mojave on the external USB boot disk ideally to be able to install both 10.13.6 High Sierra (any version) and Mojave itself, so that it will be a sort of universal disk to use with DS server
Maybe the new MacMini will have a custom version of Mojave (or standard 10.14.1 build who knows)…

Anyway, I would be very grateful if you could keep me updated on your future tests
Have a great day and thank you

#3 Re: Usage » High Sierra 10.13 Imaging Install School Manager DEP process theory » 2018-11-05 16:41:05

Hello jelockwood, I have tried creating an USB boot drive with Mojave using a standard MacOS installation and running the DS Runtime application on its own but the workflow for High Sierra fails (I would assume also thescript for Mojave your recently posted here would fail as well)
This is the error I get, it seems to refer to startosinstall missing parameters. Your script for High Sierra works perfectly when booted from Netboot with High Sierra (I would assume it would also run with an USB drive with High Sierra)

2018-11-05 16:27:42.609 DeployStudio Runtime.bin[314:4266] /dev/disk1s2        	Apple_HFS                      	/Volumes/HighSierra
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] Usage: startosinstall
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] Arguments
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --applicationpath, a path to copy of the OS installer application to start the install with.
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --license, prints the user license agreement only.
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --agreetolicense, agree to license the license you printed with --license.
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --rebootdelay, how long to delay the reboot at the end of preparing. This delay is in seconds and has a maximum of 300 (5 minutes).
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --pidtosignal, Specify a PID to which to send SIGUSR1 upon completion of the prepare phase. To bypass "rebootdelay" send SIGUSR1 back to startosinstall.
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --converttoapfs, specify either YES or NO on if you wish to convert to APFS.
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --installpackage, the path of a package (built with productbuild(1)) to install after the OS installation is complete; this option can be specified multiple times.
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --eraseinstall, Erase all volumes and install to a new one. Optionally specify the name of the new volume with --newvolumename.
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --newvolumename, the name of the volume to be created with --eraseinstall.
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] --usage, prints this message.
2018-11-05 16:27:42.653 DeployStudio Runtime.bin[314:4266] Example: startosinstall --converttoapfs YES 
2018-11-05 16:27:42.655 DeployStudio Runtime.bin[314:4266] -> Generic task action completed.
2018-11-05 16:27:42.655 DeployStudio Runtime.bin[314:4266] Task successful (elapsed time: 0.01 minutes)

When you say  it is not possible to use DeployStudio 1.7.8 to build a working Mojave NetBoot or USB boot image, do you refer to automating disk creation or using any disk with Mojave and DS Runtime?
Many thanks for your help!

#4 Re: Usage » Use DeployStudio to push packages and scripts without Netbooting » 2018-11-05 14:47:02

No, you cannot create DS master images anymore, unless you use Sierra (pre-10.12.4 if I am not mistaken) or AutoDMG for High SIerra and Mojave (OS only)
I suggest you follow/read  other posts here, such as and use the Apple supported startoinstall procedure
Too many issues with firmware and the like with recent hardware

#5 Re: Usage » Use DeployStudio to push packages and scripts without Netbooting » 2018-11-04 15:58:00

You can still boot from an external disk/USB pendrive and use the DS runtime pointing at your DS server.
With current models with T2 chip, after disabling secure boot, I am simply using a pendrive with Mojave, it's a basic configuration that allows opening DS Runtime as any other application
DS wizard does not allow to automatically build the (net)boot disk with Mojave, hopefully there will be some news in the future
Once you slightly modify your existing workflows to point to the right internal disk, there's not such a big difference to me but maybe your workflows are different

#6 Re: Debug » Mojave error trying to make NetBoot set » 2018-10-14 10:08:21

Hello, sorry for the delay. No, the workflow does not have anything special at the end.
The first workflow simply erase, rename and install MacOs (both High Sierra and Mojave, just changing the name in the script and putting both the installers within the Files/ folder in DS server)
The script is NOT postponed

"/tmp/DSNetworkRepository/Files/Install macOS High" --applicationpath "/tmp/DSNetworkRepository/Files/Install macOS High" --volume "/Volumes/Hard Disk" --agreetolicense --nointeraction
exit 0

The second workflow simply install everything I need (applications, settings and the like) pointing to the internal disk

#7 Re: Debug » Mojave error trying to make NetBoot set » 2018-10-04 17:01:04

It's just a regular MacOs client running the DS runtime.
You can do anything you as it's not "limited" as a standard DS netboot set
If you save your DS server credential into the keychain you can simply connect to your DS manually

#8 Re: Debug » Mojave error trying to make NetBoot set » 2018-10-04 16:45:08

Hello Jeremyd, nothing fancy.
I just installed Mojave from the standard installer onto an USB Key with both USB type plugs ( so that it can be used on any Mac
I have then installed DS and put DS Runtime on login items pointing to my server as it were a netboot set.
It's not a complete standalone bootable DS, it's just a way to run the DS Runtime app without netbooting (you just need to disble secureboot on 2018 laptops to use the external USB drive)
Once I have logged onto DS server, I can start my workflows pointing the internal disk (since 10.13.3 onwards I dropped AutoDMG images and using starttoinstall script)
Hope it helps

#9 Re: Debug » Mojave error trying to make NetBoot set » 2018-10-04 09:37:37

Same here, of course. For now I have remediated with an "ordinary" external disk with 10.14 and DeployStudio runtime at login
I would assume new hardware will not support netboot but it would still be nice to have DS creating an USB disk automatically

#10 Re: Future » New iMac Pro is the End of Mac Imaging! (Redux) » 2018-08-03 14:30:52

Forgot to mention this other way using a pkg to install the OS
It should allow using a single workflow in DS once an universal OS build is available (10.13.6 on AppStore would not be good for 2018 macbook pro)

#11 Re: Future » New iMac Pro is the End of Mac Imaging! (Redux) » 2018-08-02 23:02:47

Hope so...
The second part of the workflow (that is after restoring the OS and rebooting with DS runtime) can also become handy and used directly with brand new computers that come with a never booted OS and don’t need a clean install
Problem is that you also have to enable NetBoot in secureboot first, so I would think this can be a good workaround with pre-2018 models (where you can still quickly NetBoot with DS runtime) and quite cumbersome for the future (and already current T2 hardware)
DEP and MDM (where available) is where we have to go...

#12 Re: Future » New iMac Pro is the End of Mac Imaging! (Redux) » 2018-08-02 22:34:50

I think you could split your workflow in two/three
Format the disk
Install OS the supported way with a script
Reboot with DS runtime again and run the rest/second part of your workflow
Quite annoying but this is the way I am trying to solve the problem

#13 Re: Future » New iMac Pro is the End of Mac Imaging! (Redux) » 2018-08-02 22:17:44

The problem is not your 10.13.6 image you created with AutoDMG
It is the DS image you boot from (10.13.6 with a newer build version for MacBook Pro with T2), that’s why you don’t find it in AppStore
ASR works fine in restoring APFS images only up to 10.13.3
So you cannot restore an image if you have to use a newer version to boot your computer from
It would probably work using target disk mode, that is using another computer and booting with 10.13.3 and connecting the MacBook Pro T2 as an external drive
You might take a look at this topic which points to a clever idea to avoid using AutoDMG images and look promising regardless of future OS versions.

#14 Re: Usage » High Sierra 10.13 Imaging Install School Manager DEP process theory » 2018-07-31 20:10:37

Hello Christian, thanks for your message
The script Dan posted works perfectly for me
Sorry I should have explained my goal better
I was just trying to add and use the —eraseinstall option to first erase (nuke&pave) the destination drive without using Disk Utility (since the script would update a previous OS if existing)
I could not find a way to format the destination drive as APFS in DeployStudio (at the beginning of a workflow)
Maybe I am missing something!
Thanks again

#15 Re: Usage » High Sierra 10.13 Imaging Install School Manager DEP process theory » 2018-07-30 14:59:22

Hello and thanks for your reply...
Tried several times with the below script but it does not seem to work... keeps getting the "By using the agreetolicense option, you are agreeing that you have run this tool with the license only option..." message in DS log
(I skipped the -newvolumename since its optional with  --eraseinstall and deafult is  Macintosh HD)

Any help would be very much appreciated, as it seems I am missign something obvious here
Already verified the target disk is  APFS and 10.13.6 has been manually installed before on the same computer...

"/tmp/DSNetworkRepository/Files/Install macOS High" --applicationpath "/tmp/DSNetworkRepository/Files/Install macOS High" --agreetolicense --eraseinstall --nointeraction
exit 0

#16 Re: Usage » High Sierra 10.13 Imaging Install School Manager DEP process theory » 2018-07-25 09:39:24

Hello, the upgrade command dan.kuehling posted here works just fine for me!
Thank you!

I am now wondering how to erase and install the OS (limited to APFS) instead of upgrading

Taking some info from here
I tried modifying the original script


"/tmp/DSNetworkRepository/Files/Install macOS High" --eraseinstall --newvolumename "Macintosh HD" --agreetolicense

exit 0

But I get an error in DS log

"By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms"

It seems the --agreetolicense does not work as intended
Any help would be very much appreciated!

#17 Re: Usage » High Sierra 10.13 Imaging Install School Manager DEP process theory » 2018-07-21 12:15:55

I wonder if T2 machines would netboot if you disable secure boot...

#18 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2018-06-15 21:38:06

Hello and thanks for the update
In my testing with pycreateuserpkg the only drawback was the user created that way does not have a securetoken so you cannot enable Filevault
The errors you get for the “inverter” are due to NBI deploystudio created with 10.13.5 when restoring APFS images
ASR changed from 10.13.4 onwards
Unfortunately DS runtime NBI has to be not higher than 10.13.3
With HFS+, Deploystudio behaves better like 10.12.x, no major issues although I have not tried creating and uploading “the old way” an HFS+ Image directly from DS NBI
You might try using the built in option to create a local user directly with DS, skipping Apple assistant
It worked for me despite some errors here and there in the logs
Have a nice weekend

#19 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2018-06-11 15:37:47

Could it be an issue related to firmware update not being applied?
If you restore aworkflow with 10.13.4 autoDMG base image + 10.13.5 combo it should install the right firmware on top of the base image

#20 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2018-06-06 14:18:53

Hello, just a quick note to confirm that DS runtime 1.7.9 created with 10.13.5 does not fix the issue when restoring an APFS AutoDMG base image
The errors in the logs after restoring progress reach 100% still refers to:

Inverting target volume...
APFS inverter faied to invert the volume
Command failure: XSTA
restoration failed

(obvious blinking question mark at reboot)

Everything seems to work fine with DS Runtime 10.13.3 and 10.13.5 AutoDMG base image

#21 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2018-05-09 11:14:58

Hello and thank you again!
I moved the scripts to create the user, not for time zone setting. I have used the built-in step to set the time zone
There's only the network time server and city to chose from...
Since I skip the setup assistant, I will try to use a script to allow location services, I don't know how I could do it otherwise... ...but maybe I am missing something obvious!

As far as the local user is concerned, I agree, as long as the secure token is present and everything seems OK, I am fine!

#22 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2018-05-09 10:15:05

Thank you @mjsanders
It took a couple of days to figure out the correct workflow order but now it seems that my rather complex workflow (base AutoDMG image 10.13.4 + additional pkgs + AD bind and the like) works fine
There are a few errors appearing in the log (some missing files while cleaning up at reboot) but I think those are minor
As far as the user creation is concerned, I get this error
... - v1.5 (current date at imaging time) - v1.18 (current date at imaging time)
creating user 'admin' with UID=501 !
<main> attribute status eDSPermissionError
<dscl-cmd> DS error -14120 (eDSPermissionError)
Setting admin properties
Creating local home directory

but everything seems fine and secure token is present

I am not quite sure my DS scripts above are up to date (I had to move them from DSfolder/Scripts/10.5/)

Also, time zone is not set completely correctly
"Selected city not set, MacOs setup assistant might display...
NetworkTime is already on."

Still need to test with a Mac where High Sierra had not been previously installed
Not sure if latest Security Update installs the right firmware where needed
Many thanks again

#23 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2018-05-04 11:06:42

Hello, just to confirm I could successfully restore an AutoDMG APFS 10.13.4 base OS while using a 10.13.3 netboot set with DS 1.7.9 (10.13.4 does not work)
I left the latest Security Update (with firmware) to be installed at reboot with DS Software Update task
Most of my previous workflow still works, the only problem is how to create a local admin in DS workflow (skipping the setup assistant)
Using pycreateuserpkg works but with one major issue (that should be related to local users created with a script).
The secure token that is required for things like FileVault is not created using this method.
Any suggestion will be greatly appreciated!

#24 Re: Usage » Revert back to HFS+ from APFS before deploying image » 2018-01-18 16:23:21

Hello Joon many thanks for your reply
I ended up creating a script within a workflow that only formats the disk back to HFS+
Once the workflow ends, I simply choose one of the other usual workflows....

convertDisk=$(diskutil list internal | grep -B 2 "APFS Container Scheme" | grep /dev | awk '{print $1}')
diskutil apfs deleteContainer "$convertDisk"
diskutil eraseDisk JHFS+ "Hard Disk" /dev/disk0

I used "Hard Disk" (between quotes) to name the disk
Hope this helps someone with the same need

#25 Usage » Revert back to HFS+ from APFS before deploying image » 2018-01-08 11:14:56

Replies: 2

Hello, what is the smarter way to revert back to Apple's HFS+ from APFS in DeployStudio when downgrading from APFS HS to HFS 10.12?
My current workflow with DS 1.7.8 runtime (10.2.6 HFS) wait for user selection to partition the drive + allocate space for Recovery partition then automatically deploy the image on the first available disk.
When already formatted with APFS, I can see two identifier (/dev/disk1 and /dev/disk2) but partitioning from DS does not correctly work.
Usually I have to run the whole workflow twice so that the second time the disk is being correctly formatted with HFS+
Is it because I am supposed to work with a 10.13 runtime to correctly manage (and delete) APFS?
How can I automatically delete the APFS container?
Many thanks for your help

Board footer

Powered by FluxBB