Deploying Images through MDT & WDS

Associate
Joined
9 Sep 2008
Posts
40
Location
Moira, East Midlands
Hi Everyone,

Apologies in advance for the length of this post, but I want to get as much info across as possible.

I am trying to deploy images from the server through Gigabit LAN to laptops. I am using ImageX to capture the images I need, and wanting to deploy the system images I capture back onto refurbished/repaired machines using Server 2008 R2, Windows Deployment Service and the Deployment Toolkit 2010.

Server is configured with WDS, WSUS, DHCP and DNS.

I have created a PE disc, booted from this on the reference machine and used ImageX to make copies of the recovery partition and the OS partition. I have then copied these over to the deployment share on the server. No problems so far!

Now, when I use MDT to import the images it can see the OS image and imports that fine. It can see the recovery image, but after it imports it, it fails to list it in the operating systems list - it just doesn't list it anywhere. However, if you go into the operating systems folder of the deployment share, where these images are stored, it does have it in there. Curious?

I've used the Task Sequence section to format the hard drive and create two partitions. The OS is being installed onto the first partition and has been marked as 'Boot'.

I can use the LiteTouchPE file through WDS to deploy just the OS and any updates needed - everything goes through great. But it just won't allow me to add the recovery partition to the deployment.

As I can do all of this I can safely say there are no network issues, no admin restrictions issues or server issues.

I've used three brand new out-of-the-box Acers to create the images needed in case one was corrupt.
I've tried to capture the OS and Recovery partitions separately and then add them as separate images through MDT.
I've also tried to append the recovery.wim image to the OS.wim image but then MDT won't see the 'whole' image after it's been imported.

I've started to pulling my eyebrow hairs out now as none are left on my head!!

Beers on are on me for anyone who solves this!
 
Associate
OP
Joined
9 Sep 2008
Posts
40
Location
Moira, East Midlands
When the system is sold, it has to be sold with the ability to put itself back to factory condition, and we cannot supply recovery discs to do this - so we are including the original recovery partition.

We are also not allowed to use, or suggest to the customer to use, the built-in Windows 7 recovery image process either! :(
 
Soldato
Joined
9 Oct 2008
Posts
2,993
Location
London, England
May I ask what you are using to create the recovery partition? I know it should not make any difference to the process, but it would be good to know, if only to satisfy my own curiosity.
 
Permabanned
Joined
9 Aug 2008
Posts
35,707
I find it a lot easier just to do an out of the box network install then use task sequencer to build the application sets + updates.

This way all you would need to do is import the drivers into the server and deploy. This way your not creating multiple images using imagex to your server. Taking up space and time creating images for new systems. As for the image, well what you could do is provide the customer with an application that came with Acer to provide method of restoring it via imagex and your images if that's the method you want to use.

Odd how it won't allow you to create the recovery partition. Something wrong with the config of the drives somewhere via task sequencer?
 
Last edited:
Back
Top Bottom