Br4tt3

There is a tutorial for this @ unattended.msfn.org i think... inside the $OEM$ folder, create $1 fodler (which corresponds to the root of c:\) and one $$ folder (which corresponds to system32).. make the necessary changes to ur answer file that will reflect the changes u just made (OEMPreinstall = YES) and then u r all set to go ahead in VPC. Regards

Create the $OEM$ folders.. for this case especially the $$ folder which corresponds to the c:\windows\system32 folder... place in there and u will get the path variable in once. that ought to do it...

First of all download the deployment tools from MS; deploy.chm and ref.chm, they come in diffrent flavours when it comes for the support of operating systems and servicepack levels. For the links I dont have any good overview ones.. only for the ones I cant solve so u r better of trying to surf the waves there dude... Cu

There is two ways of running RIS: 1. Image based installations (limited to / HAL) which kind of static in their nature. 2. Flat installations. This is automatic generic installation of Windows according to an answer file. The nice part about it is that u only have to maintain one installation directory for all models as long as u provide all the drivers to the installation. TheWin32 installation will by itself detect if it is a P3 or P4 etc etc and install accordingly (which riprep wont since they are using diffrent HAL's). Once you have installed RIS onto the machine, youy can run risetup.exe /add to add an installation. U just point out the i386 for the source files and RIS will build a open / flat installation structure. It will create a default answer file which u prolly must edit so that it fits your installation. Also, u must add drivers and so on accordingly to the $OEM$ folder. Anyway.. once the image is in place, just add the $OEM$ folders to the same level as the i386 folder below ur image name and make sure that the entry OEMPreinstall (think that is the one ) is set to = YES. This will make the install search for a $OEM$ folder. $1 and $$ and so on will be automatically copied to ur local drive from there on. There is a tons of things to read about RIS on MS webby and tons of stuff to do that are not really documented either with the RIS feature. Best of luck.. P.S "PASCAL FEOS" rox

Ohh... u r using riprep to do an image then? this is the image based stuff of RIS. I am not to familiar with riprep.exe and how it works, i only use the flat image which is a more generic installation... since it is a image i dont know if u have to recreate the image or if is enough to just add folders post to the creation of the image. Try both... I guess u can read tons of info on how to add the OEM folders to an riprep image on MS site or if u have to add it at the "master" image directory. Sorry, dont have so many answers when it comes to the riprep case of RIS..

Is it from a CD ??? If it is u need to point out the $ dir's with the OEMFilePath = entry in ur answer file. If it is from a RIS installation, then this automatic handled by placing the $OEM$ folder with the containing $dir's on the same level as the i386 folder below ur image name. Hope u get lucky dude... keep on dancing!

Thanks, I will try it out... I was wishing for an unattend entry from MS to control this feature, but I guess they (M$) havent documented this one yet.. not in the deployment tools anyway. THX again Sonic the "hedgehog" and stay fast..

Lo folks.. trying to integrate the SP1 for Win2003 Server, and upon final install, I get the "Windows Server Post-Setup Security Update" dialog box in my face.. I know I know, you are supposed to do stuff with it but... I downloaded the SP1 deployment tools from MS: ref.chm & deploy.chm and I cant find any entries that correspond to this niffty feature... so any1 else had any luck with it yest? My guess there must be some kind of corresponding entry to the unattend file. Cheers.

I know. We will get it a bit later with OEM Partner's materials shipment in July but want to see it now. If you may help, drop me a line, or ICQ me, plz. <{POST_SNAPBACK}> I dont think u will get any luck with that.. I would recommend you to contact your MS representative, they can speed up the deliverey since you will be getting it eventually as u say...

Never used driver packs that are preconfigured, dunno about that one.. but when it comes to the masstorage part of the drivers, I defenitly prefer adding them by using the TXTSETUP.SIF way, rather then the suggested way from MS (I guess folks dont agree on that one...) The downside of adding them in the way MS suggests is that u can only load one specific chip / driver / folder that u create (as far as I know of) or you have to add multiple folders with the same driver and specifying diffrent [Default] entries for each one of them... thats a boomer when it comes to adding support for several chipsets handled by the same family software driver for example. There are loads of info on the site for how to doing it...

Dunno really... I downloaded mine (RTM version) from the MVL (MS Volume License) FTP site. I also saw that the RTM version was available for a coupple of days at the MS beta site (if u signed up for that one...) before they removed it. Have checked my MS CD's but cant find any PE 1.6 in there... Hope u get hold of it eventually, great stuff...

Overkill example: First.. script an RIS installation using vbscript for example. Easiest done by using sysocmgr.exe (with switches for the RIS feature) to the installation. Once it is installed, script risetup.exe /auto <answer.inf> to pinpoint the installation source files. After this... perform any modifications to the installation (such as specifying a custom .sif file, building $OEM$ folders and so on).. Oki.. so now u can script an entire RIS installation to work unattended! So how to get around the problem of having to logon as local admin or domain admin to perform updates? well, wrapp your scripted installation files and any required files into an .msi package, assign AD GPO to install .msi with elivated priviliges and the even system (NT_Authority\System) can run the installation. Any updates to the RIS installation can then be handled using .msp's to the original .msi file. hardest thing is to trick the NetServices object in AD to authorizing the RIS in DHCP wihtout Enterprise / Domain Admin permissions.. for example...

If u want to this kind of stuff I personally prefer the way of adding them to: Create a directory below the <image-name>\i386\ named Svcpack. add ur hotfixes into this directory (needs to be extracted). Also create or edit ur svcpack.inf file in the i386 directory, edit ur dosnet.inf to relfect the changes. A better tutorial might be: http://support.microsoft.com/default.aspx?...kb;en-us;316037 Hopes it solves it for u...

Yup, the ramdisk functionality is nice and also added is the support to boot of USB devices such keysticks...

Oki, in my case it was that someone had installed HP WebJetAdmin onto the machine. We have had issues with RIS and HP JetAdmin before.. dunno why they r incompatible but they r.. Regards sausage eater..

Hi there... Keep getting this error message upon startup: Faulting application tcpsvcs.exe, version 5.2.3790.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x0001d61b. Windows 2003 RIS Nobody seems to know, any1?

I am saying I cant find the formatufd.exe tool... I got the WinPE 2005 RTM .iso from Microsoft MVL (Microsoft Volume License) ftp site from my MS person...

Hi I have been following the development of WinPE 2005 from MS as I want to get my hands on both the USB boot options and the RAMDRIVE functionality. However, once i downloaded the WinPE 2005 RTM .iso file from MS, i can find the formatufd.exe command line tool that is mentioned in the .chm file. MS refers to the OPK for WinPE.... My understanding was that the WinPE RTM .iso was the OPK! Any1 wanna explain this if they know the diffrence? Regards

Got it.. thanks Chris!

Hi Since the SP1 for Win2003 now is released to the public, it should be a matter of days before they can lock down the upcoming WinPE based on the same binaries.. however havent gotten any information on when this can become a reality! Any1 knows time of release or if WinPE follows the same release schema as for the base binaries of the SP. Regards the sausage eater...

Dunno but u can try to see if there is something under the local policies where it would run scripts during comp startup.. dunno if this is limited to corp installations where xp / 2000 interacts with a DC but check it out.. perhaps.. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\MSConfig\startupfolder] then again, dont think this is present during initial installation of the Win32 os. keep truckin..

