- Create Image For Deployment Mac Command
- Create Image For Deployment Mac Pro
- Create Image For Deployment Mac Mojave
- Create Image For Deployment Machine
- Create Windows Deployment Image
This blog post is being reprinted with permission from the original author, Ian North. We are extremely excited and pleased to get to share his post as a special guest blog this week. Read on for Ian’s how-to for configuring a Mac image in Microsoft SCCM and Parallels Mac Management, and let us know if you are experiencing an increase in Macs in your network and the steps you’re taking to keep them centrally managed.
I touched briefly on using Parallels Mac Management for Microsoft SCCM to build Macs in my overview article but I thought it might be a good idea to go through the entire process that I use when I have to create an image for a Mac, getting the image deployed and getting the Mac configured once the image is on there. At the moment, it’s not a simple process.
MDS 3 raises the level for a Mac Deployment service. MDS 3 includes package management with Munki, inventory fleet management with MunkiReport, MDM with MicroMDM, and much more. Quickly set up and deploy MDS 3 on a Mac and have all the resources you need to successfully deploy anywhere from dozens to thousands of Macs. If for any reason you can’t use a network boot during OS deployment, you can create a bootable USB drive (flash drive or HDD) and boot each Mac computer from it. To create a bootable drive, download the Image Builder utility to the Mac: In the Configuration Manager console, navigate to Administration / Overview / Parallels Mac Management / Mac Client Enrollment; In the Mac Client Enrollment list, right-click the Mac Client installation package download URL and then click Properties in the. Create and deploy network disk images in System Image Utility on Mac. To create a NetBoot, NetInstall, or NetRestore network image, you must have valid macOS image sources or volumes and be logged in as an administrator. If you download the Install macOS app from the Mac App Store, a valid macOS image source appears in the source pop-up menu.
It requires the use of several tools and, if you want the process to be completely automated, some Bash scripting as well. The process isn’t as smooth as you would get from solutions like DeployStudio but it works and, in my opinion anyway, it works well enough for you not to have to bother with a separate product for OSD. The Parallels team is working hard on this part of the product and they tell me that proper task sequencing will be part of V4 of the agent. As much as I’m looking forward to that, it doesn’t change the fact that right now we’re on V3.5 and we have to use the messy process.
First of all, I should say that this is my method of doing it and mine alone. This is not Parallels’ method of doing this, it has not been sanctioned or condoned by them. There are some dangerous elements to it, and you follow this procedure at your own risk and I will not be held responsible for damage caused by it if you try this out.
You will need the following tools:
- A Mac running OS X Server. The server needs to be set up as a Profile Manager server, an Open Directory server and, optionally, as a Netboot server. It is also needed on Yosemite for the System Image Utility.
- A second Mac running the client version of OS X.
- Both the server and the client need to be running the same version of OS X (Mavericks, Yosemite, whatever) and they need to be patched to the same level. Both Macs need to have either FireWire or Thunderbolt ports.
- A FireWire or Thunderbolt cable to connect the two Macs together.
- A SCCM infrastructure with the Parallels Mac Management SCCM Proxy and Netboot server installed.
- This is optional but I recommend it anyway: a copy of Xcode or another code editor to create your shell scripts in. I know you could just use TextEdit but I prefer something that has proper syntax highlighting and Xcode is at least free.
- Patience. Lots of patience. You’ll need it. The process is time consuming and and can be infuriating when you get something wrong.
Create Image For Deployment Mac Command
At the end of this process, you will have an OS X Image which can be deployed to your Macs. The image will automatically name its target, it will download, install and configure the Parallels Mac Management for Microsoft SCCM agent, join itself to your Active Directory domain, attach itself to a managed wireless network and it will install any additional software that’s not in your base image. The Mac will do this without any user interaction apart from initiating the build process.
The overview of the process is as follows:
- Create an OS X profile to join your Mac to your wireless network.
- Create a base installation of OS X with the required software and settings.
- Create a Automator workflow to deploy the Parallels agent and to do other minor configuration jobs.
- Use the System Image Utility to create the image and a workflow to automatically configure the disk layout and computer name.
- (Optional) Use the Mac OS X Netboot server to deploy the image to a Mac. This is to make sure that your workflow works and that you’ve got your post-install configuration scripts right before you add the image to your ConfigMgr server. You don’t have to do this but you may find it saves you a lot of time.
- Convert the image to a WIM file and add it to your SCCM OSD image library.
- Advertise the image to your Macs.
I’m going to assume that you already have your SCCM infrastructure, Parallels SCCM management proxy, Parallels Netboot server and OS X Server working…
[button link=”http://norphus.co.uk/2015/05/building-deploying-and-automatically-configuring-a-mac-image-using-sccm-and-parallels-sccm-agent/” color=”default”]Continue Reading[/button] Spotify Downloader Apk Old version.
Click the button above to continue reading Ian North’s blog on how to configure a Mac image in Microsoft SCCM and Parallels Mac Management.
Home > Articles > Apple > Operating Systems␡
- System Deployment Overview
This chapter is from the book
This chapter is from the book
Deployment Planning Template.pdf, available at http://www.peachpit.com/acsa.deployment
Mac OS X v10.5 installation media
This chapter takes approximately 6 hours to complete, but it could take much longer depending on the complexity of your deployment.
Select a system imaging technique that meets your deployment needs
Create a cloned system image
Create a modular system image
Deploy a system image both locally and via a network
For many deployments, the best solution is a unified system disk image, which involves creating an ideal system, saving it to a disk image, and then deploying that system to all your computers. A unified system image requires a significant time investment up front, but it saves a great deal of time in the long run. Computers with identical configurations are much easier to manage; the fewer the differences between your deployed systems, the more uniform their performance and the less time spent diagnosing problems, updating software, and reconfiguring hardware.
A unified system image also greatly accelerates the deployment process for any deployment larger than a dozen computers. Once you have fully configured, tested, and created a custom system image on one computer, it can take as little as five minutes to copy it to another machine. Compare this to the time needed to deploy the system individually on every computer, and it’s easy to see the benefit of a deployable system disk image.
In this chapter you will learn two methods for creating deployable system disk images: cloning and a modular system. Cloning is generally easier to implement, but the newer modular technique yields better results. You will also learn how to deploy your system image both locally and via the network.
System Deployment Overview
Before starting the process of creating a system image, you must consider your deployment requirements: what software and configuration settings will be part of your system image. Consider your users, your systems, and the limitations of identical-system deployment on multiple computers. You also need to consider which of the two deployment techniques will best suit your needs and abilities. The choices you make while planning your system image will affect every computer on which this system is deployed.
Defining System Image Requirements
When identifying all the specific items and configuration settings that you want to include in your system image, you must take into consideration the requirements of your users, the technical requirements of your systems, and the limitations of deploying an identical system on multiple computers.
Your primary focus when developing system image requirements should be on maximizing system usability, for both users and administrators.
In some cases your target audience or usage policies may require tighter system control. This is often the case when users are inexperienced or cannot be trusted to manage any part of their systems. In this scenario you would limit application access and lock down as many system configuration settings as possible. You would also want to make things easy for the user by preconfiguring any system setting you can. As discussed in Chapter 1, “Deployment Planning,” in scenarios where you will be performing a significant amount of client management, you should incorporate directory services–based MCX settings.
In professional or creative environments, you may not need to be as restrictive in the application or settings, but you should still make sure to prepare the system based on the users’ needs; for instance, install third-party applications and peripheral drivers for inclusion with your system image.
No matter the level of your users, your system image should be as fully configured as possible, with both Apple and third-party software installed and updated, any necessary support files such as third-party drivers and fonts installed, and any systemwide configuration settings implemented. Note, though, that many settings are not well suited to deployment via a unified system image—more on this topic later in this section.
Computer-Specific System Requirements
Before you create your system image, you must determine which version of Mac OS X you intend to use.
A major administrative advantage of using Mac OS X v10.5 and Mac OS X v10.5 Server is that they are built as universal operating systems and will work on any Mac that meets the minimum system requirements, allowing you to build a single system image that can work on any Mac.
Although creating a unified system image for computers that support Mac OS X v10.5 is simple, creating a system image for brand-new Macs can present a significant problem. In many cases, because the release of new Mac computers is not in sync with the release of the retail version of Mac OS X, a custom intermediate version of Mac OS X is created just to support the new hardware. However, new Macs cannot run versions of Mac OS X released prior to their introduction—that is, the oldest version of Mac OS X supported by a new Mac computer is the version that it ships with from the factory.
Thus, a previously created system image will not work on new Mac computers, and you will have to create a new system image based on the version of Mac OS X that shipped with the new Macs. Further, these custom intermediate versions of Mac OS X may technically work with older Mac computers, but they are not officially supported by Apple to do so, presenting a problem when you are trying to build a single unified system image.
Fortunately, every general Mac OS X version update includes support for all Mac computers introduced prior to the update. For example, if you were to acquire new Macs that were introduced this week, the next general update of Mac OS X will include support for those new Macs and will support older hardware as well. Therefore, if you can wait to build your system image until you can base it on the next general update for Mac OS X, you can create a single system image for all your Macs. If you can’t wait that long, you will need to create a separate system image just for your new Macs.
It’s important to note that custom intermediate versions of Mac OS X for new computers do not sport different version numbers from the general releases. They do, however, have different build numbers, which can be identified by clicking once on the version number from the About This Mac window.
Software Update Requirements
You should strive to build your system image using the latest versions of your selected software. To do this, you’ll need to collect and keep track of all the necessary software update installers that you’ll need to apply when building your system image.
- Determine and acquire the latest version updates for Apple software by doing either of the following:
- Go to the Apple Download website at http://www.apple.com/downloads/macosx/apple/. This website lists all the latest updates and can be searched and browsed so you can locate and then download specific Apple software updates.
- Install all your Apple software to a test system and open the Software Update application to see a list of all the available updates for your installed Apple software. Download the individual updates by choosing Update > Download Only.
- Verify that you are using the latest versions of third-party applications and drivers.
Many third-party products feature a built-in automatic update system that will check online for updates. However, few of these third-party update systems will allow you to download the individual update installer so that you can later use it to build your system image. In these cases visit the software developer’s website to download the individual update installers.
Limitations of a Unified System Image
You should include as many configured settings as possible with your system image so you don’t have to spend time setting these items on each individual computer. However, there are many settings that you should not, or cannot, deploy with the same configuration to every computer.
For example, in most cases, user-specific settings should not be included with your system image. Computer-specific settings also should not be configured on the system image. For instance, a unique IP address and network name needs to be set for every Mac. Both user- and computer-specific settings are best handled using dedicated client management tools and techniques.
In deploying a Mac OS X Server system image, your primary goal will be to strike a balance between what you can safely configure as part of the generic server system image and what settings you must leave for after deployment.
Choosing a System Image Technique
When using the tools built into Mac OS X to create a deployable system disk image, you have a choice between two different techniques: cloned system images and modular system images.
With the cloned system image technique, you first set up a model computer that is configured with all the software and settings you intend to deploy. Then you create a duplicate copy of the system volume saved to a disk image that has been specially prepared for deployment.
The modular system image technique, a newer method, requires a bit more work upfront, but it has several advantages over the older method and is the Apple-recommended technique. With this technique you build a fresh system by installing a series of installation packages to a sparse disk image. The installations include the full Mac OS X system, any software updates, any additional Apple software, any third-party software, and any custom installation packages that you have created to set up your system image. This sparse image is then converted to a disk image that has been prepared for deployment.
Cloned System Image Pros and Cons
Pro—Easier workflow for novice administrators
Pro—Less time spent creating initial system image
Con—Requires that the model computer be purged of any unnecessary or troublesome files
Con—Prone to issues if model not properly “cleaned”
Con—Prone to more issues when deploying to different models
Con—Increased workload when creating multiple system images
Con—Increased workload when it’s time to update the system image
Con—New system images are never consistent with prior images
Con—Difficult to document and audit system image configurations
Con—Increased workload to test system image modifications
Create Image For Deployment Mac Pro
Modular System Image Pros and Cons
Pro—System images are clean because they have never been booted
Pro—System images have no model-specific settings
Pro—Apple updates won’t interfere with your customizations because they are always applied prior to your customizations
Pro—Decreased workload when creating multiple system images that require unique software and configurations
Pro—Decreased workload when it’s time to update system images
Pro—Multiple and updated system images are perfectly consistent for similar items every single time
Pro—All configurations are fully documented and easily audited
Pro—Simplified testing for updates and image modifications
Pro—System image creation process is easily automated
Pro—Easily integrated with system maintenance workflows and third-party deployment tools
Con—More difficult workflow for novice administrators
Con—Requires creation of custom installation packages for some third-party items and any configuration settings
Con—More time spent creating initial system image
The cloned system image technique requires less effort upfront, and you can get your first image set up quickly. However, in the long run you’ll have to spend much more time fixing bugs, updating software, and adding modifications than with a modular system image. The modular system image technique requires more initial effort to get your first properly configured system image, but maintaining your systems will be much easier because you’ll be able to build new modular images with additional items and updated software.
Create Image For Deployment Mac Mojave
- Book $55.99
Create Image For Deployment Machine
- eBook (Watermarked) $55.99
Create Windows Deployment Image
- Web Edition $55.99