Ghost Cast Server 11.5.1.2266

[Migration User]

Hi,

I have a sys-prepped Win 7 x64 ghost image that I can push out to machines at work. I deploy the image to the computer(s) using Ghost Cast Server 11.5.1.2266.

We had some new HP machines arrive today, the model number of which is HP Elitedesk 800 G1 SFF. The PC's will boot from the ghost boot disk but they remain stuck with the IP address 127.0.0.1. This in turn means that they are unable to detect/connect to my multicast server to pull down the sys-prepped image.

I figured this must be due to ghost not having the driver for the NIC in the HP 800 G1. So I downloaded the necessary Win 7 x64 driver(s) and created a new ghost boot disk with the new driver added, however despite the addition of the new driver the PC remains stuck with the IP address 127.0.0.1 despite several reboots. The NIC that the PC's contain is the following  - Intel Ethernet Connection I217-LM

Where am I going wrong?

 

[Migration User]

Jeet, If you used GSS 11.5.1 to build a PE boot image you need Vista x86 NIC drivers which may not be available. You could build your own PE v4 or v5 following instructions here: https://www-secure.symantec.com/connect/forums/winpe-30-gss-251 looking at the post by BHays which you can use to build v3 4 or 5 versions of PE or look at this post: https://www-secure.symantec.com/connect/forums/intel-i217lm-network-card Pete

[Migration User]

Hi Pete,

 

Many thanks for your reply. The solution from BHays seems to not be applicable to me as I am not using a Windows 8 PC. I am using a Win 7 x64 PC as my ghostcast server.

It looks like I will be using the solution on the following link -

https://www-secure.symantec.com/connect/articles/adventures-winpe-31

 

What I need to understand is (please bare with me), having gone through the instructions on the above link what am I then able to do? Will I be able to produce a ghost boot disk which I can then use on my HP 800 G1 PC's so that they can then connect to my ghostcast server and be imaged from there?

Bear in mind I do not and never have used the ghost console, I have only ever used the ghostcast server. Whether this has any bearing on anything I'm not sure.

[Edward Tippelt]

You may find this article by Terry Bu to be more specific to Ghost applications as my article referenced above is a more generic WinPE 3 solution.

[Migration User]

Jeet-

 

I have this same exact issue with the same exact workstations and NIC drivers.

 

I was told other people are having the same issues getting these NIC drivers to play nice with old Winpe environment. Although I have not tried it yet I was told to download the version 18.5, specifically the e1d63x64.inf... I have zipped up the file for your convenience. 

http://www.filedropper.com/hpelitedesk800driver

 

