mats

This is really strange Exactly witch fujitsu are you using? We got some diffrent ones and it could be intresting to see if we got the same modell

Hi kRUSty I think you are doing some extra steps here. you shouldn't need to create the new partion or format it since this already is in the ghost image. Your way isn't bad in any way it's just that you can save time by skipping it. have you tried to run diskpart between steps 7 and 8 and assign a letter to the new partition? I wrote a system that does the same as yours but with pqideploy insted of ghost. thee i had to assign a letter to the newly imaged drive before i could access it again. This has worked on about 30000 installations so far

According to MS you need to install recovery console to boot PE from boot.ini Well, there is another way of doing this. i prefer the new ramboot style so that will be used in this example. The iso filename should be max 8.3 according to noodles so i used test1.iso. Ofcourse you can name it whatever you like. 1. Grab a copy of mkbt and nt2peldr from bart 2. make a working ramdisk booting pe iso, place it in c:\ with the name test1.iso 3. copy setupldr.bin from a server2003sp1 disc to c:\peldr 4. run mkbt -c -x c: c:\peboot.bin 5. run nt2peldr c:\peboot.bin 6. Edit boot.ini and add a line c:\peboot.bin="PE From ram" 7. Create a winnt.sif file with the following in it [setupData] BootDevice = "ramdisk(0)" BootPath = "\i386\System32\" OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=test1.iso" Architecture = "i386" Reboot the system and enjoy

Stasys44: No offence but the main difference is that this is Winpe not barts variant and that matters for many of us who got relations with microsoft since MS want touch bartPe but they will support WiinPE

Have you tried to change the installation media for server2003?

Nice one n00dles

Yes you can. The exact steps are described in winpe.chm which is in the docs directory of the original winpe cd or download.

yep HP,DELL and FS plus vmware for us

I have done a few a those. HP remote insight boards are nice. Simply take the nic ofline and install it but i agree that it is a better soloution to enum the macs. Currently im fighting with DB2, trying to get the db2 ole driver to work in pe. Looks like we will have to use a ms sql as a proxy instead

Hi Chris It's very true that I only handle one nic in this code. But since it only takes adapters with an ip we simply pull the cables from the other adapters which are on dhcp enabled nets and since it is intended to run from PE virtual dapters are no problem. If you want to it would be easy to make the macaddress varaible an array and simply query for each mac found in the system instead. Ofcource only one should be in the database your asking for the info Bios:es kan be a major issue, HP has a nasty habit of changing the modellname as soon as they change a component for example a switch of HD vendor. So far we got two ways to handle that. either reject bad bios:es or copy the driver files to the new name

