You are not logged in.

Announcement

[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: Future » New iMac Pro is the End of Mac Imaging! (Redux) » 2018-02-28 01:42:46

I was able to boot from a DeployStudio USB drive and run a configuration workflow (with some issues afterward, but...).
I haven't tried the steps necessary to presumably/actually netboot one though.

#2 Re: Usage » ? Folder after High Sierra Reboot - Where to deploy Firmware in workfl » 2018-02-09 00:11:38

> y2j420 wrote:

> I'm trying to image a High Sierra machine (it came with High Sierra from Apple) with a High Sierra image and it always ends with a ? folder.  What do I need to do to get this working?  Since it is a native High Sierra machine, shouldn't it already have the firmware built in?  I've never had to implement scripts in the past to get Sierra and below working with DeployStudio.  Thanks.

What is the netboot image's OS version?
Are there any error messages in the DeployStudio logs (server, or target machine)?

#3 Re: Install » Cannot Connect from Mac » 2018-02-06 18:26:37

The user you created. Is the user in the admin group on the server?
Try creating a netboot set that uses the administrators credentials.
What model is your target machine?

#4 Re: Usage » Netboot created through assistant black screens and reboot » 2018-01-12 23:19:54

What model did you originally build the netboot set from? (hint: always build on your newest hardware running the most current general release of macOS)

#5 Re: Usage » Netboot and reinstall » 2018-01-11 18:34:09

When the time comes for the periodic netboot, are you available to watch the process all the way through? Does it look like it tries to netboot, but fails? Maybe an issue with the "restore-configure-periodic netboot" configuration?

#6 Re: Debug » Touch Bar, 1.7.8, 10.13.2 and APFS: cannot get device for volume » 2017-12-19 21:50:01

If you can get the touchbar updater thingee, then "restore to first..." and postponed install the updater doohickey.

#7 Re: Usage » Dual partition Fusion drive restore » 2017-12-19 21:38:48

If I'm not mistaken, Fusion drive setups require CoreStorage (unless High Sierra, but...).
Check it.

Also, there is a preventive volume repair option in one of the workflow tasks (restore, I think). Doesn't hurt to enable that either.

#8 Re: Usage » pkg installation error » 2017-12-15 22:12:01

What is the package trying to do?
Is SIP enabled on the target? (csrutil status)
Check the target's /var/log/install.log?

#9 Re: Usage » pkg installation error » 2017-12-12 21:27:17

Is the package task set as postponed? That is the common solution.
The postponed task occurs after the machine has been rebooted. If the package is not postponed, and it expects to install on "/" (the current boot volume) then it will try, but "/" during the netboot stage is the netboot volume, and not the Macintosh HD target volume.

You could repackage it, but it is generally simpler to just postpone the task. That is the whole reason for the postponed option.

#10 Re: Usage » Master Image Creation Failure » 2017-12-12 20:42:04

Are you creating the master image locally, then it is transferred to the server, or are you creating the master image on the server directly.
If locally, see if the masters are still on the local volume: ls -l /Volumes/Macintosh\ HD

Are the masters in the repository's temp directory? Repository > Masters > tmp

#11 Re: Usage » pkg installation error » 2017-12-12 20:32:40

It sounds like the package is attempting to install on the netboot disk, not the target disk.

#12 Re: Debug » 10.13 WorkFlows With Fusion Drives » 2017-12-07 00:55:14

Hopefully, they'll just stop supplying machines with fusion drives, and pony up for plain old SSD drives.

#13 Re: Usage » looking at possibly implementing this software, need more information. » 2017-12-07 00:04:02

You will probably want to use this software if you are staying on/have a large fleet of machines running 10.12.x or lower.
With 10.13, Apple has stated imaging is not supported.

That means, you will not want to capture an image of a 10.13+ machine if you can help it.
The good news, is that you can still use it to deploy most applications, and custom configuration to 10.13+ machines.

The "imaging" process would most basically be, boot into recovery, erase "Macintosh HD", reinstall the OS, netboot and deploy the add-on apps and custom configuration. A bit time consuming.

You could perform application installs and custom configuration (though I have not gone there...) through an MDM solution, though this possibly involves multiple tools/services configuration, service accounts, network port wrangling, converting plists to MDM profiles, setting expectations/policy,.. for an entirely different workflow.

#14 Re: Debug » APFS images created in DeployStudio not booting » 2017-11-30 01:34:59

I don't think the Server OS version matters. It only matters what OS version the netboot image is. That is my understanding...

#15 Re: Usage » Repository access error » 2017-11-13 18:08:00

Typically, this is a configuration error where the admin sets up a "local" path (/repository/path/folder) instead of a network path (afp://server/sharename).
Check your DeployStudio server config by walking back through the DeployStudio Assistant.app on the server.

#16 Re: Usage » Imaging USB-C MacBook, DS 1.7.8 with Belkin USB-C Ethernet adapter » 2017-11-01 16:41:10

Uninstall the current version (your repository and workflows should be uneffected) using the uninstaller, then install the 1.7.6 version.
After installing the 1.7.6 version, walk through the server config in DeployStudio Assistant and verify/reenter passwords and settings there.

If you still have your netboot image/s from the same 1.7.6 version, disable any newer netboot image/s and reenable your 1.7.6 netboot image/s.
If there are issues, then might have to recreate the 1.7.6 netboot image

#17 Re: Debug » Inappropriate Repository Error » 2017-10-28 00:38:32

Regarding server path vs. local path, I believe it is typical that the clients connect to the server, the server does not connect to the client.
Think of it in terms of where the actions are taking place. The target machine launches the runtime (from the netboot image) and the runtime has to connect to the repository from there.
The netboot image is essentially just a standalone OS downloaded from the server. The target machine is establishing the connections to the server.

Conversely, you might be using an external hard drive to boot target machines, and image from, in a one-off scenario. In that case, you "could" point to a network repository, but you'll probably have the image stored locally (in case network issues...) and so, a local path would be used in that case.

Yeah. There's probably a much better description somewhere... :P

#18 Re: Debug » DS finalize not running on Late 2015 imac16,2 iMac's » 2017-10-27 20:25:34

What disk format is that target partition?

Perhaps it's different because I'm actually imaging in the same workflow, but here is what I see in my similar recent log file (strings obfuscated for no good reason):

2017-10-24 15:37:41.455 DeployStudio Runtime.bin[332:13915] Checking if disk is complex (if it is associated with booter partitions)
2017-10-24 15:37:41.456 DeployStudio Runtime.bin[332:13915] GPT detected
2017-10-24 15:37:41.456 DeployStudio Runtime.bin[332:13915] Booter partition required at index 3
2017-10-24 15:37:41.456 DeployStudio Runtime.bin[332:13915] System partition found
2017-10-24 15:37:41.456 DeployStudio Runtime.bin[332:13915] Booter partition found
2017-10-24 15:37:41.456 DeployStudio Runtime.bin[332:13915] Preferred system partition found: disk0s1
2017-10-24 15:37:41.456 DeployStudio Runtime.bin[332:13915] Returning booter information dictionary:
2017-10-24 15:37:41.456 DeployStudio Runtime.bin[332:13915] <CFBasicHash XXXXXXXXXXXXXX [XXXXXXXXXXX]>{type = mutable dict, count = 3,
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915] entries =>
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915]     0 : <CFString XXXXXXXXXXX [XXXXXXXXXXX]>{contents = "System Partitions"} = (
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915]     disk0s1
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915] )
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915]     1 : <CFString XXXXXXXXXXX [XXXXXXXXXXX]>{contents = "Data Partitions"} = (
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915]     disk0s2
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915] )
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915]     2 : <CFString XXXXXXXXXXX [XXXXXXXXXXX]>{contents = "Auxiliary Partitions"} = (
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915]     disk0s3
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915] )
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915] }
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915] Substituting booter disk0s3
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915] IOMedia disk0s3 has UUID XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915] Setting EFI NVRAM:
2017-10-24 15:37:41.457 DeployStudio Runtime.bin[332:13915]     efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</string></dict></dict><key>BLLastBSDName</key><string>disk0s3</string></dict></array>'
2017-10-24 15:37:41.470 DeployStudio Runtime.bin[332:13915] Setting EFI NVRAM:
2017-10-24 15:37:41.470 DeployStudio Runtime.bin[332:13915]     IONVRAM-DELETE-PROPERTY='efi-boot-file'
2017-10-24 15:37:41.470 DeployStudio Runtime.bin[332:13915] Setting EFI NVRAM:
2017-10-24 15:37:41.470 DeployStudio Runtime.bin[332:13915]     IONVRAM-DELETE-PROPERTY='efi-boot-mkext'
2017-10-24 15:37:41.470 DeployStudio Runtime.bin[332:13915] Setting EFI NVRAM:
2017-10-24 15:37:41.470 DeployStudio Runtime.bin[332:13915]     IONVRAM-DELETE-PROPERTY='efi-boot-kernelcache'
2017-10-24 15:37:41.470 DeployStudio Runtime.bin[332:13915] NVRAM variable "boot-args" not set.