I am going to try this driver tomorrow, 2/16 at work and see I have the same results. For reference the forums I saw this information is copied here (https://communities.intel.com/thread/43218)

 

Let me know if you have luck with this driver as well. Thanks!

[Migration User]

@Ed,

 

Hiya, I have printed off Terrys article and will have a read through to get to grips with it and then proceed from there. Thanks.

 

@littlehubert,

 

Let me know how you get on pal, would be interesting to see if you can get this to work without the extra WinPE work.

 

 

[Migration User]

you dont NEED a win8 machine, just Win8 media for BHays's solution.

give my article a go, but, keep on mind, this is only the first part.  you need the 2nd part to get the 800G1 to work.

https://www-secure.symantec.com/connect/articles/faking-drivers-gss-251-winpe-31

you will need to do that once you get the PE3.1 image up

[Migration User]

The 800 G1 was the first comp we got that didnt have VISTA drivers for GSS.  I actually started the thread linked above by Pete (https://www-secure.symantec.com/connect/forums/intel-i217lm-network-card)

in the end, we had to bolt on some fixes, and this issue doesnt seem like it is going to go away.

i wrote the 2 articles

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

and

https://www-secure.symantec.com/connect/articles/faking-drivers-gss-251-winpe-31
 

to explain the issues, and say what i did to get around them.  they are not foolproof, but at least they dont fail 100% of the time like stock GSS does with the 800

 

[Migration User]

Hi Terry,

I am going through part 1 of your article and I seem to have hit a bit of a stumbling block. You guys will really have to bare with me on this as I am only a low level 1st/2nd line support analyst. Assume that I know nothing about ghost console or winpe.

The stumbling block I am hitting is at the commands -

copype x86 c:\winpe
Worked fine I believe as the following occurred - x86\bootmgr, x86\BootSect.exe, x86\winpe.wim 1 file(s) copied

copy c:\winpe\winpe.wim c:\winpe\ISO\sources\boot.wim
Received an error, "The system cannot find the path specified"

I know I have missed something out or I am misinterpreting something in the article but I am unable to pinpoint what it is. Any pointers?
 

EDIT: Correction - copype did not actually work. It was not recognised as a command. So Im guessing that the copype.cmd script is missing from within the "c:\program files\windows aik\tools" directory?

 

[Migration User]

Jeet, I presume you have installed the ADK? http://www.microsoft.com/en-US/download/details.aspx?id=39982 You then need to run the "Deployment and Imaging Tools Environment" from an elevated command prompt. Below is helpful; document on building PE that you can use along side the Ghost related build instructions: http://technet.microsoft.com/en-us/library/hh825144 Pete

[Migration User]

Hi Pete, yes I have the ADK installed. I ran through the first command and it seemed to run ok with 187 files copied. Unfortunately I get the same issue as before when running the second command.

Im downloading the WAIK SP1 supplement right now. Will install and see how I get on after that.

[Migration User]

when you install the AIK or ADK (depends on the version), it normally creates a folder in the Start Menu that has a Command Prompt icon and is named something like

"C:\Windows\system32\cmd.exe /k "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\DandISetEnv.bat "

if you run it from there it will open a command prompt that has in its PATH the info to the AIK/ADK files and locations, such as copype

 

[Migration User]

remember in the article i said

" Think of a nice folder name for your PE so you remember where it is!  (this guide will use "C:\winpe" as the location)  Next, come up with a holding directory for files and folders before you copy them over (maybe c:\bootcd\makepe).  Now, create your PE with the following commands"

sorry if i did not explicitly say to make that folder, but you could if you want name it anything.  just remember what you name it

[Migration User]

Jeet,

You are mixing 2 technologies WAIK which you mention in last email is deprecated and replaced by the ADK. The link I gave you is the most recent:

http://www.microsoft.com/en-US/download/details.aspx?id=39982

Pete

[Migration User]

Ok, i got completely confused so I started from scratch and removed the WAIK and WADK.

I have reinstalled WADK from the link given by Pete. Ran the Deployment and Imaging Tools Environment as admin.

Ran the first command - copype x86 c:\winpe

This created the winpe folder on the C: drive of the technician/ghost PC. I browsed the folder via explorer and it contains the following -

fwfiles
media
mount

I then ran the next command - copy c:\winpe\winpe.wim c:\winpe\ISO\sources\boot.wim

I get the following - "The system cannot find the file specified"

I'm not exactly the sharpest knife in the kitchen but this cant just be me being dull can it? Could it be a corrupt download of WADK or are things not copying across correctly with the first command?

EDIT: I am trying to workout which file it is that cannot be found. I am guessing that it cannot find the winpe.wim file on the path c:\winpe\winpe.wim because I checked the contents of the winpe folder and there is no winpe.wim file in there. Once again apologies for my slowness but should the winpe.wim file be created automatically or should I be grabbing that from here -

c:\programdata\symantec\ghost\template\common\winpe3\sources

The only file at the end of this path is boot.wim.

[Migration User]

OK, so the issue this time is that the WADK makes different folder than the WAIK.  in the WADK, you dont need to mess with that wim file just yet.  also, some of your DISM commands are going to change.

for example:

dism /image:%_location%\mount /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-HTA.cab"

i have actually converted my scripts from WAIK to WADK, but i did not post those as an article

[Migration User]

they are different.  WAIK was made for PE3.0 (Win 7).  WADK started with PE4.0 (Win 8) and now PE5.0 (Win 8.1).  the folders it creates are different, DISM commands are different, etc.

the articles i wrote were for the WAIK (Win 7/PE3.0)

[Migration User]

the winpe file is created by the WAIK/WADK.  in the WAIK its in the root.  in the WADK its in the media\sources directory

[Migration User]

Ok Im understanding a little better now. I need to be following the steps in your article for creating a win pe 5 iso image?

I might as well get the silly questions out of the way -

• The aforementioned article is written for windows 8.1. Does it matter that the ghost image I am trying to push out is not a windows 8.1 image?
• The 800 G1 PC that I am trying to image is already downgraded from windows 8 to windows 7 pro, does this make any difference?

[Migration User]

the PE version does not matter to the version of Windows that will be put on the machine.  you could use a PE5.0 image to put XP on a machine, and if you can find the drivers, you can use PE2.0 to put Win8.1 on a machine.

The articles I wrote are for creating a PE3.0/3.1 CD.  That version of PE is created with the WAIK.  The WADK updates are for the 8 (PE4.0) and 8.1 (PE5.0)

the 800G1 takes Windows 7 very nicely.  I have about 70 of them out in production running Win7 Enterprise like a charm

[Migration User]

Ok, cool beans. Things seem to be chugging along for now. Just injected some extra drivers which the image seemed to take fine. Will crack on with the rest and feedback how I get on.

Many thanks for your patience with me thus far gentlemen.

[Migration User]

Ok so I made it through the final steps of creating the WinPEv50. At risk of sounding completely dull again - where to from here?

I went back into ghost boot wizard to create a ghost boot cd and chose WinPEv50. On the final prompt screen I clicked next and then got two errors as follows -

WIM file for this configuration of WinPE is invalid
An error occurred when trying to create the boot package

I'm guessing that I cant use ghost boot wizard to create a boot disk using the WinPEv50 I just created. Do I therefore just burn the WinPEv50 directory onto a disc as is?

[Migration User]

you dont do it with the Ghost Boot Wizard.  you have to use the wizard to create a 2.0 PE, but then you replace the WIM with your new one.

from the article:

Second, on the server that is running your Ghost Solution Suite console, open the Ghost Boot Wizard.  Select WinPE, click edit.  Highlight the WinPE 2.0 boot partition you are using that has all of your drivers.  Make sure you highlight this one, and not a stock one.  Click copy, and give it a nice short name (like WinPE3).  Make note of where it is storing the files (ProgramData\Symantec\Ghost\Template\COMMON).  Your newly made PE will be in that folder under its own folder with the name you gave it.  Remember this.

and

Remember earlier when I said remember where GSS kept that WinPE3 folder under COMMON?  Open your folder, open "Sources" and replace the boot.wim in there with the one from the CD/USB key.  Confirm the move!  Now, you can NEVER EVER AGAIN open that PE in the Ghost Boot Wizard.  It will give you lots of errors.  But it does work.

[Migration User]

Sorry pal, I'm not understanding your last post.

So having created the WinPEv50 directory (which now shows up in Windows PE Editor) I select and copy the normal WinPE and create WinPE3.

Do I then copy the boot.wim from

c:\programdata\symantec\ghost\template\common\WinPEv50\sources

to

c:\programdata\symantec\ghost\template\common\WinPE3\sources

and then create the boot cd? Before doing this should I remove the WinPEv50 directory from the Windows PE Editor?

[Migration User]

so you create a new boot image inside the Ghost Boot Wizard.  Name it something that stands out to you.

that new boot image will be in the programdata\symantec\ghost\template\common\<your new PE> location.

when you are done building the WIM in the WAIK or WADK, take the new boot.wim FROM THAT, and replace the boot.wim file in programdata\symantec\ghost\template\common\<your new PE>\sources location.

you can NOT edit this in the Ghost Boot Wizard.  what you do is assign that PE to clients in the GSS console

if you want to make a CD out of it, make an ISO of it and burn it.

[Migration User]

Right, I've started from scratch again because I copied the wim across as advised and loaded up ghost boot wizard and selected the necessary WinPE option and then went to create an ISO and still get the error -

 

WIM file for this configuration of WinPE is invalid

Right now im at the stage where I have gone into Ghost Boot Wizard, made a copy of WinPE-512 and called it WinPEv50. Once that has completed I'll cancel out of the wizard and do the next lot of steps.

Here is the part I have been having difficulty with - the WinPE_X86 directory that was created earlier now contains a boot.wim along the following path -

 

C:\WinPE_x86\media\sources

 

Am I taking the boot.wim file from this location and copying it into the following location -

 

C:\programdata\symantec\ghost\template\common\WinPEv50\sources

[Migration User]

dont use Ghost Boot Wizard to make the ISO.

in the WAIK you would use

oscdimg -n -b<your PE location>\etfsboot.com <your PE location>\ISO <your PE location>\<your file name>.iso

note there is NO space between the -b and starting the location of your PE3.0 (as an example) folder

in WADK you can use

MakeWinPEMedia /ISO <your PE location> <your PE location>\<file name of ISO>.iso

[Migration User]

Ok, so this is what Ill be inputting into the command line -

MakeWinPEMedia /ISO c:\programdata\symantec\ghost\template\common\WinPEv50 c:\WinPE ISO\WinPEv50.iso

Look ok?

 

EDIT: The above did not work - ERROR: Working directory is not valid c:\programdata\symantec\ghost\template\common\WinPEv50

[Edward Tippelt]

Does the directory exist?

Are you running the command from an elevated command prompt?

[Migration User]

Definitely exists. Running the command prompt as administrator.

Just to make sure I wasnt being dull, I did the following -

Copied WinPEv50 directory from c:\programdata\symantec\ghost\template\common\WinPEv50 and pasted it directly on the C: drive so that it was a standalone folder.

Ran the command again and this time I go the error -

Failed to create c:\winpev50\winpev50.iso

Just referring back to the instructions on creating a WinPE 5.0 image. On step 6 it says to copy everything from c:\winpe_x86\media to c:\programdata\symantec\ghost\template\common\winpev50 which I took as make a copy of everything in media and paste it into the winpev50 folder.

I figured this might have been the issue when creating the ISO so I removed everything from winpev50 (apart from the 3 txt files) again and this time copied the actual media folder from winpe_x86. Tried the command again and still the same error with regards to working directory is not valid.

I did the same with the standalone WinPEv50 folder, as in putting the actual media folder in there and still get the error -

Failed to create c:\winpev50\winpev50.iso

Despairing right now.

[Edward Tippelt]

Can I suggest you review my article here: https://www-secure.symantec.com/connect/articles/adventures-winpe-31, as the methodology for Win 7 and Win 8 is pretty similar, and I recall tweaking one of the configuration files to fix an issue I ran into.

The error you are getting is either caused by permissions, which should not be an issue if running from an elevated command prompt, or by an error in a command line that is executing the steps needed to complete the ISO.  Where CMD or BAT files are involved, it is simple to add PAUSE commands in between each line so that you can identify exactly where the error is being generated and from there work back to the cause.

[Migration User]

out of curiousity, instead of using the full path to the WIM in the GSS folder, try pointing it to the WinPE5 folder you made everything in (the one you were working in before copying it to the GSS location).  you would point it to the root of the PE folder.  it needs those folders to make the ISO, and if you dont have them in the other location with the WIM, it will fail

[Migration User]

The usual reason is you are missing the following folder\files in the root of the copype folder:

C:\winpe_x86\fwfiles

Make sure they exist and run: MakeWinPEMedia /ISO C:\winpe_x86 c:\winpe_x86\winpe.iso

Pete

[Migration User]

If you mean the WinPE_x86 folder which contains the following -

fwfiles
media
mount

I ran the command on this folder already and managed to create a bootable WinPE disc. I have booted from it and right now the 800 G1 I booted from the disc is sitting at an admin command prompt. However I have no ghost files that I can run therefore I do not know how I can get the PC to connect to my ghostcast server to pull an image down.

 

Thoughts appreciated.

[Migration User]

Hi Pete,

 

Already done this. The winpe_x86 directory is fine as I can create a bootable winpe iso from it, which I have done. The problem I have in working this way is that although I can boot the pc into WinPE and it picks up an IP address, I have no idea on how to get it to connect to my ghostcast server if this is even possible.

[Migration User]

if you have the ghost files in your WIM, you can launch them by hand.  or you can set your PE to run them automatically.

my "startGhost.cmd" file in my article tells you how that works

[Migration User]

Jeet,

Assuming you copied ghost32 or ghost64 to WinPE, either to a "Ghost folder" or System32 before you unmounted the WIM you would either cd to the ghost folder and or type ghost32\64. Once ghost32\64 loads you would use the initial menu > GhostCast and choose unicate for single computer imaging or Mulitcast for multiple. Then type in the MCAST session name (if you are on same subnet) or the ip address of the server runing the ghostcast session.

Pete

[Migration User]

Ok, so I mounted the boot.wim file along the following path -

c:\winpe_x86\media\sources\boot.wim

 

After mounting the boot.wim I browsed to it via explorer and I can see that it has the GHOST folder which I copied over earlier yesterday. It also has necessary ghost files in there ie ghost32, gdisk32 and ghreboot etc

Also checked in c:\winpe_x86\media and I can see the following folders which I also copied over earlier yesterday -

ghost
pxe

Any reason why I am unable to access these from the WinPE_x86 disc I created?

[Migration User]

Yes.

Why are you still using CD\DVD's? Using a USB flash drive is infinitely quicker.

When you are at the command prompt window in WinPE, what happens if you type cd X:\Ghost?

If you don't get error then type dir

Pete

[Migration User]

Just had an idea. Since I'm booted into WinPE, if I was to insert a disc with the ghost32 exe file on there, I should be able to run ghost from the disc correct?

 

EDIT: UPDATE: Finally worked it out! Had to change to the G: drive which is the CD drive containing my WinPe disc.

When you boot into WinPe you are presented with a CMD prompt with the path X:\Windows\System32 or something along those lines. To access my WinPE disc I had to get onto the G: drive and run ghost32 and voila!

Got the 800 G1 pulling down an image right now and no issues as yet :)

 

Result!

[Migration User]

USB sticks arent allowed in my workplace due to someone stealing a whole load of data a few years ago. The company is quite stringent on that kind of stuff. Might see if I can convince the boss otherwise just for this in particular.

[Migration User]

Jeet,

Just for reference. It doesn't matter whether you boot from CD or USB other than speed. However once the command prompt window is loaded you no longer need either the CD or the USB phyiscally in the computer as WinPE is actually loaded in ram - hence the X:\Windows\Windows32 in the prompt.

Infact you don't want to cd to the CD as it will be slow. Thats why you need to either cd to X:\Ghost or just type X:\ghost\ghost32.exe - you will still be using the ram drive - its much faster.

Pete

[Migration User]

glad to hear!!  you could make that CD/DVD start pinging your GSS console as soon as it boots by editing the startnet.cmd file

[Migration User]

along these lines, we make USB sticks that start pinging the GSS console as soon as they start up.  when they start that, you can remove the USB stick and move to another comp!

[Migration User]

I havent tried the X:\Ghost option, I will try that on another machine soon as I get the chance.

Terry, did you mention you had an article on getting ghost to startup automatically once at the command prompt?

So I left the HP 800 pulling down an image last night and it seemed to have gone through fine. Went through the initial windows screen prompts and got to the windows desktop and saw the core software packages we have installed so far so good. Unfortunately there appear to be no drivers installed for the network card, USB Controller, PCI Serial Port, PCI Simple Communications Controller, SM Bus Controller.

Just to give you guys some background on the image I use. The image is taken from a previous HP8300 PC onto which all the necessary softwares were installed and then we sysprep-generalized it, which if I remember correcly should remove all SIDs and hardware specific information such as drivers and language packs. The image was then captured using ghost.

I have been able to push this image out fine to older HP8000 PC's and all drivers have installed fine and even the model name of the PC corrects itself to whatever model of PC I am applying the image to. This is not the same for the 800 G1 PC's. I suspect this is something to do with the fact that I captured the image using ghost instead of something like WDS or MDT and not using original windows 7 media *shrug*

[Migration User]

a couple of things.

1) we capture our 800 G1 using GSS, and it installs the drivers correctly during Sysprep.  BUT!  PCI Serial Port, PCI Simple Communications Controller, and SM Bus Controller are all part of Intel AMT, and the 800G1 has a newer version than the 8300.  you need the new driver set for that.  

