The 2007 Office System Service Pack 2 coming in April!

Service Pack 2 for the 2007 Office System will be made available to Windows Server Update Services in April, classified as a service pack.
Service Pack 2 includes some significant work, including: built-in ability to save as ODF & PDF formats, improvements to Outlook’s performance and calendar reliability, significant bug fixes for charts in core Office applications, the ability for client service packs to be removed using an uninstall tool, and a host of customer-requested improvements to the Office Server products.

Of course it is also a rollup of all fixes that have previously been released for Office 2007 products.  Additional information will be posted to the Office Sustaining Engineering blog

WSUS 3.0 SP2 Beta Program now available on Microsoft Connect!

I am very pleased to announce that WSUS 3.0 SP2 Beta is available today, January 26 , via the Connect Site . All you have to do is sign in to your Connect account or sign up now in order to participate in the Beta program.

 

WSUS 3.0 SP2 Beta Overview

New Windows Server and Client Version Support

·       Integration with Windows Server® 2008 R2

·       Support for Windows 7® client

·       Support for the BranchCache feature on Windows Server® 2008 R2

WSUS Beta Feature Improvements and Fixes

Auto-Approval Rules

·       New functionality lets you specify the approval deadline date and time.

·       You can now apply a rule to all computers or to specific computer groups.

Update Files and Languages

·       This release provides improved handling of language selection on downstream servers. A new warning dialog appears when you download updates only for specified languages.

Cross-Version Compatibility

·       The user interface is compatible between Service Pack 1 and Service Pack 2 for WSUS 3.0 on both the client and the server.

Software Updates

·       Stability and reliability fixes for the WSUS server, such as support for IPV6 addresses greater than 40 characters.

·       The approval dialog now sorts computer groups alphabetically by group name.

·       Computer status report sorting icons are now functional in x64 environments.

·       Fixed setup issues with database servers running Microsoft® SQL Server® 2008.

 

Download :  Connect Site
Source: http://blogs.technet.com/wsus/archive/2009/01/26/wsus-3-0-sp2-beta-program-now-available-on-microsoft-connect.aspx

Troubleshooting & Deploying WSUS clients

Deploying WSUS clients

Preface:
Installing WSUS is a relative straightforward process, very well documented not only on the Microsoft Technet Library (see ref [1] ). The step that usually causes most confusion and problems is when you try to connect the clients to the server and start deploying updates. This
With this post I intend to clarify this process of detecting clients and deploying updates. Allong with this I also give you some troubleshooting tips that you can use during this process.
About the Windows Update Process
Windows uses the Windows Update Agent to check Microsoft Update for new updates that may be applied to the machine.
You can configure Automatic Updates using one of the following options (on Control Panel -> Automatic Updates):
  1. Automatic (Recommended) – default
  2. Download updates for me, but let me choose when to install them
  3. Notify me but don’t automatically download or install them
  4. Turn off automatic updates
The update agent will look for new updates on the Microsoft Update catalog available on the Internet.
Configuring Automatic Update with WSUS involves the following steps:
  1. verifying operating system prerequisites for client computers
  2. pointing the client computers to the WSUS server and then configure the automatic updates
  3. making sure that the Windows Update Agent (WUA) software on the client machines is up to date
  4. …and that it! But if you are in a hurry to see the WSUS fully running, read this step to ;)
