[kyascian]

3. Right-click on the Boot Images container and click Add Boot Image.

i can't find the boot image in the deploymentworkbench

how i can find this folder ?

Thanks thanks

[Tripredacus]

The WinPE you created is the boot image.

[kyascian]

nothing....

the progress bar not run...
i have the same grey rectangle...

i make all the steps , gimagex x64 , startnet.cmd , and all packages..mhta...etc...

nothing

i don't understand where is MY error...

[Tripredacus]

kyascian, on 21 March 2010 - 02:10 PM, said:

nothing....

the progress bar not run...
i have the same grey rectangle...

i make all the steps , gimagex x64 , startnet.cmd , and all packages..mhta...etc...

nothing

i don't understand where is MY error...

The current code in this is still the same as v7.1 except for the code changes mentioned in this thread. So the progress bar code is still incorrect, and as such, does not work for anyone. So its not your error, no one sees the progress bar. It is good enough to see the square, on some video cards/motherboards, no rectangle appears at all! Anyways, you will know when it is done because it shows you a prompt after applying the image.

[Nosfer@tu]

Great thread gentlemen

This will help me alot in my quest to get burnintester from passmark running

AMT I have it running with Winpe 2.x but I to want to deploy the .wim file from WDS in win2k8 x64
Will update when I try more tomorrow at work

[Tripredacus]

That should not be a problem. My 2008 x64 WDS currently has 4 different boot images to choose from:

1. Atomic Bomb (WinPE 3.0 x86) ImageX Deployment Platform
2. BurnInTest (WinPE 2.1 x86)
3. Imagex (x86) (WinPE 2.1 x86) ImageX Deployment Platform
4. Imagex (x64) (WinPE 3.0 x64) ImageX Deployment Platform

So the WDS does not care what architecture the boot image is. WDSNBP figures out what the client can handle. If the client is only x86 CPU (like Celerons or Atoms or older) it will only show 1-3. The x64 boot image only appears in the menu if the CPU can handle 64bit OS.

[dicko1976]

Hi

This is a fantatsic tool.

2 additions I am trying to add to the HTA is the Description of the Images in the WIM file. I have edited the NAME section to see if I could get it but I would like to show both Name and Description for all the images within the WIM file ?

The other I am trying to add is information about the machine I am going to deploy to. I would like the Serial Number and Machine Model. I have added the vbs script to my HTA file but I cant seem to get it into the HTA. Probably I would like to put this above the Disk Information.

Any help would be great.

Thanks in advance

Dicko

[Tripredacus]

I'm not sure how to get the description out of the XML. I didn't write either the original nor modified XML code. For your other project, you are going to have to code it in VBScript in the HTA itself. If you are getting errors or not sure how to approach that, make a post here:
http://www.msfn.org/...s-cmdbatch-etc/

[dicko1976]

Hi

Thanks very much for your reply. I managed to get the VBS script working to pull the Machine Names, Model and Memory installed.

Will look into this deeper and see what I can find.

Thanks again

Dicko

[dicko1976]

Hi

I have managed to create a wim file with several images. I have taken a basic windows XP image and then several different images from different laptops.

When I try to restore one of the newer images it takes less than 5 minutes to do but it only puts on the folder structure and no files ?

Do I have to restore the basic image first and then the newer image on top, if so is there no way of doing both at the same time?

I though it would put the image back that you requested and pull the relevant files ?

Thanks

Dicko

[Tripredacus]

Yes you can have multiple images in the same WIM file. I have not seen this type of behaviour before. Of course the first thing I do when I need to troubleshoot the HTA (or any custom program I put in there) is to open the command prompt and manually run the commands. This way we can see if it is a problem with the code or something else.

So in your case, on your server you want to get the image index value (makes things easier) and make note. So then in the command prompt in the HTA, you would do something like this:

diskpart /s diskpart.txt
OR
diskpart /s misc/diskpart.txt

I have moved my file, but I think there is one in MISC still. Then:

imagex /apply z:\images\image.wim 2 c:

When it is done, do a reboot and see how it goes.

Alternatively, you could inspect the folders with Notepad after the normal deployment. NOTE: Notepad will only see *.txt files and it may appear these folders are empty until you change the type to All Files.

[dicko1976]

Got that working now thanks but I have moved on a step.

I am running all this in windows pe 3.0, the HTA file and storage.

