un4given1

yeah... just place a file in your $OEM$ directory called cmdlines.txt Create a directory in the $OEM$ directory called SP1 place the SP1 file in there Place this inside the cmdlines.txt file You can add anything you would like here, just make sure to use "" around it. You can not double quote items so if you have an item that has to already be launched with quotes in it then you will need to create a batch file to launch that and call the batch file.

no. install XP using the base image, but add SP1 to the cmdlines.txt file so that it installs during GUI mode setup. Add the hotfix script to the GuiRunOnce in the SIF file to launch upon first login. You should have the PC autologin once so that this completes. You should also add a script to restart the PC after the files are installed. Make sense? Qchain is a must when installing multiple hotfixes. It compares files versions/dates and keeps the system from using an old file when a new one was installed.

oops... forgot to mention you need to place qchain.exe in the HOTFIXES dir.

I will actually take a second to explain the method I use for hotfixes. Everyone has their own methods. There are a lot of people here who like to slipstream them into the images they create for CDs, but since you use RIS you have the ability to add files and not have to reburn a CD. This method may work well for you. Here's what I do. In the $OEM$ directory under $1 I created a directory called HOTFIXES In $OEM$\$1 i created a file called hotfixes.cmd here's the contents of the file. @echo off TITLE Hotfix Installation Script - by Donald Freeman echo Collecting list of current hotfixes... echo @echo off>>c:\RIShotfixinst.bat echo echo Please wait while current hotfixes are being installed. This may take awhile!!!>>c:\RIShotfixinst.bat dir c:\hotfixes\ie\1 /b>>c:\hotfixes\ie1.txt dir c:\hotfixes\win\1 /b>>c:\hotfixes\win1.txt dir c:\hotfixes\win\2 /b>>c:\hotfixes\win2.txt for /f %%h IN (c:\hotfixes\ie1.txt) Do @echo c:\hotfixes\ie\1\%%h /q /r:n>>c:\RIShotfixinst.bat for /f %%i IN (c:\hotfixes\win1.txt) Do @echo c:\hotfixes\win\1\%%i -u -n -z>>c:\RIShotfixinst.bat for /f %%j IN (c:\hotfixes\win2.txt) Do @echo c:\hotfixes\win\2\%%j /q /r:n>>c:\RIShotfixinst.bat ECHO c:\hotfixes\win\custom.bat>>c:\RIShotfixinst.bat echo c:\hotfixes\qchain.exe>>c:\RIShotfixinst.bat echo echo - Completed>>c:\RIShotfixinst.bat echo - Completed echo. CALL c:\RIShotfixinst.bat del /s /q c:\RIS*.bat del /s /q c:\hotfixes.bat :end under the $OEM$\$1\HOTFIXES directory I created a couple directories $OEM$\$1\HOTFIXES\WIN\1 $OEM$\$1\HOTFIXES\WIN\2 $OEM$\$1\HOTFIXES\IE\1 There are two different types of windows hotfixes and 1 type of IE hotfixes. IE\1 uses /q /r:n WIN\1 uses -u -n -z WIN\2 uses /q /r:n All you have to do at this point is drop the needed hotfixes into the directories and every time you build a PC you will get all of the hotfixes. When you need to add a hotfix just drop it into the correct directory. There you go! You need only add the launch for the CMD file in your GuiRunOnce Keep in mind that you can not install SP1 and all of the hotfixes at the same time. You will have to reboot after installing SP1. That is why you should install it from cmdlines.txt Let me know what you think!

You could also try pushing SP1 using cmdlines.txt and then use the GuiRunOnce to run a batch script for all of your hotfixes.

one of your DNS addresses needs to be the DNS of the server. Make sure you are not running roaming profiles.

I have had the same problem. I have not found a workaround for it unfortunately. I will be upgrading to Windows Server 2003 in about a week and I hope that this addresses the issue. I have a method I use that I would be more than willing to share with you if you are interested. Just to clarify, you get this error after text mode setup restarts the computer, right? It's a stop error BSOD?

it was actually created for OEM system builders. It gives them the ability to install the OS without having to activate it. The user activates it or they OEM system builder can, but this way they are able to use one disk/image to install all PCs.

GreenMachine: I do the same. All Windows files (hotfixes, updates...) I do them from cmdlines.txt. I do software installations from the GuiRunOnce. In my environment I have only found one program that requires HKCU setup, but this is only on about 10 PCs out of 500. I do not get much time to play around with some of the things that I would like to try because does not wish to give me the time to do so. Yet, they want me to make sure everything is up to date on our RIS server without giving me alocated time. (Hence the reason for my "self discovery" hotfix script I have detailed in a few posts here) I do have a setup at home but it's hard finding time to play around and take care of my 16 month old daughter. I am about 50% done with the documentation I will be using to create a HOW TO webpage on RIS. I will make sure the link is available to all here when I am done.

