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 » Restoring Images to T2 Chip Machine » 2018-12-20 19:26:42

I may have figured it out.. all of you "don't image anymore" people will probably disown me, but I'm posting the answer for anybody else that won't let imaging go just yet.

After restoring the image I had to manually delete the (encrypted at rest) Preboot and Recovery Partitions using:
diskutil apfs deleteVolume disk1s2 (deletes Preboot)
diskutil apfsdeleteVolume disk1s3 (deletes Recovery)

Manually create those Volumes again using the "role" identifer:
diskutil apfs addVolume disk1 apfs Preboot -role B
diskutil apfs addVolume disk1 apfs Recovery -role R

Then I had to populate the preboot volume with the boot information.
#Get UUID of disk1s1 to setup Preboot need to store that value into variable. the $4 indicates 4th column (spaces count as each column)
diskutil apfs list | grep "Volume disk1s1" | awk {'print $4'}

#mount the preboot Volume
diskutil mount /dev/disk1s2

#unizp the preboot files
tar -xvf /tmp/DSNetworkRepository/Masters/APFS/ -C /Volumes/Preboot

#Rename the Folder under Preboot to the UDID of disk1s1 (Using variable from grep command)
mv /Volumes/Preboot/%foldername that was extracted% /Volumes/Preboot/%Variable from Grep%

Also Restore the Recovery Partition
#mount the recovery volume
diskutil mount /dev/disk1s3

#unizp the recovery files
tar -xvf /tmp/DSNetworkRepository/Masters/APFS/ -C /Volumes/Recovery

#Rename the Folder under Recovery to the UDID of disk1s1 (Using variable from grep command)
mv /Volumes/Recovery/%foldername that was extracted% /Volumes/Recovery/%Variable from Grep%

#make the drive bootable
sudo bless -mount "/Volumes/Macintosh HD" -setBoot
#Verify Boot Info (if desired)
sudo bless -info -verbose /Volumes/Macintosh HD

#2 Re: Usage » Restoring Images to T2 Chip Machine » 2018-12-13 14:28:39

So more information as I was working on this.

If I use this command the image gets laid down ok and the Preboot and Recovery Partitions show not encrypted but they are both empty.

sudo asr restore -s /tmp/DSNetworkRepository/Masters/APFS/Mojave_10.14.2_18C54_v1.0.i386.apfs.dmg -t /dev/disk1s1 --erase --noprompt

I tried just extracting the file that is created as part of the image, but it doesn't appear to be a normal zip file. What format is that in? What command does deploy studio use in the background to extract those files?

I am able to open it using the Archive Utility program manually but I can't use the unzip command to script it?

I ideally if I can fix the problem in the original post this won't be needed, but I'm just looking at another possible way to do this if the first problem can't be resolved.


#3 Usage » Restoring Images to T2 Chip Machine » 2018-12-12 20:46:00

Replies: 3

I have a strange problem I'm trying to get around on the new T2 Chip Enabled machines. Let me give a background of the current setup.

This is testing on a 2018 Macbook Air (released Nov 2018).
I installed macOS 10.14.2 onto an external USB drive and then set it up with DeployStudio Runtime.
I changed the Security Settings on the macbook to "no Security" and Allow booting to external Media.
I am then able to boot to my external disk with Deploystudio available on the new macbook Air.

Out of the box the configuration of "diskutil apfs list" shows output with this. (not all information shown just the relevant part)

Volume disk1s1
name: macintosh HD
Filevault: No (Encrypted at rest)

Volume disk1s2
name: Preboot
Filevault: No

Volume disk1s3
name: Recovery
Filevault: No

If you notice the main drive shows Encrypted at Rest but the Preboot and the Recovery Partition do not show that.

If I use Deploystudio to lay down an image that I captured using the Capture task sequence in DeployStudio the layout changes to this:

Volume disk1s1
name: macintosh HD
Filevault: No (Encrypted at rest)

Volume disk1s2
name: Preboot
Filevault: No (Encrypted at rest)

Volume disk1s3
name: Recovery
Filevault: No (Encrypted at rest)

In this state the machine will not boot, it shows the flashing folder with a ?
I already mounted the Preboot volume to make sure the UUID folder is correct inside of that. The Bless -info also shows the correct information. I think the root issue is encrypted at rest component.

If I make an image file using AutoDMG and restore that using Disk Utility it gets back to a working state with the Preboot and the Recovery back to not encrypted again.

Is there a way to turn off Encryption at rest for those two volumes, If not is there a way to delete and manually create those volumes without the encryption enabled?
I would be ok even with a way to restore just the Macintosh HD volume only without touching the other two partitions.

I was able to copy the image down successfully using SuperDuper but I am looking for a way to do this via task sequence so it is one click and done.

Any insight into this? If more information is needed I'm happy to provide that.

#4 Re: Debug » Mojave error trying to make NetBoot set » 2018-10-05 21:53:40

Thanks for the help, I think I got this to work mostly. Was even able to setup the delpoystudio to autologin using the deploystudio.plist from preferences.

I am stuck on how to get the system to reboot automatcially at the end of the script though. Using the old boot key once the task was done and exited the system rebooted itself into the finalize stage. Now when it ends it just closes but never reboots. I tried adding a script at the end to run shutdown -r but that doesn't seem to work. It just sits at the screen like its paused at that task and never gets past it.

Do you have yours set to reboot automatically at the end?

#5 Re: Debug » Mojave error trying to make NetBoot set » 2018-10-04 16:50:11

Ok, I may give that a try, Is there a way to customize the background image and autologin to the server that way also?

#6 Re: Debug » Mojave error trying to make NetBoot set » 2018-10-04 13:47:05

Hey Carlo - How do you make an "ordinary" external USB with deploystudio set to auto run at login?

#7 Re: Debug » Mojave error trying to make NetBoot set » 2018-09-25 19:21:02

I am having this same problem. I haven't found a solution yet, but figured I would post so you don't feel alone in your pain on this one.

#8 Future » Ability to Open Terminal without Login » 2018-01-22 16:59:33

Replies: 0

I had an issue a few weeks back with a machine not being able to connect to the server to login. I booted the machine using a USB Boot key. Without logging in to the server all the tools are greyed out and won't open. I wanted to try to open terminal to see what the IP address was and if the server was pingable to verify network connectivity. It looks like there is no way to do this without first logging in. Could this be a feature request to make terminal available before login?

I open a thread in the "Usage" forum but there were no responses so I'm assuming this is not already available. That thread is available here for reference:


#9 Usage » Load Terminal Before Login » 2017-12-18 17:44:56

Replies: 1

I have a machine that is having trouble connecting to our Imaging server. It boots up to the USB DeployStudio Boot key just fine, but then gives a "host is unreachable" error. I wanted to try to bring up a Terminal window so I can see if the machine is pulling an IP address and if so what the IP address is. Maybe do a few test pings etc to check physical connectivity.

The option to bring up Terminal is greyed out until I can login to the imaging server. Is there a way to check IP address and network connectivity before login? I don't have switch level access to login and look at the port or lookup the MAC address of the NIC etc.

Thanks for the help.

Board footer

Powered by FluxBB