Here in our Small Dog Support room we’ve begun the process of giving our server a much-needed sprucing up. After clinging to our last generation Power Mac G5 for as long as we could we have finally moved to a Mac Pro and have made the switch from our beloved, but outdated, NetRestore to the hipper and more functional DeployStudio.
I’ve been playing with DeployStudio for several months now and have been very impressed with its endless features. The first big question that I’m sure you’re asking is, “What the heck is DeployStudio?” It’s a set of netboot tools that includes an interface that helps automate master image creation and restore to machines across the local network. The features go far beyond stationary image creation and restore by supporting customized workflows including drive partitioning, multiple-OS restores, User creation, Open and Active Directory Binding, and even full scripting support. Beyond full image deployment, it’s also possible to send individual packages across the network for easy updating.
There are several ways DeployStudio can be an exciting addition to the netboot service in Server. My first experience with it was setting it up for a local school district who, up until now, has been imaging their Macs one at a time. With DeployStudio, they’re now able to create an image on one machine, netboot that machine to their Mac mini running 10.6 Server, create the master image and then netboot an entire lab of machines and let them restore from that master overnight. After restore, the workflow they’ve created in DeployStudio binds each of the machines to their Active Directory server, installs custom printers, and authenticates Adobe software. Basically, it eliminates their need to go machine to machine to tweak things after imaging. Talk about a time saver!
In our shop, we have a few specialized needs for DeployStudio. It’s a simple way to run customer backups directly to our server; just netboot the machine and create a master image from the customer’s machine. We also create master images from brand new machines so we can quickly and easily restore machines that are returned or exchanged. This also helps us image drives when we perform hard drive replacements or Erase and Installs for customers.
Netbooting machines can also be a great troubleshooting technique. For example, if a machine will not boot from its internal hard drive, but has no problem netbooting, we know the issue is with the software or hardware of the computer’s internal hard drive. We also use our own Netboot Image (NBI) that includes some of our favorite troubleshooting software, such as Disk Warrior, Drive Genius and Data Rescue, for an even better troubleshooting solution. Using netboot functions for troubleshooting and restore, as opposed to external hard drives or CDs, saves us space, money, and the hassle of keeping several drives up-to-date.
Our IT department is jumping on board too, and is using DeployStudio to deploy new images and updates to our work stations. One of the big allures of DeployStudio is the security features. One can set DeployStudio to require authentication upon netboot, transfers can be encrypted across the network, and machines allowed to netboot can be limited by MAC address, group, or several other criteria. The features are not only robust, but since the software is Open Source it’s constantly being updated and the source code is fully available for your tweaking pleasure.
Obviously, DeployStudio is not for everyone. One of cons (though some of us find it a pro) of Open Source software is that no one is going to hold your hand through the process. There are great forums available on the DeployStudio website, but I do recommend only undertaking the setup if you have some basic experience with Mac OS X Server and the patience to make adjustments to your setup as needed. As for hardware requirements, the software can be run in Mac OS 10.4-10.6.2, but to take advantage of the netboot functions you will need Mac OS X Server running 10.4 or higher; my experience has been in 10.5.8 and 10.6.2 Server. That also means that you need a machine that can handle Mac OS X Server. To get the process running smoothly, I also recommend using gigabit ethernet across the network. It’s never recommended to netboot wirelessly.
If you’re feeling adventurous and decide to give DeployStudio a try, I’d love to hear how you use it and how it works for you!