Br4tt3

What kind of drivers? What version of PE? Both NIC and masstorage drivers / hba's can be incorporated within PE easily. Check the winpe.chm or do some googling on txtsetup.sif for those two types of drivers. Also, build PE from a Win2003 SP1 source (WinPE 2005) if possible as it has the most PnP detection of these devices in comparsion with the prior versions.

thx mats. dunno if the swedish doc would have solved my alzheimers though..

k... been trying like 20 times.. never got it right! the 21 first time.. working! as for the request to have a guide for this, all I can say is that: READ the documentation! not just think u have read it... its all in the winpe.chm file: (stupid me) seems to have dyslexia & alzheimers light edition. cu later, of to the testing...

Hi pepz. I have been in this forum and seen numerous entries on PXE booting WinPE 2005 (built from Win2003 SP1) into RAM from that RIS box. However, none of them seems to do the trick for me so my question is: 1. Is there anyone that has a nice guide on how to place a winpe.iso on the RIS box? 2. What entries that are relevant to the .iso boot in regards to the .sif file? I know that this would be somewhat of the "over and over" subject.. but what do u do when things dont work out for ya? I guess lots of folks would like to know how this works.. The functionality works great running it from a CD / DVD, but not RIS.. when reading the MS documentation on how to place WinPE on RIS isnt exactly clear, as there seems to be several ways to do it according to diffrent webbies. Soz for bringing this 1 up again... Best Regards ThaSausageEater..

Greetings techie from .se!

