Bilou_Gateux

I've have found an alternative to hexedit some bootsector. I've have restored from network the original OS image shipped on a recovery CD by the manufacturer. Image was made with Ghost and i've used GhosCast Server from Symantec Ghost solution Suite to restore gho image stored on network shared CD to my local notebook HDD. Partition restored is FAT32. Now, i can boot the partition 3. Next step, on partition 3 i have swapped XP files (ntdetect.com ntldr) with 2003 Server SP1 files.

How to integrate software updates into your Windows installation source files if you follow instructions (especially do not skip 9.) it will works.

Getting the Hotfixes, Method 4, HFNetChk The Microsoft Baseline Security Analyzer (MBSA) also scans and reports common security-related misconfigurations and can help you install missing security updates for Windows-based computers. +--------------------------------------------------------------+ Integrate and slipstream Security Updates above: download all HFs: Windows Update Catalog HF Integrate Phase 1 batch: HF1.cmd requires hiveupd.cmd to output hivesft.txt and hivecls.txt extract HFs and integrate files into source HF Slipstream Phase 2 batch: HFINT.cmd compress updated binaries into source using Microsoft autogenerated i386\svcpack\HFINT.DAT (not done) Phase 3 batch used to merge hivesft.txt and hivecls.txt: all registry additions are being handled within hivesft.inf and hivecls.inf: Insert text into existing .inf with gsar and sed. Do various edit to TXTSETUP.SIF and DOSNET.INF +--------------------------------------------------------------+ Windows Update Agent 2.0 Install Method 1: SVCPACK.INF Install Method 2: slipstreaming into source EDIT: integrated in HFSLIP. This method is only for educational purpose. I have written a small batch wuagnt20.cmd which download required files and slipstream into source. Edit the file, search ::Initialize variables section, set variable CDROOT = correct_path, set variable DOWNLOADER = correct_path_to_exe, save as without .txt extension How can I create a Windows Server 2003 bootable CD-ROM that has Service Pack 1 (SP1) slipstreamed into it?

hi mod's, i would like to remove an old attachment to a post: XPC Test, post #30 to save some space for future use on My Controls. the attached file can be deleted because it doesn't contains valuable infos and will not make the whole topic not understandable. Unfortunately, topic has been closed a long time ago by GreenMachine XPCreate. Please could a mod remove the attachment for me. Thanks.

