/build/static/layout/Breadcrumb_cap_w.png

Bootcamp os x/win 7

I am in the process of developing a better method for imaging our dual boot Mac lab and am looking for a way to image it with Kbox. I am not sure how I would go about formatting and partitioning in the preinstall script, specifically the ntfs partition for Windows 7. Has anyone had any success or could shed some light on this?

0 Comments   [ + ] Show comments

Answers (7)

Posted by: WhitzEnd 8 years ago
7th Degree Black Belt
1
Resurrecting an old question.  But here is another option that allows you to do it in one imaging job.  There is a tool called winclone that you can use to capture a windows install from a bootcamp partition  then deploy it out as a post install task during your mac imaging job.  

Posted by: Blacks2 13 years ago
Orange Belt
1
Okay, I am aware Kbox does not officially support this process.

However, I feel I am extremely close. Here is what I did:

Built a full image with OS X & Bootcamp Windows 7

Captured both the OS X partition and Bootcamp partition

Boot to Kbox OS X boot environment. Have a preinstall task set to partition the drive into two parts... HFS and FAT32, with the FAT32 set to 80 GB and the HFS set for the remainder of the drive. HFS is in partition 02 and FAT32 is in 03 (with the EFI being in the first portion).

Load up the OS X image, then reboot into Windows Kbox environment from a boot CD

Preinstall task under Windows is set to use the convert command to convert the FAT32 drive to an NTFS partition, and then it deploys the Windows partition.

The Mac sees the Windows partition under Startup Disks, however if I hold option on boot it does not show up on the boot menu, and if I try to boot to Windows I get a Disk not Found black screen error.

I have a feeling it's some kind of MBR issue... I feel I am so close to solving this with that minor issue. Any assistance would be welcome as I really need to get a solution for deploying this dual boot image for our organization ASAP.
Posted by: MisterVertigo 11 years ago
Senior White Belt
1

I haven't tested this, but I wonder if it would work. Reading the original reply here gave me the idea, so I certainly can't take all the credit if this works. When I have a bit of time here I'm going to test this and see what happens.

  1. Setup the source Mac with both operating systems
  2. Capture the OSX partition by itself in it's own image
  3. Boot the Mac into a Windows KBE via a CD
  4. Capture the Windows partition
  5. On the destination computer, deploy OSX on a single partition
  6. Once the image is complete, run the Boot Camp setup. I think this is required to get the MBR setup properly on the drive so it can recognize the bootable Windows partition. Let the utility partition the drive, but don't install Windows.
  7. When the Mac shuts down, boot it to the Windows KBE again from the CD
  8. Deploy the captured Mac Win 7 image to the newly created NTFS partition.
It's not perfect, as you have to manually run the Boot Camp assistant utility, but I think that is required to get the MBR set properly. Before I had my KACE appliance I used another tool to image macs and it was a similar two-step process. With KACE though, you may be able to use the same Windows 7 images that you use for PCs if you can set up a post-install task to install the Boot Camp drivers.
 
Here soon I will test this and see what happens, but if any of you have a chance to test it first let me know!
Posted by: fizban1 12 years ago
Senior Yellow Belt
0
By chance, is there an update on this project?
Posted by: ScottinOkla 12 years ago
Orange Belt
0
I am interested in learning of updates to this thread also.
Posted by: MisterVertigo 11 years ago
Senior White Belt
0

Well, my process worked up until the same point the original poster got to. The BOOTCAMP partition does not appear in the boot menu, but it does in the Startup Disks. If I try to boot to it though I get the same error as above.

Posted by: MisterVertigo 11 years ago
Senior White Belt
0

I got it to work! I was able to use my existing PC Windows 7 Pro 64 bit images on the Bootcamp partition of an Apple MacBook Pro. Here is what you will need:

  • An Apple computer
  • Windows operating system disc (for me, I used Windows 7 Pro 64 bit. I would assume Windows 8 would work as well, but I have not tried)
  • A boot CD or bootable USB drive of your Windows 64 KBE
  • A captured Windows image. I use WIM images but I believe K Images should work too.
  • A Postinstallation Mid-Level task to run a DiskPart script (detailed below)
