question about office network isntalls

Discussion in 'Update Services' started by John Smith, Jun 7, 2005.

  1. John Smith

    John Smith Guest

    I have been rolling out updates via a network install, (REINSTALL=ALL
    REINSTALLMODE=vomu /qb) now with WSUS the master network copy will be out of
    sync with the clients... how will that work?

    Up till now if a client went to "Add remove programs" to change the office
    install and were not up to date with any patches that I had applied to the
    network install, they would have to first run the above command to sync up,
    and then they could proceed. Now if updates are being added by WSUS, when
    they go to add remove a component how will that react? The network install
    may not even have the patches that have been applied by WSUS, will it be a

    Are there any KBs/White Papers on how office updates effect network

    John Smith, Jun 7, 2005
    1. Advertisements

  2. I was reading about this problem a while back but can't find the doc. Here
    is a blurb from an Office resource on that may shed some

    Applying client updates between service packs

    As an efficient alternative to recaching and reinstalling Office with every
    new release of a critical update or security update, you can distribute
    these interim updates directly to clients, even if they rely on an
    administrative image as a source. You must first have established all users
    on the most recent baseline of Office 2003.

    For example, you may have updated your administrative image to Office 2003
    Service Pack 1 (SP1) and reinstalled Office throughout the organization.
    Shortly thereafter, Microsoft releases a security update in response to a
    new virus. You can download the patch and run the EXE file directly on
    client computers. In this scenario, you would not patch your administrative
    image - that would put clients out of sync with the patched source. You can
    continue with this strategy until the next service pack is released.

    Note that you cannot use the same tactic to deploy service packs themselves.
    The client versions of service packs require a source at the original
    release level - such as an unpatched administrative image or a local
    installation source.

    Source for this article --

    If I run across the other doc I'll re-post here.
    Jeff Centimano [MVP - Windows Server], Jun 7, 2005
    1. Advertisements

  3. So, for those using an AIP, in other words they can go ahead and use WSUS
    without worrying about their AIP itself - until a service pack rolls around.
    In that instance, they would have to update their AIP or image.

    That's helpful - thanks. We don't have an AIP yet, but hope to soon. It's
    ridiculous running around from computer to computer - or worse yet, waiting
    two years to re-image their workstation. Very frustrating and poor practice
    Allen McGuire, Jun 7, 2005
  4. I believe that this will be a fairly common question, and probably deserves
    some documentation around Office install/patching best practices. I don't
    know if anything like that already exists but I'll see if I can either dig
    up some links to existing documentation or ask for new documentation
    regarding this.

    Don Cottam
    Microsoft Corporation
    Windows Server Update Services

    donco AT microsoft DOT com
    (I prefer to communicate through the newsgroup, so please do not email me
    unless necessary...but if necessary, don't hesitate to email me. Thx!)

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Don Cottam [MS], Jun 8, 2005
  5. John Smith

    John Smith Guest

    thanks... I think some good docs are in order...
    John Smith, Jun 8, 2005
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.