want to bet the webcast gets nailed? It's sick, but I bet thousands will want to watch it.

yoru posted image is dead...

OK... so what OS are you trying to install?

Acrobat Reader uses ISS files. They really aren't needed anymore. You can accomplish an unattended install by editing the abcpy.ini file and launching the setup.exe file. Office 2k will require you to create an administrative installation point. Launch the setup of office using a /a switch. You can not create an admin point using an OEM version. (You can, but there is a lot you have to do, and it's not legal) I am not sure of the switches used by WinRAR. I am sure that you can search the forum and someone else has posted them. Good Luck. If you have any other questions, ask away.

Welcome tosk... I haven't been here long but it's definately one of the more informative forums on the net. I think you will enjoy it!

It's not very good "netiquette" to post things such as this.

There is no such variable as "OemSigningPolicy" DriverSigningPolicy is correct. Keep in mind that some video drivers will not install using this technique. You may need to find an INF version of your drivers for this to work. If you are unable to install your drivers using Device Manager instead of the "setup.exe" file included then it will probably not work for you.

This also needs to be changed.... AutoUpdate=pff I think you "fat fingered" that one.

Leon2003 - Unless you are using a corporate version (unlikely) then you will have to activate it. There is a way to make your disk think it's a different disk, but I believe that that might break the policies of this forum to discuss it.

Sorry if this is in the wrong thread, but I could not find one more fitting... Here's what's going on. I have an office administrative installtion point for Office XP Professional that has SP2 slipstreamed into it. I want to launch a command from the client PC that will update it's self using the admin install point. I have done this with 2000 but I can NOT find the information on how to do it with Office XP. Ok, I need to throw this into the mix too... The problem isn't that I can not find the information, it's that the information I find assumes that you want to reinstall all components. The "featurelist" is what I can not find. This is the command I have used for Office 2000: msiexec /i \\server\Office\2000\pro\data1.msi REINSTALL=ACCESSFiles,ACCESSNonBootFiles,AccessWizards,ClipGalleryFiles,DeveloperWizards,EXCELFiles, EXCELNonBootFiles,ExcelAddInEuroToolFiles,ExcelAddinATPFiles,ExcelAddinSolverFiles,ExcelHelpFiles,GR APHFiles,GrammarFiles,MSVisualDesignTool,OfficeWebComponents,PPTFiles,PPTNonBootFiles,ProductFiles,P roductNonBootFiles,QueryFiles,SpellingFiles,SpellingFiles_ESN,TCWord6ExportFiles,ThesaurusFiles,WORD Files,WORDNonBootFiles,WebDiscussFiles,WebPublFiles REINSTALLMODE=vomu /qb The one for XP should be similar but before doing it I want to verify that the featurelist is correct. The only difference from the "ALL" featurelist and what I need is that I would not like outlook to be installed on these PCs. The MST file on the admin point does not install this by default. Outlook is locked out in AD from being used, but it's important that it is also not on the PCs. If someone can possibly point me to a detailed featurelist I would apprecitate it. I have searched MSKB and not been able to find it. Edit: edited to remove company specific server information (oops!)

it is not installed by default, but it is available on the CD. Look for Veritas WinInstall LE.

I guess I do not understand the "facination" of running Windows Server 2k3 as a workstation. I run it at home myself (eval edition), but as a fully functional server. I use it to emulate a "real" domain so that I can play around with it and try things that I wouldn't dare at work. I also use it to play around with RIS, AD and run my own local webserver. I can understand if you want to learn about it, but who in their right mind would spend $800+ on an OS to have on their home PC? I also understand the need for some people to deconstruct things, but this seems stupid to me.

Here's a utility that allows you to load windows from a CD. This would probably better suit your needs. Bart's PE Builder http://www.nu2.nu/pebuilder/

There is one that is included with Windows 2000 (not so sure if it's included with XP too) Veritas WinInstall LE. There is WISE, AdminStudio, SMS installer, and a lot more. Just an FYI... these programs are NOT cheap.

It is still refered to as "BATCH SCRIPTING" thus .bat is not technically incorrect. Files with .cmd are concidered "Windows NT Command Scripts" and basically do the same thing. Granted Windows XP sees them as "MS-DOS batch scripts" it does not make them obsolete. You can name them .cmd all day long but they will still be refered to as batch scripts.

Greenmachine: great guide! And, yes it was kinda obvious, but then again I was the one who was involved