How to distribute and install more than one boot image on a client
Using DeployStudio workflows under General Tasks you will find "Partition a disk"
Partition a disk in to single, dual or triple boot partitions and is pre-configured with various options or can be custom configured. The size and partitioning scheme can be modified so that it is customized for the specific desired partition mappings. Partitioning of the disk is necessary since current Mac lab machines would contain only one image.
This step will concentrate on deploying a dual boot system with the Mac OS X image and Windows image created using the previous workflow. It will include a description of many of the relevant workflow objects including: partition the disk, restore images, bind to Active Directory, bind to Open Directory, install packages, run scripts, reconfigure the system, set the firmware password and shutdown the system when finished. The many steps to create this workflow are as follows:
- Launch DeployStudio Admin.
- Select WORKFLOWS.
- Click the “+” button at the bottom of the window.
- Double click the newly created workflow and rename it “!MultiBoot Restoration and Customization”.
- Next to where it says “Drop tasks here”,select the “+” button.
- Before imaging a volume it must be partitioned. There are a number of partition options, some of which are important to understand with multi-boot deployments. Drag the “Partition a disk” icon to the “Drop tasks here” location and customize the settings as follows:
- Specify the “Targetdisk:” volume name (i.e., “Macintosh HD”). Note: “Partition the first disk available” may be chosen but this could be problematic on Mac Pros with multiple internal drives or external USB or FireWire drives connected to the system. The first drive available is the drive that spins up the fastest. Note: Choosing the available drives from the drop down “Target disk:” menu will only show drives visible to the running DeployStudio Admin system and may not reflect the drives that will be deployed to, when an actual deployment occurs.
- From the “Apply layout template” drop down, choose “MacOSX+Windows” (if dual booting mac OS and Windows) Note: When adding more than three partitions, because of the EFI plug-in used on Mac hardware, the Windows partition must always be the last partition created. It is important to note that Macs use a hidden EFI partition, which will be visible using the “diskutil list” command in Terminal. In an example where the machine will be set up using a Mac partition, a FAT32 partition and a Windows partition, the Windows partition will technically be the fourth partition. In an example where Linux, Mac OS X, Windows and a shared partition are deployed, DeployStudio recognizes the first EFI partition and properly places Windows as the third partition when partitioning the drive. Mac OS X will be the fourth (technically fifth) partition, as DeployStudio does not actually display the EFI partition in the list.
- Rename the volumes accordingly (i.e., Macintosh HD and BOOTCAMP). To do this, mouse over the partition name and click the pencil icon in the upper right corner. To complete the partition rename click the check mark icon, which now appears after clicking on the pencil icon. Note: These partitions will be renamed when the image is deployed, based on the name of the master image(s). The name will be important and used in the next step where the “Restore a disk image” task must have the correct name of the partition to restore to.
- Adjust the size of the partitions by adjusting the slider bar(s) to the desired partition size or click the pencil icon (when mousing over the partition). Then set the percentage accordingly. Linux partitions must be set to a GB value manually.
- Leave “Write random data to the disk before partitioning (takes a lot of time)” unchecked. Use this function only if you need the existing data on the drive to be overwritten in a secure manner. This process could take several hours depending on the size of the drive and speed of the machine.
- Check Automate.
- Restoring a Mac image is straightforward but does offer a number of useful options. Drag the “Restore a disk image” to the right of the “Partition task” and customize the settings as follows:
- Specify the“Target volume:” as “Macintosh HD” or whatever name the partition was given in the Partition task step.
- Choose “HFS” from the “Image:” drop down menu.
- From the drop down, select the Mac .dmg created by the previous Dual Boot Master Image Creation Workflow.
- Uncheck “Restore image on the first drive available”.
- Leave “Rename volume to:” blank unless another name is required.
- Check “Donʼt check restoration (faster)”.
- Check “Erase target for block copy restoration (faster)”.
- Check “Rename By Host prefs”.
- Check “Cleanup machine dependent files and caches”.
- Uncheck “Enable multicast restoration”.
- Uncheck “Expand restored NTFS volume”.
- Check “Set as default startup volume”.
- Check “Automate”.
- Deploying a second Restore task for the Windows image is similar to deploying the Mac image, albeit with a few settings differences. Drag the “Restore a disk image” again to the right of the “Restore task” and customize the settings as follows:
- Specify the “Target volume:” as “BOOTCAMP” or whatever name the partition was given in the Partition task step.
- Choose “NTFS” from the “Image:” drop down menu.
- From the drop down, select the Windows ntfs.gz created by the previous DualBoot Master Image Creation Workflow.
- Leave “Rename volume to:” blank unless another name is required.
- Check “Donʼt check restoration (faster)”.
- Check “Erase target for block copy restoration (faster)”.
- Uncheck “Rename By Host prefs”. Note:This setting is irrelevant to Windows images, but will not effect the deployed image if checked.
- Uncheck “Cleanup machine dependent files and caches” .Note: This setting is irrelevant to Windows images, but will not effect the deployed image if checked.
- Uncheck “Enable multicast restoration”. Note: Multicast deployments are not possible for Windows images.
- Check “Expand restored NTFS volume”. IMPORTANT: Be sure to check thisoption so the Windows image will utilize the full Windows partition. Unchecking this option can result in unusable space on the Windows partition.
- Uncheck “Set as default startup volume”. IMPORTANT: Mac OS X has several tasks to run at start up, as well to finalize the deployment of the image. Note: Whichever volume is “Set as the default startup volume” last in the Workflow will be the default start up volume.
- Check “Automate”.
Other tasks can be performed on each partition.
Problems
-- EdwardChrzanowski - 2015-01-23