SPOILER ALERT!
Ways to integrate computer software updates into Windows installation source files.txt
This short article discusses how administrators can integrate Windows software program updates that use Update.exe with their Windows installation source files. (Computer software updates incorporate essential updates, feature packs, patches, security updates, service packs, updates, and cumulative updates.) When the installation is from a Windows distribution folder designed by an administrator, and also the administrator have to apply one or With multiple application updates, these processes could possibly be beneficial. These procedures are also useful if you'd like to integrate security updates to ensure that when a new installation starts it will not be infected by a virus.
Note: In the event the software program update does not use Update.exe because the installer, these procedures are not applicable. For instance, some Microsoft World-wide-web Explorer updates for Microsoft Windows 2000 and Microsoft Windows XP use INF-based installations rather than Update.exe. For that reason, you can't use these processes to integrate these World wide web Explorer updates for Windows 2000 or Windows XP. In case you use these processes to integrate computer software updates, the technique won't generate the Filelist registry crucial correctly. For instance, when you integrate the 824146 security patch in to the Microsoft Windows Server 2003 installation source file, the program is not going to appropriately produce the following registry essential: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\WindowsServer2003\SP1\KB824146\Filelist whenever you use these procedures When any with the updates is integrated, an entry is added for every single update in the 'Add or Remove Programs' manage panel. Having said that, the 'Delete' button will not be readily available due to the fact if the update is deleted, the updated file doesn't have an earlier version to restore. If the following circumstances are also established, the administrator may possibly also need to apply software program updates to the Microsoft Windows Preinstallation Environment (WindowsPE): The administrator uses WindowsPE to run the Windows installer. Administrators use operating systems which have integrated software program updates on network shares. For much more details regarding the certain operation method, click the report quantity below to view the corresponding article within the Microsoft Understanding Base: 828217 The best way to apply the 824146 safety patch to Windows Preinstallation Atmosphere. The directions in this short article can also be utilised for remote installation services (RIS ) The image of RISETUP. The I386 directory structure in the RISETUP image is definitely the same because the network distribution folder. For RIPREP images, please 'pull' the image in to the client, install software updates, and after that place the image back into the server by means of RIPREP. When utilizing these procedures to defend against viruses, we advise that you only integrate software updates that demand no user action. In case your integrated software update does not hinder the completion in the Windows installer, make use of the '[guirunonce]' section in the Unattend.txt file, or make use of the Software Update Service (SUS) to deploy the update following the installation is total. This method is developed for new installations, not for upgrade installations. Note: Only WindowsXPHomeEdition and WindowsXPProfessionalEdition help integrated service pack. Windows Media Center Edition will not support integrated service packs. Back to the leading Extra data The section 'Update.exe five.four.15.0 or later' describes the procedure of integrating software packages that use Update.exe version five.4.15.0 or later. The 'Early Version of Update.exe' section describes the approach of integrating application packages that use earlier versions of Update.exe.
To decide no matter whether the computer software update package makes use of Update.exe version 5.four.15.0 or later as the installer, adhere to these actions: Extract the application update package to a one of a kind temporary folder. For example, to extract the update package file named KBArticleNumber.exe to a folder named ExtractedPackage on drive C, sort the following command in the command prompt: KBArticleNumber/X:C:\ExtractedPackage to open the incorporated computer software update The short-term folder for the unzipped files of your package. By way of example, open C:\ExtractedPackage. Right-click the Update.exe file in this folder, then click Properties. Around the Version tab, verify the value of File Version. When the version number is five.4.15.0 or greater, the new capabilities pointed out within this short article are supported. Update.exe will figure out no matter if the update is appropriate for the installation supply. As an example, the patch integrated in Windows 2000 Service Pack 4 (SP4) will not be integrated into the Windows 2000 installation source that has integrated SP4. Update.exe will also ascertain whether or not the installation supply is available for the appropriate hardware platform. The /integrate switch cannot be applied for decompressed packages.
When you don't choose to integrate the software program update of Update.exe version 5.four.15.0, please don't perform actions 6 to 13. If you would like to integrate computer software updates with a version reduce than Update.exe five.four.15.0, execute measures 6 to 13 to integrate these updates. Back to the top Update.exe five.four.15.0 or later To integrate computer software updates that use Update.exe five.four.15.0 or later in to the Windows installation supply file, adhere to these methods: insert a drive Map for the network share on which the distribution folder should be to be developed. Or, log on towards the computer system exactly where you want to create the distribution folder. The following actions assume that you simply develop a distribution folder on drive X. Develop a distribution folder. For example, to make a distribution folder named Winflat on drive X, type the following command at the command prompt: mkdirX:\Winflat\ Set permissions on the Winflat distribution folder in order that the administrator has only “full control” 'Permissions, all other users have only 'read' and 'execute' permissions. Insert the Windows item CD in to the CD drive, and after that copy the contents in the CD towards the Winflat distribution folder developed in step two. To accomplish this, type the following command in the command prompt: xcopy/E/I/VD:X:\Winflat\ To integrate application updates that use Update.exe version five.4.15.0 or later because the installer, visit At the command prompt, sort the following for each and every update to be integrated: KBArticleNumber/integrate:path Note: For path, specify the path for the distribution folder. By way of example, to integrate the KB123456.exe file within the distribution folder situated at X:\Winflat, sort: KB123456/integrate:x:\winflat Back to the leading from the earlier version of Update.exe To work with the earlier version of Update. The computer software update of your exe is integrated into the Windows installation supply file, follow these actions: map a drive to the network share where the distribution folder will be to be developed, or log in for the laptop where the distribution folder is always to be created. The following actions assume that you build a distribution folder on drive X. Create a distribution folder. For video data recovery , to create a distribution folder named Winflat on drive X, sort the following command at the command prompt: mkdirX:\Winflat\ Set permissions on the Winflat distribution folder to ensure that the administrator has only “full control” 'Permissions, all other users have only 'read' and 'execute' permissions. Insert the Windows solution CD in to the CD drive, and after that copy the contents of the CD to the Winflat distribution folder produced in step two. To accomplish this, type the following command at the command prompt: xcopy/E/I/VD:X:\Winflat\Edit X:\Winflat\i386\dosnet.inf and add 'svcpack' to the [OptionalSrcDirs] section. For example: [OptionalSrcDirs]
uniproc
svcpack Note: For WindowsXP or WindowsServer2003 distribution folders, you may must generate a [OptionalSrcDirs] section inside the Dosnet.inf file. The Dosnet.inf file incorporated in Windows 2000 already contains this section. Develop the X:\Winflat\i386\svcpack folder. To do this, form the following command in the command prompt: mkdirX:\Winflat\i386\svcpack Copy the update package to be integrated (ProductName-KBArticleNumber-Option-Language.exe) towards the X:\Winflat\i386\svcpack folder in. To complete this, make use of the 8.3 naming format (KBArticleNumber.exe), where ArticleNumber would be the Microsoft Knowledge Base short article number related together with the update. If you want to apply many updates, copy and rename all update packages. Unzip every update package into a one of a kind temporary folder. One example is, to extract the files of an update package to a folder named ExtractedPackage on drive Y, form the following command in the command prompt: C:\i386\svcpack\KBArticleNumber/X:Y:\ExtractedPackage For each update, copy the catalog file (KBArticleNumber.cat) as well as the updated binary file (one example is, .exe, .dll, or .sys file) from Y:\ExtractedPackage. To do this, follow these methods: For every update, copy KBArticleNumber.cat from Y:\ExtractedPackage towards the X:\Winflat\i386\svcpack folder. Use the same name as the update package (KBArticleNumber.cat) for the .cat file, and don't copy Empty.cat. For each update, if the identical binary file exists in Y:\ExtractedPackage, only the file with the highest version is retained. For each update, you should verify every binary file contained in Y:\ExtractedPackage to decide no matter if the identical file exists in the X:\Winflat\I386 folder. If the file exists inside the I386 folder, delete the file from X:\Winflat\I386.
Note: The last character of your file extension in the I386 folder could possibly be underscore (_). By way of example, Rpcss.dll is named Rpcss.dl_ within the I386 folder. For each update, copy the updated binary file from Y:\ExtractedPackage to X:\Winflat\I386. For each update, check whether or not there is certainly any subfolder with the very same name as the subfolder of X:\Winflat\I386 in Y:\ExtractedPackage. If a folder contains any such subfolders, copy the updated binary files in the Y:\ExtractedPackage subfolder for the corresponding subfolder in X:\Winflat\I386. For example, if Y:\ExtractedPackage includes a folder named Uniproc, copy the files in Y:\ExtractedPackage\Uniproc to X:\Winflat\I386\Uniproc. Note: Since Microsoft offers support for the latest and next-new service packs (N and N-1), Microsoft packages specific updates as dual-mode updates. You could apply these dual-mode updates to computer systems with various service pack levels. For example, the Windows XP update might contain each SP1 and SP2 subdirectories, where the SP1 folder includes the update files for the original version of Windows XP, and also the SP2 folder consists of the update files for Windows XP SP1. Within this instance, if the installation supply could be the original version of Windows XP (version 2600), you must make use of the files in the SP1 directory. In the event the installation supply is WindowsXPSP1, you should make use of the files in the SP2 directory. For additional details about the Windows XP dual-mode update package, click the following article number to view the corresponding report in the Microsoft Understanding Base: 328848 WindowsXP dual-mode update package description Microsoft may perhaps also package the Windows Server 2003 update as dual soon after the release of Service Pack 1 Mode update. The WindowsServer2003 update package also contains two sets of updated binary files inside the nnnQFE and nnnGDR folders, that are applied for the latest and next-new ServicePacks (N and N-1), respectively, where nnn is the most current and next-new ServicePack (N and N-1) ) The original release version, 'SP1', 'SP2', and so on. In this case, it's essential to make use of the files in the corresponding nnnQFE folder. For extra facts concerning the contents on the Windows Server 2003 update package, click the following article number to view the corresponding short article in the Microsoft Know-how Base: 824994 Windows XP Service Pack 2 and Windows Server 2003 software program update package contents indicate that you simply do not have to copy the files within the Widespread or Update folder, One example is, Update.exe, Update*.inf, SPmsg.dll, SPcustom.dll, SPuninst.exe, Update.ver or symbol (.dbg file). For recovery format and every file copied in step 9 (except KBArticleNumber.cat), look inside the X:\Winflat\I386\Dosnet.inf file to ascertain whether the file name is listed within the [Files] section. All files listed inside the [Files] section are preceded by 'd1,'. E.g:
d1,Filename
In the event the file name of any file you copied in step 9 just isn't listed, use this syntax to add an entry. For instance, when the patch consists of Win32k.sys, given that Win32k.sys just isn't listed in Dosnet.inf, d1,win32k.sys really should be added for the [Files] section of X:\Winflat\I386\Dosnet.inf. This addition ensures that the updated version of Win32k.sys is copied throughout the Windows installation procedure. Delete the X:\Winflat\I386\Svcpack.in_ file. Build the Svcpack.inf file within the X:\Winflat\I386 folder. To complete this, depending on no matter if you want to deploy a single update or numerous updates, use the corresponding section within the following. (Replace ArticleNumber using the information base article number of your updated .cat file): Windows2000[Version]
Signature='$WindowsNT$'
MajorVersion=5
MinorVersion=0
BuildNumber=2195
[SetupData]
CatalogSubDir='\i386\svcpack'
[ProductCatalogsToInstall]
KBArticleNumber.cat
[SetupHotfixesToRun]
KBArticleNumber.exe/optionsWindowsXP[Version]
Signature='$WindowsNT$'
MajorVersion=5
MinorVersion=1
BuildNumber=2600
[SetupData]
CatalogSubDir='\i386\svcpack'
[ProductCatalogsToInstall]
KBArticleNumber.cat
[SetupHotfixesToRun]
KBArticleNumber.exe/optionsWindowsServer2003[Version]
Signature='$WindowsNT$'
MajorVersion=5
MinorVersion=2
BuildNumber=3790
[SetupData]
CatalogSubDir='\i386\svcpack'
[ProductCatalogsToInstall]
KBArticleNumber.cat
[SetupHotfixesToRun]
KBArticleNumber.exe/options Note: The advisable selections for installing updates are /Q, /N, and /Z. For more data, click the following post number to view the post in the Microsoft Understanding Base: 262841 Command-line switch for Windows software update package 824687 Command-line switch for Microsoft application update package If you would like to apply various updates , Please add an entry for every single update under each [ProductCatalogsToInstall] and [SetupHotfixesToRun] sections. In an installation where a number of updates are installed, examples of these sections are as follows: [ProductCatalogsToInstall]
KB123456.cat
KB123478.cat
KB123490.cat
[SetupHotfixesToRun]
KB123456.exe/options
KB123478.exe/options
KB123490.exe/options If you would like to install a service pack, you don't have to include the details with the service pack, for the reason that a further procedure will manage the service pack installation. Back to the major Set up updates on a laptop or computer running Windows Server 2003 To install updates on a computer, run the update plan Windows Server 2003-KB######-x86-LLL.exe on that laptop or computer. If you'd like to set up the update on many computer systems, you may make a distribution folder for the update around the network. The following process describes the way to use this system to set up one particular or much more updates. Essential note: SP1 need to be installed in conjunction with updates released just after SP1, or just before installing the update. Installing several recently released updates before installing SP1 may bring about difficulties with the program.
Note: For the following procedure, Drive:\ represents the network drive or pc drive where the distribution folder is situated.
To set up the update by operating the Update.exe program, follow these actions: Connect to the network or computer exactly where you want to build the distribution folder. In the shared network target folder, create a distribution folder for the update files. One example is, to create a distribution folder named Update, form the following: mkdirDrive:\Update Copy the WindowsServer2003Update.exe system to the distribution folder produced in step two. For instance, to copy the SP1Update.exe program to the distribution folder named Update, form the following: xcopyC:\WindowsServer2003-KB######-x86-LLL.exeDrive:\Update in the shared network To install updates within the distribution folder, please run the WindowsServer2003-KB######-x86-LLL.exe system. One example is, to set up the update in the distribution folder named Update, form the following: Drive:\Update\WindowsServer2003-KB######-x86-LLL.exe To make sure that the update requires impact, please set up all updates Following restarting the personal computer. Note: The WindowsServer2003-KB######-x86-LLL.exe file and Update.exe support exactly the same command-line selections.
Note: In the event the software program update does not use Update.exe because the installer, these procedures are not applicable. For instance, some Microsoft World-wide-web Explorer updates for Microsoft Windows 2000 and Microsoft Windows XP use INF-based installations rather than Update.exe. For that reason, you can't use these processes to integrate these World wide web Explorer updates for Windows 2000 or Windows XP. In case you use these processes to integrate computer software updates, the technique won't generate the Filelist registry crucial correctly. For instance, when you integrate the 824146 security patch in to the Microsoft Windows Server 2003 installation source file, the program is not going to appropriately produce the following registry essential: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\WindowsServer2003\SP1\KB824146\Filelist whenever you use these procedures When any with the updates is integrated, an entry is added for every single update in the 'Add or Remove Programs' manage panel. Having said that, the 'Delete' button will not be readily available due to the fact if the update is deleted, the updated file doesn't have an earlier version to restore. If the following circumstances are also established, the administrator may possibly also need to apply software program updates to the Microsoft Windows Preinstallation Environment (WindowsPE): The administrator uses WindowsPE to run the Windows installer. Administrators use operating systems which have integrated software program updates on network shares. For much more details regarding the certain operation method, click the report quantity below to view the corresponding article within the Microsoft Understanding Base: 828217 The best way to apply the 824146 safety patch to Windows Preinstallation Atmosphere. The directions in this short article can also be utilised for remote installation services (RIS ) The image of RISETUP. The I386 directory structure in the RISETUP image is definitely the same because the network distribution folder. For RIPREP images, please 'pull' the image in to the client, install software updates, and after that place the image back into the server by means of RIPREP. When utilizing these procedures to defend against viruses, we advise that you only integrate software updates that demand no user action. In case your integrated software update does not hinder the completion in the Windows installer, make use of the '[guirunonce]' section in the Unattend.txt file, or make use of the Software Update Service (SUS) to deploy the update following the installation is total. This method is developed for new installations, not for upgrade installations. Note: Only WindowsXPHomeEdition and WindowsXPProfessionalEdition help integrated service pack. Windows Media Center Edition will not support integrated service packs. Back to the leading Extra data The section 'Update.exe five.four.15.0 or later' describes the procedure of integrating software packages that use Update.exe version five.4.15.0 or later. The 'Early Version of Update.exe' section describes the approach of integrating application packages that use earlier versions of Update.exe.
To decide no matter whether the computer software update package makes use of Update.exe version 5.four.15.0 or later as the installer, adhere to these actions: Extract the application update package to a one of a kind temporary folder. For example, to extract the update package file named KBArticleNumber.exe to a folder named ExtractedPackage on drive C, sort the following command in the command prompt: KBArticleNumber/X:C:\ExtractedPackage to open the incorporated computer software update The short-term folder for the unzipped files of your package. By way of example, open C:\ExtractedPackage. Right-click the Update.exe file in this folder, then click Properties. Around the Version tab, verify the value of File Version. When the version number is five.4.15.0 or greater, the new capabilities pointed out within this short article are supported. Update.exe will figure out no matter if the update is appropriate for the installation supply. As an example, the patch integrated in Windows 2000 Service Pack 4 (SP4) will not be integrated into the Windows 2000 installation source that has integrated SP4. Update.exe will also ascertain whether or not the installation supply is available for the appropriate hardware platform. The /integrate switch cannot be applied for decompressed packages.
When you don't choose to integrate the software program update of Update.exe version 5.four.15.0, please don't perform actions 6 to 13. If you would like to integrate computer software updates with a version reduce than Update.exe five.four.15.0, execute measures 6 to 13 to integrate these updates. Back to the top Update.exe five.four.15.0 or later To integrate computer software updates that use Update.exe five.four.15.0 or later in to the Windows installation supply file, adhere to these methods: insert a drive Map for the network share on which the distribution folder should be to be developed. Or, log on towards the computer system exactly where you want to create the distribution folder. The following actions assume that you simply develop a distribution folder on drive X. Develop a distribution folder. For example, to make a distribution folder named Winflat on drive X, type the following command at the command prompt: mkdirX:\Winflat\ Set permissions on the Winflat distribution folder in order that the administrator has only “full control” 'Permissions, all other users have only 'read' and 'execute' permissions. Insert the Windows item CD in to the CD drive, and after that copy the contents in the CD towards the Winflat distribution folder developed in step two. To accomplish this, type the following command in the command prompt: xcopy/E/I/VD:X:\Winflat\ To integrate application updates that use Update.exe version five.4.15.0 or later because the installer, visit At the command prompt, sort the following for each and every update to be integrated: KBArticleNumber/integrate:path Note: For path, specify the path for the distribution folder. By way of example, to integrate the KB123456.exe file within the distribution folder situated at X:\Winflat, sort: KB123456/integrate:x:\winflat Back to the leading from the earlier version of Update.exe To work with the earlier version of Update. The computer software update of your exe is integrated into the Windows installation supply file, follow these actions: map a drive to the network share where the distribution folder will be to be developed, or log in for the laptop where the distribution folder is always to be created. The following actions assume that you build a distribution folder on drive X. Create a distribution folder. For video data recovery , to create a distribution folder named Winflat on drive X, sort the following command at the command prompt: mkdirX:\Winflat\ Set permissions on the Winflat distribution folder to ensure that the administrator has only “full control” 'Permissions, all other users have only 'read' and 'execute' permissions. Insert the Windows solution CD in to the CD drive, and after that copy the contents of the CD to the Winflat distribution folder produced in step two. To accomplish this, type the following command at the command prompt: xcopy/E/I/VD:X:\Winflat\Edit X:\Winflat\i386\dosnet.inf and add 'svcpack' to the [OptionalSrcDirs] section. For example: [OptionalSrcDirs]
uniproc
svcpack Note: For WindowsXP or WindowsServer2003 distribution folders, you may must generate a [OptionalSrcDirs] section inside the Dosnet.inf file. The Dosnet.inf file incorporated in Windows 2000 already contains this section. Develop the X:\Winflat\i386\svcpack folder. To do this, form the following command in the command prompt: mkdirX:\Winflat\i386\svcpack Copy the update package to be integrated (ProductName-KBArticleNumber-Option-Language.exe) towards the X:\Winflat\i386\svcpack folder in. To complete this, make use of the 8.3 naming format (KBArticleNumber.exe), where ArticleNumber would be the Microsoft Knowledge Base short article number related together with the update. If you want to apply many updates, copy and rename all update packages. Unzip every update package into a one of a kind temporary folder. One example is, to extract the files of an update package to a folder named ExtractedPackage on drive Y, form the following command in the command prompt: C:\i386\svcpack\KBArticleNumber/X:Y:\ExtractedPackage For each update, copy the catalog file (KBArticleNumber.cat) as well as the updated binary file (one example is, .exe, .dll, or .sys file) from Y:\ExtractedPackage. To do this, follow these methods: For every update, copy KBArticleNumber.cat from Y:\ExtractedPackage towards the X:\Winflat\i386\svcpack folder. Use the same name as the update package (KBArticleNumber.cat) for the .cat file, and don't copy Empty.cat. For each update, if the identical binary file exists in Y:\ExtractedPackage, only the file with the highest version is retained. For each update, you should verify every binary file contained in Y:\ExtractedPackage to decide no matter if the identical file exists in the X:\Winflat\I386 folder. If the file exists inside the I386 folder, delete the file from X:\Winflat\I386.
Note: The last character of your file extension in the I386 folder could possibly be underscore (_). By way of example, Rpcss.dll is named Rpcss.dl_ within the I386 folder. For each update, copy the updated binary file from Y:\ExtractedPackage to X:\Winflat\I386. For each update, check whether or not there is certainly any subfolder with the very same name as the subfolder of X:\Winflat\I386 in Y:\ExtractedPackage. If a folder contains any such subfolders, copy the updated binary files in the Y:\ExtractedPackage subfolder for the corresponding subfolder in X:\Winflat\I386. For example, if Y:\ExtractedPackage includes a folder named Uniproc, copy the files in Y:\ExtractedPackage\Uniproc to X:\Winflat\I386\Uniproc. Note: Since Microsoft offers support for the latest and next-new service packs (N and N-1), Microsoft packages specific updates as dual-mode updates. You could apply these dual-mode updates to computer systems with various service pack levels. For example, the Windows XP update might contain each SP1 and SP2 subdirectories, where the SP1 folder includes the update files for the original version of Windows XP, and also the SP2 folder consists of the update files for Windows XP SP1. Within this instance, if the installation supply could be the original version of Windows XP (version 2600), you must make use of the files in the SP1 directory. In the event the installation supply is WindowsXPSP1, you should make use of the files in the SP2 directory. For additional details about the Windows XP dual-mode update package, click the following article number to view the corresponding report in the Microsoft Understanding Base: 328848 WindowsXP dual-mode update package description Microsoft may perhaps also package the Windows Server 2003 update as dual soon after the release of Service Pack 1 Mode update. The WindowsServer2003 update package also contains two sets of updated binary files inside the nnnQFE and nnnGDR folders, that are applied for the latest and next-new ServicePacks (N and N-1), respectively, where nnn is the most current and next-new ServicePack (N and N-1) ) The original release version, 'SP1', 'SP2', and so on. In this case, it's essential to make use of the files in the corresponding nnnQFE folder. For extra facts concerning the contents on the Windows Server 2003 update package, click the following article number to view the corresponding short article in the Microsoft Know-how Base: 824994 Windows XP Service Pack 2 and Windows Server 2003 software program update package contents indicate that you simply do not have to copy the files within the Widespread or Update folder, One example is, Update.exe, Update*.inf, SPmsg.dll, SPcustom.dll, SPuninst.exe, Update.ver or symbol (.dbg file). For recovery format and every file copied in step 9 (except KBArticleNumber.cat), look inside the X:\Winflat\I386\Dosnet.inf file to ascertain whether the file name is listed within the [Files] section. All files listed inside the [Files] section are preceded by 'd1,'. E.g:
d1,Filename
In the event the file name of any file you copied in step 9 just isn't listed, use this syntax to add an entry. For instance, when the patch consists of Win32k.sys, given that Win32k.sys just isn't listed in Dosnet.inf, d1,win32k.sys really should be added for the [Files] section of X:\Winflat\I386\Dosnet.inf. This addition ensures that the updated version of Win32k.sys is copied throughout the Windows installation procedure. Delete the X:\Winflat\I386\Svcpack.in_ file. Build the Svcpack.inf file within the X:\Winflat\I386 folder. To complete this, depending on no matter if you want to deploy a single update or numerous updates, use the corresponding section within the following. (Replace ArticleNumber using the information base article number of your updated .cat file): Windows2000[Version]
Signature='$WindowsNT$'
MajorVersion=5
MinorVersion=0
BuildNumber=2195
[SetupData]
CatalogSubDir='\i386\svcpack'
[ProductCatalogsToInstall]
KBArticleNumber.cat
[SetupHotfixesToRun]
KBArticleNumber.exe/optionsWindowsXP[Version]
Signature='$WindowsNT$'
MajorVersion=5
MinorVersion=1
BuildNumber=2600
[SetupData]
CatalogSubDir='\i386\svcpack'
[ProductCatalogsToInstall]
KBArticleNumber.cat
[SetupHotfixesToRun]
KBArticleNumber.exe/optionsWindowsServer2003[Version]
Signature='$WindowsNT$'
MajorVersion=5
MinorVersion=2
BuildNumber=3790
[SetupData]
CatalogSubDir='\i386\svcpack'
[ProductCatalogsToInstall]
KBArticleNumber.cat
[SetupHotfixesToRun]
KBArticleNumber.exe/options Note: The advisable selections for installing updates are /Q, /N, and /Z. For more data, click the following post number to view the post in the Microsoft Understanding Base: 262841 Command-line switch for Windows software update package 824687 Command-line switch for Microsoft application update package If you would like to apply various updates , Please add an entry for every single update under each [ProductCatalogsToInstall] and [SetupHotfixesToRun] sections. In an installation where a number of updates are installed, examples of these sections are as follows: [ProductCatalogsToInstall]
KB123456.cat
KB123478.cat
KB123490.cat
[SetupHotfixesToRun]
KB123456.exe/options
KB123478.exe/options
KB123490.exe/options If you would like to install a service pack, you don't have to include the details with the service pack, for the reason that a further procedure will manage the service pack installation. Back to the major Set up updates on a laptop or computer running Windows Server 2003 To install updates on a computer, run the update plan Windows Server 2003-KB######-x86-LLL.exe on that laptop or computer. If you'd like to set up the update on many computer systems, you may make a distribution folder for the update around the network. The following process describes the way to use this system to set up one particular or much more updates. Essential note: SP1 need to be installed in conjunction with updates released just after SP1, or just before installing the update. Installing several recently released updates before installing SP1 may bring about difficulties with the program.
Note: For the following procedure, Drive:\ represents the network drive or pc drive where the distribution folder is situated.
To set up the update by operating the Update.exe program, follow these actions: Connect to the network or computer exactly where you want to build the distribution folder. In the shared network target folder, create a distribution folder for the update files. One example is, to create a distribution folder named Update, form the following: mkdirDrive:\Update Copy the WindowsServer2003Update.exe system to the distribution folder produced in step two. For instance, to copy the SP1Update.exe program to the distribution folder named Update, form the following: xcopyC:\WindowsServer2003-KB######-x86-LLL.exeDrive:\Update in the shared network To install updates within the distribution folder, please run the WindowsServer2003-KB######-x86-LLL.exe system. One example is, to set up the update in the distribution folder named Update, form the following: Drive:\Update\WindowsServer2003-KB######-x86-LLL.exe To make sure that the update requires impact, please set up all updates Following restarting the personal computer. Note: The WindowsServer2003-KB######-x86-LLL.exe file and Update.exe support exactly the same command-line selections.
