Anyone managed to inject the correct drivers so we can see the local hard disk to capture the image. I have injected the chipset and intel storage matrix inf files but still cannot see the drive to capture it.
Any help appreciated
Anyone managed to inject the correct drivers so we can see the local hard disk to capture the image. I have injected the chipset and intel storage matrix inf files but still cannot see the drive to capture it.
Any help appreciated
I assume you have injected them into the correct boot image etc?
Also, as an idea, on another laptop of that model, see if its running in ACHI mode in the BIOS and change it to something else, and then boot that one to see if you can see the HDD then?![]()
tosh74 (3rd March 2011)
I have injected into both my capture and deploy images. I have change the BIOS from AHCI to Compatible and back. No change. I guess I missing something obvious. Thanks for your suggestions
The image is sysprepped right?
tosh74 (4th March 2011)
I assume you have the correct network drivers injected for the laptop? It would be able to boot via PXE so far without any but when it comes to connecting to the server it wouldn't be able to pick up an IP address
tosh74 (4th March 2011)
@Tommej. not yet. I'm taking a backup of the image before I sysprep it
@themightymrp. I am trying to capture the image just now. When I get to the volume to capture screen there are no volumes in the drop down list ( I'll deal with the NIC when I get to that stage)
Thanks both for your suggestions
I think by design WDS will only allow you to image a sysprepped drive/volume.
e: yes. http://technet.microsoft.com/en-us/l...8WS.10%29.aspx
If you just want to have a backup of the operating system as they come out of the box i'd consider something like clonezilla live, very simple to use.Known issues when creating custom install images
When you boot into the capture image, the Image Capture Wizard will start. Note the following about the wizard:
* You will only see drives that contain operating systems prepared with Sysprep. If you do not run the command in step 4, you will not see any drives to capture.
Also note if you're worried about problems with your unnattend file you can use imagex after you have the image to edit this.
Last edited by tommej; 4th March 2011 at 11:14 AM.
tosh74 (4th March 2011)
What I mean is, presumably you have booted the laptop via PXE which loads up the necessaries from WDS? At some point it is going to switch from basic PXE protocols to loading the actual NIC drivers to establish a TCP/IP connection to the WDS server. If the server cannot make that link to the laptop then it isn't going to be able to reach the information about the hard drives. The NIC drivers would need to be injected into the winpe environment to continue. Tell me if I'm being dense as I do my images via Ghost and only use WDS to link with MDT to do an initial source machine install.
tosh74 (4th March 2011)
Cheers. I'll give it a go
There are currently 1 users browsing this thread. (0 members and 1 guests)