2) Another BUT!  The USB controller chipset on the 800G1 is different than the 8300.  Watch out.  The 800G1 USB ports do not work correctly if it pulls the 8300 driver.  the 8300 will blue screen if they get the 800G1 drivers.  EACH OF THOSE WILL ALWAYS PULL THE WRONG ONES IF BOTH DRIVERS ARE AVAILABLE TO IT!!  We solved this by uninstalling all the USB 3.0 drivers and pushing them down afterwards based on hardware queries.  learn from my giant headache

3) the auto phone home to ghost is in the same article as creating the PE3.0 image.  the sections starts "Third, the most important script.  This is flat out taken from a boot partition and makes the comp phone home to the console.  call it "startGhost.cmd".  It has the following (yes line 3 is blank)"

[Migration User]

You sir are a gentlmen and a scholar! I thought it was just me and a duff image hence the drivers problem. Think it might be best that I create a reference 800 G1 PC, sysprep and then capture the image just so that I dont mess things up with my 8300 image.

When you say you uninstalled and then pushed down the USB 3.0 drivers afterwards, Im guessing you  installed them manually then?

Ill check out the article again. Might have overlooked that part due to tunnel vision.

[Migration User]

actually, we ended up making SCCM groups based on some queries that determine if its an 8300 or 800G1.  those collections then get a package to install the correct drivers for the USB 3.0 chipset.

