Category Archives: 7840

Windows Server Update Services Tools and Utilities

 

  • Windows Update Agent API Updated Header Files

    Download the updated WUA API header files for developing applications leveraging the WUA Agent public interfaces. You can download header files for the following platforms: i386, ia64bit, and x64bit.

  • WSUS Reporting Rollup Sample Tool

    This tool uses the WSUS application programming interface (API) to demonstrate centralized monitoring and reporting for WSUS. It creates a single report of update and computer status from the WSUS servers into your WSUS environment. The sample package also contains sample source files to customize or extend the tool functionality of the tool to meet specific needs. The WSUS Reporting Rollup Sample Tool and files are provided AS IS. No product support is available for this tool or sample files. For more information read the readme file.

  • Windows Server Update Services

    You can now register for and download WSUS. See for yourself how easy it is to have full control over the software that you distribute to computers in your network.

  • Server Diagnostic Tool

    Download this tool, which has been designed to help administrators gather WSUS server debugging logs and configuration information for further troubleshooting. The Windows Server Update Services Server Diagnostic tool is provided AS IS. No product support is available for this tool. For more information, read the readme file.

  • Client Diagnostics Tool

    Download this tool, which has been designed to aid the WSUS administrator in troubleshooting client machines that are failing to report back to the WSUS Server. The tool will conduct preliminary checks and test the communication between the WSUS Server and the client machine. Once the tool has completed the tests it will display the results in the console window. The Windows Server Update Services Client Diagnostic tool is provided AS IS. No product support is available for this tool. For more information, read the readme file.

  • Windows Server Update Services API Samples and Tools

    These samples and tools allow administrators and developers to control the functionality of the WSUS server. For more information, read the readme file.

Windows Server Update Services Tools and Utilities

Black Screen woes could affect millions on Windows 7, Vista and XP

 

Firstly, there appears to be many causes of of the black screen issue. The symptoms are very distinctive and troublesome. After starting your Windows 7, Vista, XP, NT, W2K, W2K3 or W2K8 PC or server the system appears normal. However, after logging on there is no desktop, task bar, system tray or side bar. Instead you are left with a totally black screen and a single My Computer Explorer window. Even this window might be minimized making it hard to see.

If you have these symptoms you can safely try our free Black Screen Fix. It will fix the most common cause we have seen of this issue.

Black Screen woes could affect millions on Windows 7, Vista and XP

Microsoft Security Bulletin Major Revisions

********************************************************************
Title: Microsoft Security Bulletin Major Revisions
Issued: August 25, 2009
********************************************************************

Summary
=======
The following bulletins have undergone a major revision increment.
Please see the appropriate bulletin for more details.

* MS09-044 – Critical
* MS09-029 – Critical

Bulletin Information:
=====================

* MS09-044 – Critical

- http://www.microsoft.com/technet/security/bulletin/ms09-044.mspx
- Reason for Revision: V2.0 (August 25, 2009): Corrected the
download link for RDP Version 5.2 for Windows XP Service Pack
2 (KB958469). Also corrected the footnote that prescribed an
erroneous install sequence for KB958471 and KB958470.
Customers who have successfully installed these updates do
not need to reinstall.
- Originally posted: August 11, 2009
- Updated: August 25, 2009
- Bulletin Severity Rating: Critical
- Version: 2.0

* MS09-029 – Critical

- http://www.microsoft.com/technet/security/bulletin/ms09-029.mspx
- Reason for Revision: V3.0 (August 25, 2009): Added an entry to
the section, Frequently Asked Questions (FAQ) Related to This
Security Update to communicate the rerelease of the
Japanese-language update for Windows XP Service Pack 2,
Windows XP Service Pack 3, and Windows XP Professional x64
Edition Service Pack 2. Customers who require the
Japanese-language update need to install the rereleased
update. No other updates or locales are affected by this rerelease.
- Originally posted: July 14, 2009
- Updated: August 25, 2009
- Bulletin Severity Rating: Critical
- Version: 3.0

