imagex and Windows 7 deployment

Delvis

Delvis

Delvis

Caporegime
Joined
7 Nov 2004
Posts
30,197
Location
Buckinghamshire
Hello all

I'm trying to successfully capture a windows 7 image as a .wim file, then deploy it manually to each system using imagex, the problem I'm getting is Windows 7 by default creates the stupid partition before the OS partition, apparently taking an image of both partitions and applying them to the drive in question doesn't seem to work.

Anyone have an easy to use method to deploy Windows 7 over the network? We use imagex as it's free and you can deploy anywhere, ideally I just want to take an image of the entire drive then apply this image to another drive and be done with it!

Thanks
 
Imagex can be a pain in the arse to be honest. As a rule, it does actually work if you restore the two partitions. After you've done it, boot from a Windows disc and try running a repair/fix boot problems. I've known that to bring them back to life before now, but it's not really ideal if you have loads of machines.
 
Yeah I tried the repair option but it did nothing sadly.

I've managed to put a wim file in to the Deployment Workbench and create some random Task Schedule to apply the image, seems to have worked anyway, just seems bizarre how Microsoft haven't developed imagex to take a wim file of the whole drive....Or is that what VHD files do?

Still need to iron out the way we deploy the image though as it's completely different to what we've been doing for the last 5 years
 
Do you have a server that has windows deployment services? You need a boot.wim file to configure the system reserved partition. I use gimagex to take the image, put that in wds and along with a boot.wim (from win 8 disc) and install over the network. You can create an answer file to make it automated if you needed to.
 
Yes we have a server solely for WDS, however since Windows 7 and the stupid system reserved partition it's just been a pain, before we had one partition and we just deployed that.

Its just over complicated for what it needs to be.

Oh, and yes we have a boot.wim file, I've had to edit and create a new one due to needing extra network drivers to be able to boot to the network.
 
you can install windows without the 100mb partition. when you get to the part in the installer where you partition your disk, press shift+f10 to open a command prompt window. from that, you can use diskpart to partition the drive. when that is done, refresh the drive list in the GUI part of the installer and windows will install there no problemo.
 
It can be but once its set up that's it. Do you have an answer file that you use for deployment? If so could that be not creating the reserved patition?
 
Cheers Marc, I did a similar thing with the GUI (is just format rather than creating a new partition and it seemed to work before) just this time around it was a pain.

No answer file from what recall, we only use the win file to boot to the network, then we use 'net use' and capture or apply the image manually, just creating two partitions and making them work appears to be less straightforward than one would think.

I'll see if I can create another image like you said Marc and do it that way...I've done it via a scheduled task at the moment which works its just 'new' as you need to create the scheduled for each individual image.
 
Marc2003 is correct – you can install Windows 7 without the 100mb system partition that is created automatically by Windows Setup. Likewise, you should also be able to capture the Windows 7 OS partition without also capturing the system partition.

Since you have a dedicated server for WDS you might want to consider using the Microsoft Deployment Toolkit (MDT) for both the imaging process as well as the deployment process. First off, MDT is also free, just like ImageX. MDT can integrate directly with WDS and can be setup to PXE boot for both a Sysprep and Capture task sequence and lite-touch deployment.

Next, MDT can be used to deploy Windows XP, Windows 7, Windows 8, Windows Server 2003, Windows Server 2008 and Windows Server 2008R2. Using MDT, you can easily add both applications and drivers, manage Windows updates, create task sequences, prompt for a computer name, join a domain, add a KMS or MAK product key, create an administrator account, specify time zone, etc. You can also import all user data into the new environment using the User State Migration Tool (also free). In addition to creating standard client task sequences, as stated above, you can create sysprep and capture task sequences that will do just that – sysprep and capture an image of your reference machine. To become familiar with the process of using MDT, you might want to check out these videos from the Springboard Series page on TechNet:

Deployment Day Session 1: Introduction to MDT 2012
Deployment Day Session 2: MDT 2012 Advanced

Alternatively, if you do still wish to use ImageX for your capture needs, you might want to watch the Preparing an Image Using Sysprep and ImageX video which is available from the Springboard Series page on TechNet.

Finally, there is also a great deal of resources for various deployment, virtualization and management scenarios available from the Springboard Series on TechNet.

Hope this helps and keep us posted on your progress!

Jessica
Windows Outreach Team – IT Pro
 
Chrikey :D

Thanks Jess, much appreciated. I did install MDT and have deployed an image using that, however it still created the system partition?

Currently I have a .wim file in WDS to PXe boot to our network which I can add network drivers to (in MDT) which is a major help. I've then imported a captured .wim file of our OS NOt including the system partition, I've then had to make a standard task sequence which installs that WIM file...However I think it still made a system partition.

I'll have a look through the links again because if we can use MDT to capture images and deploy them I think it will be much easier in the long run.
 
Hi Delvis,

You’re very welcome for all the links. I also found the TechNet magazine article, Understand (and Get Rid of) the Mysterious Small Partition, which is helpful in both explaining the purpose of the 100MB system partition but also explains how to create a reference machine without this partition in the first place.

Next, within MDT, you will want to check the settings of your Windows 7 Deployment TS. Under the Preinstall folder, you will want to navigate to the New Computer only folder and select / highlight the option for Format and Partition Disk. On the right hand side, in the center of the Properties screen, you should see a box checked for “Create extra ‘Active’ partition”. Uncheck this box and select Apply. Alternatively, according to this TechNet blog article by Michael Niehaus, you can also add a DoNotCreateExtraPartition=YES variable to your CustomSettings.ini.

Now you will want to recapture an image of your reference machine you created without the 100MB partition. I strongly suggest using a sysprep and capture task sequence from within MDT to do so as it will simplify the future deployment process.

Let me know if you have any questions with this.

Jessica
Windows Outreach Team – IT Pro
The Springboard Series on TechNet
 
Last edited:
Weirdly, we use bitlocker but had no issues previously as you save the recovery key to an external usb.....?
 
MDT for capturing the image just seems overcomplicated? For a start when I go to setup the task sequence it wants me to select a current .win file from the operating systems in the workbench?

Turns out I was being dumb anyway as the drive was encrypted.
 
Delvis said:
MDT for capturing the image just seems overcomplicated? For a start when I go to setup the task sequence it wants me to select a current .win file from the operating systems in the workbench?

Turns out I was being dumb anyway as the drive was encrypted.
Click to expand...

Using MDT to Sysprep, Capture and deploy the image can be simpler in the long run. The process of capturing an image and adding it to your deployment share is fairly simple as all it requires is the creation of a Sysprep and Capture Task Sequence (TS). To answer your question regarding needing to select a current .WIM file when creating a sysprep and capture TS the reason is to ensure the proper sysprep files are used for the correct version of Windows; this is lightly touched upon in the How to run a Sysprep and Capture Task Sequence from MDT 2010 blog article form TechNet.

Let me know if you have any other questions. :)

Jessica
Windows Outreach Team – IT Pro
The Springboard Series on TechNet
 
It makes no sense though, what if you don't have a current .wim image? What if you are wanting to just sysprep the system and upload it so you can then actually deploy it across the network? :p

You need a basic sysprep task sequence already in MDT that gives you the options to keep things like the video driver installed (which, by the way is highly annoying as a default option) - Once it's been captured you shouldn't then have to create seperate task sequences for Operating systems / wim images, it's just clunky in my opinion.

Improve the GUI so when you PXE boot you can just select 'capture image from disk' then allow the option to deploy that image again and it would be amazing, much like the simplicity that was PQDI for instance.
 
You must log in or register to reply here.
Back
Top Bottom