Join Sean Colins for an in-depth discussion in this video Configuring a simple workflow, part of Imaging and Deploying Macintosh Computers.
Now that we have deploy studio set up, we can open up the admin console, and we can start working with it. So let's go to our utilities menu, and let's go to the folder, and open up the admin software, deploy studio admin. And when we do, it will present you with a username and password field where you can log in. And yours may not be pre-populated, but yours should if you followed along with me. List 127.0.0.1 as the IP address of the server you're connecting to. That means all internal.
And you're going to be putting in your username and password and clicking Connect. Okay. Once you get in here, we have several different areas along the side. We have Activity, which shows activity. Computers are all the computers that DeployStudio on this hard drive has ever encountered. Workflows gives you the list of work flows. We'll be talking about how to create a simple one of those in this movie. Masters shows you all the masters that have been created and packages and scripts, which mirror exactly what is inside of the repository folder that we set up in the previous movie.
We have our configuration profiles, the databases, the Database of Computers, Files, Masters, Packages, Scripts, all of these things. Masters, packages, scripts show up right there. Our files, and so forth, show up inside of workflow element. So let's get into the workflows and I'll show you what that looks like. Now, by default, we get four workflows that are great examples that can help you to sort of build your knowledge. One is just going to create a master from a volume. And for the most part, you could almost use this as it comes to build a default master image.
We're going to show you some tweaks that you can make and then we'll create a master image in a later movie. You can also install a package with this one. This is great because you could just boot any computer into DeployStudio and boom, install a package. It makes it super easy. That's kind of cool to. Restore a master in a volume is a great way to restore one image on one partition without doing anything too fancy. And then a triple OS restore is their example of doing something a little more fancy, right? You're building three different partitions on a drive as it's encountered by DeployStudio.
And then it installs a different operating system on each of the partitions. kind of nifty. So, let's talk about a simple workflow. Creating a master from a volume is about as simple as it gets. And it comes with the system as a example. If you wanted to modify this, you'd click the little plus button next to the workflow area here. And you would add, any of these additional workflow items. And as you can see, there's a lot of them. We'll be talking about many of these, not all of them, but many of these in later movies.
But for now, let's just say we're going to work with only what we have here in this window. Let's explain this, what we have in front of us. So, a disk image is what we're going to be creating from our master. And as you can see here, we're booted from a Thunderbolt drive, and our Macintosh HD. The internal hard drive on the system where we have this external drive booted, is here. But because it's not the booted volume, we can unmount it, and we can make an image of it, which is awesome.
So, I'm just going to allow the user to pick a source rather than defining one ahead of time. We're definitely going to create a compressed read only image and we're going to not auto detect. We are going to say that the format is HFS plus journaled because HFS plus journaled is what we are going to be making images of. And OS10 works much, much better in an HFS Plus journaled volume, right? We don't want to be case sensitive journal, just HFS Plus.
There are some edge case scenarios where that might be useful, you're not going to be working with one of them. We're going to use HFS Plus journal, you can add key words here if you wanted to, but we're not going to. And then we're going to uncheck image NTFS volumes with OS10 built in tools. Because we're not going to be imaging NTFS volumes here. We're simply going to be creating an image of an OS10 volume. We're also not going to try to create intermediate files on a local volume to preserve network bandwidth. A, we're on a local hard drive in this case, so that's irrelevant.
But B, we mostly won't do that, even when we are doing a network deployment because we are recommending that you go with a gigabit network across the board. You're not going to be on a network that is 100 megabit or slower, if you're following our recommendations. And so you don't need to worry about preserving network bandwidth. Also, if you put all the intermediate files on a local volume, that local volume is likely going to be the same volume on which your booted, and you may run out of space and certainly there are speed concerns with reading and writing and all of that.
It's much, much better to get everything written over to your repository as quickly as possible. So, we're going to leave that unchecked, all three of these, in fact unchecked. And we're going to uncheck Automate. Because I want to be able to go into the system and boot from the deploy studio solution. I want to go into the, to the workflow and when I'm running the run time, I want to be able to choose options when I get to that point. When I get really comfortable with my workflow, and this is the case with even the complicated workflows we'll show you next.
Automation can be a great time saver. But only after you've tested the workflow, and you know that every part works. You certainly wouldn't want to automate something before you test it, right? It makes sense. So I'm going to click save. Once you've clicked save, that is now committed to the database, and the next time you go into the runtime, you will see the results of your work. I'm going to quit the DeployStudio Admin software, and whenever we get to making a monolithic image, you will see us use that very workflow when we create that monolithic image
- Exploring the monolithic and modular imaging methodologies
- Working with Fusion Drives and Recovery partitions
- Ensuring physical security and installing a firmware password
- Choosing source hardware
- Installing apps
- Building a complete monolithic master for imaging
- Deploying apps and accounts in a modular master system
- Building a base master
- Performing hard-drive-to-hard-drive imaging
- Exploring VLANs
- Performing network-to-network imaging
- Deploying using NetInstall or DeployStudio across a network