@Jaclaz Here the report: Partition 3 (which i can't boot with Bootpart added bootsector in boot.ini) NTFS boot sector jump value = EB5B90 Partition 0 (which boot with Bootpart added C:\xpe.bin bootsector in boot.ini) NTFS boot sector jump value = EB5290 What's strange is that i have started a new 2003 SP1 install on this Partition 3 drive letter E: from my current running Win2003Server (WINNT32.EXE /syspart:E: blahblahblah_others_switches_here) in order to get a bootable partition. Unfortunately, when reboot done, my active partition becomes this Partition 3 and isn't bootable (blinking cursor). Question: can i change the Jump value of partition 3 to EB5290 without backing first all data (is this change destructive?) @cdob Is there a tool to do the same from within WinPE. My laptop has no internal or external CD Drive and can't boot from USB Key. I can only boot from Network (PXE) or from a PCMCIA 5Gb hard drive which i don't have (too expensive) to do some manipulation on the MBR, I PXEboot a SDI WinPE in RAM for example to switch back Partition 2 to active with MBRTool. I haven't got a PXEBootable from LAN image of recovery console Thanks for your help to both, i will becomes a MBR / bootsector expert

Updating of this page will be discontinued from now on. I am really sorry for that but this is a necessary step, for a number of reasons, including serious time constraints as I am engaged in a number of professional activities & projects. Getting the Hotfixes, Method 3, Windows Update Catalog How to download updates and drivers from the Windows Update Catalog excluded from selection not available through Windows Update Catalog Some updates have been superseeded but not removed from download. ie, you will find in the log file many 'Cumulative Security Update for Internet Explorer'. Keep only the most recent. Summary: required tools: SetEnv Lilles Lasteprogram A/S v2.0 NirCmd v1.85 copy SetEnv.exe LileDL.exe and NirCmd.exe to %SystemRoot%\System32 folder. save "Windows_Update.log" file in %SystemRoot% folder. Copy HFSlip dir path to clipboard (from the 'full path in the address bar' in explorer) Click the Start button, and then click Run. In the Run dialog box, in the Open box, paste the command below, and then click OK. Click the Start button, and then click Run. In the Run dialog box, in the Open box, paste the command below, and then click OK. Click the Start button, and then click Run. In the Run dialog box, in the Open box, paste the command below, and then click OK. Security Releases on Windows Update Quick Details: December 12th, 2006 new November 20th, 2006 +3 new, +1 new for MSXML4, +1 new for MSXML6 October 10th, 2006 +5 new, +1 new for NDP20 September 27th, 2006 +1 Critical OutofCycle Security Bulletin released September 12th, 2006 +1 new, +2 re-released August 8th, 2006 +8 new July 11th, 2006 +3 new, +1 re-released, +1 new for NDP20 June 13th, 2006 +7 new May 9th, 2006 +0 new April 11th, 2006 +5 new March 14th, 2006 +0 new February 14th, 2006 +3 new, +1 new for WindowsMedia January 5th and January 10th, 2006 +2 new November 2005 MS05-053: Vulnerabilities in Graphics Rendering Engine Could Allow Code Execution (896424) Update: When Windows Automatic Updates tries to download updates on a Windows Server 2003-based or Windows XP-based computer, an access violation error may occur (910437) October 2005 MS05-045: Vulnerability in Network Connection Manager Could Allow Denial of Service (905414) MS05-046: Vulnerability in the Client Service for NetWare Could Allow Remote Code Execution (899589) MS05-048: Vulnerability in the Microsoft Collaboration Data Objects Could Allow Remote Code Execution (907245) Note: 907245 MS05-048 = WindowsServer2003-KB901017-x86-ENU.exe adding more confusion... MS05-049: Vulnerabilities in Windows Shell Could Allow Remote Code Execution (900725) MS05-050: Vulnerability in DirectShow Could Allow Remote Code Execution (904706) MS05-051: Vulnerabilities in MSDTC and COM+ Could Allow Remote Code Execution (902400) MS05-052: Cumulative security update for Internet Explorer (896688) This update replaces previous Cumulative security update for IE 896727 and includes 903235 September 2005 Non-Affected Software August 2005 MS05-039: Vulnerability in Plug and Play could allow remote code execution and elevation of privilege (899588) MS05-040: Vulnerability in Telephony service could allow remote code execution (893756) MS05-041: Vulnerability in Remote Desktop Protocol could allow denial of service (899591) MS05-042: Vulnerabilities in Kerberos could allow denial of service, information disclosure, and spoofing (899587) July 2005 MS05-036: Vulnerability in Microsoft Color Management Module could allow remote code execution (901214) MS05-037: Vulnerability in JView Profiler could allow remote code execution (903235) superceeded by 896727 June 2005 MS05-026: A vulnerability in HTML Help could allow remote code execution (896358) MS05-027: Vulnerability in Server Message Block could allow remote code (896422) MS05-032: Vulnerability in Microsoft agent could allow spoofing (890046) MS05-033: Vulnerability in Telnet client could allow information (896428) May 2005 An update for Windows Installer 3.1 is available for Windows Server 2003 SP1 (898715) April 2005 Windows Server 2003 Service Pack 1 (SP1) (889101) +--------------------------------------------------------------------------------------------------------------------------+ Recommended Updates These updates are not critical to your computer's security or performance but they can improve how some features, programs, or devices work. Microsoft Base Smart Card Crypto Provider Package: x86 (KB909520) - (Posted Date: November 18, 2005) Base Smart Card Cryptographic Service Provider (Base CSP) allows smart card vendors to more easily enable their smart cards on Windows with a lightweight proprietary card module instead of a full proprietary CSP. Microsoft .NET Framework 2.0: x86 (KB829019) - (Posted Date: November 04, 2005) The .NET Framework version 2.0 improves scalability and performance with improved caching, application deployment and updating with ClickOnce, and support for the broadest array of browsers and devices with ASP.NET 2.0 controls and services. Update for Windows Server 2003 (KB904942) - (Posted Date: May 19, 2006) Install this update to resolve HTTP authentication issues in Windows-based systems that do not appear until Microsoft Internet Explorer 7 is installed. Update for Windows Server 2003 (KB912945) - (Posted Date: February 26, 2006) This update includes minor changes to how Internet Explorer handles some web pages that use Microsoft ActiveX controls. Certain webpages will require users to manually activate Active X controls by clicking on it or using the TAB key and ENTER key. This update contains all previously released security updates. +--------------------------------------------------------------------------------------------------------------------------+ Windows Update Agent 2.0 build: 5.8.0.2469 WUA API required for accessing Microsoft Windows Update V6 +--------------------------------------------------------------------------------------------------------------------------+ Security updates are available on ISO-9660 CD image files from the Microsoft Download Center

Installing Windows Server 2003 on HP ProLiant Servers with RIS: HP ProLiant Servers uses specific NICs (based on Broadcom chipsets) and MassStorage (Adaptec, LSI and COMPAQ/HP Smart Array controllers) A good start is to download (free) the latest SmartStart CD ISO image containing all drivers for newest HP ProLiant Servers: SmartStart Current: HP SmartStart CD version 7.40 (9 Sep 05) WARNING 1: HP NC10xx/67xx/77xx/150x/320x/324x/325x/326x Gigabit Ethernet NIC Driver for Windows Server 2003 Drivers located on <HP SmartStart CD>\compaq\drivers\wnet\q57xp32 file that are to be placed in the RemoteInstall\Setup\Language\Images\WIN51IA.SP1\$OEM$\$1\drivers\net folder: q57win32.cat q57win32.inf q57xp32.sys file that are to be placed in the RemoteInstall\Setup\Language\Images\WIN51IA.SP1\I386 folder q57xp32.sys q57win32.inf <<<edited edit RemoteInstall\Setup\Language\Images\WIN51IA.SP1\I386\templates\ristndrd.sif file [Unattended] DriverSigningPolicy = Ignore NtUpgrade = No Win9xUpgrade = No OemPnPDriversPath = drivers\net;drivers\pnpdrvs OemPreinstall = Yes OemSkipEula = Yes OverwriteOemFilesOnUpgrade = No DisableVirtualOemDevices = yes LegacyNIC = 1 WARNING 2: HP Storage Controllers Driver for Windows Server 2003 txtsetup.oem single file located on <HP SmartStart CD>\compaq\install\wnet *.* files for each controller listed in txtsetup.oem located on <HP SmartStart CD>\compaq\drivers\wnet\<controller> excluding txtsetup.oem file located on some <controller> subfolder and excluding NICs subfolders bxvbdx n100 n1000 q57xp32 file that is to be placed in the RemoteInstall\Setup\Language\Images\WIN51IA.SP1\$OEM$\textmode folder edit RemoteInstall\Setup\Language\Images\WIN51IA.SP1\I386\templates\ristndrd.sif file [OEMBootFiles] ADPU160M.SYS CPQARRY2.SYS CPQCISSM.SYS MegaIDE.sys Symmpi.sys LsiCsb6.sys HPCISSs2.sys TXTSETUP.OEM [OEM_Ads] Logo=Compaq.bmp [MassStorageDrivers] "Adaptec Ultra160 Family Manager Set"=OEM "Compaq Smart Array Controllers"=OEM "Smart Array 5x and 6x Controllers"=OEM "Integrated Ultra ATA-100 IDE RAID Controller (Windows 2000)"=OEM "LSI Logic Ultra320 1020/1030 Driver (Windows Server 2003)"=OEM "Carte h“te SCSI LSI Logic C8100 PCI"=RETAIL "Carte h“te SCSI LSI Logic C896 PCI"=RETAIL "Carte h“te SCSI LSI Logic C8xx PCI"=RETAIL "CD-ROM IDE (ATAPI 1.2)/Contr“leur IDE PCI"=RETAIL "CSB-6 Ultra ATA-100 IDE RAID Controller (Windows Server 2003)"=OEM "Smart Array SAS/SATA Controllers"=OEM "Adaptec RAID Controller"=OEM others OEM Drivers: HP ProLiant iLO Advanced and Enhanced System Management Controller Driver for Windows 2000/Server 2003 Drivers located on <HP SmartStart CD>\compaq\csp\nt\cp005397.exe SFX to extract HP ProLiant Integrated Lights-Out Management Interface Driver for Windows 2000/Server 2003 Drivers located on <HP SmartStart CD>\compaq\csp\nt\cp005410.exe SFX to extract Intel 6300ESB Chipset Support for Windows 2000/Windows Server 2003 Drivers located on <HP SmartStart CD>\compaq\csp\nt\cp004823.exe SFX to extract file that are to be placed in the RemoteInstall\Setup\Language\Images\WIN51IA.SP1\$OEM$\$1\drivers\pnpdrvs folder

Post the $WINNT$.INF file found in %SystemRoot%\System32 of your above running config in order to check the dospath value. Don't forget to replace ProductKey with xxxxx.

I will try again. Using bootpart /list: Physical number of disk 0 : 73f973f9 0 : C: type=7 (HPFS/NTFS), size= 514048 KB, Lba Pos=63 1 : C: type=45 , size= 8032 KB, Lba Pos=1028160 2 : C:* type=7 (HPFS/NTFS), size= 7984305 KB, Lba Pos=1044225 3 : C: type=7 (HPFS/NTFS), size= 20788110 KB, Lba Pos=17012835 Applying command: BOOTPART 0 LBA C:\xpe.bin "Windows XP Embedded", i'm able to boot partition 0 from active partition 2. Applying command: BOOTPART 3 LBA C:\bootpe.bin "WinPE Recovery"; i get the blinking cursor as mentionned in my previous post. it look like there is an issue with my partition 3. I have to make some backup of data content and delete and recreate it to check again. i hope the issue is not related to Server 2003 with SP1 used as source to build my WinPE. What OS source were you using?

boot.ini: [boot loader] timeout=7 default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Windows Server 2003, Web" /noexecute=optout /fastdetect c:\peboot.bin="RAMDisk WinPE" c:\xpe.bin="Windows XP Embedded" c:\bootpe.bin="WinPE Recovery" Partition information from MBRFixGUI 2.1 # Boot Size (MB) Type 1 502 7 NTFS or HPFS 2 7 69 Boot-US boot manager / Priam / Enhanced Write Filter 3 Yes 7797 7 NTFS or HPFS 4 20300 7 NTFS or HPFS From the active partition, SystemBootDevice multi(0)disk(0)partition(3) i can boot: "Windows Server 2003, Web" on partition(3) "RAMDisk WinPE" SDI Image on partition(3)\Recovery "Windows XP E" on partition(1) with xpe.bin bootsector created with bootpart util the fourth option: "WinPE Recovery" SDI Image on partition(4)\Recovery don't works. i've got only the header from bootpart util and a blinking cursor On the fourth partition (where i try to add my WinPE image built with 2K3SP1 binaries as source) i have the following files:

I have checked the MBSA 2.0 install with regshot tool (before and after install and made a compare). It's not so bloated. it don't add binary files in other folder than it's own install folder and add a few registry keys: You can update the registry by running these two commands: REGSVR32.EXE /s "C:\Program Files\Microsoft Baseline Security Analyzer 2\serversecure.dll" REGSVR32.EXE /s "C:\Program Files\Microsoft Baseline Security Analyzer 2\xmldb.dll" Important note: Microsoft Baseline Security Analyzer (MBSA) 2.0 is built on the Windows Update Agent and Microsoft Update infrastructure. If Windows Update Agent 2.0 isn't installed first (or already slipstreamed into OS source install with HFSlip), MBSA will fail to scan your computer. My main goal is to install it without using MSI installer because i hate msi packages which add a lot of bloat in registry and in %windir%\Installer folder

Actually the au3 script don't parse any file searching for some path. It only runs two commands, the first is WatchDriverSigningPolicy.exe which stays in memory, then launch SetupCopyOEMInf.exe which scan the specified folder and add all infs to Windows inf folder and when job is finished, WatchDriverSigningPolicy is removed from memory (like using taskill to kill the process). The path to use is first searched from WINNT.SIF with the Detached command which parse $WINNT$.INF to find dospath value. What value want you to get from prodspec.ini? You may ask confirmation to hp38guser but his method works with all flavour of modern OS (Win2K, WinXP and Win2003). SetupCopyOEMInf If all drivers are digitally signed (have a .cat file), we can avoid using WatchDriverSigningPolicy.exe. I have already launched an install without it (all my drivers are digitally signed) and having no issues.

Sample to add IIS later on a W2K Server (although it will not work for you if you have removed IE because i can't imagine IIS will works without IE ) IIS.txt [Components] iis_common=on iis_dbg=off iis_doc=off ii_ftp=on iis_htmla=on iis_inetmgr=on iis_nntp=off iis_nntp_docs=off iis_smtp=on iis_smtp_docs=on iis_www=on [InternetServer] PathFTPRoot=D:\Inetpub\ftproot PathWWWRoot=D:\Inetpub\Wwwroot command to launch from command line (no GUI tool because you have removed IE) sysocmgr.exe /i:%windir%/inf/sysoc.inf /u:c:\i386\$oem$\iis.txt

Unattended Installation of Windows Components

[quote name='Incroyable HULK' post='401140' date='Oct 8 2005, 01:02 PM']Thanks Bilou but this doesn't solve the problem completly... altought I don't get the second error anymore[/quote] Would you like to try this method described [url="http://www.msfn.org/board/index.php?s=&showtopic=25515&view=findpost&p=176587"]here[/url] It will skip the possible issue with your multiboot CD which doesn't use standard \I386 path for source. If you don't plan to add multiple MassStorage drivers to your multibootcd, it takes less than 2 mn to do the dosnet.inf and txtsetup.sif editing and add the compressed binary file to the source. for the [SCSI] section of TXTSETUP.SIF, use a single generic string for description: [code]iaStor = "Intel RAID/AHCI SATA storage controller"[/code]

Thanks for crediting me. But according to the first post by a06lp: Nethertheless, i highly recommend using autoit method by hp38guser because you don't need to use the special setup.exe by Pyron and presetup.cmd. AutoIT method don't need to swap original MSFT files with special ones.

Thanks for your input. I will change my bootpart command replacing 1 (primary partition booting Windows 2003 Server with the number of my partition where i will store my WinPE SDI image. but actually, this second primary partition is just used for storing my swap file. If the partition is formated with NTFS, i should be able to extract the boot sector.

You will get better answer concerning BartPE in www.911cd.net/forums Using the search function, here your answer: BitComet-plugin, ...working like a charm! Credits to the author cool400

[quote name='Incroyable HULK' post='400713' date='Oct 7 2005, 12:33 PM'][b]winnt.sif[/b] [quote][MassStorageDrivers] "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL" "Intel® 82801FR SATA RAID Controller (Desktop ICH6R)" = "OEM" "Intel® 82801FR SATA AHCI Controller (Desktop ICH6R)" = "OEM" "Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M)" = "OEM" "Intel® 82801ER SATA RAID Controller (Desktop ICH5R)" = "OEM" "Intel® 6300ESB SATA RAID Controller" = "OEM" [OEMBootFiles] txtsetup.oem iaahci.inf iaahci.cat iastor.cat iastor.inf iastor.sys[/quote] Keep in mind I have a multiboot CD and the path to the source file is: \SYSTEME\XPSP2[color="#FF0000"]FR[/color]... this means my $OEM$ and I386 folders are there and not at the root of the CD Any help? [/quote] As you build an uA CD with French language, you [b]must[/b] use the french string from your txtsetup.sif to add in WINNT.SIF go back to [url="http://www.msfn.org/board/index.php?s=&showtopic=19792&view=findpost&p=137722"]post #7[/url] and you will get the french string (avec l'accent circonflexe)

Thanks for your input, i would like to try it but due to barrier language, i need more details to understand the whole process: Q: Additional partition with X: drive letter: could i format it with NTFS file system? Q: BOOTPART usage: assuming my boot partition, which the files NTLDR, NTDETECT.COM and BOOT.INI reside on is partition(1) with drive letter C: syntax of the bootpart command: BOOTPART 1 C:\PEBOOT.BIN WinPE correct? Q: Changed usage use x:\winnt.sif what should i do to use my WINPE.SDI image described in my previous post? Copy it to X:\ along with WINNT.SIF. I'm not in front of the box with the dual boot (Windows Server 2003 SP1 and WinPE) and will check this method later. All supplemental infos you can give us will help to accomplish this method.

How to check if [Critical] Security Updates have been applied with HFSlip without using http://windowsupdate.microsoft.com 1/ download Microsoft Baseline Security Analyser in your language. 2/ install it on your HFslipstreamed Windows running box. Default install path is "%ProgramFiles%\Microsoft Baseline Security Analyzer 2" 3/ download the latest security updates catalog and save it in "%ProgramFiles%\Microsoft Baseline Security Analyzer 2" folder. 4/ Open command prompt: cmd /k cd /d "%ProgramFiles%\Microsoft Baseline Security Analyzer 2" 5/ run : mbsacli /catalog wsusscan.cab /n password+IIs+OS+SQL /nd you will get a screen output of the currently missing and installed [Critical] Security Updates. To Do: check what are the required files (dll dependency) and registry keys required to run the command line client without first having to install a lot of bloat from MSFT (as usual) Feel free to post suggestions or your own experience with this method

Installing Windows from a flat installation D:\source Running WINNT32.EXE /s:d:\source\i386 /unattend:D:\source\unattend.txt /syspart:c: /makelocalsource and using only digitally signed drivers from OEMs, i have changed my unattended response file UNATTEND.TXT section: %SystemDrive% after reboot (end of txtmode stage of the setup) and before start of the GUI stage of install (T39) $WINNT$.INF %I=C:\$WIN_NT$.~LS %J=C:\$WIN_NT$.~LS\$OEM$ DOS command run at T39=C:\$WIN_NT$.~LS\$OEM$\HidCon.exe C:\$WIN_NT$.~LS\$OEM$\CopyInfs.exe C:\$WIN_NT$.~LS\$OEM$\PnPDrvrs Note: My modified WINNT.SIF command don't work for a CD based installation. dospath value in $WINNT$.INF returns a local HDD path for my install method and returns an install CD path for a CD based installation. My method don't use AutoIT script but all drivers are copied from source $OEM$\PnPDrvrs to %SystemDrive%\$WIN_NT$.~LS\$OEM$ during install

Thanks for this new version. I appreciate the idea not having to hardcoding path (fixed or cdrom disk) like previous scripts. and thanks for idle.newbie, the writer of Snippet for OemPnPDriversPath, setDevicePath clone he has a good knowledge of batch scripts. Unfortunately, it is no longer active on this board.

Download the Windows OEM Installation Kit - NEW posted by DarkShadows

download newer version following instructions here. If you build a new WinPE using Windows 2003 Server with SP1 as source, you will be able to integrate newer Intel® PRO Network Connections Drivers e1000325.inf without any problems.