Best Practices for Dual-Boot Deployments?

[brlittle]

Right now, we use DeployStudio to drop monolithic images on Mac and Windows partitions for our dual-boot machines in public facilities. I'm looking to change the Mac side procedure to a thin imaging routine as described at JNCU 2011 by Robert Hammen. Any suggestions for the best way to handle the Windows side?

Since we can't PXE boot the iMacs or Mac Pros, we're thinking about using JSS to cache a basic Windows OS image to the Mac partition, then having WinClone image the Windows side. From there, SCCM would take over. Sound reasonable? Better/worse than sticking with DeployStudio? Anyone else doing anything like this?

B

[brad]

Not sure if this is best practice but we use winclone images Self Service policies. The Self Service policy has a script that adds a partition and then images the new partition with the winclone image. We can also trigger that policy a few different ways. For lab machines we can just trigger that policy with the jamf policy -id # command. This policy is only scoped to our IT staff.

[brlittle]

That is an especially slick process. We build systems at user request by total reimage, but I see a lot of potential in what you're doing WRT our personal workstations.

Most of what we do dual-boot, though, is deployment to labs, where everything is prebuilt and shared, with minimal post-deployment attention from staff.