When I try to run the create or append a new wim option I follow it and it says that the image has been created or appended but when I look into it a bit further or refresh the HTA there is nothing else added either file wise or to the appended image.

I ran the command manually in dos screen and it throws up an error about disk space. I have the new wim file or appending file on a 1TB USB hard drive formatted in NTFS and created via diskpart. There is 400GB left on the disk and the wim file is only about 5GB.

If I do it manually with GImagex to the same USB hard drive then the image creates OK or appends OK.

Any ideas ?

Thanks

Dicko

This post has been edited by dicko1976: 23 September 2010 - 03:43 AM

[Tripredacus]

I'm not sure about using a USB drive. In theory it should work. Make sure you are using the correct drive letters. In my HTA I have replaced the functions of the capture and append buttons because I did not want our regular technicians to have the ability of changing the images. All of my images are stored on a file share. I do all my capture/append/delete work using the command prompt button.

Oh I have also seen there are some instances where imagex does not like capturing and saving the WIM file to the same physical hard disk. I ran into this problem when trying to create recovery with WinPE 2 on netbooks for XP.

[dicko1976]

Thanks for you response. The C: drive is where I am capturing the image and the usb is where the wim file is. If I do it via GimageX then it captures all OK.

I would like to use the HTA to capture and restore but if its not possible then it looks like GImageX. Just wanted a simpler screen for the engineers

Thanks again

Dicko

[Tripredacus]

I have made a v7.2 which is available on SkyDrive

This version has both 32bit and 64bit support. It includes a very simple readme. It has the fixes to the Messageboxes that I made, and the XML fix that Dabone made. It also includes the two background images I had created. Let me know if you have any problems with it. I made it from my customized version that I run, so hopefully it works properly! I have not tested it.

[surrealpro]

i first wanted to say thanks to everyone that worked on this hta, and for tripredacus for your time and taking this further. i have a few questions.

i have winpe 3.0 and just created a new win7 wim. i need to have our deskside techs use a thumbdrive to start upgrading users to windows 7.

do to the size limit on thumbdrives, do to the format, i have to split out .wim into .swm files.

i dont see any .swm file support within the code, is this correct, or something that i can add or change?

i also dont see a /apply function. in theory i would just like to have the deskside tech boot in winpe from the thumbdrive and be able to imagex /apply with new win7 .swm files onto the system.

im will to help if needed, just let me know!

thanks again for you help with this in advance.

d@ve

This post has been edited by surrealpro: 06 October 2010 - 08:43 PM

[Tripredacus]

This HTA was designed to use WIM files, which is why you aren't seeing SWM files. I have little to no experience with SWM files other than the ones WDS creates by itself.

If you want to modify the code to work with SWM files, go right ahead. Of course I do not share my full HTA with everyone, just the generic base copy, so that's totally up to you.

[Tripredacus]

I made an update to the current version to v7.3. The Code has not been changed, I just changed the readme file. The SkyDrive link should still work without a problem.

[Tripredacus]

Moved some content from post 1 to post 2. Changed the intro to show as more of a project rather than just a support thread.

Added "development opportunities" which is basically just a list of things that have been requested, or that I wanted to change as well. A little note about some of these...

The App and Custom OS installer is something present in my version of the HTA, but is removed from the public version. Currently, my HTA has buttons (the mount/capture/append buttons) changed to install applications and deploy custom images such as Win7+WinRE, Server 2008 + WinRE, custom partition values with XP. These menus are hand-coded and I've recently come into a situation where I cannot easily maintain these menus anymore aka the actual server is no longer at my location. So I wanted to come up with a program that would look on the file share for a file, and that file would tell those menus what apps or images are available, and populate the menus appropriately.

This idea also ties in with the "local os detection", custom partition support/browse for diskpart script items as well.

If you have any other ideas or want to help out, feel free to post here!

[dwburkett]

I keep getting an error when adding my boot.wim to my wds. It keeps telling me that the file does not contain a valid boot image. I have followed the examples to a tee and even modified where appropriate for an x86 environment. All the configuration was done using waik. Any input would be greatly appreciated.
Edit:FIXED, my virtualization waas being screwy, however, do i want to add the winpe.wim or the boot.wim in the iso\sources directory?
It wont let me delete this post,but it's solved..still having resolution/button functionality issues though...

This post has been edited by dwburkett: 08 February 2011 - 12:49 PM