its an annoyance, but better than before.

we only maintain one setup here, so it has tons of drivers, and that problem was not a fun one to deal with

[Edward Tippelt]

You can load drivers from the WinPE command line using the DRVLOAD utility. The following article explains DRVLOAD:  https://www-secure.symantec.com/connect/articles/do-i-have-correct-driver-winpe

As well as running WinPE from a USB stick, you can do it from a USB hard disk as well - this might be more acceptable to management.

WinPE also supports WMI if the WMI module is loaded and you can use that to establish the exact machine you are running on. The following example code was used to detect from a range of Lenovo machines, amongst others, so you can see how simple it is to detect others:

' Set Environment

 

ver="CHASSIS 2 September 2009"

subtype=""

mdl="-(SUPPORTED)"

desc="UNSUPPORTED"

Const ForReading = 1, ForWriting = 2

Dim fso, f, yesno

Set fso = CreateObject("Scripting.FileSystemObject")

strComputer = "."

Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")

 

' Identify Machine Type and then partition accordingly

 

Set colEnclosures = objWMIService.ExecQuery("Select * from Win32_SystemEnclosure") 

 

   For Each objEnclosure in colEnclosures

      For Each intChassisType in objEnclosure.ChassisTypes

 

Select Case intchassistype

 Case "1" : strchassistype = "(1)Other"

 Case "2" : strchassistype = "(2)Unknown"

 Case "3" : strchassistype = "(3)Desktop"

 Case "4" : strchassistype = "(4)Low Profile Desktop"

 Case "5" : strchassistype = "(5)Pizza Box"

 Case "6" : strchassistype = "(6)Mini Tower"

 Case "7" : strchassistype = "(7)Tower"

 Case "8" : strchassistype = "(8)Portable"

 Case "9" : strchassistype = "(9)Laptop"

 Case "10" : strchassistype = "(10)Notebook"

 Case "11" : strchassistype = "(11)Hand Held"

 Case "12" : strchassistype = "(12)Docking Station"

 Case "13" : strchassistype = "(13)All in One"

 Case "14" : strchassistype = "(14)Sub Notebook"

 Case "15" : strchassistype = "(15)Space-Saving"

 Case "16" : strchassistype = "(16)Lunch Box"

 Case "17" : strchassistype = "(17)Main System Chassis"

 Case "18" : strchassistype = "(18)Expansion Chassis"

 Case "19" : strchassistype = "(19)SubChassis"

 Case "20" : strchassistype = "(20)Bus Expansion Chassis"

 Case "21" : strchassistype = "(21)Peripheral Chassis"

 Case "22" : strchassistype = "(22)Storage Chassis"

 Case "23" : strchassistype = "(23)Rack Mount Chassis"

 Case "24" : strchassistype = "(24)Sealed-Case PC"

 Case else : strchassistype = "(Undefined)"

