Batch-based Windows Update

[Ambassador]

I've been thinking about FDV'd Windows 2000, and how many unimaginative people complain about the lack of Windows Update and how they think they can't install another update.

So to shut these people up, I've been thinking of a simple, batch-based alternative to WU, which uses the Windows port of WGET to download the updates. I could use M$'s RSS security bullentin feeds to get the latest update information.

A question though:

Does HFSLP leave any sort of log that say what hotfixes, etc, it slipstreamed?

[tommyp]

You don't need windows update, MSIE or any browser to see what updates you are missing. See this link. Just grab the two zip files and extract them to a folder and run the CMD file. Works like a champ. The bad part is that you have to manually download the updates. If you keep your HF folder up to snuff, then it's a piece of cake. You can see what updates you have slipstreamed via the hfslip.log file that was created after running hfslip.

[Ambassador]

The bad part is that you have to manually download the updates.

But the post you gave me mentioned WGET:

2) Download wgetwin-1_5_3_1-binary.zip from this site and extract wget.exe into the same folder as above. I realize this is an older version, but this one is smaller, doesn't require additional files and does the job. Use a newer version if you know what you're doing.

And this "CAB file" you mention, is it some sort of summary of all MS updates? And does this utility take into account that some of the updates are imcompatible with FDV'd 2000?

That's why I wanted to make a custom update specifically from FDV'd installs, so it only chooses the updates that work with these types of installs.

You can see what updates you have slipstreamed via the hfslip.log file that was created after running hfslip.

But does this become a part of the slipstreamed image or is it just placed in the HFSLP folder?

Edited October 24, 2008 by Ambassador

[tommyp]

When tomcat's cmd file is run, wget is called to get a cab file from microsoft. The cab file downloaded via the script is the same cab file used for windows update and the microsoft baseline security analyzer. The cab is good for windows OSs (not sure if 95 or 98 or vista because I don't use them). It has info on file names, versions and registry checks. As far as full functionality with FDV's fileset, I recommend testing the waters out to see the results.

By default, the hflsip log file is placed inside the sourcess folder and inside the hfslip working directory.

[Ambassador]

By default, the hflsip log file is placed inside the sourcess folder and inside the hfslip working directory.

Ok, makes sense.

Can you just clear up a few things about HFSLIP for me? I originally though that HFSLIP made a slipstreamed Windows CD like nLite, and didn't actually the setup process and such. However, the HFSLIP website mentioned a HFSLIP command window that pops up during Windows setup. So does HFSLIP make it so when you actually install Windows, HFSLIP-related folders are made as part of the setup process. You mentioned keeping "your HF folder up to snuff"; is that automatically created with a slipstreamed Windows install for example?

[Martin H]

Please first read up on the instructions given on the HFSLIP homepage...

The HF folder is where you place HFSLIP supported updates...

HFSLIP runs some batch/inf-files and makes a temp folder on your systemdrive during the Windows install, since there needs to be added some reg-entries and post-install commands during/after the install, but that's nothing to worry about at all, since it runs flawless and is much more intelligent/effecient than MS's own imbecile update-slipstreaming method, which bloats your disc with the update installers, leaves the updated binaries uncabbed and runs/unpacks each update installer just to be able to add the needed reg-entries and post-install commands...

Edited October 26, 2008 by Martin H

[Ambassador]

The HF folder is where you place HFSLIP supported updates...

Of course I know that.

HFSLIP runs some batch/inf-files and makes a temp folder on your systemdrive during the Windows install, since there needs to be added some reg-entries and post-install commands during/after the install, but that's nothing to worry about at all, since it runs flawless and is much more intelligent/effecient than MS's own imbecile update-slipstreaming method, which bloats your disc with the update installers, leaves the updated binaries uncabbed and runs/unpacks each update installer just to be able to add the needed reg-entries and post-install commands...

Ah, I see. Thanks you for explaining.

So I suppose combining my suggestion with TommyP's already existing solution is the logical course of action.

[Ambassador]

Well, apparently my idea is obsolete:

It used to be that three Windows components were removed as a byproduct of installing with IE.

- Windows Update. Install Microsoft Windows Update Agent 3

Still, if I read this correctly, all this does is restore Automatic Updates (bleeeeeeeh). I'd rather to my updates manually.

Is my assumption correct?