Step 1: Verify operating system prerequisites for client computers
Windows Vista
  • Windows Server 2008
  • Microsoft Windows Server 2003
  • Microsoft Windows XP Professional SP 2
  • Microsoft Windows 2000 Professional with Service Pack 4 (SP4), Windows 2000 Server with SP3 or SP4, or Windows 2000 Advanced Server with SP3 or SP4
  • Step 2: Point the client computers to the WSUS server and then configure automatic updates
    How best to configure Automatic Updates and WSUS environment options depends upon your network environment. In an Active Directory environment, you would use Group Policy. In a non-Active Directory environment, you might use the Local Group Policy object or edit the registry directly.

    Administrator-defined configuration options driven by Group Policy—whether set with Group Policy in an Active Directory environment or via the registry or Local Group Policy object—always take precedence over user-defined options. When you use administrative policies to configure Automatic Updates, the Automatic Updates user interface is disabled on the target computer.

    To do this follow the steps described on ref [6]. In the end of this procedure, your clients have automatic updates configured and are using you WSUS server for that.

    WSUS 3.0 Service Pack 1 Released!

    Windows Server Update Services 3.0 Service Pack 1 delivers important customer-requested mangement, stability, and performance improvements, while incorporating further enhancements to local publishing of drivers and the Client Servicing API addition.

    WSUS 3.0 SP1 delivers new features that enable administrators to more easily manage and deploy updates across the organization. This package installs both the WSUS 3.0 Server and WSUS 3.0 Administration Console components, for all Windows Server 2003 SP1 supported languages. Additionally, the WSUS 3.0 SP1 client is included in all supported client platform languages. You must install the server components on a computer running Windows Server 2008 or Windows Server 2003 SP1 or later. You may install the Administration Console on a remote computer running Windows Vista, Windows Server 2008, Windows Server 2003 SP1, or Windows XP SP2.

    WSUS 3.0 SP1 Server Installation on Windows Small Business Server 2003

    If you are installing the WSUS 3.0 SP1 product on Windows Small Business Server 2003, follow the instructions in Installing Windows Server Update Services 3.0 on Windows Small Business Server 2003.

    Release Notes for Windows Server Update Services 3.0 SP1These release notes describe known issues affecting Microsoft Windows Server Update Services 3.0 Service Pack 1 (WSUS 3.0 SP1) and include recommendations and requirements for installing the application.    
    Microsoft Windows Server Update Services 3.0 SP1 OverviewThis paper introduces Microsoft Windows Server Update Services 3.0 Service Pack 1 (WSUS 3.0 SP1) and provides information about features, and server and client computer requirements.    
    Deploying Microsoft Windows Server Update Services 3.0 SP1This paper describes how to deploy Microsoft Windows Server Update Services 3.0 Service Pack 1 (WSUS 3.0 SP1).    
    Step-by-Step Guide for Windows Server Update Services 3.0 SP1This guide provides instructions for getting started with Microsoft Windows Server Update Services 3.0 Service Pack 1 (WSUS 3.0 SP1).    
    Microsoft Windows Server Update Services 3.0 SP1 Operations GuideThis paper documents the major tasks involved in administering and troubleshooting Microsoft Windows Server Update Services 3.0 Service Pack 1 (WSUS 3.0 SP1).

    Download Here

    Managing changes from a WSUS Server

    There are multiple ways updates can be deployed through WSUS to client machines (“client machines” mean clients of the WSUS server – the machines may be running either client or server operating systems). This posting describes these mechanisms and the way they can be controlled by the administrator in order to ensure unexpected changes do not occur.

    ·         Explicit approval. An administrator can explicitly approve an update for installation to a group of machines.

    ·         Auto-reapprove revisions. By default, when a new revision of an approved update is synchronized to the WSUS server we move the approval to the new revision. Normally this is what customers want, since new revisions never contain new binaries, just fixes to the metadata that describe how to automate the installation of the update. However we had one incident when a new revision of the Windows Desktop Search update changed the metadata so that the new revision was offered to *all* machines but the old revision was offered only to machines with older versions of Desktop Search installed, which caused it to be deployed more widely than expected for many customers (see http://blogs.technet.com/wsus/archive/2007/10/25/wds-revision-update-expanded-applicability-rules-auto-approve-revisions.aspx for details). Since then, we’ve added processes to ensure this type of change will not happen again. The administrator has direct control over this and can disable the option to auto-reapprove revisions.

    o        Warning: turning off auto-reapprove revisions can create problems if the administrator has “definition updates” (signatures) in their synchronization options, because definition updates get created and expired fairly quickly and the expired ones won’t get auto-unapproved. As described in KB 938947, this can quickly lead to having too many updates approved which can cause problems for client-server communication. If auto-reapprove revisions is turned off, the administrator will need to manage revisions themselves; looking for older revisions that are approved and either unapproving them (if the new revision is marked “expired”) or move the approval to the new revision. We have provided a PowerShell sample script at http://www.microsoft.com/technet/scriptcenter/scripts/sus/server/susvms09.mspx that can be used to manage revisions.

    ·         Auto-approve WSUS updates. Some updates are marked as “infrastructure” updates, which means they are needed by WSUS or WUA for proper detection and scanning for many updates. These updates include MSI 3.1. WSUS creates approval rules to these by default, since they are necessary for the update system to work properly. The administrator has direct control over this and can disable the option to auto-approve WSUS updates. If disabled, WSUS will notify the admin in the home page (TODO list) that there are unapproved WSUS updates, which can lead to infrastructure problems (e.g., if MSI 3.1 is not installed on client machines, then many updates including Office Updates, can’t be properly detected).

    ·         Auto-approval rules. Administrators can create custom rules to auto-approve updates (e.g., auto-approve all security updates to all computers, or auto-approve all updates to a test target group). The administrator has direct control over this and there are no auto-approval rules enabled by default.

    ·         Initial client self-update. When a WSUS client’s Windows Update Agent (WUA) first synchronizes  against a WSUS server, it checks if the server has a newer version of the agent available in the servers “self-update” tree. If a newer version is available, the agent will self-update before completing the synchronization. Although Automatic Updates will check for self-update on every synchronization, the self update will only occur on the first synchronization unless the admin explicitly applies an update to the WSUS servers self-update tree (the next scenario).

    o        Note: Newer versions of WUA on a particular operating system are backwards-compatible with the older versions of WSUS that support that operating system.  So after WUA self-updates to the latest version, the client can later be managed by an  older WSUS server if desired. The agent never “self-downgrades” (it will stay on the latest version of WUA when talking to an older server).

    ·         Subsequent client self-updates. The WSUS team may provide an update to the WSUS server itself that modifies the client self-update tree on the server. As of this writing, only two such update have been released; WSUS 2 SP1 (which modified the WSUS 2 self-update tree) and KB 936301 (which modified the WSUS 2 SP1 self-update tree). Such updates flow to the WSUS server as normal updates. If the admin approves such an update for install on the WSUS server, then the WSUS server self-update tree will be updated and subsequently all clients that synchronize against the server will self-update. The administrator has direct control over this since clients will only perform this subsequent self-update if the administrator approves an update to the self-update tree.

    ·         Update from Microsoft Update. End users on client machines can go to Windows Update or Microsoft Update and install updates (and WUA self-updates) directly. The administrator has direct control over this since they can configure the Windows Update Agent to disallow end-user access to Windows Update and Microsoft Update.

     

    WSUS and AU have log files that allow customers to understand when and why a given update was installed on a machine:

    ·         The Windows Update Agent has a log file “%windir%\WindowsUpdate.log” with verbose logging on updates that have been installed.

    ·         WSUS 3.0 has a log file “%Program Files%\Update Services\LogFiles\changes.log” that contains a record of all recent approvals and who made them. If the approval was created automatically (e.g., auto-reapprove revision, auto-approval rule, or auto-approve WSUS updates), the user in the log will be “WSUS Service”.

    WSUS 3.0 SP1 Public RC Available

    Microsoft just announced the public availability of WSUS 3.0 SP1 Release Candidate 1. Improvements include support for Windows Server 2008 and product bug fixes. More information is available on Microsoft Connect. Click the ‘Available Connections’ link and look for Windows Server Update Services 3.0 SP1 Release Candidate. Here’s a brief overview of the WSUS page on Connect:

    “Thank you for joining the WSUS 3.0 Service Pack 1 Release Candidate Program and we welcome you to provide feedback on the Service Pack 1 through the channels listed below. By including you in our development process, we can ensure that our products meet the needs of our customers and are reliable.

    WSUS 3.0 SP1 addresses a number of product fixes and includes the addition of support for forth coming Windows Server 2008 (code named Longhorn Server).  The release notes on this release can be downloaded along with the build which provides more details on the installation.”

    Download Service Pack 1 and Documentation:
    The downloads link on the left hand menu will take you to the download page for the following SP1 builds and documentation:
    – WSUS 3.0 SP1 Beta x86 Build
    – WSUS 3.0 SP1 Beta x64 Build
    – WSUS 3.0 SP1 RC ReadMe
    – WSUS 3.0 SP1 RC Pre Release License
    – WSUS 3.0 Overview Document
    – WSUS 3.0 Operations Guide
    – WSUS 3.0 Step by Step Guide

    Continue Here

    b4810b334f" />