End Select

 

'Find the model

 

 Set colComputerSystems = objWMIService.ExecQuery("Select * from Win32_ComputerSystem")

 For Each objComputerSystem in colComputerSystems

   strManufacturer = objComputerSystem.Manufacturer

   strModelA = objComputerSystem.Model

 Next

 

 strModel = Left(strModelA,4)  'Extract first four digits of model number

 

Select Case strModel

 

  Case "8171":desc="S51 Desktop"

  Case "8143":desc="M51 Desktop"

  Case "6223":desc="Zpro Desktop"

  Case "9228":desc="ZPro Desktop"

  Case "8811":desc="M55 Tower"

  Case "8808":desc="M55 SFF"

  Case "6072":desc="M57 SFF"

  Case "6075":desc="M57 Tower"

  Case "6234":desc="M58p SFF"

  Case "6209":desc="M58p Tower"

  Case "2672":desc="X32 Laptop no Fingerprint sensor"

  Case "2668":desc="T43 Laptop with Fingerprint sensor"

  Case "2008":desc="T60P Laptop with Fingerprint sensor"

  Case "1707":desc="X60 Laptop with Fingerprint sensor"

  Case "7674":desc="X61 Laptop with Fingerprint sensor"

  Case "6457":desc="T61P Laptop with Fingerprint sensor"

  Case "7459":desc="X200 Laptop with Fingerprint sensor"

  Case "2055":desc="T500 Laptop with Fingerprint sensor"

  Case "2056":desc="T500 Laptop with Fingerprint sensor"

  Case "1866":desc="X41T Tablet with Fingerprint sensor"

  Case "7763":desc="X61T Tablet with Fingerprint sensor"

  Case "CF-U":desc="CF-U1 Ruggedised Portable"

  Case "HP x":desc="HP xw8600 Workstation"

  Case "HP Z":desc="HP Z800 Workstation"

  Case "VMwa":desc="VMware Virtual Platform"

 

