Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am wondering, what is the best way to automatically update a new installation of Windows (Windows 7)?

When I manually update a new install of Windows 7 SP1, I get about 45 updates. Installing those is not the problem, but after installing those, up come new updates. One installs them and then again: new updates and so on. All together it takes a long time - and you have to come back every few minutes to check for new updates and install them.

So, how is that done in business / how to automate this? Is WSUS a good way for this or does it only cache updates locally?

Using WSUS, is it possible to force immediate install of updates, reboot and install more updates automatically?

WSUS wouldn't help me, if updates are only installed when the system is shutdown, because then it again would require user interaction (shutting down the system, wait for reboot, shutdown again...).

Thanks for any hint!

share|improve this question

9 Answers 9

If you are starting from a bare metal install, you can slipstream updates into your installer disc so it already has updates in it (this depends on how many installs you're doing to make it worth it).

WSUS will not reboot your computer for you. It only keeps track of your updates and will act as a repo for updates so that rather than updating 300+ meg of updates from your Internet connection, they'll come from the local network. It can also control which systems get updates (I want to update IE for all the computers in HR, but restrict it from Marketing...) and give you reports on what updates your systems in the network have. The update mechanism sucks in terms of giving feedback of what is happening, but that's a shortcoming of Windows Updates. It also won't prevent the constant "You're updated! No, wait, you're not..." reboot cycles. Through group policy, you can have the system update with Windows Updates automatically on a scheduled basis just like regular Windows can be set to do individually if you don't mind becoming fully updated over a few days and leaving it on overnight to regularly check for updates and reboot.

Another method is to use the Windows Deployment Services (if you have, say, a lab of systems to update.) You take one of the systems, fully update and configure it, then sysprep it and upload that to the WDS server. Then netboot the subsequent systems and install the full image, fully updated. You have a lot of time invested in the first system but save time when you have 30 systems to install straight from the WDS server. Even if you don't create and auto-deployment script to finish the post-sysprep state you'll save a lot of time not having to do service packs, MS Office, custom installed software, etc. plus you can re-deploy the image when a system gets screwed up.

Otherwise you will have to do the updates repeatedly by hand, which as you've found, takes quite a bit of time. But at least you know that it was done without issues or errors.

share|improve this answer
    
thanks for your reply! if one uses the slipstreaming way, where to get all required updates? I know tools like WSUS Offline update [it's not from Microsoft], but I am wondering, if there is an official way? –  stefan.at.wpf Oct 12 '11 at 11:10
1  
This is probably as official as you'll get for Win7 support.microsoft.com/kb/913086 –  Bart Silverstrim Oct 12 '11 at 12:26
    
@stefan.at.wpf When I package updates with my thin image using DISM I just install a reference computer, check for windows updates and write down the KB number. You can find that on the Microsoft support site easily and download the MSU files for the update. Lather, rinse, repeat. –  MDMarra Oct 12 '11 at 14:55

I can highly recommend WSUS Offline Update. You can use it to create an USB stick or DVD which you can use afterwards to automatically install all critical updates for every currently supported Windows or Office version.

It will automatically restart and continue the update process, so you just need time but can let it work unattended.

share|improve this answer
    
This is amazing! –  GeenHenk Apr 25 at 10:47

Businesses do two things:

  • First, have internal WSUS which makes updates faster.
  • Second, they DO NOT INSTALL A FRESH WINDOWS.

They have an image with core drivers etc. that they maintain and regularly update. For example, we have a machine with Windows and the drivers that just updates and is not used, and every 3-6 months we use it as the base for a new image. Plus after every service pack.

A new machine gets the image and all updates since then. Not that many.

share|improve this answer
2  
Not all businesses do things the same way, for all kinds of reasons. –  John Gardeniers Oct 12 '11 at 10:55
    
Businesses of a certain size that own their employees' computers should really go trough a system image. –  ZJR Oct 12 '11 at 15:35

One of the problems you face is that it is not possible to install all the updates in one go because some are dependant on others and they may not be applied until the machine has rebooted. This is why you have to go through the update, reboot, update, reboot, etc. Using WSUS makes no difference as it's merely a distribution point for the updates and doesn't directly affect how those updates are applied, other then whether or not they are approved.

There are settings for Windows Update to install and reboot if necessary, although in my opinion it's ill advised as it's known to be troublesome. Have a look at either GPO or local policies for the relevant settings.

share|improve this answer

I am using with great success the free version of WuInstall alongside with a GPO assigned startup script.

One way (there are others) to fast update a fresh windows install from WSUS

  1. Pre-create new machine accounts on AD and a group to contain those new machines and a GPO assigned to that group.
  2. "Specify Intranet Microsoft update service location" on that GPO.
  3. Create a new group in WSUS to contain the new machines (named staging, perhaps?).

Approving needed updates

  1. Start by approving latest Service Pack for that group.
  2. Add one of the new machines to domain using the account name create on step 1.
  3. After reboot, open Windows Update and search for new updates. Select the Service Pack approved on step 1 for installation.
  4. After installation, search for new updates again, but do not install yet.
  5. Now, you shall have the list of needed updates for that machine on WSUS. Start by approving and installing all needed not superseded updates. Later approve superseded ones, if needed.

At this point you shall have all needed updates for new machines approved.

Its time to automatize installation and reboot.

  1. Download wuinstall.exe to a network location accessible to new machines.
  2. Assign this startup script using GPO create on step 1.

    set path_to_wuinstall=\\server\path\wuinstall.exe
    set path_to_log=\\server\path\WU-%computername%.txt        
    
    %path_to_wuinstall /install >> %path_to_log%
    
    if %errorlevel% EQU 10 goto reboot
    if %errorlevel% EQU 2 goto done
    
    goto end
    
    :reboot
    shutdown -r
    goto end
    
    :done
    echo Updating completed. >> %path_to_log%
    
    :end
    
  3. Add more machines to domain as in step 7.

  4. As said in Brazil: Agora é só correr pro abraço. (Something like "seat back and relax watching machines being updated").
share|improve this answer

I figured out in the latest version of WuInstall is another way to update windows without user interaction and extra scripting. for example:

wuInstall /install /reboot_if_needed /rebootcycle 3

this command installs all available updates from microsoft update server or a configured wsus until a reboot is necessary. then wuinstall restarts the system without user interaction. At start up it executes again and searches for more updates to install and restarts again. If needed... this can be limited to a maximum number of reboots (in this example 3) to prevent getting into a infinite reboot loop.

share|improve this answer
2  
We normally do not prefer 3rd party components like Wuoffline...WUinstall since they all are not officially supported and the method they use to update is not open source. Anything we can apply out of the box which is officially supported is very preferred. –  user138518 Sep 26 '12 at 12:04

To my knowledge there has to be a level of user interaction.. you can set the computer to automatically install updates but it will still prompt you to restart the computer. I dont believe wsus has the power to remotely reboot for you.

I'd be interested to know if anyone does have a solution to this, could save me a lot of time!

share|improve this answer
3  
With Group Policy, you can configure Automatic Updates to trigger a restart (if required) without user interaction after a timeout period. See this TechNet blog for some relevant information. –  jscott Oct 12 '11 at 12:22
    
excellent, thanks for that. I'll have a look in to it –  Tommy Whitmore Oct 14 '11 at 11:01

WSUS can't force updates, but you can use Group Policy to do some of this:

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

You could probably find the associated Registry entries, too and just do it manually as required. Or, set it on the local machine policy.

share|improve this answer

I realise I'm a bit late but there were a couple of unlisted cases here. Setting up a WSUS group with all updates with a past deadline and a GPO set up for automatic installs and updates works very well.

There are also auto update scripts for use with MDT / WDS which eliminate the need for slipstream or imaging (at the cost of deploying each update to an imaged system). This is the route my company uses. It avoids the time requirements of maintaining images at the cost of an extra 30 to 45 minutes per deployment.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.