Video Screencast Help

Windows 7 X64- Unable to take image

Created: 08 Dec 2013 | 16 comments

I am unable to take image of windows 7 using winpe

this is hp prodesk 600 g1 sff desktop

the desktop has no windows vista driver

I have injected windows 7 32 bit driver but it hangs before starting the image creation stage

Operating Systems:

Comments 16 CommentsJump to latest comment

EdT's picture

What version of Ghost?

You cannot use Win 7 32 bit driver with WinPE V2 unless the driver specifically supports Vista.

However, try applying this article to create a WinPE V3.1 solution which does support Win 7 32 bit drivers:

https://www-secure.symantec.com/connect/articles/creating-and-using-winpe31-image-gss-251

 

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

SteffenBorge's picture

Im having the same(ish) problem with our new and shiny HP ProDesk 600 G1 SFF business desktops.

I'cant find a driver that preboot works with. It loads PXE, but once inside, the cmd windows just says:
"Restarting DHCP client serverce: retry 1" 20 times, and exites. Ipconfig /all shows im having no IP adresse :(

 

So, i think the Mehdim is also having issues with not finding a driver that works with "Integrated Intel® I217LM" in preboot.

Im running Altiris 7.5, and WinPE 4.0

mehdim's picture

RE Edt::

I am following steps

I am kind of stuck on step where copype.cmd x86 c:\winpe_x86  is not creating any folder from WAIK command prompt

EdT's picture

If the folder does not exist, how about just creating it first?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

rocdiver's picture

I believe you need the elevated command prompt.  Deployment Tools Command prompt.

SteffenBorge's picture

Yesterday Hp.com hadent released the win8 64 bit drivers for the prodesk 600.
Today, i see they have :)

Now downloading the driverpack for 8, to see if that driver will work in the pxe enviornmen.

 

Since winPE is built on win8 technology its worth a shot :)

 

http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome/?sp4ts.oid=5387440&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3DswEnvOID%253D4132%257CswLang%253D%257Caction%253DlistDriver&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

EdT's picture

@SteffenBorge

WinPE is built on whatever operating system was current at its version release.

Therefore WinPE V1.x == XP

WinPE V2 == Vista  (this is the version in Ghost Solution Suite 11.5.1.2266)

WinPE V3.x == Win 7

WinPE V4.x == Win 8

Consequently, you need to add drivers that are appropriate to the VERSION of WinPE you are using.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

mehdim's picture

@Edt

 

I manage to create the folder c:\winpe_x86 from deployment command prompt

I am on step Add IMAGEX or GIMAGEX to your holding folder.

I have done the download for GIMAGEX and copied under "c:\winpe\mount\windows\system32" folder

Please explain "holding folder" Does it mean creat folder with anyname under "C:\winpe\ and copy "GIMAGEX" and create "script" folder

EdT's picture

Are you referring to the article written by Terry Bu ?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

mehdim's picture

Sorry yes correct I should write it under that article

I am doing it now

EdT's picture

When you create a WinPE image, the eventual boot.wim that will be created is mounted as a virtual folder on your system. The virtual folder is located under C:\winpe\mount.  WinPE when booted creates a ramdisk on X: and loads and runs from there.  The path c:\winpe\mount\windows\system32 will become X:\windows\system32 when winpe is booted. Thus any utilities that you copy into c:\winpe\mount\windows\system32 will be found under x:\windows\system32.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

muhammadm's picture

@ Edt

I am sort of lost in your last statement.

I should give you some idea about setup I am using

I have ghost server and I do pxe boot using two different sessions depends on occasion

1 - "Manual session.wim" saved under (C:\TFTPBOOT\boot\)

2 - "Automatic session.wim" saved under (C:\TFTPBOOT\boot\)

I beleive your "winpe" folder is "TFTPBOOT" folder under ghost server I have

I beleive I need to know some basic rules before I go and upgrade winpe for windows 7

 

EdT's picture

@muhammmadm

Perhaps this article may help: https://www-secure.symantec.com/connect/articles/readyadventures-winpe

Although it refers to WinPE V2, there is also a link to a similar article that covers WinPE V3.1

The articles describe how to roll your own WinPE boot environments independent of the Ghost environment so that you can understand the basic rules.

As far as WinPE is concerned, it is a command line version of Windows (basically a Super-DOS) using windows kernel files but no GUI. The entire environment is contained within the ".wim" file within a WinPE boot device, and the boot process consists of creating a virtual disk in RAM, usually X:\ and mounting the WIM file on that virtual disk so that WinPE runs entirely from memory. 

It is possible to edit a WIM file, but it has to be mounted as a virtual folder first. Once mounted, you can add files to the folders in the WIM file, then commit the changes to the WIM. Any files you delete within a WIM are not actually purged from the WIM unless you commit the WIM and then export it to a new WIM so that redundant content is left behind.

When using TFTP, this is just another way of booting to WinPE. Rather than booting off a local device such as a WinPE CDROM or USB stick or USB drive, you are using a network connection to PXE boot from the remote server, and the PXE process loads the WIM boot environment onto the local machine.

PXE boot uses firmware on the NIC to pull down a standard boot header and this pulls down the WinPE environment and hands over control to it. When control is handed over to the WinPE environment, it also hands over control of the NIC, so continues access to the network relies on WinPE having a valid NIC driver present.

I hope this helps clarify.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

muhammadm's picture

@Edt

I manage to create winpe_x64.iso

I have burned iso image onto CD

I boot computer with burned CD using cdrom and I get to screen x:\windows\system32

How I can create the image of desktop from this screen. to external hard drive.

 

2 - Re: "When using TFTP, this is just another way of booting to WinPE"

I still prefer to do tftp boot but the issue is network driver for windows 7 and PC NIC does not have vista driver.

How I can  make tftp work with windows 7 please?

EdT's picture

1. Run the Ghost program from the WinPE command prompt. Locate the external USB hard drive by its drive letter and use that as the target.

2. Check out this article:

https://www-secure.symantec.com/connect/articles/creating-and-using-winpe31-image-gss-251

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.