Hi U should really have a look @ the BDD (Business Desktop Deployment) concept from Microsoft. Within this concept there is a way of installing XP and migrating user data using SMS / USMT called ZTI (Zero Touch Installation). USMT migration of user data is not be run during the WinPE phase (according to me) but during Win32 full mode as USMT often migrates user data based on who is logged on as the script is running (HKCU). USMT (2.6) reads %UserName% and other variables that is not present within the WinPE environment. When u create a SMS OSD package to distribute, u can assign certain properties (called programs within SMS, on those propeties, u can specify to assign USMT to be run prior to the actual installation of the OSD package, and also post to the installation. That would be: 1. SMS detects to install the XP package onto the machine 2. Prior to actual installation, USMT is run and migrates the data 3. XP is installed through SMS OSD 4. Post to the installation, the package will migrate back the data to the client 5. U r all happy and get a increased christmas bonus.. Anyway, more to read within the BDD documentation which is free of charge from M$. U could pick the pieces that suits u and leave the rest... Best Regards ThaSausageEater...

boot, F8, failsafe mode (or whatever it is called), change... there is also a reg haXx for disabling SFC. For the reg haXx i am sure it is in here @ msfn.org forums, try the "Customizing Windows" subforum... best regards ThaSausageEater

lo.. I have the exact same controllers (both 4e/Di / 4e/Si & /4e/DC) on my Dell's. Just like Chris is into.. a matter of TXTSETUP entries and it works.

lo there krusty tha clown.. mkimg.cmd would rebuild ur image directory (where u store ur image folders & files) prior to the building of an .iso file. I would recommed u to do the following: 1. Rebuild the PE image using mkimg.cmd with tha options u want 2. Rebuild the optional components into a seperate dir 3. Merge the files and folders of the two above mentioned steps, replacing already existing files.. YES! 4. Add any of ur own custom settings / scripts / customizations... 5. Build an .iso of ur WinPE build and check it in a Virtual Machine... Simply put, do the work from scratch.. Best Regards Tha Sausage Eater

Thanks guys! I will go with the IcemanND solution. Tried it and it did the work... again, thx! Best Regards ThaSausageEater..

lo pepz.. I am prolly of the chart on this one, but it is annoying! What I want to do is to the delete everything below a certain directory (for example c:\temp). However, I dont wanna delete the temp dir, just all folders and files below it... If I check the /? for del / erase and rmdir it doesnt really solve it (if I am not mistaken). rmdir /S comes closest but it will also delete the c:\temp which I wanna keep in this cfg. So, can anyone please prove me wrong? Also, I dont wanna right big messy .vbs enumerations and recursively delete all files or folders with diffrent commands. Best Regards ThaSausageEater...

Lo pepz I am running RIS with the usage of a Linux based DHCP function in my net. The formost important DHCP cfg for RIS (in order to work) is that is authorized beneath the Site & Services MMC snapin (Site & Services, select the root object, from the view menu choose the "Show the services node", choose services down in the list, then NetServices, within that list u should find the IP of the RIS box.) If not, then ur RIS machine is not registered, authorized in DHCP correctly by Active Directory. Dunno really how this adds up with / between Active Directory Site & Services and an external DHCP solution, but that is just the way it is.. Best Regards ThaSausageEater...

I have never used WPI but from I get of it, it should defintly be possible to implement. With RIS, u get for example the same time / point of executions as from an ordinary unattend install (GuiRunOnce) where u could launch the app from. I guess it is just a matter of configuration (some cfg file) to point out where to obtain the .exe / .msi files to install.. Best Regards Tha Sausage Eater

First of all there is a "file" that will "cut down" the size of the PE image included with the scripts released from MS (think it is something like SERVERSP1-REMOVELIST.TXT or XPSP2-REMOVELIST.TXT), found in the SAMPLE directory. However, the SMS OSD Kit custom WinPE is NOT a ordinary WinPE (I think) as it is in a WIM format and so on (the shell is also changed). I would imagine that u would have to use the update WinPE option within the OSD section to have this new feature "sucked" into SMS. I would try to build the minimized WinPE from the BDD interface firstly as u could intergrate the "minimizing" feature when pressing the "build iso" within the BDD interface. These are just pure speculations as I never have stumbled onto the issue so please dont take my word on it. Best of luck to u and keep us posted (if that solves it for u or how u solved it).. Tha Sausage Eater.

U build WinPE from scratch using scripts delivered from MS, add the optional components u want to have included, WSH / ADO / WMI / HTA. Once u have that done, when u boot WinPE, u will end up with a cmd console (startnet.cmd) where u can launch, .vbs or bacth scripts from (like u wanna) to customize the drives / msg and so on. Everything can be wrppaed in a cute hta and so on.. for more info, check out the WInPE forum subsection within MSFN.. Best of luck to u

I dont have the exact value to edit to but I do know that Microsoft released a vbs script that will do the trick within BDD 2.5 (Business Desktop Deployment), which is a solution accelerator free of charge, which can be obtained from the MS website. Maby some hardcore reg dude (there is alot of them in here.. ) know the value for ya... Best Regards Tha Sausage Eater!

I agree with RogueSpear... I even had a server where I could detect the cd drive unite correctly, a firmware later and the whole thing was a problem again.

Sure, this can be done. However, u gonna need a runtime to perform that. Either DOS or WinPE would ez do that for u, can burn a bootable CD/DVD with DOS as the boot media and so on.. of course WinPE is alot nicer. If u dont have access to MS PE, try out BartPE which also solve this issue. best regards from tha sausage eater!

Check! download newer version of the subinacl.exe util and then leave out the <computername>\myusername string of the command and it will default to the local machine.

lo pepz I have tcp/ip port connected/installed network printer on my file servers. However, by default the built in group "Print Operators" is not populated in the ACL of a newly installed printer. To get around the issue I wanna do a script that will enum all tha printers and for each and every one of them add the "Print Operators" group to the ACL. Fair enough... googled and found that subinacl.exe will do this for ya (even if there seems to be issues with spaces and length in the names). My problem is.. even if the subinacl.exe accepts the command I enter, nothing happens and the .exe wont update the ACL of the printer. So, do anyone have an example where they have used this .exe for performing the same thing? Best Regards Tha Sausage Eater

lo again dude... According to me the 112 line is the "HELP" text entry... try enclose the string in "" as in: Help="This will install Windows XP Professional on VL420" and see if it makes a diffrence, mine is atleast enclosed within my .sif. Good lyck to ya..

Hi Check the <drive:>\RemoteInstall\tmp directory for a file corresponding to the name in the error msg. RIS is using this dir for the temporary installations. Also, u prolly have configured the RIS box to base the naming convension of the machines based on their mac addresses. U can verify this from dsa.msc / properties on your RIS machine / Remote Install tab / Advanced settings button and then the customize button... that would display which temp naming convention RIS is using upon install... Hope it helps

U already provided the answer... $OEM$. U can still have as many raid drivers u want as long as u dont exceed the 2000 charchters limit of the OEMPnPDriverPath entry. But to answer ur question, no I dont know how to do that.. GL

Have u checked that the correct driver is installed once the Win32 setup is done, is working and is in place? Can you manually change the video resolution once the installation is done to the desired res?

"During the installation it appears a message for the video resolution... can I skip that?" -> I am not sure which dialog box that is? Exactly what does it say? Sometimes, when the Win32 installation detects an Plug n' Play monitor, it will dispaly a dialog box to point out the correct drivers for the screen @ T-34 minutes into the installation. If u ignore this box it will dissapear by itself. Or provide a driver that is correct to the $OEM$folder structure. As I said I am not sure weather it is that error u r getting? Also, if there is a bad software driver (that doesnt match) u sometimes get a dialog box which instructs u to confirm if u want to keep the current graphic settings, however, that normally comes after the [GuiRunOnce] section. have u made the video setting in ur .sif / txt file? e.g [Display] BitsPerPel = 16 XResolution = 1024 YResolution = 768 VRefresh = 75 Gimme something more (error msg or stribg in dialog box)... boered, nothing to do! *** CU DUDE ***