Wiener

So, I will go out on a limb and assume that you want to install the Sierra and Cisco software on a notebook without regard to whether or not the wireless card is installed. Cuz if you only want to install software with corresponding hardware, then it would be better to test for the hardware existance rather than system enclosure type. Dim objWMIService, colItems Set objWMIService = GetObject("winmgmts:\\" & "." & "\root\cimv2") Set colItems = objWMIService.ExecQuery("Select * from Win32_NetworkAdapter",,48) For Each objItem in colItems Wscript.Echo "Name: " & objItem.Name Next So test for Name = Your Sierra Wireless card and if true, install the software.

You could take a look at Microsoft's Business Desktop Deployment or BDD. We have adopted this method and have succesfully remotely upgraded 500 Win2k PCs in our own organization, 250 "bare-metal" installs for another customer and are preparing to remotely upgrade 9000 NT PC for yet another customer. 3 prepared images per customer (ACPI, AACPI and MACPI HAL types) cover all current makes and models. Enterprise edition is designed around using SMS but the Standard edition can be used with Ghost or similar imaging products. All drivers are included in the $OEM$ structure. The base PC is booted up using WinPE, connects to the server, downloads XP with all hotfixes, drivers, hardware apps (Roxio, ATI, HP stuff). The PC reboots, installs XP and once GUI, it then installs base apps such as Office, Virusscanner, Media Player, Codecs, Adobe Reader and WinZip from the network. Then the image is syspreped and captured. Using SMS or Ghost or whatever, you then deliver the image to the PCs. The PCs once rebooted go through minisetup and install all the drivers and startup batch file checks the hardware and installs whatever hardware apps are needed for that particular PC. During an upgrade using SMS, all the user's stuff is protected under a single folder, the remainder of the HD is wiped clean and the new OS is installed. During startup, the user's stuff is returned to their new profile that is created on the PC. Any additional applications that they require (that were not included as part of the base image) are delivered via Add-Remove programs using either AD or SMS. It works very slick and using SMS it really is "Zero-Touch" without having to visit the client's location. Ian

There is another option if you can get hold of a copy of Windows PE 2004. Microsoft Solution Accelerator for Business Desktop Deployment (BDD) offers a means of building your base PC and then using it to create an image that you can mass deploy. In the situation where you only want to build a box or two, it can still be used to create the base PC using the Computer Imaging component. BDD quick look will give you an idea of the work required to fire it up. I have been using it both at work and at home for the past year and it works great. At work we have created 3 images that can be deployed to all different models of Compaq, HP and IBM PCs.

Use this and save as Whatever.cmd: @echo off rd "C:\Documents and Settings\Administrator\Start Menu\Programs" /s /q md "C:\Documents and Settings\Administrator\Start Menu\Programs"

Strange, I just tried it and it worked here .... I first tried del C:\...\.* and like you mentioned got access denied. Then I tried the rd line and it worked just fine.

Thanks, I did search but I didn't use the word "integrate" (I tried preinstall) so I did not find any usefull results. Guess I should search how to use search!! Thanks again.

Not quite sure exactly what you want to do but why not simply a batch file that deletes the objects? rd C:\Documents and Settings\Administrator\Start Menu\Programs /s /q then simply recreate an empty Programs folder md C:\Documents and Settings\Administrator\Start Menu\Programs You could do the same thing for All Users Programs folder. Ian

After building a PC using an unattended method .. I use WinPE and BDD ... I then like to connect to Windows Update to check for any missing patches or hotfixes. But the first time it connects, the PC downloads and installs the "Windows Updater" which takes forever on my dial-up line. How do I include this with the unattened install so that Windows Update can simply proceed and check for any missing updates without having to download and install yet another bit of software. Thanks. Ian

I use Microsoft's BDD and WinPE to create my build. All files are located on the network share and the WinPE disk connects to the network, prepares the HD, downloads all the files and then the PC reboots and completes the unattended setup. However, this current process uses Hotfixes under SVCPACK folder and SVCPACK.INF and Driver folder under $OEM$\$1\Drivers which are copied to the HD during the copy phase. All the driver paths are hand copied into the Unattended.txt file. Not very elegant, time consuming and always out of date ... I would love to use the combination of RyanVM's hotfix pack, BTS's driver packs and nLite to incorporate all of this into my network install. All of the reading I have done seems to be toward creating a bootable CD with all the above goodies. I do not require the CD, but need the files installed on the network for use with WinPE and installing using the Unattended.txt file. If someone could point me in the right direction towards this goal, I would appreciate the pointing. I posted a similar message on the nLite Forum so if that is considered cross-posting, my apologies and the admin can feel free to toast this message or the other. Thanks. Wiener

Great script! I have a couple of issues: - Matrox drivers include file names with spaces. The process seems to choke on these. For example the files are - "Multi-Display Utility.exe"; "Multi-Display UtilityEng.cnt"; "Multi-Display UtilityEng.hlp" etc. When Compress is run against these, I get Error: Multi-Display not found! for each similar entry in the INF file. - Intel e1000325.inf. I get Error: Class in e1000325.inf not found! Yet, the e100a325.inf file gets parsed perfectly fine as does e100b325.inf. The first few lines of the failing e1000325.inf file are: [Version] Signature = "$Windows NT$" Class = Net ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318} Provider = %Intel% CatalogFile = e1000a325.cat DriverVer=10/28/2003,7.3.13.0 [Manufacturer] %Intel%=Intel, NTx86, NTIA64 The first few lines of the working e100a325.inf file are: [Version] Signature = "$Windows NT$" Class = Net ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318} Provider = %V_INTEL% CatalogFile = e100a325.cat DriverVer = 03/04/2005,8.0.19.0 [Manufacturer] %V_INTEL% = Intel, NTx86