I'm back at the office and here comes Dim objWSHShell Dim objWSHNetwork Dim objWSHProcessEnv Dim fso '***************************************************************************** '* '* Deklarera konstanter '* '***************************************************************************** Const SHOWHIDDEN = 0 Const SHOWNORMAL = 1 Const SHOWMIN = 2 Const SHOWMAX = 3 Const FILEATTRNORMAL = 0 Const FILEATTRREADONLY = 1 Const FILEATTRHIDDEN = 2 Const FILEATTRSYSTEM = 4 Const FILEATTRVOLUME = 8 Const FILEATTRDIRECTORY = 16 Const FILEATTRARCHIVE = 32 Const FILEATTRALIAS = 64 Const FILEATTRCOMPRESSED = 128 Const FORAPPENDING = 8 Const FORWRITING = 2 Const FORREADING = 1 '***************************************************************************** '* '* Initiera objekt '* '***************************************************************************** Set objWSHShell = WScript.CreateObject("WScript.Shell") Set objWSHNetwork = WScript.CreateObject("WScript.Network") Set objWSHProcessEnv = objWSHShell.Environment("PROCESS") Set fso = CreateObject("Scripting.FileSystemObject") '***************************************************************************** '* '* Initiera Variabler '* '***************************************************************************** '***************************************************************************** '* '* Huvudprogram '* '***************************************************************************** '***************************************************************************** '* '* Subrutiner '* '***************************************************************************** dim colItems dim objitem dim counter dim ismobile dim objwmiservice dim macaddress dim ipaddress dim manufacturer dim Model ismobile=0 Set objWMIService = GetObject("winmgmts:\\.\root\cimv2") Set colItems = objWMIService.ExecQuery("Select * from Win32_NetworkAdapter", , 48) For Each objItem In colItems if not isnull(objItem.MACAddress) then macaddress= "Macaddress: " & objItem.MACAddress end if next Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled = True") For Each objItem in colItems If Not IsNull(objItem.IPAddress) Then For counter = 0 To UBound(objItem.IPAddress) ipaddress ="Ipaddress: " & objItem.IPAddress(counter) next End If next Set Colitems = objWMIService.InstancesOf ("Win32_ComputerSystem") for each objItem in Colitems manufacturer = "Manufacturer: "& trim(ObjItem.Manufacturer) if right(manufacturer,1)="." then ' Dell och VMware got a point in the name manufacturer= left(manufacturer,len(manufacturer)-1) end if Model= "Modell: " & trim(ObjItem.Model) next if instr(ucase(Model),"SCENIC") then 'Fujitsu siemens namnes multiple boxes to Scenic Set ColItems = objWMIService.InstancesOf("Win32_BaseBoard") 'for these we use the mainboard as name For Each objItem In ColItems Model = "Modell: " & trim(ObjItem.Product) next end if Set ColItems = objWMIService.InstancesOf("Win32_Processor") For Each objItem In ColItems if instr(objitem.name,"Pentium(R) M") or instr(objitem.name,"Mobile") then ismobile="Is a mobile" end if next msgbox macaddress & vbcrlf & ipaddress & vbcrlf & manufacturer & vbcrlf & model & vbcrlf & ismobile then simply do a copy \\server\manufacturer\model\*.* to c:\something include c:\something in the pnpoemdriverspath in the target registry and it will scan c:\something for drivers the sysprep runs

Virtual pc and Vmware uses virtual hardware that is true but to get that virtual hardware to work you will need drivers for it. XP has theese drivers built in straight out of the box but a stripped PE doesn't and therefore you will have to add the nic driver for Intel 21140-Based PCI Fast Ethernet Adapter. that is net21x4.inf and dc21x4.sys

yepp the -m switch does the trick we have deployed a few hundred machines from DVD. Mainly locations with only 10Mbit networks

This is also a very good way to apply a patch to already infected machines in a safe way. It's on my todo list to make a cd with easy hta screens and modular backend so that an user can fix his/her own machine in case of an outbreak where we can't use sus/tivoli to fix the problem

If yoy want a writeable system drive. Nope according to MS that cant be done. If you want an extra writeable ramdrive ex r: yes, the examples I have posted works

Hi Again I'm currently on vacation but I'll see what I got on my laptop.

Oki sorry I just needed the CD letter and that was what I was using before 2004/2005 Br4tt3: Hej Själv. Alltid rolig med landsmän

Is it simply the existens of a cd drive you need? in that case this might do sub getcddrive() Dim ObjDrives Dim ObjDrive Set ObjDrives = fso.Drives For Each ObjDrive in ObjDrives If ObjDrive.DriveType = 4 Then cddrive= fso.GetDriveName(ObjDrive) exit sub End If Next end sub

There is a killer function in this too. Try PXE on a 10 Mbit network. Some nics will need up to 30 min. to boot, with ramdisk, they do it in 5.

PE2005 can build from Server2003Sp1 or XPSP2. If your disc only can build from XPSP2 it's not a 2005 but a 2004

Hi Chris That was a nice one. Do you manually select the server modell or have you done it with WMI/DMI I'm doing about 35 workstation models with a single XP image and DMI to do vendor specific changes

Could you be more specific? What is it that doesn't work? how did you create the image, did you follow the docs on the disc or a webppage or something else? Can you boot from from the disc. The first thing that strikes me is what version of ghost are you using, you must have a 32 bit version. Ghost 8.x in 32 bit versions is the easiest to get working

weaz1dls: You don't need a boot.bin for this. Pebuilder creates a bootable cd image. xtremee: You didn't say what version of pebuilder you use but download 3.1.3 and let it create the iso and burn it. That always works for me

Are you sure that it is pe 2004 you are using? Usb boot isn't supported before 2005 and I'm not sure about 64 bit either

Had exactly that problem with the boot order corectly defined. Had to reinstall system from scratch to fix it