The first thing I did was make a duplucate copy of my PC Windows 7 image. In the new copy I am going to have a few different Pre and Post install tasks as I do on a PC. For Preinstallation Tasks, make sure you do NOT have any tasks that change the partition tables or boot records. You will need to use the "Format C: as NTFS" task though. I copied the default one and modified it to add the "BOOTCAMP" label to the drive.
 
Now, the important step. I created a new Postinstallation Mid-Level Task that runs a DiskPart script to make the Windows partition on the drive active. This is why it will not boot. Create a text file called script.txt. In the text file put the following commands:
 
LIST DISK
SELECT DISK 0
SELECT PARTITION 3
ACTIVE
EXIT

On my computer the last partition was number 3, but you may want to check your systems to make sure. Now, create a new Postinstallation task of the type "Application". Upload the script.txt file, and put the following in the Command Line box:

 diskpart.exe /s script.txt

Make sure in the Postinstallation Task Detail window you choose "K2000 Boot Environment (Windows)" as the Runtime Environment.

Now, just add this new task to the image. I made it the last thing that runs.

It's time to deploy! Here are the basic steps I took:

  1. Setup the source Apple computer as a single boot Mac OSX machine
  2. Once everything in the OSX system is set as you like, capture the image by netbooting the Mac into the Mac KBE.
  3. You can now deploy the Mac image to another Apple computer, or continue using the source computer.
  4. Boot the Apple computer into the Mac OSX (not the KBE, just off of the hard drive)
  5. Run the Bootcamp Utility and partition the drive however you like. I used 50-50. Make sure you have a Windows operating system disc in the drive.
  6. After the drive is partitioned, the computer will automatically reboot. While it is booting back up hold down the Option key on the keyboard to bring up the boot menu.
  7. Eject the Windows Operating system disc and insert your boot CD or bootable USB drive of your Windows 64 KBE. Boot the system off of the CD or the bootable USB drive.
  8. Once the KBE has booted, deploy your Windows image as you normally would on a PC. It will format the drive as NTFS, deploy the image, and then run the DiskPart utility to make the Windows partition active.
  9. Reboot the computer. It should boot into Windows.
The last piece of the puzzle is creating a postinstall task that will install the Windows Bootcamp drivers. I have not played around with that yet, but it's my next step!
 
Hopefully this will help out someone else trying to image their Macs!

Comments:
  • Hi!

    When I booted from the KBE USB i created it imaged/.reformated the HD into 1 NTFS partition. It did not give me an option to select the bootcamp partition. What step am I missing? - Chadg001 10 years ago
    • Make sure you do not have a preinstallation task that partitions the drive. On most of my Windows images one of the first preinstallation tasks I have is "Create Single Partition". If you are deploying to a Mac computer you want to make sure you do NOT have that task set, otherwise it will wipe out the Mac partition. - MisterVertigo 10 years ago
  • Ok that was it. Now I did it again and it looks like it pushed e image but when I try and boot to it it says Bootmgr missing Press CTRL+ALT+Delete. I am thinking I did the Disk Part Post installation task wrong. I created an Application Post Installation task. I put it in the mid level task area. The only other reason I can think it failed is the original image had aC and D partition.

    Chad - Chadg001 10 years ago
    • Yeah, if your Windows image had two partitions then you may need to set up your diskpart postinstall task differently. My example is for a single partition Windows install.

      You may want to boot the computer to the KBE and go to the command prompt and use diskpart to see how the partitions are laid out. It could be that since you have more than one windows partition your partition number for the script may be different than mine. On my systems I use "SELECT PARTITION 3" but yours may be different. - MisterVertigo 10 years ago
  • Edited this post as I made a mistake in the previous one. Sorry!

    I've been using this again lately and I came across a couple of other issues that others may have encountered. I believe I have found a way to make it work so I wanted to share with everyone.

    On my older intel Macs I followed the above steps and put the Windows image on the BOOTCAMP partition. However, when I tried to boot I got a blinking cursor in the corner and the BOOTCAMP partition did not appear as a bootable option when I'd hold down the Option key at boot time. Here is how I fixed it:

    1. I made a copy of the "Install Vista/2008/7/8/2012 MBR" Preinstallation Task.
    2. Edit the new Preinstallation task with the following:
    bootsect.exe /NT60 c: /mbr
    3. I set my Windows image to have this the last Preinstallation Task.

    This should fix it so the Windows partition is bootable. I hope that helps! - MisterVertigo 10 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