[Streamline 'Microsoft Update' into IE for unattended XP instal]

Here's how I got it working...

On a machine with Microsoft Update installed:

create c:\msupdate

stop the automatic updates service and rename the %windir%\softwaredistribution\datastore\datastore.edb file to datastore.old.

start the automatic updates service so it creates a "clean" datastore.edb file (1mb) and then stop the service again.

copy the datastore.edb file to c:\msupdate

delete %windir%\softwaredistribution\datastore\datastore.edb

rename %windir%\softwaredistribution\datastore\datastore.old to datastore.edb

start the automatic updates service

copy %windir%\system32\muweb.dll to c:\msupdate

save the bolded text beneath as c:\msupdate\msupdate.cmd

@echo off

copy "muweb.dll" %windir%\system32

net stop wuauserv

del %windir%\SoftwareDistribution\DataStore\DataStore.edb

copy "DataStore.edb" %windir%\SoftwareDistribution\DataStore

regsvr32 /s muweb.dll

net start wuauserv

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains\microsoft.com" /v "*" /t REG_DWORD /d "2" /f

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains\windowsupdate.com" /v "*" /t REG_DWORD /d "2" /f

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\1" /v "1001" /t REG_DWORD /d "0" /f

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\1" /v "1809" /t REG_DWORD /d "3" /f

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\1" /v "1200" /t REG_DWORD /d "0" /f

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\2" /v "1200" /t REG_DWORD /d "0" /f

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\2" /v "1001" /t REG_DWORD /d "0" /f

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\2" /v "1809" /t REG_DWORD /d "3" /f

Run the batch file in the folder during your unattended setup. This doesn't actually install the activex control but will silently install it the first time you visit the website and the user will be none the wiser.

[VBscript in commandline]

How do you call the vbscript, by just using the vbscript.vbs?

or do you use a batch file which contains:

call cscript somescript.vbs //nologo
exit

yes

call cscript somescript.vbs //nologo

this way i don't get prompted to run somescript.vbs

somescript.vbs removes the zone checks that bring up the 'ok' prompt.

then it calls a bunch of other scripts that need wscript to run...

[Slipstreaming NIC drivers into WDS Boot file]

Or if you created a WinPE 2.0 image using Windows Automated Installation Kit, you could also use

PEIMG /INF=inffile.inf mount\Windows

as described here

...and as also described in doders' original post... lol

i integrated all the driver packs by using this batch file.

@echo off
for /R %%z in (*.inf) do peimg /inf="%%z" \winpe\mount
pause

just save it into your expanded drivers folder, change \winpe\mount to your mounted folder location, run it and put the kettle on...

[WDS on separate server to DHCP]

...so the old RIS images are useless...

use wdsutil to convert the rip images to wds wim files...

eg.

wdsutil /Convert-Riprepimage /Filepath:"riprep.sif" /DestinationImage /Filepath:"XP.wim"

[DHCP Problem]

Hi

I've got a working RIS server on a test network. DHCP is not installed on the RIS server and clients get their IP addresses from a scope on the test 2003 pdc.

I now need to move this server to our prod network, but the problem is that DHCP on prod network is still on a NT4 box. Will RIS still work?

If not and I decide to install DHCP on my RIS server as well, how can I force all workstations in the company to get IP from the old DHCP server and only RIS clients to get addresses from the DHCP scope on the RIS server?

I tried to test this on our test network by installing DHCP and creating a scope on the RIS server as well, but RIS clients still get their IP's from the scope on the pdc, not the RIS server.

Thanks for the help.

yes, ris will still work.

dhcp requests will go to the dhcp server (nt4) and pxe requests will go to the ris server (2003).

you've even proved this yourself by installing dhcp on the ris server and it not responding to clients.

[WDS Specific Clients Freezing]

have you tried creating the image manually from the command line of your boot image?

imagex /capture C: image.wim "Name"

you'll need to copy the imagex.exe program from your waik installation to your windows\system32 folder on your pe2.0 boot image...

reboot the pc, finish sysprep then copy the file manually to your wds server.

[RunOnceEx Windows asks if i trust the DL appl. ?]

Windows XP sp2 ask if i trust the Downloaded application.

how can i turn this of,

right click the downloaded .exe, properties, unblock, ok.

[VBscript in commandline]

myscript.vbs will run another .vbs script without the prompt.

myscript.vbs:

Dim WSHShell, WshEnv
Set WSHShell = CreateObject("WScript.Shell")
Set WSHEnv = WSHShell.Environment("PROCESS")
WSHEnv("SEE_MASK_NOZONECHECKS") = 1
WSHShell.Run "\\MYDOMAIN\NETLOGON\scripts\login\calledvbs.vbs",1,True
WSHEnv.Remove("SEE_MASK_NOZONECHECKS")

call it from a batch file...

@echo off
setlocal extensionsenable
cscript \\server\netlogon\scripts\login\myscript.vbs //nologo
exit

you'll need to modify those files to suit your needs.

[RyanVM Issue]

hi,

afaik the permission to load/unload device drivers only applies when the 'add new hardware' wizard is invoked manually.

cancel the credentials box and run the 'add new hardware' wizard, it should then see your new, uninstalled device and load the drivers...

[Slipstreaming NIC drivers into WDS Boot file]

hi,

you'll only need a network driver to connect to the "microsoft windows network" for mapping drives etc...

it's not needed for operating system deployment as it just uses the same protocols it used to boot from the network to transfer your install image.

use the \sources\boot.wim from a vista dvd as your boot image. this connects back the the wds server and lets you choose which install image to deploy.

if you do want to integrate the driverpacks, extract them and...

move all .inf files to (i386 or windows)\inf

move all .sys files to (i386 or windows)\system32\drivers

move all other files to (i386 or windows)\system32