Temporary use of a WSUS

[jamesbird]

We build a few new PCs a month, these machines are usally going out to individuals/ small organisations. I'd like to set up a WSUS server to save time downloading updates from the web. What I'd like is a pair of batch files that I load to the newly built PC, run the 1st which hacks the registry to point updates at my WSUS, then before I ship the machine, run the 2nd which 'unhacks' the PC back to it's 'I'll get updates from the web'.
Anyone seen such a thing?

 

[goombawaho]

http://msmvps.com/blogs/athif/articles/Manually_Configure_WUA.aspx

You need to understand all the options though before you turn it loose.

http://technet.microsoft.com/en-us/library/cc708449(WS.10).aspx

 

[Glenn9999]

Or another thought is that you could maintain a collection of downloaded updates and then set your batch file to install them in sequence. Probably a lot easier than what you are proposing. You can use Microsoft Update Catalog (

http://catalog.update.microsoft.com)

to obtain the updates.

I'm waiting for the white paper entitled "Finding Employment in the Era of Occupational Irrelevancy

 

[goombawaho]

It wouldn't be any easier at all using a batch file if he already has a WSUS server up and running and waiting for clients to connect. If he had to SET UP the WSUS server and downloads just for this, I might agree.

If it's set up, leverage your previous work. It will work like a charm, but you'll have to allow for reboots in those options (automatic reboots probably best for your situation) and set the options that you want.

If it was normal users, I'd say don't do automatic reboots that the user couldn't override.

 

[BadBigBen]

Take a look at:

WSUS Offline Update

http://www.wsusoffline.net/

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[goombawaho]

Why do offline if he has a server already online?

 

[Glenn9999]

Why do offline if he has a server already online?

Maybe because the OP said "I'd like to set up a WSUS server to save time downloading updates from the web.". Since the OP says that he would "like" to set up the server as opposed to some other word, that would mean that he does not have a server already online...

So the other "offline" options have been mentioned.

I'm waiting for the white paper entitled "Finding Employment in the Era of Occupational Irrelevancy

 

[jamesbird]

Thnaks guys, I'm happy to set up a WSUS, once it's set up it'll make my life easier. I think I'll spend so much time maintaining an offline store, I'm happy to invest the time in setting up the WSUS initially. I'll take a look at the script pointers goombawaho sent over the weekend.
Thanks for all your ideas.
James

 

[goombawaho]

Wow - I had totally read the original post as being that he HAD a WSUS server. Looks like that's NOT the case, so now I change my opinion. Don't set on up just for that purpose!!!

Haste makes waste.

 

[jamesbird]

Why not? looks like just a wizard to follow, I've plenty of space on my production server. Am I missing a trick?

 

[goombawaho]

Go for it if you want to. You actually SHOULD have one for internal computers vs. having them go out to the internet for their updates. Plus you can DECIDE which updates they get. This is important (in theory) so that you can test updates BEFORE you release them to all the computers.

Every once in a while, a MS update will screw up something that you need to have working. So, NOT just rolling updates out because Microsoft releases them is a good idea.

 

[Glenn9999]

For setting up computers, it really doesn't help to go too much out of the way. Like was mentioned, the Microsoft Update Catalog site is good for obtaining updates.

Then if you want to check if you've missed anything, just have a computer in-house set on automatic update to "advise but not install" so you can have an idea of what new is required. Of course, test first before you roll anything out.

The batch option that's been mentioned is definitely the easiest for update sake after install (*), especially for the situation of occasional system building as you describe. Throw them on a CD along with a batch file and you can just run the updates. There are options on "making" this batch file as well, if it gets too annoying. Then you can let Windows Update pick up the slack later if you happened to miss something on the disk.

(*) If your Windows install source is stable enough (Microsoft licenses the install key, not the source itself), you can always slipstream updates into the original source. That way you can do the install and have the updates automatically incorporated in. Again, test out of the gate to make sure you know what you have and can be confident on them before they go out the door.



I'm waiting for the white paper entitled "Finding Employment in the Era of Occupational Irrelevancy

 

[goombawaho]

Personally, I've never seen a windows update on my personal or client computers at work which actually screwed something up. So, the ocurrence is relatively rare, given all the windows patches that are out there.

But............... having said that, you would be smart to test before installing. But a lot of people don't have that kind of time or don't care enough so they just approve any updates that are available from Microsoft as they become available on the WSUS server.

I'd wait a week or so and see if you hear of any complications before approving new updates, thus you wouldn't have to test them yourself and let other guinea pigs test for you.