Download Winclone Pro 8 Crack For Mac
Shay Silvertooth
Hey everyone (or even the WinClone folks).
We have a few machines that when you boot into WinPE the EFI partition is not visible either when you try and mount it with mountvol S: /S or when you look for it with diskpart.
I noticed however that when you run WinClone's "Make EFI Bootable" command it then becomes visible, it's not a function of the copying of the files, but there must be some final process like a bless or something that cause this behaviour.
Does anyone have any insight into exactly what function does this as I'd love to be able to replicate it in a script.
It's at this point it does something that results in either the EFI or the Windows partition (most likely the EFI partition) on a fresh Mac suddenly making the EFI visible and mountable as a drive if you boot to an external USB i.e. SCCM boot media.
It's the very last function I am trying to replicate
I have given up on trying to make SCCM prestages capture and deploy correctly using Winclone due to EFI only boot on new macs and the fact it defaults to normal Windows boot rather than RAM WinPE boot and just want to use that function to prep the drive instead (even a command line way of doing that using the framwork contained with a winclone image would be sufficient).
Didn't manage to get prestaging working, what I did manage to get working was imaging out of SCCM using USB media and EFI boot.
With a bit of help from Two Canoes I worked out that you can use fdisk (some to remove the MBR data off a FAT32 volume which then makes the SCCM boot media do everything using EFI, it's get slighty complicated with Fusion drives as you get a couple of EFI partitions.
The following script will find an EMPTY FAT32 partition called exactly WINDOWS and then use fdisk to destroy it's relevant MBR data. It will also create a file called FORMATC.BAT which you call from the SCCM workflow to reformat the disk as NTFS before applying the image.
There is a small routine to hide a NONE partition as well which is part of a process of tricking a fusion machine into using the right partition.
The other parts of the puzzle are SIP that has to be disabled, you can actaully make this easier by putting refind onto the SCCM boot media with the SIP and Recovery tools enabled and set to only detect the SCCM boot itself, works quite nicely.
Then there is the formating itself I created the following script to be run as part of the imaging work flow.
ONCE AGAIN ITS DSTRUCTIVE AND REMOVES ALL PARTITIONS AS PART OF THE PROCESS
It also requires the OS X partition be named exactly Macintosh HD and you can specify the WINDOWS partition size as the first argument, leaving it blank will mean no WINDOWS partition is created.
It will rebuild a fusion drive if an SSD and HDD are present, putting WINDOWS entirely on the HDD.
It also does all the same stuff as the above EFI script if a WINDOWS partition was created.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
I was told by Twocanoes support that there are scripts in Casper that are editable and i should be able to find the find the solution to keeping the BCD in the image in the script support documentation from JAMF.
Hi Roy,
This is Russell, who you've been working with at Twocanoes. I just realized that you're asking about preserving the BCD when imaging. The "-b noreplace" option pointed out by Kumarasinghe is correct. This flag is applied when restoring an image. The assumption is that you may have a custom BCD created specifically for restoring the image of a file system like WinPE. When imaging, the BCD is always retained. It is when restoring an image that the BCD may need to be created new (typically hard drive or system migrations) or retained, like for WinPE restores. The Winclone GUI provides a preference set to retain the BCD or not. The "-b noreplace" option is the command line equivalent. We will expand on the documentation for this feature in the winclone_helper_tool usage and our website. I can't speak to the contents of the Casper deployment scripts, but you should be able to include the winclone_helper_tool commands in your deployment plan. Get in touch if you need any help. rts sup...@twocanoes.com
1.Do you use Casper bulit-in function to partition the drive ?
2.If i use the step above , I don't see how you can incorporate script to ask Casper to retain the BCD during imaging since Casper just put the image down.
Yes i am using a custom BCD. It may be a good idea to include in your documentation to have example script and deployment method to retain BCD since Twocanoes already wrote the white paper of using Casper as an deployment tools to image a winclone image.
@malroy
We do not use the Casper built-in function to partition the drive or deploy Winclone image.
We use a custom script to partition and deploy our SCCM Prestage in a Winclone image to do dual-boot imaging.
Hi Roy,
Another option to consider is to create a self-contained installer package using Winclone Pro. Once you've manually tested restoring the WinPE image successfully, select the image file and select "make package". Once completed, right-click the package and select "show package contents", navigate to and open in a text editor the file (packagename).pkg/Contents/Resources/postflight. Scroll to the bottom and you'll find the command "./winclone_helper_tool" with flags specified. Edit this command to include the -b noreplace option to preserve the BCD during restore.
Winclone allows you to clone your Boot Camp partition, and now includes Vista cloning!
New Machine Setup a breeze - If you are in charge of setting up a bunch of machines with both Mac OS X and Boot Camp, Winclone will make your job a breeze. Simply create an image as your would for a backup, and Winclone will create the Windows partition and restore the OS and data onto the new partition.
Quick Lab Deployment - Deploy images with ARD: Using the included script and the image created with Winclone, you can easily send a new winclone image to a group of Intel Macs, imaging the entire lab in minutes.
Features:
- Clone Windows XP or Windows Vista with ease.
- Clone to your Boot Camp partition either on a separate drive or on the same that contains your Mac OS X partition.
- Creates image documents that can be stored on any media and double-clicked to open in WinClone.
- Verbose logging so you know what is going on.
- Built on the open source ntfstools, which are included in Winclone, so you don't have to install anything else.
- Fast: Restore a 10 GB image in less than 10 minutes.
- Create a Boot Camp partition from within Winclone.
- Do it all from the boot drive: You don't need to boot from a Firewire drive to clone the Windows partition.
- Clean and uncomplicated interface