JuMz

If I have a licensed copy, Do you guys know of the way to silently install it with the serial and registration information too? Thanks!

It worked perfectly! To the T! Nice work buddy!

ahh I see. I know net use * will auto assign the drive letter...the question is....can I somehow obtain which drive letter it chooses... USB key works! Yes!

Thank you! All I needed to do was change %CDROM% to %Root% and it now works via network and CDROM. Now to test USB... BTW, can PUSHD take username / password for network share?

Has there been any changes in the new WPI on how to run it from a network? i.e. I map a drive letter , say 'Z' to the root of my installation source which contains the WPI folder: (sharename)Z: \WPI \I386 \Applications ...etc My config.js has entries like : "%CDROM%\Applications\appname\appinstaller.exe" I want to make ONE version of WPI that can be ported to either network installs or CD/DVD/USBKEY based installs.... How should I proceed or what should I change.... mapping the drive to the share above does NOT seem to work for me...WPI fails to install...

Wow, thanks. I was looking for something like this! I needed a way to UNATTENDEDLY enable this on my server!

Do you guys happen to know the silent install switches, say if we were not integrating, but deploying out to PC's?

I would like to say that the "new" method indicated in the first post (with lots of red) worked flawlessly for me on a DFI NF4 SLI-DR Motherboard using 2 Raptors on NVRAID 0. Thank you very much!

Do you mind informing us what the required entries would be in the dosnet.inf for his example?

What is a UL File and how is it used (Sorry, I don't know much about Jcarles utilities and have never used them)... EDIT: I think I got it! Thanks!

What is LIP?...

http://www.msfn.org/board/index.php?showto...mp;#entry536321 Founf that to be very useful

Umm...since when isn't RIS supported? I did not know this...

I answered your similar question in another thread. Yes, it is on the XP Pro CD in the CMPNENTS folder. HOWEVER, you need to have netfx=on in your unattend.txt for it to acutally install...it is NOT installed by default.

I see this as being useful. I am also interested in finding out how...

Sure thing...What typically happends is that the R2 setup starts and also asks for your R2 CD IF it is not in the a specific location specified in the registry. What I do is run the R2, then change those specfic keys to point to where my CD actually is. I think the code below will clarify my confusing statements above. EDIT: This is my RunOnceEx.cmd...OEM is a specific folder copied to the "systemdrive" using the $oem$\$1 structure. Essentially, my Cmpnents folder is also copied directly to the C drive and it is not the first place the installer will look (by default, I believe it will look at the drive in which you installed the OS). In my case, since this is a Server OS, I find it wise to keep all sources required for additional components stored directly on the HD so if you have to add things like IIS for example, you don't need to look for the CD, its already on your HD and the OS knows where to look for it via the reg commands below...hope this clears some things up CMDOW @ /HID @ECHO OFF SET TAGFILE=\OEM FOR %%i in (c d e f g h i j k l m n o p q r s t u v w x y z) DO IF EXIST "%%i:%TAGFILE%" set CDDRIVE=%%i: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Configuring Your System" /f REG ADD %KEY%\001 /VE /D "Completing Windows Server 2003 R2 Setup" /f REG ADD %KEY%\001 /V 1 /D "%CDDRIVE%\cmpnents\r2\setup2.exe /q /a" /f REG ADD %KEY%\001 /V 2 /D "cmd /c reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup /v SourcePath /t REG_SZ /d %CDDRIVE% /f" /f REG ADD %KEY%\001 /V 3 /D "cmd /c reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup /v ServicePackSourcePath /t REG_SZ /d %CDDRIVE% /f" /f Edited

Thank you for that. I will give it a whirl (with some variations). Seems that we have helped each other in this situation!

What scripts / interface are you using to do all this? Sounds interesting, right now, my install doesn't have any custom options like this...startnet goes, factory -winpe, then XP installs, based on the same unattend.txt for all my machines...

What do you mean by "machine was unable to operate"? Do you mean not boot or boot but it says missing NTLDR or something like that? If so, check the boot order in your bios and make it to your primary HD and not the controller card

http://www.windowsnetworking.com/articles_...-Drop-Site.html Found this article very useful. Perhaps it could solve your problem...

Answer File = Winbom.ini WinbomType = WinPE The [WinPe] section contains entries for identifying the configuration set and Windows operating system that you install. Unless you run the factory -winpe command, Setup ignores all entries in this section. PageFilePath Specifies the path to the paging file on computers with less than 64 MB of RAM. Syntax PageFilePath = path_to_pagingfile Value path_to_pagingfile Default Value c:\pagefile.sys Example c:\mypagefile.sys WinbomType WinPE Comments The path to the paging file must be fully qualified. Return to top PageFileSize Specifies whether to create a paging file on computers with more than 64 MB of RAM. Syntax PageFileSize = number_ of_megabytes Value number_ of_megabytes Optional. Default Value 0 Example PageFileSize = 360 WinbomType WinPE Comments On computers with 64 MB or less of RAM, the factory -winpe command automatically creates a 64-MB paging file to ensure that the computer does not run out of memory when installing the network or when users run programs that require a larger amount of memory than usual. That's all I can answer for now...

I believe if you look in the R2 disc, there should be a deploy.chm that talks about how to silently install R2. It worked for me...

I know how to enable the pagefile in WinPE 1.6 if your interested...but it seems you are using a hybrid of BartPE / WinPE so I don't know if this would be of much use to you...do you have a winbom.ini that executes? EDIT: I shouldn't say I know "how" but I have all the documentation that indicates the procedures neccessary...

you can use the offiline driver installation utility to add PNP NIC drivers to your winpe...

I have never used the OemRunOnce section before...not sure exactly how...Here is what the helpfile says... It seems you are missing the structure the helpfile seems to say is required...