End Select

 

 

   Next

      Next

 

'Get the serial number

Set colSMBIOS = objWMIService.ExecQuery ("Select SerialNumber from Win32_SystemEnclosure")

For Each objSMBIOS in colSMBIOS

strSerial=objSMBIOS.SerialNumber

'Wscript.Echo "Serial Number: " & objSMBIOS.SerialNumber

Next

 

'Display the result

'msgbox "Manufacturer = " & strManufacturer & chr(13) & chr(10) &"Model = " & strModelA & chr(13) & chr(10) &"Description = "&desc& chr(13) & chr(10) & "WMI Type = "&strChassisType & chr(13)& chr(10) & "Serial Number = " & strSerial,4160,ver

msgbox "Manufacturer = " & strManufacturer & chr(13) & chr(10) &"Model = " & strModelA & chr(13) & chr(10) & "WMI Type = "&strChassisType & chr(13)& chr(10) & "Serial Number = " & strSerial,4160,ver

 

yesno = msgbox ("Do you want to save this information to a file",4100,ver)

 

if yesno = 6 then 

Set f = fso.OpenTextFile(strManufacturer&"+"&strModelA&".txt", ForWriting, True)

f.writeline "Manufacturer = " & strManufacturer

f.writeline "Model = " & strModelA

' f.writeline "Description = "&desc

f.writeline "WMI Type = "&strChassisType

f.writeline "Asset Tag = " & strSerial

f.close

msgbox "Information written to "&strManufacturer&"+"&strModelA&".txt",4160,ver

end if

[Migration User]

nice post!

as for what i was talking about earlier with the USB 3.0 drivers, its not a PE issue for me, but an actual real Windows issue, after sysprep