gadget

I use VB 6 to do all my work. All i need for that is to run vb6.exe at pe startup. Items can be registered individually but I cannot be bothered to go to all the trouble. I cannot remember the original filename of vb6.exe. it weighs in at under 1mb so if you require it IM me.

Why don't you just create a menu within one core pe image. My entire operation runs from one PE image via WDS. Menu and data collection is all run inside VB but HTA would probably suit you more.

WMI support in pe1.x is really bad. I use a utility called peshutdown. This shuts down, restarts ect. Mine shuts down any system after 23 hours to stop pe rebooting itself. Canuse it in pe2 as well.

Sorry, double post peshutdown.zip

I take it you like typing TofuBug. It's nice when a plan comes together.

this is my code snippet for detecting installed memory. It reports each module but you can just add up the total. This may also pick up any flash rom as well. Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_PhysicalMemory", "WQL", _ wbemFlagReturnImmediately + wbemFlagForwardOnly) For Each objItem In colItems txtfile.writeline "Name : " & objItem.DeviceLocator txtfile.writeline "Bank : " & objItem.BankLabel totmemory = ((objItem.capacity) / 1024) / 1024 txtfile.writeline "Capacity : " & totmemory & " Mb" txtfile.writeline "MemoryType : " & objItem.MemoryType txtfile.writeline "" Next

I have not found a way yet without using the 64bit version. What I do is to use wmi to read the dims and total the memory up that way.

At what point are the nic drivers not loading. When running winpe 2.0 to deploy the image or within the deployed operating system? Are you using a different winpe.wim for capture and deployment? If so you will need to apply the drivers to both winpe.wims Bit more detail may help us to help you.. PS Welcome to MSFN

Depends on what type of routing you have. The DHCP server requires to forward certain requests to the network and if this is not setup then no amount of pxe installations you do will work. Easiest is to get your network team to forward bootp and tftp requests and your existing dhcp server should work.

Well, in case you are interested, I add registry entries Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "WUServer"="http://server" "WUStatusServer"="http://server" "ElevateNonAdmins"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU] "UseWUServer"=dword:00000001 "DetectionFrequencyEnabled"=dword:00000001 "DetectionFrequency"=dword:00000001 "AutoInstallMinorUpdates"=dword:00000001 "NoAutoUpdate"=dword:00000000 "AUOptions"=dword:00000004 "ScheduledInstallDay"=dword:00000000 "ScheduledInstallTime"=dword:00000003 "RescheduleWaitTimeEnabled"=dword:00000001 "RescheduleWaitTime"=dword:00000001 "NoAutoRebootWithLoggedOnUsers"=dword:00000000 "RebootWarningTimeoutEnabled"=dword:00000001 "RebootWarningTimeout"=dword:00000001 "IncludeRecommendedUpdates"=dword:00000001 Then reboot the system running shutdown scripts resetting these setting Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update] "ConfigVer"=dword:00000001 "AUOptions"=dword:00000001 "NextDetectionTime"="2008-01-20 13:49:08" "ScheduledInstallDate"="2008-01-20 03:00:00" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Detect] "LastSuccessTime"="2008-01-23 13:45:02" "LastError"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Download] "LastSuccessTime"="2008-01-23 13:41:11" "LastError"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Install] "LastSuccessTime"="2008-01-23 13:36:18" "LastError"=dword:00000000 Not very tidy but seems to work in general. Need to install the latest windows installer first tho.

