We decided the best way is to place as many install and configuration files on a samba share on a Unix server (tardis). We created a share nfs: /usr/tardis/winpack-a smb: \\winpack\pack

1. Copy the WinXP-Professional CD-ROM to a file system.
   
2. Download the SP2 from Microsoft SP2 page and unpack the service pack with the option -x
   
3. Apply the sp2 to the original cd-source. [sp2 path]\update\update.exe -n -s:[cd source copy]

   Apply the sp2 for windows xp with

    [sp2 path]\update\update.exe /n /integrate:[cd source copy]
   

   

1. Create a new separate NTFS Partition. This partition must have a separate drive letter. It is not possible to mount this partition in a directory on C:.

    ex: format d: /FS:NTFS /V:RIS_HOME /Q
   

   
2. To create a RIS Image you have to use the program risetup this asks you for the source path for the WinXP and create the image. My answers:

    D:\RemoteInstall
    x Respond to client computers requesting service
    x Do not respond to unknown client computer
    \\winpack\pack\src-cd\wxp-sp2\i386
   

   

1. Download all the hotfixes after sp2 from windows catalog from the windows update page. Create .bat file for installing hotfixes with special parameter for integrating in RIS for example:

   hotfixQ123456.exe /o /n /integrate:D:\RemoteInstall\Setup\English\ 
   \Images\winxp-sp2
   

   Since there can be about 70 hotfixes the fastest way is to create .bat file from bash:

   for i in*.exe
   do
   echo $i /o /n /integrate:fullpath
   echo pause
   done >> patch.bat
   

   That's how you will have a batch file with all hotfixes in a minutte. I did copy my patch.bat file and directory hotfixes with all executables in D:\RemoteInstall\Setup\English\Images\. Before you start patching make a copy of the directory i386 just in case. Now start patch.bat file from the directory hotfixes and your image will be patched. Check patch.bat file for details: I did use PAUSE after each hotfix and also remove PASSIVE option, so that it is possible to see if instalation of some hotfix failed.

