Join Sean Colins for an in-depth discussion in this video Preparing for network imaging, part of Imaging and Deploying Macintosh Computers.
- View Offline
In this final chapter, we're going to go over the process of network to network imaging using DeployStudio and NetInstall. Let’s start talking about preparation for that network imaging process. First of all, to get started with this, we're assuming that you already know how to set up an OS X server. If you don't know what you need to know, in order to get that going, you need to go over and watch Up and Running with OS X Server, which is also on the online training library, also authored by Shawn Collins.
It gives you everything you need to know to get up to this point. And, in fact, includes about eight minutes of movie time devoted to the process of simply getting up and running with the NetInstall service. So, that's got everything you need to know to get up to this point and be functional for this chapter. Before you get started in your environment, coordinate with your IT department, let them know what you're doing. Specially if you're going to be working in the multi-cast portion of this chapter. Multi-cast, as you'll hear in the next movie, has some big concerns that you need to be aware of and that you need to make your IT department aware of.
You need to plan accordingly and they will help you with that. Be sure your ports are open between your server and your clients, if you've installed a firewall on your server be sure you aren't blocking the necessary ports. Check all of your cables. And once you've got everything ready and you think it should work, test your network deployment to one computer. See if it works. If it does work, you're good to go and you can deploy to many more computers. So, I mentioned ports to open. Let's talk about those again. We've talked about those in a previous movie but it bears mentioning here.
67 and 68 for UDP for DHCP and BSDP, discovery. 69 UDP for TFTP, that's to load the kernel and booter across the network to the client so that they can net boot. UDP and TCP over 2049 for NFS. That is to continue loading the operating system that the client will boot from. And then TCP 80 for HTTP and TCP 548 for AFP, or 139 for SMB, and that's in the DeployStudio environment for accessing the repository and for image transfer across the network.
So, make sure that those are open as well, and you'll be successful. Server concerns. Remember DHCP is a must. You've got to have that present on the network you're imaging from. If you are working on a network where you've pulled the uplink, that means your DHCP server is going need to be on this little segregated network you're creating. OS X Sever is enormously beneficial in this process. There are ways you can hack other operating systems to do what you need to do here. But it is far, far easier for you to do this with OS X server.
I highly recommend it. It is what we're teaching. File sharing and NetInstall are obviously mandatory here, otherwise your files aren't going to get across the network and your clients won't be able to net boot into an NBI set. And, of course, DHCP may be hosted elsewhere on the network. But it can be hosted on the server if you're on a segregated network. For troubleshooting, don't forget that Apple has a great support area where they have support articles and you can look up technical service document TS 3678 and you'll be able to get to some more information about this. That file hasn't been updated in a couple of years, but it still has some very useful information if you need further troubleshooting.
- 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