boredazfcuk

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.

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...

...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...

use wdsutil to convert the rip images to wds wim files... eg. wdsutil /Convert-Riprepimage /Filepath:"riprep.sif" /DestinationImage /Filepath:"XP.wim"

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.

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.

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

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.

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...

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