2. 

   It is the same procedure with one exception, before you can apply the image you must change the file:

    [...]/w2ssel_en/i386/txtsetup.sif
    (http://support.microsoft.com/support/kb/articles/Q214/7/94.ASP )
    change: ProductType = 1   to  ProductType = 0
   

   Now you can apply the image with risetup. When this is finished you have to change the file txtsetup.sif again. D:\RemoteInstall\Setup\English\Images\win2000.srv\i386\txtsetup.sif ProductType = 0 to ProductType = 1

   Microsoft has finaly released a patch witch makes it possible to add a W2k Server with out this changes.

    http://support.microsoft.com/default.aspx?scid=kb;en-us;Q308508
   

   

   To obtain an answer file easily you can use the GUI tool setupmgr. After this you have to customize the sif file for the fine tuning. ex: rembosg.sif

    ;SetupMgrTag
    [Data]
    AutoPartition=1
    MsDosInitiated="1"
    UnattendedInstall="Yes"
    floppyless="1"
    OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%"
    OriTyp="4"
    LocalSourceOnCD=1
   

    [SetupData]
    OsLoadOptions="/noguiboot /fastdetect"
    SetupSourceDevice="\Device\LanmanRedirector (no newline)
                       \%SERVERNAME%\RemInst\%INSTALLPATH%"
   

    [Unattended]
    UnattendMode=FullUnattended
    OemSkipEula=Yes
    OemPreinstall=yes
    TargetPath=\WINNT
    FileSystem=LeaveAlone
    ExtendOemPartition=0
    NtUpgrade=No
    OverwriteOemFilesOnUpgrade=No
    DriverSigningPolicy=Ignore
    OemPnPDriversPath="Drivers\Video\Matrox\G4XX;
                       Drivers\Audio;Driver\Chip\VIA"
   

    [GuiUnattended]
    AdminPassword=[sorry]
    OEMSkipRegional=1
    TimeZone=%TIMEZONE%
    OemSkipWelcome=1
    AutoLogon=YES
    AutoLogonCount=1
   

    [UserData]
    FullName="%USERFULLNAME%"
    OrgName="%ORGNAME%"
    ComputerName=%MACHINENAME%
   

    [Display]
    BitsPerPel=24
    Xresolution=1024
    YResolution=768
    Vrefresh=72
   

    [TapiLocation]
    CountryCode=41
    Dialing=Tone
    AreaCode=01
    LongDistanceAccess="0"
   

    [RegionalSettings]
    LanguageGroup=1
    SystemLocale=00000409
    UserLocale=00000807
    InputLocale=0409:00000409
   

    [SetupMgr]
    DistFolder=C:\win2000dist
    DistShare=win2000dist
   

    [GuiRunOnce]
    Command0="%SYSTEMDRIVE%\w2k-isg-addon\install.bat"
    Command1="%SystemRoot%\Shutdown.exe /L /R /T:2 /y /C"
   

    [Identification]
    JoinDomain=%MACHINEDOMAIN%
    DoOldStyleDomainJoin=Yes
   

    [Networking]
    InstallDefaultComponents=Yes
   

    [NetProtocols]
    MS_TCPIP=params.TCPIP
   

    [params.TCPIP]
    DNSSuffixSearchOrder=hades,ee.ethz.ch,ethz.ch
   

    [NetServices]
    MS_Server = params.MS_Server
   

    [params.MS_SERVER]
    Optimization = Balance
   

    [RemoteInstall]
    Repartition=Yes
   

    [OSChooser]
    Description="(US Keyboard - Swiss Settings) Win-pro-SP2 - ISG"
    Help="W2k SP2 with us keyboard and swiss german settings."
    LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
    ImageType=Flat
   

   You can place a directory of additional drivers and files in the ris image. Create the directories

   D:\RemoteInstall\Setup\English\Images\win2000.pro\$oem$\$1\Drivers
   

   and place there e.g. a directory Video. Then you can place the parameter

    OemPnPDriversPath=''Drivers\Video''
   

   in the answerfile and the video drivers will be installed as well.

   Our scripting is mostly based on perl so we want to have it available on every system. We placed in the same $oem$\$1\w2k-isg-addon directory a system of batchfiles that get executed during the RIS installation. You can start the installation with the parameter [GuiRunOnce] Command0=''%SYSTEMDRIVE%\w2k-isg-addon\install.bat''.

   This batchfile looks like:

   %SystemDrive% CD \w2k-isg-addon

    REM create %SystemDrive%\unconfig, so that bootmgr doesn't start too early
    ECHO "X" >%SystemDrive%\unconfig
    ECHO "X" >%SystemDrive%\reboot
   

    CALL perl\install.bat
    CALL cdromtor\install.bat
    CALL multlang\install.bat
    CALL shutdown\install.bat
   

    CD \ 
    MKDIR Temp
    RMDIR /S /Q w2k-isg-addon
   

   with this batch file other batch files get started. We install a perl msi from Activestate, set the cdrom drive letter to R cdromtor.pl and install the multi language pack from Microsoft.

   This GuiRunOnce thing gets executed with administrator logged in and if something fails the client remains with administrator logged in at the end of the installation. To be sure that this does not happen we execute a shutdown binary from the resource kit. Command1=''%SystemRoot%\Shutdown.exe /L /R /T:2 /y % /C''

   

   I didn't get why this GUI is so well hidden

   1. Go to (START -> Programs -> Administrative Tools -> Active Directory Users and Computers)
      
   2. Click on Domain Controllers - now there should be a computer on the right side of the window. Click on this computer with the right mouse button and select Properties.
      
   3. Click on the tab Remote Install -> Advanced Settings -> Images. I never found a straight way to these GUI.
      
   4. Click on Add and go to the prepared .sif file. It is possible to add many different sif files.
      
   5. You can all ways change your sif file without clicking anything. Just change the file under

       D:\RemoteInstall\Setup\English\Images\win2000.pro\ 
       i386\templates\file.sif.
      

      This file is accessible from all w2k clients in our domain so you should change the permission to that only the administrator can read the file otherwise everyone can look at the local administrator password.

      
   6. There is a possibility to get to the ADD-Image Wizard easier. Got to START -> Run and enter: risetup -add
      
   7. I got the information, that it is possible to just add new sif file to the template directories and it will be visible right away when on the pxe client list.