First get the Installshield runtime in place on the WinPE.. never done it either.. but I guess this would be the logical way to go about the issue. Installshield wont work unless the runtime is in place. then again, might need to file monitor an installation using installshield to see what it is trying to access in the Win32 OS (of course that goes for registry also) so if it need to register dynamic anything to the OS structure. then u prolly need go to a kind of write media... good luck to ya...

I guess the easiest way would be if u have ur OPK kit, then just open up the winpe.chm file and read which version u r running... if u havent modified the WinPE image.. a green field (blizz) = winpe 1.2 if u have the moon and mountain stuff... winpe 1.5 or new beta 2005 winpe i guess.. dont have file versions infront of me...

I would say... "u shouldnt remove it" instead of "u cant remove it" yes, IE is a pain in tha a** when it comes to security fixes and so on.. removing it and all associated components and I can ensure that lots of intgrated security / features that are shared between win32 and the IE components wont work anymore... as MS has carefully integrated IE components into Win32 so that u for the specific purpose shouldnt remove it (otherwise it wont work correctly = as in all features) but the again.. go ahead and see if it works. Would be intressting to see tha results as feedback to the community if any issues arises. regards

I have had a similar problem... if i didnt include the driver for the monitor, the popup dialog box showed on where to point out the correct driver for the installation. However, i then noticed that if i ignored the display dialog, after a coupple of minutes (1-2 min) it continued of itself. hopes this turns out the same way for u... or just include the correct driver for the monitor in the OEMDriversPath entry under ur $OEM$ folder structure. cheers-.