Jump to content

Recommended Posts

Posted

Does a program or method exist that will integrate a batch of update patches into a Windows 2000/XP/Server 2003 installation source using a Microsoft supported method (which I believe is using /integrate switch or adding to DOSNET.INF and SVCPACK.INF)?

I am not looking for a tool that will make any other modification to Windows setup.

From what I understand about nLite, nLite modifies Windows setup and replaces the files in the update patches directly. If this is not what it does, please let me know.


Posted

There's two msft supported methods for integrating updates into an install-source(i.e. there's msft docs available about those methods), and that's to either use the /integrate switch, or to use svcpack.inf to get all the update-installers to install at T-13.

The /integrate switch method dosen't seems to be what you're after, since that method will also directly replace outdated binaries in the install-source with the new updated ones(besides integrating all the installers and running them at T-13).

If you still wants to do this, then the easiest way is to simply just make a batchfile, like e.g.

for %%g in (*.exe) do "%%g" /q /integrate:D:\XPCD

For the svcpack.inf method, then again, the easiest method is to just do it yourself, and the MSFN 'Unattended Guide' shows you how this is done(and also the previous method)...

Posted (edited)

I had posted a long reply to this thread (took me about 30 minutes), but Internet Explorer stopped responding on click of the "Add Reply" button.

Edited by Ascii2
Posted (edited)
Was either of our posts helpful to you?
Yes.

I have also known about HFSLIP. It has, however, been unclear if HFSLIP can be forced to only use Microsoft supported methods of integration.

If the Windows installation source binaries are updated when the /integrate switch is used, that may be acceptable.

A method of integration for the update packages that do not support the /integrate switch is described in KB828930 ( http://support.microsoft.com/kb/828930/ ) starting "Earlier versions of Update.exe". The method is not the SVCPACK.INF described on unattended.msfn.org. The method seems too time consuming to manually repeat many times. I was looking for a tool that would support this method of integration without doing something different.

Edited by Ascii2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...