I'm also running version 1.7.5 of DeployStudio.

#19 Re: Debug » DS finalize not running on Late 2015 imac16,2 iMac's » 2017-10-26 22:58:12

On the iMacs in question, is there a ds_finalize.log in /var/log?

#20 Re: Debug » Inappropriate Repository Error » 2017-10-23 22:23:16

For the netboot set, I would change the destination to the desktop of the machine you are creating the set on.
There were issues, many moons ago, when creating the netboot set and automatically sending it to the NetBootSP0 folder on the server.
Ever since then, I've always created the netboot set on the desktop, then manually copying it to the server's NetBootSP0 folder.

Otherwise, I'm not seeing anything too odd...

#21 Re: Debug » Inappropriate Repository Error » 2017-10-19 18:33:00

If you are using a server, and netbooting to the server from your target machines, the DeployStudio server configuration must specify the repository as  "a network sharepoint" path.

One of the configuration windows is dedicated specifically to designating whether the server will use "a local folder" or "a network sharepoint".
Select "a network sharepoint".

In the next window, see the examples under the URL: field.
The URL will typically be like afp://yourservers.name/Images, or smb://yourserver.name/Images
You can substitute the IP address for yourserver.name if you suspect a DNS issue.

I'd recommend going into Server.app and unsharing your repository, moving your repository to /Users/Shared then resharing your repository.
It's counter intuitive, and possibly problematic to have the repository in your home folder.

#22 Re: Debug » uploading a new image seems to be limited to 4.52GB !!! » 2017-10-16 22:27:24

are you using an intermediary disk (typically the same disk you are capturing)?
how big is the intermediary disk? you need almost 3 times the image size in, free space, to complete a capture.

#23 Re: Debug » Runtime issue » 2017-10-13 20:18:49

Do you have more than one DeployStudio server running in that subnet?

#24 Re: Usage » Booting to Black Screen of Death » 2017-10-13 20:13:26

What are your specific netboot image creation steps?

#25 Re: Install » build v1.7.7 cannot create bootable NetBoot Set » 2017-10-09 23:54:53

On the master, try running the 10.12.6 Combo Updater on it, then create the .nbi?

Board footer

Powered by FluxBB