WSUS 3.0 SP2 RC is now live on Connect!

Connect Site

WSUS 3.0 SP2 RC Overview

New Windows Server and Client Version Support

·       Integration with Windows Server® 2008 R2

·       Support for the BranchCache feature on Windows Server 2008 R2

·       Support for Windows 7 client

WSUS Feature Improvements

Auto-Approval Rules

·       Auto-approval rules now include the ability to specify the approval deadline date and time for all computers or specific computer groups.

Update Files and Languages

·       Improved handling of language selection for downstream servers includes a new warning dialog that appears when you decide to download updates only for specified languages.

Easy Upgrade

·       WSUS 3.0 SP2 can be installed as an in-place upgrade from earlier versions of WSUS and will preserve all of your settings and approvals. The user interface is compatible between WSUS 3.0 SP1 and SP2 on the client and the server.

Reports

·       New Update and Computer Status reports provide the ability to filter on updates approved for installation. You can run these reports from the WSUS console or use the API to incorporate this functionality into your own reports.

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.

·       A new release of Windows Update Agent is included with WSUS 3.0 SP2 that provides improvements and fixes, such as support for APIs called by non-local system callers in a non-interactive session.

 

For more information about this release refer to the Release Notes for Windows Server Update Services 3.0 SP2 RC.

 

Connect Site

Steve Rachui’s Manageability blog – ConfigMgr/OpsMgr : ITMU/SCCM/Patchinstall command line switches

 

A question came up the other day about how to set the patchinstall command line switches for ITMU in SCCM.  In SMS 2003 it was a simple edit to the command line for the program but in SCCM there is no such ability since we do all of the command line building based on UI settings and don’t expose the result (except in the patchinstall log when the deployment runs) for the user to edit.

I did some testing and come up with the list of switches below along with the corresponding SCCM UI setting that determines whether the switch is used or not.  This list is possibly not exhaustive and there are some command line switches that appear to be static and always used, like /p.

/s – This switch maps to the setting 'collect hardware inventory immediately' that is in the 'SMS 2003 settings'. The /s switch is present when the option is NOT selected.

/q – This switch maps to the setting 'hide deployments from sms 2003 client computers' in the advanced node of 'SMS 2003 settings'. The /q switch is present when the option IS selected.

/l – This switch maps to the setting 'enforce start time' in the advanced node of 'SMS 2003 settings'. The /l switch is present when this option IS checked and the numerical value for the switch comes from the configured time value.

/t – This switch seems to map to the 'maximum run time' for the patch.  There may be more to it for this switch since this setting is per update rather than per deployment.

/p – This switch appears to be set by default and no UI setting I've found has an impact on removing this switch. But removing the switch really shouldn't be necessary as long as it is paired with a properly configured /g switch.

/g – This switch maps to the setting 'set a deadline for software update installation' in deployment properties. The /g switch is present if this option is selected and the numerical value for the switch comes from the configured time value. Setting a value of 0 for this switch will cause the deployment to execute immediately even with the /p switch.

/n – This switch maps to the 'allow display notifications on clients' in deployment properties. The /n switch is present if 'allow notifications on clients' option IS selected.

/z – This switch maps to the system restart settings in deployment properties. The /z switch is present when a restart is suppressed for either servers or workstations.

/f – This switch maps to the system restart settings in deployment properties. The /f switch is present when no restart suppression is configured.

Steve Rachui's Manageability blog – ConfigMgr/OpsMgr : ITMU/SCCM/Patchinstall command line switches

The WSUS Support Team Blog : WSUS 3.0 SP2 beta now available

 

Today the WSUS product group launched the WSUS 3.0 Service Pack 2 beta program over on our Connect site so if you want to get a head start on testing and evaluating this Service Pack then you'll want to make your way over there and download a copy today.  WSUS 3.0 Service Pack 2 addresses a number of product features and fixes and includes the addition of support for Windows Server 2008 R2 and Windows 7.  Just remember that you have to be a registered Connect user and logged in or you won't see the download being available.

