At first, it may seem that something like the following should work in a batch script to automate the integration of all patches that support the "/integrate" switch, but running it reveals problems:
FOR %%f IN (*.exe) DO "%%f" /passive /integrate:%~dp0Source
When the simple FOR loop to run all patches with the "/integrate" switch is run, update patches may run simultaneously. I have noticed that the batch file running the update patches continues to run the update patches while other update patche(s) (previously run) are still running. Patches start extracting or running while other patches are being extracted or running.
Most update patches (but not all) seem to integrate correctly while other updates patches are running. When this happens, integration may fail.
How can the integration of many update patches into a Windows 2000/XP/Server 2003 installation source be copletely automated when the update patches support the "/integrate" switch?
EDIT: I run all my integration tasks on Windows 2000 Professional with Service Pack 4
This post has been edited by Ascii2: 29 January 2010 - 01:35 PM