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: Future » Workflow item SDK? » 2015-07-08 20:42:48

n8felton and I are wondering if there are any updates. We're presenting on DS tomorrow.

#2 Re: Usage » Trusted binding to OD » 2013-05-25 02:47:11

is the account you're using for authenticated binding work to bind? Does it work in the GUI with the same settings you give DeployStudio?

#3 Re: Install » need help » 2013-05-24 01:37:00

Are you speaking about running the DeployStudio Assistant to setup a DS server? Like the screen at 6:08 here?:

Could be that you just need to type it in, do you know the address to your current server? Or is this the first time you've set up DeployStudio? Do you have network connections? Is DNS forward and reverse working?

#4 Re: Usage » How can I deploy installESD.img and auto add users? » 2013-03-28 19:44:22

I would suggest using createOSXinstallPkg and CreateLionUser.pkg.

#5 Re: Debug » iMac won't boot » 2013-03-13 14:20:53

You can try to apply the 10.8.2 machine specific install over top the restored image. Try to do an Internet Recovery on the iMac and see if it works!

#7 Re: Usage » DS corrupts unattend.xml during deployment of Windows image » 2013-02-12 21:07:14

I've never touched unattended.xml files, can you pair it down to just a few things, like naming and something else minor for testing? If it works, start adding the other junk back in?

#8 Re: Install » Big Problem :( Client NetBoot doesnt appear in startupdisc » 2013-02-12 21:06:13

Try making the netboot set on the client, then copying it to the server.

#9 Re: Install » imac wont connect to net boot server after update to 1.0rc134(b121013) » 2013-02-12 21:05:04

Your webserver looks like it's out to lunch. Can you reinstall the server OS?

#10 Re: Install » Netboot issues » 2013-02-12 21:02:42

Try re-creating the netboot set on the hardware you want to netboot.

Disable all other netboot sets.

#11 Re: Install » Runtime » 2013-02-12 21:01:27

Do you get any errors in the logs?

#12 Re: Usage » Escaping $ in DeployStudio Scripts Parameter field » 2013-02-12 21:00:16


sudo dscl . passwd /Users/$1 ${3}

The {} expand the variable before passing it to the dscl tool.


$ ./ Te$t Thi$ $cript
1: Te
2: Thi$

Run it yourself:


# Written by Rusty Myers
# 2013-02-12


echo "Variables\n"
echo "1: "$1
echo "2: "${2}
echo "3: $3"

exit 0


#13 Re: Usage » Package installs regardless of InstallationCheck script failure » 2013-02-12 20:53:21

Try adding more logging to your VolumeCheck that you can use to determine what it's doing during runtime. Post the logs here.

#14 Re: Usage » Trusted binding to OD » 2013-01-18 15:18:21

You could try running your own script to bind:

#15 Re: Install » Repository Error! Help! » 2013-01-17 21:27:33

When you set up the DeployStudio server, you tell it to use the network share and give it the AFP server/path. Is this how you set it up:

#16 Re: Install » Repository Error! Help! » 2013-01-17 19:14:38

When you set up DeployStudio, did you tell it to look for a local repository or a network repository? I'm guessing you said local, pointed it to the folder on your server, then tried to netboot a mac with DeployStudio. It tried to find the local folder and couldn't. You'll probably need to specify a network share in DeployStudio Assistant.

We talk about this in our setup video:

#17 Re: Debug » NB121205 and 10.8.2 » 2013-01-15 15:31:10

Is this making an NBI from an firewire/thunderbolt attached device? Are the permissions set to ignore on the device?

#18 Re: Usage » Master DS with two Replica's » 2013-01-15 15:28:54

Try running through the DeployStudio Assistant again and setting the replica as a master.

#19 Re: Install » DHCP » 2013-01-15 15:23:28

Did you manually configure your OS X server with the router IP for the subnet?

#20 Re: Install » Trouble getting Mac's to netboot » 2013-01-15 15:21:02

Here are a few of Apple's suggestions for netbooting:

I'm guessing you need to configure "bootpd relay to forward requests"

#21 Re: Install » triple boot questions » 2013-01-15 15:19:31

Try creating the OS X partition first. You may want to recreate the OS X image so that it doesn't include a recovery partition, too.

#22 Re: Usage » Active Directory Binding » 2012-12-19 00:34:26

Sounds like you have the ou wrong...

try to run this command from a Mac that was bound to AD while logged into the mac (GUI):

dsconfigad -show

Perhaps what it's using is different from what you've put in DS.

#23 Re: Install » AFP vs NFS » 2012-12-03 19:31:48

What's the question here?

#24 Re: Install » I currently rebuilt our deployment server and reinstalled DS » 2012-12-03 19:30:47

When you installed DeployStudio, did you set it up to point to a network repository share or local repository?

#25 Re: Usage » same image for different material » 2012-11-30 14:40:57


You could deploy the image to all of them, but it may not work.
Check this kbase article from Apple:

It will show you which build shipped with each model. If the build you created is newer than what was shipped with the other Macs, you're probably OK.

However, in some cases Apple creates special builds for only certain machines. Lets look at the latest shipping versions for each of the models you have recently received:

Model | Supported Builds
MacPro (Mid 2012): 11D2001, 12A269
Mac Mini (Late 2012): 12B2100, 12C2304
MacBook Air (11-inch, Mid 2012): 11E2520, 11E2702, 12A269
MacBook Pro (Retina, 13-inch, Late 2012): 12B2100, 12C2304

Since we don't know which models you've purchased, I've just grabbed a few for example purposes.

You can see each of the models has multiple supported builds. You should be able to compare the latest ones. From the above list, it would look like the MacBook Pro (Retina, 13-inch, Late 2012) (and the Mac Mini) has the latest build because it starts with '12C', where the rest of the builds start with 11 or 12A &12B.

So, based on those builds, you should be making an image from a Mac that has 12C2304 installed. That build, theoretically, has everything that the other Macs would be expecting.

I'll skip a long lecture on why you shouldn't be making a single image to deploy to multiple machines because of problems that builds can cause. I will say, you may not immediately see problems when deploying the image, but things could pop up later. I've heard of images being deployed to iMacs that caused fans to not run and the hardware to overheat. Since there were no fans, no one noticed it until multiple Macs were burnt out. Thin imaging, or modular imaging, is often a better option. Since I don't know your exact deployment scenario, I can't say what's best for sure.

TL;DR: Yes, it should work.

Board footer

Powered by FluxBB