Hi, I need to run windows updates on systems fresh out of the box before shipping to end users. I am looking at deploying to XP, server 2003, Vista and don't really want to script manual installs of patches. Windows Update is too slow so looking into using WSUS server. Everything works in getting patches from the server ect but I would like to automate the download, install and reboot of the client systems automatically. I can script everything to set/clean registry ect but the best I can do so far is to run wuauclt to download and notify that updates are ready to install which required user intervention to run. I have tried scanning then changing system times to try and get automatic updates to install these but it is not reliable. Has anyone got any ideas on this? Registary settings: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "ElevateNonAdmins"=dword:00000001 "TargetGroup"="All Computers" "TargetGroupEnabled"=dword:00000001 "WUServer"="http://server" "WUStatusServer"="http://server" [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU] "AUOptions"=dword:00000004 "AutoInstallMinorUpdates"=dword:00000001 "DetectionFrequency"=dword:00000001 "DetectionFrequencyEnabled"=dword:00000001 "NoAutoUpdate"=dword:00000000 "RebootRelaunchTimeout"=dword:00000001 "RebootRelaunchTimeoutEnabled"=dword:00000001 "RebootWarningTimeout"=dword:0000001 "RebootWarningTimeoutEnabled"=dword:00000001 "RescheduleWaitTime"=dword:00000001 "RescheduleWaitTimeEnabled"=dword:00000001 "ScheduledInstallDay"=dword:00000000 "ScheduledInstallTime"=dword:00000005 "UseWUServer"=dword:00000001 "NoAutoRebootWithLoggedOnUsers"=dword:00000000

Sorry, it works for me. On Error Resume Next Const wbemFlagReturnImmediately = &h10 Const wbemFlagForwardOnly = &h20 arrComputers = Array(".") For Each strComputer In arrComputers WScript.Echo WScript.Echo "==========================================" WScript.Echo "Computer: " & strComputer WScript.Echo "==========================================" Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_Processor", "WQL", _ wbemFlagReturnImmediately + wbemFlagForwardOnly) For Each objItem In colItems WScript.Echo "LoadPercentage: " & objItem.LoadPercentage WScript.Echo Next Next Function WMIDateStringToDate(dtmDate) WScript.Echo dtm: WMIDateStringToDate = CDate(Mid(dtmDate, 5, 2) & "/" & _ Mid(dtmDate, 7, 2) & "/" & Left(dtmDate, 4) _ & " " & Mid (dtmDate, 9, 2) & ":" & Mid(dtmDate, 11, 2) & ":" & Mid(dtmDate,13, 2)) End Function

Only a pe2 wim can be bootable then script the install from within that..

Br4tt3, Give me a call when you need to refresh your estate, give you a good price on 54000 new HP's.... Even apply your image for you.

How strange, I have just been tasked with ripping the BDD 2007 apart to see how we can integrate it into our current systems and visa versa. Wish me luck..

Correct, Service Pack 2 is a bit of a bugger, plan your Ris Server upgrades carefully. Mind you, if you are reading this then it's probably happened to you already.....

Glad you cracked it... Well done... We load PE 2 onto around 300 systems a day here, might put up some interesting statements on the loader.....

It's not a simple case of user the correct syntax for domain users ie net use t: \\server\share\ password /user:[domain]\username.

PE2 is part of the WAIK (Windows Automated Installation Kit) which is freely available from Microsoft. In many ways it is a major improvement over 1.x but it still fails in some areas. I use a mixed bag of 1.6 and 2.0 here.

Put the commands in batch file and call setup using start /wait J:\windist\i386\winnt32.exe /syspart:c: /unattend:J:\windist\unattend.txt /s:j:\windist\i386 then on the next line use the wpeutil.exe to restart the server [wpeutil reboot]. If your PE only does this then put it into the startnet.cmd Diskpart you type all your commands into a txt file and call it by diskpart /s diskpartscp.txt

Have you turned the firewall off?

You can remove to prompt entirly if it helps, just can't remember the file to delete. I will have a look further into this problem tomorrow to see if the time can be increased.

pe does mix up the partitioning. When running diskpart, select drive 1 partition 1 and assign a new drive letter except c: then assign disk 0 partition 1 as c:. As a check, in your cmd file, do if exist c:\*.* or c:\[Wim Directory]\*.* goto blah blah if it contains data then do it for the other partition, if it finds a blank drive then use that drive letter to deploy your image to.

If you only have a few different models then use the model name or model type from wmi. FROM Win32_ComputerSystem model.

The Problem you may face is the environment. PE out of the box will not run the 16bit code and will probably not allow the calls the program requires. It's a bit of a pain but what we do is either use a virtual floppy with PXE/RIS or to load a small image onto the hard drive and boot onto the hdd. Thank god most manufactures are creating a windows based 32bit flash method.