The official Connect site where you can read the documentation and download your own copy of the beta is here:

http://connect.microsoft.com/site/sitehome.aspx?SiteID=110

The WSUS product team blog also has a nice write-up detailing our new OS support, feature improvements and fixes in the SP here:

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

The WSUS Support Team Blog : WSUS 3.0 SP2 beta now available

The Configuration Manager Support Team Blog : ConfigMgr 2007: How to install patches manually on Windows Vista and Windows Server 2008

 

Our very own Steve Rachui has a cool post over on his blog that talks about how to install patches manually on Windows Vista and Windows Server 2008 machines.  While that may sound trivial, if you've every tried this with Vista or Win2K8 SCCM patches you may be left scratching your head on how exactly this is done. 

========

Prior to Windows 2008 and Vista software updates delivered through SMS/SCCM would come down in the form of .exe files and be stored in the client cache.  During patch troubleshooting one option might be to attempt to run the patch directly, from the cache. 

With Windows 2008 and Vista updates now come down as .cab files and if you double click them to attempt a manual install you will end up just opening the cab to display the packaged content.  And, none of the files in the packaged content have an extension that appears to be actionable….

To continue reading see http://blogs.msdn.com/steverac/archive/2009/01/17/how-to-install-sccm-patches-manually-on-vista-server-2008.aspx.

The Configuration Manager Support Team Blog : ConfigMgr 2007: How to install patches manually on Windows Vista and Windows Server 2008

Microsoft Security Bulletin Advance Notification for January 2009

 

Microsoft Security Bulletin Advance Notification issued: January 8, 2009
Microsoft Security Bulletins to be issued: January 13, 2009

This is an advance notification of security bulletins that Microsoft is intending to release on January 13, 2009.

This bulletin advance notification will be replaced with the January bulletin summary on January 13, 2009. For more information about the bulletin advance notification service, see Microsoft Security Bulletin Advance Notification.

To receive automatic notifications whenever Microsoft Security Bulletins are issued, subscribe to Microsoft Technical Security Notifications.

Microsoft will host a webcast to address customer questions on these bulletins on January 14, 2009, at 11:00 AM Pacific Time (US & Canada). Register now for the January Security Bulletin Webcast. After this date, this webcast is available on-demand. For more information, see Microsoft Security Bulletin Summaries and Webcasts.

Microsoft also provides information to help customers prioritize monthly security updates with any non-security, high-priority updates that are being released on the same day as the monthly security updates. Please see the section, Other Information.

Bulletin Information


Executive Summaries

This advance notification provides the software subject as the bulletin identifier, because the official Microsoft Security Bulletin numbers are not issued until release. The bulletin summary that replaces this advance notification will have the proper Microsoft Security Bulletin numbers (in the MSyy-xxx format) as the bulletin identifier.

The following table summarizes the security bulletins for this month in order of severity.

For details on affected software, see the next section, Affected Software.

Bulletin ID
Maximum Severity Rating and Vulnerability Impact
Restart Requirement
Affected Software

Windows

Critical
Remote Code Execution

Requires restart

Microsoft Windows

Top of sectionTop of section


Affected Software

This advance notification provides the software subject as the bulletin identifier, because the official Microsoft Security Bulletin numbers are not issued until release. The bulletin summary that replaces this advance notification will have the proper Microsoft Security Bulletin numbers (in the MSyy-xxx format) as the bulletin identifier.

The following tables list the bulletins in order of major software category and severity.

How do I use these tables?

Use these tables to learn about the security updates that you may need to install. You should review each software program or component listed to see whether any security updates pertain to your installation. If a software program or component is listed, then the severity rating of the security update is also listed.

Note You may have to install several security updates for a single vulnerability. Review the whole column for each bulletin identifier that is listed to verify the updates that you have to install, based on the programs or components that you have installed on your system.


Windows Operating System and Components

Microsoft Windows 2000

Bulletin Identifier

Windows

Aggregate Severity Rating

Critical

