#DEPLOYSTUDIO SERVER HOW TO#

The Runtime will connect to the DeployStudio server, mount the Repository, and let you run whatever deployment workflows (imaging/updating/configuring/whatever processes) you have set up. This is a NetBoot image (.nbi) that you'll serve from your NetInstall server, which boots clients into a 'DeployStudio Runtime' environment.

#DEPLOYSTUDIO SERVER HOW TO#

This does a number of things, but the most important is to tell clients how to mount the Repository. A Mac running the DeployStudio server daemon.

An AFP, SMB, or NFS file server sharing a 'Repository' folder that'll contain the master images, installer packages, scripts, etc.

DeployStudio is more flexible and powerful than the basic NetInstall service, but it's also more complex to set up. While NetInstall doesn't support Windows ( or Linux images, there's a free third-party package, DeployStudio that supports them (as well as OS X images). nbi folder) is created, copy it to whatever version of OS X Server you're running, drop it in /Library/NetBoot/NetBootSP0, and it'll be available in the Server.app interface. So if you want a Yosemite image, you need to copy the Yosemite installer to a Mac running Yosemite, and run the Yosemite version of System Image Utility. It can serve multiple versions (El Capitan, Yosemite, Mavericks, whatever), but you must create the images under the same major version as the image you're creating. The NetInstall service only (directly) supports OS X network images.

Deploystudio server