Microsoft Windows 2000 Service Pack 4

Microsoft Windows 2000 Service Pack 4
(Critical)

Windows XP

Bulletin Identifier

Windows

Aggregate Severity Rating

Critical

Windows XP Service Pack 2 and Windows XP Service Pack 3

Windows XP Service Pack 2 and Windows XP Service Pack 3
(Critical)

Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2

Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2
(Critical)

Windows Server 2003

Bulletin Identifier

Windows

Aggregate Severity Rating

Critical

Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2

Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2
(Critical)

Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2

Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2
(Critical)

Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems

Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems
(Critical)

Windows Vista

Bulletin Identifier

Windows

Aggregate Severity Rating

Moderate

Windows Vista and Windows Vista Service Pack 1

Windows Vista and Windows Vista Service Pack 1
(Moderate)

Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1

Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1
(Moderate)

Windows Server 2008

Bulletin Identifier

Windows

Aggregate Severity Rating

Moderate

Windows Server 2008 for 32-bit Systems

Windows Server 2008 for 32-bit Systems*
(Moderate)

Windows Server 2008 for x64-based Systems

Windows Server 2008 for x64-based Systems*
(Moderate)

Windows Server 2008 for Itanium-based Systems

Windows Server 2008 for Itanium-based Systems
(Moderate)

Notes for Windows Server 2008

*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

Top of sectionTop of section

Top of sectionTop of section


Detection and Deployment Tools and Guidance

Security Central

Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers in your organization. For more information see the TechNet Update Management Center. The TechNet Security Center provides additional information about security in Microsoft products. Consumers can visit Security At Home, where this information is also available by clicking “Latest Security Updates”.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update".

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool (ESUIT). For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer

The Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems.

For more information about how to deploy this security update using Windows Server Update Services, visit Windows Server Update Services.

Systems Management Server

Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and to perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. The next release of SMS, System Center Configuration Manager 2007, is now available; see also System Center Configuration Manager 2007. For more information about how administrators can use SMS 2003 to deploy security updates, see SMS 2003 Security Patch Management. SMS 2.0 users can also use the Software Updates Services Feature Pack to help deploy security updates. For information about SMS, visit Microsoft Systems Management Server.

Note SMS uses the Microsoft Baseline Security Analyzer and the Microsoft Office Detection Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, see Deploying Software Updates Using the SMS Software Distribution Feature. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Top of sectionTop of section

Other Information

Microsoft Windows Malicious Software Removal Tool

Microsoft will release an updated version of the Microsoft Windows Malicious Software Removal Tool on Windows Update, Microsoft Update, Windows Server Update Services, and the Download Center.

Top of sectionTop of section

Non-Security, High-Priority Updates on MU, WU, and WSUS

For information about non-security releases on Windows Update and Microsoft update, please see:

Microsoft Knowledge Base Article 894199: Description of Software Update Services and Windows Server Update Services changes in content. Includes all Windows content.

New, Revised, and Released Updates for Microsoft Products Other Than Microsoft Windows.

Top of sectionTop of section

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Top of sectionTop of section

Security Strategies and Community

Update Management Strategies

Security Guidance for Update Management provides additional information about Microsoft’s best-practice recommendations for applying security updates.

Obtaining Other Security Updates

Updates for other security issues are available from the following locations:

Security updates are available from Microsoft Download Center. You can find them most easily by doing a keyword search for "security update".

Updates for consumer platforms are available from Microsoft Update.

You can obtain the security updates offered this month on Windows Update, from Download Center on Security and Critical Releases ISO CD Image files. For more information, see Microsoft Knowledge Base Article 913086.

IT Pro Security Community

Learn to improve security and optimize your IT infrastructure, and participate with other IT Pros on security topics in IT Pro Security Community.

Top of sectionTop of section

Support

The affected software listed have been tested to determine which versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your software version, visit Microsoft Support Lifecycle.

Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.

International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit International Help and Support.

Top of sectionTop of section

Microsoft Security Bulletin Advance Notification for January 2009