Export (0) Print
Expand All
33 out of 53 rated this helpful - Rate this topic

Windows Vista SP2 and Windows Server 2008 SP2 Test Focus Guide

Updated: April 28, 2009

Applies To: Windows Server 2008, Windows Vista

Microsoft continuously improves Windows Vista® and Windows Server® 2008 by providing ongoing updates while working with software and hardware vendors to deliver application compatibility and hardware compatibility improvements. Service Pack 2 (SP2) is another vehicle through which Microsoft provides operating system improvements to customers.

SP2 is an update to both Windows Vista and Windows Server 2008 that, along with improvements delivered to users via other channels, addresses feedback from our customers. As with previously released updates, SP2 contains changes that are focused on addressing specific reliability, performance, and compatibility issues, supporting new types of hardware, and adding support for several emerging standards. SP2 also continues to improve upon the IT administration experience. SP2 is not intended to be a vehicle for releasing new features; however, some existing components do gain slightly enhanced functionality in SP2.

Scope of This Document

This document focuses on key changes introduced with SP2 on both Windows Server 2008 (“Server”) and Windows Vista (“Client”). These changes, spanning several key areas, fall into three categories:

  • Changes to simplify administrative and management tasks

  • Ongoing improvements to overall quality: security, reliability, and performance

  • Support for emerging technologies and standards

Each change and its associated test scenarios are provided along with known issues and KB articles wherever appropriate. This document highlights the changes and some common and interesting scenarios for each change. Some of the scenarios might require special hardware (for example, 1394 storage device). Such prerequisites are also mentioned for each scenario.

Providing Feedback

Please use your Connect account to provide suggestions or file bugs regarding this content.

ImportantImportant
Before you begin, log onto your Connect account and download the Data Grabber tool. Once it is downloaded, you can use Data Grabber for the duration of the beta program.

To send feedback:

  1. Log onto your Connect account.

  2. Open and fill out a bug submission form.

    1. Run the Data Grabber tool.

    2. Attach the resulting Data Grabber CAB file to the bug.

  3. Submit the bug.

Major Changed Components

This section describes the major Areas and Subareas that underwent various changes toward improving quality across the operating system.

 

Area Changed Major Subareas

Base Technologies

.NET Framework

COM/COM+

Emulation Layer

File Systems (Local)

File Systems (Remote)

HAL

Kernel

Plug and Play

Power Options

Reliability

Client Technologies

Client Platform

Control Panel

Copy Engine

Desktop Shell

Explorer Operations

Graphics Infrastructure

Internet Explorer

Logon

Organize & Storage

Shell APIs and Controls

Text Input Services

USER

Windows Search

Computer Management

Automated Tasks

Configuration Management

WMI (wbem)

Core Virtualization

Hypervisor (HV)

Virtual Devices

Virtual Machine Management Services (VMMS)

Data Services

Data Access Components

Drivers

1394

Audio

Bluetooth

PCI

Printers

Secure Digital (SD)

USB Core

Multimedia

Audio/Video Core

Codecs & DSP

Media Center

Media Center Extender

Media Foundation

Media Player

Photos - Data Services

Windows TV

Networking

Client/Server

DHCP

IPsec

NetSh

Network Driver Interface Specification (NDIS)

RRAS

TCP/IP

Windows Filtering Platform (WFP)

Wireless Services

Printing & Imaging Technologies

Authentication

Crypto

Imaging

PKI

Printing

Server Technologies

ADFS

Clustering and High Availability

Directory Services

DNS Server

Internet Information Services (IIS)

Indexing Service

Message Queuing

Microsoft SMB Protocol

Small Business Server

Terminal Services

Virtual Disk Service

Storage

Core Storage

Personal Storage

Volume Management

Windows Server Backup

SP2 Test Guidance for IHV

This section describes the test scenarios for third party drivers/devices. The aim of this testing is to find regressions in third party device driver functionality from previous service packs and to find high impact, high applicability/opportunity issues in third party devices and drivers relatively early in the ship cycle.

Test Environment & Setup

  1. Coverage on both x86 and x64 platforms. IA64 would be nice to have as well.

  2. Coverage on both Windows Vista and Windows Server 2008 operating systems (as applicable).

  3. Coverage on latest WHQLed driver.

  4. Coverage on Home, Ultimate, Business, and Server SKUs.

Test Scenarios

In the following table, the devices refer to the device that is controlled by your driver: Audio, Video, Print, Networking, USB, Storage, Optical, etc. In most cases, the driver under test should be installed prior to performing these tests.

 

Categories Test ID Test Variations

SP Update

T1

  1. SP Install: Ensure that all devices continue to work after a service pack install, for example Windows Vista SP2 installs fine on Windows Vista SP1 or Windows Server 2008 SP2 installs on Windows Server 2008.

  2. SP Uninstall: Ensure that all devices continue to work after a service pack is uninstalled, for example after SP2 is uninstalled from Windows Vista or Windows Server 2008.

  3. Ensure that there is no crash or other issues while installing or uninstalling SP2

  4. Default Device Settings: Device settings are preserved across SP installs and uninstalls

  5. Non-Default Device Settings: Non Default device settings are not turned on across SP uninstall/installs

  6. Please ensure that the non-Microsoft applications (Developed by the IHVs) that controls/configures the devices are functioning properly post update

Power Options

T2

  1. S2, S3, S4, Hybrid Sleep (standby, hibernate states): Ensure that devices continue to function properly after returning back from low power states in SP2.

  2. Test some of T2, T3 & T4 on DC (Battery) in the Power Saver scheme.

Plug and Play

T3

  1. Ensure devices continue to function after plugging them in and out of the system where applicable.

  2. Hybrid of Plug and Play and power management tests: Go to standby, unplug, come back from standby, and then plug in and test for functionality.

  3. Docking: Ensure that devices continue to function properly after docking and undocking of laptops.

  4. Driver Install: Ensure that installing new version of driver functions properly.

  5. Driver Uninstall: Uninstall of Driver reverts back to the previous version of driver.

  6. Inbox: Device Driver load works when device is activated.

Scenario Based

T4

Video

  1. Record video images or photos on peripheral devices, capture on disk, save and upload to a Web site.

  2. Extend displays to second or third monitors or external projectors.

  3. Use video chat IM along with text IM.

Networking

  1. Copy large files to/from network using wired/wireless connection.

  2. Stream videos from network.

  3. Load songs from Web sites to peripheral devices such as Zune or iPod.

Audio

  1. Stream and play an audio file from the Internet.

  2. Play back an audio file.

  3. Play back a DVD.

Print

  1. Open a picture with photo gallery and print it.

  2. Open an Excel Spreadsheet, put data in tables, and then print it.

  3. Scan a paper document and view the scanned image on the computer.

  4. Print from PowerPoint.

  5. Print an Adobe PDF file.

  6. Print from Word.

Basic OC install/uninstall scenario

  1. Enable all optional components before installing SP.

    Run optionalfeatures.exe in an elevated command prompt and select every check box within the tree.

  2. SP Install: Ensure that SP installed successfully, for example Windows Vista SP2 installs fine on Windows Vista SP1 or Windows Server 2008 SP2 installs on Windows Server 2008.

  3. Ensure that all optional components are intact.

  4. Disable all optional components.

  5. Ensure that all optional components are disabled successfully.

Basic scenario for compcln.exe

noteNote
SP2 cannot be uninstalled after running the compclean command.

  1. SP Install: Ensure that SP installed successfully, for example Windows Vista SP2 installs fine on Windows Vista SP1 or Windows Server 2008 SP2 installs on Windows Server 2008.

  2. Capture the installed components state by running the following command:

    Run dir “%windir%\” /b/s/a:-d>files_before.txt

  3. Run compcln.exe in an elevated command prompt to remove the staged components superseded by SP install:

    Run %windir%\system32\compcln.exe

  4. Capture the installed components state by running the following command:

    Run dir “%windir%\” /b/s/a:-d>files_after.txt

  5. The difference between files_before.txt and files_after.txt is the list of items that were removed  by compcln.exe.

  6. Ensure that SP2 cannot be uninstalled from Software Explorer.

Unexpected Results

  • Bug checks

  • Crash

  • Loss of functionality

  • Unusable system after update to SP2

Test Result Reporting

Driver Name & Version:

PNP ID:

Operating System / Platform:

 

Test ID Result

T1

Pass

T2

..

..

..



In case any issues are being reported, please capture the following logs:

  • %WINDIR%\WindowsUpdate.log

  • %WINDIR%\Inf\setupapi.dev.log

  • %WINDIR%\Inf\setupapi.app.log

  • %WINDIR%\Logs\CBS\CBS.log

  • %WINDIR%\Logs\CBS\CBS.persist.log

  • %WINDIR%\Panther\setupact.log

  • %WINDIR%\Panther\setuperr.log

  • %WINDIR%\MEMORY.DMP (if exists)

  • %WINDIR%\Minidump\*.dmp

  • Dxdiag

  • Msinfo32

Server Roles & Priorities

Following are priorities of Roles based on the changes that were made in various components related to each of these roles. These priorities can be used to prioritize various tests and scenarios on Windows Server 2008.

 

S No Role Priority Server Roles

1

P0

DHCP Server

2

P0

Active Directory Domain Services

3

P0

Active Directory Lightweight Directory Services

4

P0

DNS Server

5

P0

File Services

6

P0

Print Services

7

P0

RRAS

8

P0

Terminal Services

9

P1

Network Policy And Access Services (NAP)

10

P1

Active Directory Certificate Services

11

P1

Active Directory Rights Management Services

12

P2

Windows Deployment Services

13

P2

Windows Media

Base Technologies

Kernel

What’s New in Kernel?

Following are the new improvements inside Kernel:

  1. Missing callback support for registry operations - NtSaveKey, NtRestoreKey and NtReplaceKey were added inside kernel.

  2. WoW64, which enables running 32-bit applications on 64 bit systems, has been improved to increase system reliability.

  3. Exception handling has been improved on 64 bit systems.

Key Scenarios

Scenario 1 – Improvements in wow64

Goal:
Improve performance/reliability of 32-bit applications running on 64-bit Windows Server 2008 SP2.

Prerequisites or specific configuration for the scenario:
Installation of 64-bit Windows Server 2008 SP2.

Applicability:
Server & Client

Step-by-step scenario description:
Normal use of any 32-bit applications on 64-bit Windows Server 2008 SP2.

Expected results:
Users should not notice any negative performance/reliability hit in running 32-bit applications on 64-bit Windows Server 2008 SP2 systems. Any system performance degradation or hangs/crashes should be reported.

Exceptions:
None

Scenario 2 – Improved exception handling on 64 bit systems

Goal:
To catch all application generated exceptions on 64-bit Windows.

Prerequisites or specific configuration for the scenario:
Installation of 64-bit Windows Server 2008 SP2.

Applicability:
Server & Client

Step-by-step scenario description:
Normal use of various 32-bit and 64-bit applications on 64-bit Windows Server 2008 SP2.

Expected results:
Users should not notice any difference in running the applications. Any abnormal termination of the applications should be reported.

Exceptions:
None

COM/COM+

Quality Improvements in COM/COM+

Component Object Model (COM) & COM+ has been improved for scalability and reliability.

Key Scenarios

Scenario 1 – Add 1000+ dedicated IP addresses to the loopback adapter

Goal:
To increase the number of IP addresses binded to adapter (say, more than 1100 bindings). This scenario is mostly applicable to Web hosts.

Prerequisites or specific configuration for the scenario:
Add the wordpad.exe as an exception in the firewall.cpl when the firewall is on.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Install a new virtual network adapter and rename the connection name to “Microsoft Loopback Adapter”.

    1. Run “control” to start the control panel.

    2. Click “add hardware”.

    3. Select “network adapter” from the hardware list.

    4. Select the hardware company name “Microsoft” in the left side with the hardware name “Microsoft loopback adapter” in the right side.

    5. Select “next” to install a virtual network adapter “Local Area Connection2”.

    6. Rename the name of the virtual network adapter from “Local Area Connection2” to “Microsoft Loopback Adapter”.

  2. Add the IP address to that network adapter in the machine.

    Example command to add IP address:

    netsh interface ip add address name = "Microsoft Loopback Adapter" addr = 192.168.10.1 mask = 255.255.255.0
    
  3. Create an object of a registered DCOM component.

    Example VB Script:

    Set theObject = CreateObject("Wordpad.Document.1", WScript.Arguments(0))
    If theObject Is Nothing Then
        WScript.Echo "the Object is null"
    Else
        WScript.Echo "the Object was created"
    End If
    
    
Expected results:
IP addresses can be successfully binded. NO “out of memory” message appears.

Exceptions:
None

Scenario 2 – Test COM+ Event System

Goal:
Verify that the applications that rely on COM+ event system behave the same as a non-patched operating system.

noteNote
The change has been released as a security update on Windows Update.

Prerequisites or specific configuration for the scenario:
None

Applicability:
Server & Client

Scenario description:
Technical user should create Event Classes using standard MSDN guidelines. Third party applications are likely to be affected by these changes.

Expected results:
Users should see no obvious change in behavior.

Exceptions:
None

Scenario 3 – Create SxS COM components

Goal:
To improve the performance when creating SxS COM components.

Prerequisites or specific configuration for the scenario:
Customers have implemented COM components and use Windows’ Side by Side technology to deploy those components.

Applicability:
Server & Client

Scenario description:
Programmatically activate/load SxS COM components.

Expected results:
The time to load an SxS COM component should be almost same as that of loading it via registry.

Exceptions:
None

Power Options

What’s Changed in Power Options?

Processor Power Policy is responsible for efficient power consumption by the processor. For Intel Processors, Process Power Policy defaults have been optimized on clean installs of Windows Server 2008.

Key Scenarios

Scenario 1 - Confirm power savings without loss of performance on your specific scenarios

Goal:
Confirm power savings without loss of performance on your specific scenarios.

Prerequisites or specific configuration for the scenario:
Intel processor and clean install of Windows Server 2008 SP2.

Applicability:
Server

Step-by-step scenario description:
Clean install of Windows Server 2008 SP2.

Expected results:
Less power is used without any performance regressions.

Exceptions:
AMD processors or SP2 update installs are not applicable.

Networking

TCP/IP

Quality Improvements in TCP/IP

TCP/IP had issues fixed with customers not able to access TOS (DSCP) Field with RAW sockets call. Changes have been made to improve large file copy over SMB.

Key Scenarios

Scenario 1 – Any application (Exp: VPN) which might modify TCP/IP per-interface registry key values

Goal:
Make sure that there is no extra delay and performance hit when running applications that modify TCP/IP per-interface registry key values.

Prerequisites or specific configuration for the scenario:
Applications that would modify TCP/IP per-interface registry key values.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Run application as normal.

  2. Disable/enable the network interface.

  3. Set the machine to sleep/hibernate/resume/restart.

Expected results:
No network performance hit for applications. No extra delay introduced during network interface enable, machine resume, and startup.

Exceptions:
None

Scenario 2 – Large file copy utilizes 1G network bandwidth

Goal:
Make sure that TCP/IP stack can fully utilize Gigabit or 10G network bandwidth for large file copy (image/content replications) over TCP.

Prerequisites or specific configuration for the scenario:
Large file or contents need to be replicated over 1G or 10G network.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Copy large file/contents which can fully fill 1G or 10G network.

  2. Monitor that TCP performance can utilize the network bandwidth.

Expected results:
Significant performance improvements on Windows Server 2008 SP1 over Windows Server 2008 RTM. Performance should be the same or better than Windows Server 2003.

Exceptions:
None

Scenario 3 – TCP Chimney offload

Goal:
Make sure that TCP chimney offload works fine: no packet loss, connection drop and performance hit.

Prerequisites or specific configuration for the scenario:
Network Card which supports TOE (TCP Chimney Offload functionality).

Applicability:
Server & Client

Step-by-step scenario description:
  1. Netsh int tcp set gl chimney=enabled (enables stack’s TCP/IP chimney offload).

  2. Enable TCP chimney offload on the NIC if it’s not enabled by default.

  3. Normal TCP communications.

Expected results:
TCP connections are offloaded to TOE NIC, no data loss, connection drop and performance hit.

Exceptions:
None

Scenario 4 – IPv6

Goal:
Make sure network stack compliance RFC specification for stateful IPv6 address assignment and address selection.

Prerequisites or specific configuration for the scenario:
DHCPv6 is configured on the network.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Disable router advertisement on the IPv6 router.

  2. Network communication over IPv6.

Expected results:
Stack get stateful IPv6 address from DHCPv6 if failed to receive router advertisement from IPv6 router. Native IPv6 address are preferred than 6to4/ISATAP/Teredo IPv6 address even the routing metric are same.

Exceptions:
None

Scenario 5 – Network status monitoring for multiprocessor machine

Goal:
Make sure no data loss or break when performing network status monitoring on multiprocessor machine.

Prerequisites or specific configuration for the scenario:
Test on multiprocessor machine.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Periodically run command “netstat –a” to monitor network status.

  2. Heavy network communication.

Expected results:
No data loss or break.

Exceptions:
None

Scenario 6 – Boot performance

Goal:
Make sure that restart during machine boot/initialization does not break.

Prerequisites or specific configuration for the scenario:
None

Applicability:
Server & Client

Step-by-step scenario description:
  1. Force restart during machine boot/initialization (specifically during IPv6 virtual interface initialization).

  2. Manual commands for above scenario (steps b, c to be run as close as possible):

    1. Net stop iphlpsvc

    2. Net start iphlpsvc

    3. Shutdown /f /r /t 0

Expected results:
No break and no extra delay during next boot.

Exceptions:
None

DHCP

Quality Improvements in DHCP

DHCP can now lease out addresses to Solaris & Suse Clients. Changes have been made so as to enable customizing Cache size of DHCP server, which significantly improves overall performance.

Key Scenarios

Scenario 1 – DHCPv6 server is not leasing out address to Solaris and Suse clients

Goal:
Server should lease out addresses to these clients. Basically any client which sends an IANA without IAAddress in the request packet was not being leased out address earlier.

Prerequisites or specific configuration for the scenario:
Any non-MS V6 client that sends IANA without IAAddress and tries to receive an ipv6 address from Windows Server 2008 SP2.

Applicability:
Server

Step-by-step scenario description:
  1. Connect a non-MS V6 client to Windows Server 2008 SP2.

  2. It should get a V6 IP.

  3. To confirm that this bug has actually solved the problem check in the netmon captures that there was no IAAddress specified in the request packet during SARR sequence.

Expected results:
Client should get V6 address.

Exceptions:
None

Scenario 2 – Improve performance of DHCP server by increasing DHCP Database cache size

Goal:
To improve performance of DHCP server by increasing database cache size.

Prerequisites or specific configuration for the scenario:
The user should have a large number of V6 + V4 clients say 1000 or more that are asking for address from a DHCP server.

Applicability:
Server

Step-by-step scenario description:
  1. Create a new registry key(DWORD) JetDatabaseMaxCacheSize at HKLM\SYSTEM\CurrentControlSet\Services\DhcpServer\Parameters\ exactly where other keys like DatabaseName key are there. The DWORD value specifies the maximum cache size in MB.

  2. Give it a value smaller than your RAM size say 2048. This means that the DHCP database can increase up to 2 GB. Note that it is auto adjustable so even if you allocate 2GB that does not mean that it will statically keep the 2GB with itself.

  3. One can delete the key to get the default behavior of quite small cache size which causes many disk reads and thus lower performance.

  4. In perfmon the active queue length and other factors like ACK/sec, disk reads per second will improve after increasing the cache size.

  5. Make sure you restart DHCP server service after modifying the registry key.

Expected results:
All clients should get addresses immediately. The server should respond to all V4 V6 requests without keeping them long in the active queue.

Exceptions:
None

Windows Filtering Platform

Quality Improvements in Windows Filtering Platform

Windows Filtering Platform has been improved to be more reliable and compatible.

Key Scenarios

Scenario 1 – Make sure third party Internet Security Software are compatible with Windows Components

Goal:
Application compatibility.

Prerequisites or specific configuration for the scenario:
Third-party firewall installed.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Install third-party Enterprise Firewall.

  2. Try VPN.

  3. Try Access internal Web site required IPSec.

  4. Try to use Outlook to send/receive e-mails.

  5. Try to browse Web site.

Expected results:
Everything works fine.

Exceptions:
None

Storage

Storage

Quality Improvements in Storage

USB and 1394 storage drivers have been improved fixing many bug checks. These devices will be more reliable on both Windows Windows Vista SP2 and Windows Server 2008 SP2.

Key Scenarios

Scenario 1 – USB and 1394 storage devices behavior with various power management scenarios.

Goal:
Ensure the device works as expected during and after all its supported sleep states.

Prerequisites or specific configuration for the scenario:
  • Enable driver verifier on usbstor.sys, sbp2port.sys.

  • Any scripts/tools that put the machine in continuous sleep cycles covering all sleep states will be ideal to test this scenario (for example, PMTE, Cycler Sleep, DRS Sleep stress).

Applicability:
Server & Client

Step-by-step scenario description:
#1

  1. Connect 1394 storage/USB storage devices to the machine.

  2. Put the machine into different supported sleep states (Sleep, hybrid sleep and hibernate).

  3. Ensure that the device is functional even after it resumes from the sleep state.

  4. Test needs to run continuously for hours to ensure the device works under rigorous conditions.

#2

  1. Connect 1394 and USB storage devices to the machine.

  2. Enable ready boost to USB 2.0 storage devices.

  3. Run multiple shutdown and restart cycles overnight.

Expected results:
  • The device should not be banged out in Device Manager.

  • There should not be any error message in the event viewer entries.

  • The device should be functional after the sleep states.

Exceptions:
None

Scenario 2 – Plug / Unplug the 1394 and USB storage devices along with daisy-chain

Goal:
Ensure the device reacts as expected during PnP and while daisy chaining.

Prerequisites or specific configuration for the scenario:
Enable driver verifier on usbstor.sys, sbp2port.sys.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Connect multiple 1394 Storage devices to the machine through daisy chaining.

  2. Put the machine into different sleep states.

  3. Ensure that the devices works even after it resumes from the sleep state.

  4. Plug and Play the devices.

  5. Disable/Enable/Uninstall/Reinstall the plugged in devices randomly or using automated script or tools.

Expected results:
  • The devices should not be banged out in device manager.

  • There should not be any error message in the event viewer entries.

  • The device should be functional after these tests.

Exceptions:
None

Scenario 3 - Move large sized file to/from the device

Goal:
Improve performance when moving files/folders on the same volume.

Prerequisites or specific configuration for the scenario:
  • Enable driver verifier on usbstor.sys, sbp2port.sys.

  • The user should have files of size 3GB or more.

Applicability:
Server & Client

Scenario description:
Move files from internal hard disk to the 1394/USB Storage devices and vice versa.

Expected results:
Files/folders are moved nearly instantaneously.

Exceptions:
None

Scenario 4 – Configuration Manager APIs

Goal:
Test the device driver’s remove code path, the query-device-relations code path, and the CM and PNP IO APIs.

Prerequisites or specific configuration for the scenario:
  • Enable driver verifier on usbstor.sys, sbp2port.sys.

  • Query Remove Tests (qr.exe).

Applicability:
Server & Client

Step-by-step scenario description:
  1. Remove device using Safely Remove Hardware.

  2. Perform Surprise Removal of the device.

  3. Eject the device media (CD/DVD drives).

Expected results:
The device must be functional after an uninstall/reinstall cycle. There must not be a prompt for a system restart when uninstalling or installing the device.

Exceptions:
None

Scenario 5 – PNP and power management combination

Goal:
The 1394 and USB storage devices should not cause any bug check. To test the device drivers remove code path, the query-device-relations code path along with power management combination.

Prerequisites or specific configuration for the scenario:
Connect a USB and a 1394 Storage Device.

Applicability:
Server & Client

Step-by-step scenario description:
#1

  1. Put the system into S3 state for 5-10 min. and disconnect the USB and 1394 storage devices.

  2. Resume from S3 and make sure that it really disconnected from the system.

  3. Try this scenario for at least 10 cycles.

#2

  1. Put the system into S4 state for 5-10 min. and disconnect the USB and 1394 storage devices.

  2. Resume from S4 and make sure that it really disconnected from the system.

  3. Try this scenario for at least 10 cycles.

#3

  1. Put the system into S3 state for 5-10 min. and connect the USB and 1394 storage devices while the system in S3 state.

  2. Resume from S3 and make sure that newly connected devices are active and work fine.

  3. Try this scenario for at least 10 cycles.

#4

  1. Put the system into S4 state for 5-10 min. and connect the USB and 1394 storage devices.

  2. Resume from S4 and make sure that newly connected devices are active and work fine.

  3. Try this scenario for at least 10 cycles.

Expected results:
The device must be functional when the system resumes from S3 and S4 states and it should not cause any deadlock or bug check.

Exceptions:
None

Scenario 6 – I/O with power management combination

Goal:
Check reliability of 1394/USB storage devices.

Prerequisites or specific configuration for the scenario:
  • Enable driver verifier on usbstor.sys, sbp2port.sys.

  • Enable ready boost to USB 2.0 storage devices.

  • User should have USB/1394 devices and files of size greater than or equal to 3GB.

Applicability:
Server & Client

Step-by-step scenario description:
#1

  1. Copy files from internal hard disk to the 1394/USB Storage devices and vice versa.

  2. While copying the large files from internal HDD to 1394 HDD and vice versa, put the system into S3 state.

  3. Resume from S3 and make sure that copy continues.

#2

  1. Copy files from internal hard disk to the 1394/USB Storage devices and vice versa.

  2. While copying the large files, put the system into S4 state.

  3. Resume from S4.

  4. Copy will not complete and it will throw the copy-file error dialog but device should be active and it should not cause any bug check.

Expected results:
When the system resumes from S3/S4 while copying the large file, it should not cause any bug check.

Exceptions:
None

Scenario 7 – I/O with PNP Combination

Goal:
Check reliability of 1394/USB storage devices.

Prerequisites or specific configuration for the scenario:
  • Enable driver verifier on usbstor.sys, sbp2port.sys.

  • Enable ready boost to USB 2.0 storage devices.

  • User should have USB/1394 devices and files of size greater than or equal to 3GB.

Applicability:
Server & Client

Step-by-step scenario description:
#1

  1. Connect USB/1394 storage devices to the machine.

  2. Copy files from internal hard disk to USB/1394 devices and vice versa.

  3. Disconnect the USB/1394 device while the files are getting copied.

Expected results:
Copy fails and the system doesn’t bug check.

Exceptions:
None

Windows Server Backup

What is Windows Server Backup?

The Windows Server Backup feature in Windows Server 2008 consists of a Microsoft Management Console (MMC) snap-in and command-line tools that provide a complete solution for your day-to-day backup and recovery needs. You can use four wizards to guide you through running backups and recoveries. You can use Windows Server Backup to back up a full server (all volumes), selected volumes, or the system state. You can recover volumes, folders, files, certain applications, and the system state. And, in case of disasters like hard disk failures, you can perform a system recovery, which will restore your complete system onto the new hard disk, by using a full server backup and the Windows Recovery Environment.

You can use Windows Server Backup to create and manage backups for the local computer or a remote computer. You can also schedule backups to run automatically and you can perform one-time backups to augment the scheduled backups.

You can use the CLI (Command Line Interface) or UI (User Interface) to do the backup.

Quality Improvements in Windows Server Backup

Windows Server Backup has been fixed to address scheduling backups on target disk size exceeding Two TeraBytes.

Key Scenarios

Scenario 1 – Schedule a backup from snap-in

Goal:
Schedule a backup when the target disk storage size is greater than 2 terabytes.

Prerequisites or specific configuration for the scenario:
Make sure you have an additional hard disk of more than 2 terabytes before running this scenario.

Applicability:
Server

Step-by-step scenario description:
Refer to http://go.microsoft.com/fwlink/?LinkId=128732 for a step-by-step guide to set up Windows Server Backup.

Using UI:

  1. For UI, launch mmc.exe and add the Backup snap-in. Then, use the Backup Now Wizard to back up.

  2. Choose Schedule Backup. Select a hard disk and schedule backup onto it.

  3. Choose Backup Now and back up the entire server.

Expected results:
Backup is scheduled and no errors are thrown.

Exceptions:
None

Scenario 2 – Schedule a backup from Command Line Interface (CLI)

Goal:
Schedule backup using wbadmin CLI.

Prerequisites or specific configuration for the scenario:
The user should have Target disk storage of more than 2 terabytes.

Applicability:
Server

Step-by-step scenario description:
You can create scheduled backups using the wbadmin enable backup command to configure scheduled backups. For examples and syntax for this command, see the Command Reference (http://go.microsoft.com/fwlink/?LinkId=128733).

Using CLI:

In CLI the command is:

wbadmin start backup -include:C:,D:,E: -backuptarget:F: -allcritical
  • C:,D:,E: is the list of volumes to be included in the backup.

    This should contain the System volume, the boot volume and all the volumes which have system data.

  • F: is the backup target (the volume on which the backup is to be placed). This can be a hard disk volume [internal /external].

    The backup target (F:) must be on a separate disk, and it should be bigger than size(C: + D: + E:). Don’t create F: on Disk 0 alongside C:.

  • The -allcritical flag adds all the critical volumes to the backup set. In this case the volumes that are backed up are the union of C:,D:,E: and the critical volumes on the machine.

The easiest and recommended method is to get a USB external disk and create a huge volume on it and take the backup onto it. Label F: as BackupTarget.

Expected results:
Backup is scheduled and no errors are thrown.

Exceptions:
None

Server Technologies

DNS Server

Quality Improvements in DNS Server

DNS Server is been improved to enable listening over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) addresses.

Key Scenarios

Scenario 1 –Query DNS server on ISATAP address

Goal:
Make sure that DNS server is listening and replying to ISATAP interface addresses.

Prerequisites or specific configuration for the scenario:
ISATAP interface on DNS server should be available, and server should have the DNS Server role installed.

Applicability:
Server

Step-by-step scenario description:
  1. Open Dnsmgmt.msc.

  2. Right-click and open the Interface properties tab.

  3. Make sure that ISATAP Interface is checked.

  4. Clients are IPv6 only.

  5. The default DNS server on client should be the ISATAP address in step 3.

Expected results:
The clients set in Step 5, along with all other clients, should resolve all the DNS queries.

Scenario 2 –File backed secondary MS-DNS server with continuous changes in zone records

Goal:
Verify that incremental zone transfer doesn’t cause any issue for constantly updating zones.

Prerequisites or specific configuration for the scenario:
  • File backed zone with MS-DNS as secondary.

  • Incremental zone transfer interval should be less than 15 min.

  • The records in the particular zone should be frequently and constantly changing.

Applicability:
Server

Step-by-step scenario description:
After a period of 15 minutes, the MS-DNS secondary should have all the records updated.

Expected results:
Incremental zone transfer doesn’t cause any issue for constantly updating zones.

Exceptions:
None

Scenario 3 – File backed Internet facing, heavy load servers.

Goal:
Detect memory leak in Internet-facing, file backed servers.

Prerequisites or specific configuration for the scenario:
  • Server must be Internet-facing.

  • Should host non-AD integrated zones.

  • Recursion Enabled.

Applicability:
Server

Scenario description:
Monitor DNS performance counters for memory usage.

Expected results:
The memory usage by DNS server should not increase over time.

Exceptions:
None

Terminal Services

Quality Improvements in Terminal Services

Windows Server 2008 SP2 Terminal Services has fixed issues to improve reliability, scalability and security.

Key Scenarios

Scenario 1 – Remote Desktop Connection

Goal:
User can do remote desktop connection without the “Version mismatch” error dialog.

Prerequisites or specific configuration for the scenario:
Both client and server machine should be Windows Vista SP2 or Windows Server 2008 SP2.

Applicability:
Server & Client

Step-by-step scenario description:
Run mstsc.exe or launch Remote Desktop from the Start Menu.

Expected results:
Users should be able to launch Remote Desktop successfully.

Exceptions:
None

Scenario 2 – Set session time limits in UserParameter blob in mixed Windows Server 2008 and Windows Server 2003 DC setting

Goal:
Improved interoperability between Windows Server 2008 and Windows Server 2003.

Prerequisites or specific configuration for the scenario:
Set up a domain with 2 DC: one Windows Server 2008, one Windows Server 2003. Join a TS server to the domain, create a test domain user.

Applicability:
Server

Step-by-step scenario description:
  1. Open the UserParameter dialog from dsa.msc on one DC.

  2. Set active session time limit to 5 minutes in the Sessions tab and click Apply.

  3. From another DC open the User Parameter dialog for the same user.

  4. Use the test user account to TS to the TS server.

Expected results:
The active session time limit displayed in the other DC should be 5 minutes too. The TS session should time out after 5 minutes.

Exceptions:
None

Scenario 3 – Remote Desktop should not use TS roaming profile

Goal:
Consistent user experience for Windows Vista SP2.

Prerequisites or specific configuration for the scenario:
Set both the TS profile and the regular roaming profile path for a user (to different location).

Applicability:
Client & Server

Step-by-step scenario description:
Use the test user account to TS to a Windows Vista SP2 client machine.

Expected results:
The regular roaming profile should be applied in this scenario, not the TS profile; in other words, the user should see the same desktop regardless of whether logging in from the console or remotely.

Exceptions:
None

Scenario 4 – MaxConnections setting for TS server

Goal:
MaxConnections setting for Windows Server 2008 TS server should work properly.

Prerequisites or specific configuration for the scenario:
Set up a Windows Server 2008 TS server.

Applicability:
Server

Step-by-step scenario description:
  1. Set MaxInstanceCount of listener to 2 (TSConfig->RDP-TCP->Netwok Adapter->Maximum Connections=2).

  2. Launch 2 remote connections to the machine.

  3. Disconnect one of the active remote connections.

  4. Try to launch another remote connection.

Expected results:
The third session should succeed since there’re only two active sessions.

Exceptions:
None

Scenario 5 – TS SB incorrectly increments PendingRedirection count, upon discovering a disconnected session

Goal:
PendingRedir count should not be incremented for a disconnected session.

Prerequisites or specific configuration for the scenario:
Set up a TS farm with a Session Broker doing the load balancing.

Applicability:
Server

Step-by-step scenario description:
  1. Setup a standard SB farm with two TS servers (A and B).

  2. To make the Repro take less time, create the following reg key in the SB box:

    HKLM\System\Current Control Set\Services\tssdis\parameters [LB_MaxNumberOfPendingRedirections]

  3. Set the key value to 4 (By Default it is 16).

  4. Mstsc using the Farm name. SB will redirect to one of the servers (for example, Server A).

  5. Disconnect the session.

  6. Mstsc again using the Farm name. SB will redirect you to the disconnected session in Server A.

  7. Disconnect/Connect 4 times.

  8. Due to the bug, the PendingRedirection count will increase to 16 (at this point TS A will not be considered for LoadBalancing until TS B has same Pending redirection count).

  9. Mstsc using the Farm name, with a different user name. SB will redirect you to Server B.

  10. Try mstsc with a few more user names. SB will redirect you to Server B every single time, even though Server A has only one active session.

Expected results:
PendingRedir should not be charged for a disconnected session. TS A should be considered for LoadBalancing for the subsequent “new user” connections.

Exceptions:
None

Scenario 6 – RemoteApp MSI omits the last file name extension in the list

Goal:
All file name extension association should be picked up by the MSI.

Prerequisites or specific configuration for the scenario:
Install Terminal Server role in WS 08.

Applicability:
Server

Step-by-step scenario description:
  1. Make sure on the server WordPad is associated with only one file name extension (for example, .txt).

  2. Launch TS Remote App Manager.

  3. Click Add RemoteApp Programs.

  4. Select WordPad from the list.

  5. Click Next.

  6. Click Finish.

  7. Select the published app from the published app list (located in the lower pane of the TS RemoteApp Manager snap-in).

  8. Right-click and select Create Windows Installer Package.

  9. Click Next twice.

  10. On the Configure Distribution Package page, select "Associate client extensions for this program with the RemoteApp Program."

  11. Click Next, and verify that the extension has not been picked up.

  12. Click Finish to generate the MSI.

  13. Just as a double check, install the MSI on the client machine.

  14. Verify that ".txt" has not been associated with Remote WordPad.

Expected results:
The .txt extension on the client side should associate with Remote WordPad.

Exceptions:
None

Directory Services

Quality Improvements in Directory Services

Windows Server 2008 SP2 directory services has fixed issues to improve reliability. Changes have been made to enable Paged Search to search a DC.

Key Scenarios

Scenario 1 – Install From Media with Sysvol pre-seeding

Goal:
User can use IFM with pre-seeded Sysvol to cut down replication traffic while promoting a new DC.

Prerequisites or specific configuration for the scenario:
Existing domain.

Applicability:
Server

Step-by-step scenario description:
  1. Create IFM backup, including Sysvol, on a DC.

  2. Copy the IFM files to the machine that will be promoted.

  3. Promote the new DC using the IFM created in step 1.

Expected results:
Pre-seeded Sysvol was used (verification instructions “Analyzing the Dcpromo.log and Dcpromoui.log files” section of KB311078).

Exceptions:
None

Scenario 2 – Use WMI filters in Group Policy

Goal:
Group Policies that use WMI filters perform as expected.

Prerequisites or specific configuration for the scenario:
Existing domain.

Applicability:
Server

Scenario description:
Setup Group Policy in the domain that uses a WMI filter to determine which machines it is applied to.

Expected results:
No delays are experienced when user logs on.

Exceptions:
None

Scenario 3 – Replication of schema extensions in non-English domains

Goal:
Replication works fine in non-English domains that have AD-integrated applications installed.

Prerequisites or specific configuration for the scenario:
Existing domain, non-English domain (for example, Japanese).

Applicability:
Server

Scenario description:
Install AD-integrated applications that extend the AD Schema (e.g. Exchange 2007).

Expected results:
Replication of all attribute values (including newly introduced attributes) succeeds on all DCs in the domain.

Exceptions:
None

Scenario 4 – Paged Search

Goal:
User can search a DC using paged search.

Prerequisites or specific configuration for the scenario:
Existing domain, large number of objects (> 10,000).

Applicability:
Server

Step-by-step scenario description:
  1. Perform paged searches that retrieve large number of objects per page (> 10,000).

  2. Perform searches nested inside paged searches (for example, perform search on each result of a paged search).

Expected results:
  • Paged search retrieves all objects queried for.

  • Nested searches on base fail; all other nested searches succeed.

Exceptions:
None

Scenario 5 – OpenLDAP queries against AD DC

Goal:
User can interact with AD DC using OpenLDAP libraries.

Prerequisites or specific configuration for the scenario:
Existing domain, Unix-/Linux-based machine with OpenLDAP libraries.

Applicability:
Server

Scenario description:
Perform queries from an OpenLDAP client using any combination of signing and sealing technologies.

Expected results:
Queries should return results as expected.

Exceptions:
None

Scenario 6 – Seizing PDC role in virtual environments

Goal:
User can seize the PDC role from/to virtual machines.

Prerequisites or specific configuration for the scenario:
Existing domain running in Hyper-V environment.

Applicability:
Server

Scenario description:
Seize the PDC using virtual machines as Domain Controllers.

Expected results:
PDC role should be properly seized to the Domain Controller.

Exceptions:
None

Internet Information Services (IIS)

Quality Improvements in IIS

IIS has been enhanced to add query string support for request filtering. With SP2, IIS addresses the token kidnapping issue by allowing adding a new appPool identity.

Key Scenarios

Scenario 1 – New Application Pool Identity

Goal:
Verify the applicationPoolIdentity.

Prerequisites or specific configuration for the scenario:
None

Applicability:
Server

Step-by-step scenario description:
  1. Launch inetmgr UI.

  2. Select the localhost node in the treeview.

  3. Go to Application Pools node in the UI and add a new applicationPool 3.5 (Verification).

  4. Select the newly added applicationPool.

  5. Select the Advanced Settings task from the actions pane.

  6. Restart the application Pool.

  7. Make a request to an aspx page.

Expected results:
  • The new application pool (3.5) that gets created is assigned the ApplicationPoolIdentity.

  • The ApplicationPoolIdentity has 4 options for the Built-in Account radio button (ApplicationPoolIdentity being one of them).

  • The appPool recycles successfully.

  • The worker process (w3wp) runs as the appPool identity.

Exceptions:
None

Scenario 2 - Query string support for Request Filtering module in IIS7 on Windows Server 2008

Goal:
Add new rules for request filtering module in the configuration file. Verify the runtime behavior for different query strings.

Prerequisites or specific configuration for the scenario:
None

Applicability:
Server

Step-by-step scenario description:
  1. Add a new element to DenyQueryStringSequences to “!Query”.

  2. Add a new element for AlwaysAllowedQueryStrings to “Allow =GoodQuery”.

  3. Make a request to an aspx page with the query string “?Allow=GoodQuery”.

  4. Make a request to an aspx page with the query string “?Allow=!Query”.

  5. Make a request to an aspx page with the query string “?Allow= %21Query”.

  6. Set UnescapeQueryString to FALSE.

  7. Make a request to an aspx page with the query string “?Allow=!Query”.

  8. Make a request to an aspx page with the query string “?Allow= %21Query”.

Config snapshot:

<system.webServer>
  <security>
    <requestFiltering unescapeQueryString="true">                  
      <denyQueryStringSequences>
        <add sequence="!Query" />
      </denyQueryStringSequences>
<alwaysAllowedQueryStrings>
<add queryString="Allow=GoodQuery"
</alwaysAllowedQueryStrings>
    </requestFiltering>
  </security>
</system.webServer>
Expected results:
Response status codes:

  • 200 for 3

  • 202 for 8

  • 404 for 4, 5, 7

Exceptions:
None

Clustering and High Availability

Quality Improvements in Clustering and High Availability

Cluster service has been improved, fixing reliability issues reported from various customers.

Key Scenarios

Scenario 1: Virtual machines running on Hyper-V which are part of NLB Cluster work properly if a huge amount of TCP traffic is sent between clients and server

Goal:
Verify that virtual machines running on Hyper-V which are part of NLB Cluster work properly if a huge amount of TCP traffic is sent between clients and server.

Prerequisites or specific configuration for the scenario:
  • Network Adapter should be used, not the Legacy Adapter while configuring adapters for virtual machines.

  • Unicast MAC Address needs to be assigned.

Applicability:
Server

Step-by-step scenario description:
  1. Create a two-node NLB Cluster of virtual machines running on Hyper-V (reference: http://go.microsoft.com/fwlink/?LinkId=128729). The two nodes of the cluster act as the Client.

  2. Take another two machines which are in the same network but not part of the cluster, which will act as the server.

  3. Send a huge amount of TCP/UDP/ICMP traffic between Client and server, roughly greater than 1200 CPS, and check if there is a bug check.

Expected results:
The traffic should flow without causing any break.

Exceptions:
If Legacy Network Adapters are used, then there is no bug check.

Scenario 2 – Deploy a cluster in a disjoint namespace with a File Share Witness for quorum

Goal:
To verify the cluster works fine in a disjoint namespace.

Prerequisites or specific configuration for the scenario:
In an environment with a disjoint namespace, deploy a cluster where its nodes’ DNS suffix portion of its FQDN is not the same as the domain name where the computer is located.

Applicability:
Server

Step-by-step scenario description:
  1. Create a disjoint namespace (reference: http://go.microsoft.com/fwlink/?LinkId=128723).

  2. Create and validate a minimum two-node cluster (reference: http://go.microsoft.com/fwlink/?LinkId=128730).

  3. Bring the cluster online to ensure that the Network Name comes online.

  4. Change the quorum configuration to use a File Share Witness (reference: http://go.microsoft.com/fwlink/?LinkId=129345).

  5. Ensure that the File Share Witness comes online.

Expected results:
The Network Name comes online, the File Share Witness comes online, and the entire cluster is online and functional.

Exceptions:
None

Scenario 3 – Orphaned groups should move to preferred owner

Goal:
Verify that groups move to the preferred owners when they are orphaned.

Prerequisites or specific configuration for the scenario:
A minimum two-node cluster (reference: http://go.microsoft.com/fwlink/?LinkId=128730).

Applicability:
Server

Step-by-step scenario description:
  1. Add two groups, group1 and group2, through Cluadmin.msc with a different list of preferred owners.

    1. Add groups through Services and Application and follow the High Availability Wizard.

    2. Create the preferred owners list from the properties of the groups.

  2. Evict or shut down the active node.

Expected results:
Orphaned groups should move to the next best node listed in the preferred owner list.

Exceptions:
None

Scenario 4 - Cluster disk should not fail when temporary files are stored in the cluster root folder

Goal:
Check that the cluster disks work properly with temporary files in the cluster root folder when I/O operation is happening.

Prerequisites or specific configuration for the scenario:
Set the cluster root folder as the default location for temporary files of highly available workloads.

Applicability:
Server

Step-by-step scenario description:
  1. Deploy a validate cluster running a workload, such as Exchange, which stores temporary files in the cluster root folder.

  2. Ensure that the disk does not fail.

Expected results:
Cluster disk or resources should properly come up and they should not fail intermittently.

Exceptions:
None

Scenario 5 – Hyper-V: Add multiple virtual machines on the same LUN to the same resource group

Goal:
Create a resource group with more than 1 VM.

Prerequisites or specific configuration for the scenario:
Two or more Hyper-V enabled machines.

Applicability:
Server

Step-by-step scenario description:
  1. Create a two-node cluster using Hyper-V Windows Server 2008 machines (reference: http://go.microsoft.com/fwlink/?LinkID=125397).

  2. Open Hyper-V Manager (Control Panel-> Administrative Tools -> Hyper-V Manager).

  3. In Hyper-V Manager, click a node (for example, N1) and then click New -> Create a New VM Wizard.

  4. Create VM1 and save the VM on (for example) Cluster Disk 2.

  5. Create VM2 and use the same Cluster Disk 2 for it.

  6. Open Cluadmin.msc. Under the cluster name, right-click Services and Application.

  7. Go to Configure a Service or Application. This opens up the High Availability (HA) Wizard.

  8. Use the HA Wizard and select both the VMs created in step 3 and 4 - VM1 and VM2 to form a VM group and click Next. The VM group is configured successfully with both VMs in the same group.

  9. Click Services and Application to see that the new VM group configured.

  10. Go to Hyper-V Manager -> Node N1 where the VMs have been created-> Settings for VM1.

  11. Change the vhd file settings (for example, if it’s using Cluster Disk 3 then change it to some other disk, such as 4). Make changes to the vhd file for VM2 in the same way.

  12. On the Cluadmin Wizard, in the Services and Application, click the VM HA group.

  13. On the right-hand side of the wizard page, there are a number of actions for the VM group. Click the Refresh Virtual Machine action.

  14. Click the Refresh action to reflect changes which have taken place in the vhd file for both VM1 and VM2. The new cluster disks added should show up in the VM HA group configuration and the old ones should be removed from it.

  15. Right-click the VMs in the VM HA group and go to Properties. Check the dependencies for both VM1 and VM2. They should reflect the changes done to the VHD file disks.

Expected results:
Both VMs are in the same resource group and can be refreshed successfully.

Exceptions:
The VMC file cannot be changed once created, so no VMC file and VHD file changes on the same disk can be detected. Only vhd file changes to a different disk would be detected during Refresh.

Scenario 6 – Hyper-V: Proper Configuration of VMs when using Clustered disks without drive letter

Goal:
Provide support for clustered disks without a drive letter.

Prerequisites or specific configuration for the scenario:
Two or more Hyper-V enabled machines.

Applicability:
Server

Step-by-step scenario description:
  1. Create a two-node cluster using Hyper-V Windows Server 2008 machines (reference: http://go.microsoft.com/fwlink/?LinkID=125397).

  2. To view the clustered disks, open Cluadmin.msc and go to the Name -> Storage.

  3. Change the drive letter of any one of the clustered disks to None.

  4. Open Hyper-V Manager (Control Panel-> Administrative Tools -> Hyper-V Manager).

  5. Create a VM on the same node (say, N1/N2 for a two-node cluster).

  6. In Hyper-V Manager, Right-click a node (for example, N1) and click New -> Create a New VM Wizard.

  7. Create VM1 and save the VM on the Clustered disk without drive letter using the volume details.

  8. To view volume details for the disk, right-click the disk and select Properties.

  9. Go to the Cluadmin Wizard. Under the Cluster name, right-click Services and Application.

  10. Go to Configure a Service or Application. This opens up the High Availability (HA) Wizard.

  11. Use the HA Wizard and select both the VMs created in step 4 - VM1 to configure a VM HA group and then click Next. The VM group is configured successfully without any errors.

  12. Click Services and Application to see the new VM group configured successfully with the VM configuration and disk resource.

Expected results:
Able to configure the VM using the Clustered disks without drive letter. Also, the disk resource comes up as part of the VM HA group. The resultant VM group contains the VM Configuration, disk resource and VM resource, if any.

Exceptions:
None

Scenario 7 – Deploy a cluster in an environment with a third-party DNS server

Goal:
Ensure a cluster can be successfully created and validated.

Prerequisites or specific configuration for the scenario:
Environment must use a non-Microsoft DNS server.

Applicability:
Server

Step-by-step scenario description:
  1. Create and validate minimum two-node cluster (reference:http://go.microsoft.com/fwlink/?LinkID=128730).

  2. Ensure that when the cluster nodes are specified, their DNS name is resolved to a third-party DNS server and the error message “The Network Name {x} is already in used in the network” is not displayed.

Expected results:
The cluster can be successfully created and validated.

Exceptions:
None

Microsoft SMB Protocol

What is SMB Protocol?

The Server Message Block (SMB) Protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol. The set of message packets that defines a particular version of the protocol is called a dialect. The Common Internet File System (CIFS) Protocol is a dialect of SMB.

Quality Improvements in Microsoft SMB Protocol

Various bugs reported in SMB have been fixed in areas like reliability, compatibility and security.

Key Scenarios

Scenario 1 – Applying Group Policy settings

Goal:
Customer should be able to apply Group Policy settings correctly.

Prerequisites or specific configuration for the scenario:
Enable the following policies on Windows Server 2003 DC and join the Windows Vista SP2 computer to the domain.

The following policies are enabled on a domain controller that is running Windows Server 2003 in a domain:

  • Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Digitally sign communications (always)

  • Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Digitally sign communications (if client agrees)

The following policies are enabled on a member computer that is running Windows Vista SP2:

  • Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (always)

  • Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (If server agrees)

Applicability:
Server

Step-by-step scenario description:
  1. Perform the above configuration.

  2. Restart Windows Vista SP2 machine.

Expected results:
Group Policy Settings applied correctly (see http://go.microsoft.com/fwlink/?LinkId=128731).

Exceptions:
None

Scenario 2 – Multiple Users accessing a file

Goal:
Customer should be able to access the same file from multiple sessions.

Prerequisites or specific configuration for the scenario:
Create a share on Windows Server 2003 and grant Read/Write permissions to two Windows Vista SP2 clients. Put an Excel document inside the share.

Applicability:
Server

Step-by-step scenario description:
  1. Open the Excel document from the first client.

  2. Open the Excel document from the second client and modify contents.

  3. Close Excel document from the first client and reopen it.

Expected results:
First client should see updated data.

Exceptions:
None

Scenario 3 – Changing attributes of file shares or removing shares from machine

Goal:
Customer should be able to change the attributes of a share and delete shared directories without errors.

Prerequisites or specific configuration for the scenario:
Windows Vista SP2 machine and Windows XP SP2 machine as client.

Applicability:
Server

Step-by-step scenario description:
  1. Create a directory on Windows Vista SP2 machine and share it with Read/Write permissions.

  2. From the XP machine create files and folders.

  3. Change share permission/attributes on share.

  4. After some time, on the Windows Vista SP2 machines remove the share and delete the folder.

Expected results:
The share should be deleted from machine and folder should be able to be deleted with no errors.

Exceptions:
None

Scenario 4 – SMBHelperClass can return incorrect diagnosis for access denied

Goal:
Customer should get accurate information from SMBHelperClass in situations where user doesn’t have access to share resource.

Prerequisites or specific configuration for the scenario:
Windows Server 2008 machine and Windows Vista SP2 client.

Applicability:
Server

Step-by-step scenario description:
  1. Set up a share \\Server\test where test is a DFS namespace.

  2. Try accessing the \\Server\test\abcd (from start -> run), where user doesn’t have access to test.

Expected results:
SMBHelperClass should return that user doesn’t have access to the resource.

Exceptions:
None

Scenario 5 – SMB sessions not being cleaned up on server machine

Goal:
All SMB sessions should be cleaned up after all sessions are closed to server machine.

Prerequisites or specific configuration for the scenario:
Install two Windows Vista multi processor boxes and connect workgroup network.

Applicability:
Server

Step-by-step scenario description:
  1. Create the same user account on each machine and logon this user.

  2. Create a network share on one (for example, \\testpc1\share1) and give access permission.

  3. Access a shared resource multiple times from the same computer.

Expected results:
After some time of inactivity on the share all the sessions should be cleaned up. Use ‘net session’ to verify.

Exceptions:
None

Scenario 6 – Interop with earlier versions of operating system

Goal:
Make sure that the interop with down-level operating system is working correctly.

Prerequisites or specific configuration for the scenario:
Install Windows Server 2008, Windows Server 2003, Windows XP, Windows 2000, and NT4.

Applicability:
Server

Step-by-step scenario description:
  1. Create network shares on each server and give appropriate share permissions.

  2. Access shared resource from all different machines.

Expected results:
Files should be accessible as expected.

Exceptions:
None

Message Queuing

Quality Improvements in Message Queuing

Message Queuing (also known as MSMQ) has increased security, reliability, and usability of Message Queuing. Message Queuing now supports SHA2 HTTP/Multicast message.

Key Scenarios

Scenario 1 – Message Queuing masvc.exe security fix

Goal:
Verify impact of Windows mqsvc.exe security fix.

Prerequisites or specific configuration for the scenario:
Windows 2000 and Windows NT4 server configured with MSMQ.

Applicability:
Server

Step-by-step scenario description:
  1. Create a queue with names of different lengths (small, medium, large, etc.) and reference the computer name for the queues to be created on via a fully qualified domain name.

  2. Repeat step 1 using a dependent client/supporting server configuration.

  3. Perform basic send/receive tests using public, private, transactional, and non-transactional queues.

Expected results:
No memory leak or blue screen occurs.

Exceptions:
None

Scenario 2 – Start Message Queuing when HTTP-FIPS enabled

Goal:
Verify Message Queuing functionality when HTTP FIPS is enabled.

Prerequisites or specific configuration for the scenario:
Install target Windows operating system with IIS/Message Queuing configured.

Applicability:
Server

Step-by-step scenario description:
  1. Disable FIPS, and stop Message Queuing service.

  2. Enable FIPS, and then try to start Message Queuing service.

  3. Perform basic send/receive tests using HTTP message.

Expected results:
Message Queuing service can start when FIPS is enabled.

Exceptions:
None

Scenario 3 – Message Queuing works with SHA2 for HTTP / Multicast message.

Goal:
Verify Message Queuing functionality when user requests SHA2 for HTTP or Multicast messages.

Prerequisites or specific configuration for the scenario:
Install target Windows operating system with IIS/Message Queuing configured.

Applicability:
Server

Step-by-step scenario description:
Enable SHA2 for authentication when sending HTTP or multicast messages.

Expected results:
No system hung or blue screen occurs.

Exceptions:
None

Virtual Disk Service

What is Virtual Disk Service?

Virtual Disk Service (VDS) is a set of application programming interfaces (APIs) that provides a single interface for managing disks. VDS provides an end-to-end solution for managing storage hardware and disks, and for creating volumes on those disks.

For more information about VDS, please see the following TechNet article: http://go.microsoft.com/fwlink/?linkid=50517.

What’s New in Virtual Disk Service?

VDS has been changed to improve stability and reliability. On IA64 processor, VDS can now enable to extend/shrink of dynamic discs.

Key Scenarios

Scenario 1 – Dynamic Disks on Cluster scenarios

Goal:
Customer should be able to use two LOCAL disks on different ports in order to configure dynamic disks.

Prerequisites or specific configuration for the scenario:
Cluster system should be setup and there should be two local disks on different ports.

Applicability:
Server

Step-by-step scenario description:
  1. Build a cluster system.

  2. Use two local disks on different ports.

  3. Using diskpart, try to configure the disk on the second port to be a dynamic disk.

Expected results:
The disk should be converted to dynamic correctly.

Exceptions:
None

Scenario 2 – Extend/Shrink on IA64 boot partition

Goal:
Extend/Shrink should work correctly on IA64 scenarios.

Prerequisites or specific configuration for the scenario:
IA64 machine & GPT disks.

Applicability:
Server

Step-by-step scenario description:
  1. Convert a system disk to dynamic disk.

  2. Restart.

  3. Shrink or extend system volume.

  4. Restart.

Expected results:
The machine should come back and you should be able to start your system.

Exceptions:
None

Scenario 3 – Block shrink on dynamic Logical Unit Number (LUN)

Goal:
Shrinking of a dynamic Logical Unit Number (LUN) should be blocked as it is not a supported scenario and could result in data loss.

Prerequisites or specific configuration for the scenario:
SAN environment with LUNs.

Applicability:
Server

Step-by-step scenario description:
  1. Create a LUN of a certain size (for example, 10GB).

  2. Unmask the LUN to a machine.

  3. Initialize the disk that appears on the machine that corresponds to the LUN and create a simple NTFS volume on it that is smaller than the LUN size (for example, 5GB).

  4. Convert this disk to Dynamic.

  5. Using diskraid, attempt to shrink the LUN size by 1GB.

Expected results:
Shrink of the LUN should be blocked by disk raid. Error message should read “The SHRINK operation against the selected LUN cannot be completed. The current state of the disk associated with the LUN is DYNAMIC.”

Exceptions:
None

Scenario 4 – Block extends on volumes that will exceed the maximum FS size

Goal:
User should not be able to extend their volumes past the maximum file system size.

Prerequisites or specific configuration for the scenario:
Large amount of disk space (more than 2 terabytes).

Applicability:
Server

Step-by-step scenario description:
  1. On your large disk, create a simple volume of size 1.5 terabytes using the disk management UI.

  2. When on the format partition page, make sure to select an Allocation unit size of ‘512’. This will cause the maximum file system size to be 2 terabytes.

  3. After the volume is created and formatted, attempt to extend the volume by 1 terabyte.

Expected results:
The extend operation should fail.

Exceptions:
None

ADFS

What is ADFS?

ADFS is a component in Windows Server 2008 that provides Web single-sign-on (SSO) technologies to authenticate a user to multiple Web applications over the life of a single online session. ADFS accomplishes this by securely sharing digital identity and entitlement rights, or "Claims," across security and enterprise boundaries.

For more information about ADFS, please see the following TechNet article: http://go.microsoft.com/fwlink/?LinkId=128726

What’s changed in ADFS?

In ADFS federated trusts are made non-transitive.

Key Scenarios

Scenario 1 – Transitive Federated Trusts

Goal:
Federated trusts are not transitive

Prerequisites or specific configuration for the scenario:
None

Applicability:
Server

Step-by-step scenario description:
  1. Set up ADFS trust between configurations A and B such that A is the account partner and B is the resource partner.

  2. Set up ADFS trust between configurations B and C such that B is the account partner and C is the resource partner.

  3. Create a claims-aware application on configuration C that allows access by users from configuration B’s domain (through the federated trust).

  4. Create a claims-aware application on configuration B that allows access by users from configuration A’s domain (through the federated trust) and also includes a link to the claims-aware application on configuration C (see step 3).

  5. Access the claims-aware application on configuration B as a user from configuration A’s domain.

  6. Click through to the claims-aware application on domain C.

Expected results:
The claims-aware application in configuration B should load properly. The claims-aware application in configuration C should not load properly.

Exceptions:
None

Client Technologies (Applicable to both Server & Client)

Windows Search

Quality Improvements in Windows Search

Windows Search has been improved for users to see noticeable differences in overall performance, stability, and reliability of Windows Search. 85%+ Watson reported crashes for Windows Search have been fixed. Query performance improvements have been made. Windows Search now indexes shared folders by default, encrypted documents (optional), and delegate mailboxes (optional). Additional group policies have been created in response to enterprise customer requests.

Key Scenarios

Scenario 1 – Improved search performance, stability, reliability

Goal:
Observe improvements to search.

Prerequisites or specific configuration for the scenario:
SP2 is installed and index is built.

Applicability:
Client

Scenario description:
Observe that in general there are fewer indexer crashes; improved ability for index and registry to recover from corruption events.

Expected results:
Search just works better.

Exceptions:
None

Scenario 2 – Search and find what I need, fast and effectively

Goal:
Effectively find all your data.

Prerequisites or specific configuration for the scenario:
SP2 is installed. Activate ‘advanced’ option to include “encrypted files” into the index. Wait for the index to be built. Activate Group Policy to index delegate mailboxes.

Applicability:
Client

Step-by-step scenario description:
  1. Click the Start Button.

  2. In the Start Menu Search Box type query.

  3. Start Menu results view appears. Items are in the result list but none of them are the item that you’re looking for.

  4. From the Start Menu results view click the “Search everywhere” link.

  5. Explorer launches with the full results list.

  6. Scroll through the results in a view that includes your own e-mails, e-mail from your delegate mailbox, and documents that may or may not be encrypted.

  7. Sort or group by type or kind.

Expected results:
  • Common search and browse queries are fast.

  • Search results are efficiently presented.

  • Search results include documents that are encrypted (EFS).

  • Search results include mail items that the user owns or has access to. (Delegate mail access.)

Exceptions:
None

Copy Engine

Quality Improvements in Copy Engine

Copy Engine has been improved to detect accurate free space of the reparse point destination (DFS, junction, symbolic links and mount points).

Key Scenarios

Scenario 1 – Copy file to share folder (share folder\folder)

Goal:
Verify the copy function on share folders by copying a file to a share folder or folder using Map Drive or UNC path.

Prerequisites or specific configuration for the scenario:
  • When testing on SMBv1 use Windows Server 2003 as a server. For SMBv2 use Windows Server 2008 as a server.

  • D drive with 1GB free space.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Create the mainFol folder on D drive.

  2. Create the subFol folder under D:\mainFol.

  3. Share the mainFol folder.

  4. On the SP2 machine, map a drive (for example, Z) to \\server\mainFol\subFol.

  5. Copy a file from the SP2 machine to Z:\ or “\\server\mainFol\subFolCreate” the mainFol folder on the D drive.

Expected results:
  • File size <= 1GB copies successfully.

  • File size > 1GB fails to copy.

Exceptions:
None

Scenario 2 – Copy file to share folder (share folder\mount point)

Goal:
Verify the copy function on share folder by copying file to share folder\mount point using Map Drive or UNC path.

Prerequisites or specific configuration for the scenario:
  • When testing on SMBv1 use Windows Server 2003 as a server. For SMBv2 use Windows Server 2008 as a server.

  • D drive with some free space (suggest 1GB).

  • E drive with more free space than D drive (suggest 5GB).

Applicability:
Server & Client

Step-by-step scenario description:
  1. Create the mainFol folder on D drive.

  2. Create the subMP folder under D:\mainFol.

  3. Mount the subMP folder to E drive. (For instructions, see http://go.microsoft.com/fwlink/?LinkId=128893.)

  4. Share the mainFol folder.

  5. On SP2 machine, map a drive (for example, Z) to \\server\mainFol\subMP.

  6. Copy a file from the SP2 machine to Z:\ or “\\server\mainFol\subMPCreate” the mainFol folder on the D drive.

Expected results:
  • File size <= 5GB copies successfully.

  • File size > 5GB fails to copy.

Exceptions:
None

Scenario 3 – Copy file to share folder (share folder\symbolic link)

Goal:
Verify the copy function on share folder by copying file to share folder\symbolic link using map drive or UNC path.

Prerequisites or specific configuration for the scenario:
  • When testing on SMBv1 use Windows Server 2003 as a server. For SMBv2 use Windows Server 2008 as a server.

  • D drive with some free space (suggest 1GB).

  • E drive with more free space than D drive (suggest 5GB).

Applicability:
Server & Client

Step-by-step scenario description:
  1. Create the mainFol folder on drive D.

  2. Create the subLink directory junction under D:\mainFol and point to drive E (D:\mainFol>mklink /j subLink E:\).

  3. Share the mainFol folder.

  4. On the SP2 machine, map a drive (for example, Z) to \\server\mainFol\subLink.

  5. Copy file from the SP2 machine to Z:\ or \\server\mainFol\subLink.

Expected results:
  • File size <= 5GB copies successfully.

  • File size > 5GB fails to copy.

Exceptions:
None

Scenario 4 – Copy file to reparse point (DFS\DFS)

Goal:
Verify the copy function on reparse point by copying file to DFS\DFS using map drive or UNC path.

Prerequisites or specific configuration for the scenario:
  • When testing on SMBv1 use Windows Server 2003 as a server. For SMBv2 use Windows Server 2008 as a server.

  • D drive with some free space (suggest 1GB).

  • E drive with more free space than D drive (suggest 5GB).

Applicability:
Server

Step-by-step scenario description:
  1. Create the mainDFS folder on D:\ and share this folder.

  2. Create the subDFS folder on E:\ and share this folder.

  3. Host the DFS root to mainDFS.

  4. Create new link under mainDFS point to subDFS.

  5. On SP2 machine, map a drive (for example, Z) to \\server\mainDFS\subDFS.

  6. Copy file from SP2 machine to Z:\ or \\server\mainDFS\subDFS.

Expected results:
  • File size <= 5GB copies successfully.

  • File size > 5GB fails to copy.

Exceptions:
None

Scenario 5 – Copy file to reparse point (DFS\mount point)

Goal:
Verify the copy function on reparse point by copying a file to DFS\mount point using Map Drive or UNC path.

Prerequisites or specific configuration for the scenario:
  • When testing on SMBv1 use Windows Server 2003 as a server. For SMBv2 use Windows Server 2008 as a server.

  • D drive with some free space (suggest 1GB).

  • E drive with more free space than D drive (suggest 5GB).

Applicability:
Server

Step-by-step scenario description:
  1. Create the mainDFS folder on D:\ and share this folder.

  2. Create the subMP folder under D:\mainDFS.

  3. Mount the subMP folder to E drive. (For instructions, see http://go.microsoft.com/fwlink/?LinkId=128893.)

  4. Host the DFS root to mainDFS.

  5. On SP2 machine, map a drive (for example, Z) to \\server\mainDFS\subMP.

  6. Copy file from SP2 machine to Z:\ or \\server\mainDFS\subMP.

Expected results:
  • File size <= 5GB copies successfully.

  • File size > 5GB fails to copy.

Exceptions:
None

Scenario 6 – Copy file to reparse point (DFS\symbolic link)

Goal:
Verify the copy function on reparse point by copying file to DFS\symbolic link using map drive or UNC path.

Prerequisites or specific configuration for the scenario:
  • When testing on SMBv1 use Windows Server 2003 as a server. For SMBv2 use Windows Server 2008 as a server.

  • D drive with some free space (suggest 1GB).

  • E drive with more free space than D drive (suggest 5GB).

Applicability:
Server

Step-by-step scenario description:
  1. Create the mainDFS folder on D:\ and share this folder.

  2. Create the subLink directory junction under D:\mainDFS point to E drive (D:\mainDFS>mklink /j subLink E:\).

  3. Host the DFS root to mainDFS.

  4. On SP2 machine, map a drive (for example, Z) to \\server\mainDFS\subMP.

  5. Copy file from SP2 machine to Z:\ or \\server\mainDFS\subMP.

Expected results:
  • File size <= 5GB copies successfully.

  • File size > 5GB fails to copy.

Exceptions:
None

Scenario 7 – Copy file to multiple reparse point (DFS\DFS\mount point)

Goal:
Verify the copy function on multiple reparse point by copying file to DFS\DFS\mount point using map drive or UNC path.

Prerequisites or specific configuration for the scenario:
  • When testing on SMBv1 use Windows Server 2003 as a server. For SMBv2 use Windows Server 2008 as a server.

  • D drive with some free space (suggest 1GB).

  • E drive with more free space than D drive (suggest 5GB).

Applicability:
Server

Step-by-step scenario description:
  1. Create the mainDFS folder on D:\ and share this folder.

  2. Create the subDFS folder on D:\ and share this folder.

  3. Create the subMP folder under D:\subDFS.

  4. Mount the subMP folder to E drive. (For instructions, see http://go.microsoft.com/fwlink/?LinkId=128893.)

  5. Host the DFS root to mainDFS.

  6. Create new link under mainDFS that points to subDFS.

  7. On SP2 machine, map a drive (for example, Z) to \\server\mainDFS\subDFS\subMP.

  8. Copy file from SP2 machine to Z:\ or \\server\mainDFS\subDFS\subMP.

Expected results:
  • File size <= 5GB copies successfully.

  • File size > 5GB fails to copy.

Exceptions:
None

Scenario 8 – Copy file to multiple reparse point (DFS\DFS\symbolic link)

Goal:
Verify the copy function on multiple reparse point by copying file to DFS\DFS\symbolic link using map drive or UNC path.

Prerequisites or specific configuration for the scenario:
  • When testing on SMBv1 use Windows Server 2003 as a server. For SMBv2 use Windows Server 2008 as a server.

  • D drive with some free space (suggest 1GB).

  • E drive with more free space than D drive (suggest 5GB).

Applicability:
Server

Step-by-step scenario description:
  1. Create the mainDFS folder on D:\ and share this folder.

  2. Create the subDFS folder on D:\ and share this folder.

  3. Create the subMP folder under D:\subDFS.

  4. Mount the subMP folder to E drive. (For instructions, see http://go.microsoft.com/fwlink/?LinkId=128893.)

  5. Host the DFS root to mainDFS.

  6. Create new link under mainDFS that points to subDFS.

  7. On SP2 machine, map a drive (for example, Z) to \\server\mainDFS\subDFS\subMP.

  8. Copy file from SP2 machine to Z:\ or \\server\mainDFS\subDFS\subMP.

Expected results:
  • File size <= 5GB copies successfully.

  • File size > 5GB fails to copy.

Exceptions:
None

Desktop Shell

Quality Improvements in Desktop Shell

Custom properties have been enabled to be indexed by Legacy IS on Windows Vista.

Key Scenarios

Scenario 1 – Tablet machine Logon UI in different DPIs

Goal:
Improve end user experience with Logon UI in different DPIs.

Prerequisites or specific configuration for the scenario:
Windows Vista SP2 running in a tablet machine.

Applicability:
Tablet Client

Scenario description:
Use different DPI values for better visibility. By changing this, the font/text size is affected globally on all components in Windows.

Expected results:
Logon screen should be able to scale properly (User ID, PW edit boxes and the on-screen keyboard).

Exceptions:
Logon screen is broken; user/pw edit boxes are overlapped.

Scenario 2 – Testing with low level integrity applications

Goal:
Improve application compatibility of Windows Vista SP2.

Prerequisites or specific configuration for the scenario:
Windows Vista SP2

Applicability:
Client

Step-by-step scenario description:
  1. Windows Vista SP2 introduces the Integrity Mechanism to improve the security architecture of the operating system but it sometimes bring some troubles to third parties who write applications for Windows but are not aware of this.

  2. Test should be done with low integrity applications. IE is an example and its embedded applications (ActiveX, Plug-ins, etc.).

Expected results:
Low integrity applications work well.

Exceptions:
Sometimes we do have problems reported by third parties that their applications cannot access resources that are designed for low integrity level application. LocalLow folder is one of the local resources designed for low integrity application.

Scenario 3 – Network and Sharing Center with power management

Goal:
Improve reliability of Network and Sharing Center components.

Prerequisites or specific configuration for the scenario:
Windows Vista SP2

Applicability:
Client

Step-by-step scenario description:
  1. Disable all network interfaces (wired, wireless, etc.).

  2. Put machine in sleep/hibernate mode.

  3. Wake up machine.

  4. Enable/Disable, Plug/Unplug network cable.

Expected results:
Network status and icons show property in Control Panel\Network and Internet\Network and Sharing Center.

Exceptions:
Icons do not match; sometimes machine is connected but the Disconnected icon shows up.

Scenario 4 – Use custom icons for Credential Provider

Goal:
Improve user experience in using Credential Provider.

Prerequisites or specific configuration for the scenario:
Windows Vista SP2 with Customer Credential Provider installed. The test scenario is somehow complex since we need to build an example of a credential provider.

Applicability:
Client

Step-by-step scenario description:
  1. Customer wants to use different icons in their implementation of Credential Provider to improve the end user experience.

  2. Customer changed some lines of code as documented to show the customized icons on LogonUI screen but it did not work because the feature in our LogonUI component had not been implemented.

Expected results:
Valid icons showed.

Exceptions:
Expected icon does not show up.

Miscellaneous

Setup

This section describes several test scenarios for installing Windows Vista SP2 and Windows Server 2008 SP2 using the standalone installer. For other methods of deploying Windows Vista SP2 and Windows Server 2008 SP2 please refer to the deployment guidance document.

The installer also supports several command-line options, which makes it easy to script the installation process.

What’s New in Setup?

Significant improvements were made to the SP2 standalone installer.

  • Single installer for both Windows Vista and Windows Server 2008.

  • Ability to detect an incompatible driver and block service pack installation or warn users of any potential loss of functionality.

  • Better error handling and descriptive error messages where possible.

  • Better manageability through logging in system event log.

  • Secure install experience.

  • Ability to service the installer post release.

Key Scenarios

Scenario 1 – Standalone install experience

Goal:
Verify the service pack install experience.

Prerequisites or specific configuration for the scenario:
Machine is already on Windows Vista SP1 (client) or is a Windows Server 2008 machine.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Copy Windows6.0-KB948465-<arch>.exe to your hard disk.

  2. Double-click Windows6.0-KB948465-<arch>.exe.

  3. The SP2 Setup Wizard will guide you through the install experience. If you have a Windows Vista SP2 Update DVD, it will automatically prompt you with the Setup Wizard when the DVD is inserted.

Expected results:
To confirm that SP2 is successfully installed, perform the following steps:

  1. Right-click Computer.

  2. Click Properties.

You will find a reference to the Service Pack 2 in the Windows Edition section.

Exceptions:
  • In case you have a driver/hot fix which will not work in conjunction with SP2, the installer will display an error message.

  • In case of disk corruption, the installer will fail and prompt you with the correct error code.

  • If you have any other language pack installed other than English, German, Japanese, Spanish and French, the Service Pack install will be blocked.

Windows Portable Devices

Quality Improvements in Windows Portable Devices

Windows Portable Devices has been fixed to support storage card on T-Mobile Dash. Scalability improvements have been made.

Key Scenarios

Scenario 1 - Sync content to storage card on T-Mobile Dash / smart phones

Goal:
Verify storage cards are enumerated and usable in T-Mobile Dash and other smart phones.

Prerequisites or specific configuration for the scenario:
Windows Vista SP2 SLP or Windows Vista SP1 + SP2, T-Mobile Dash or other Smartphone with storage card.

Applicability:
Client

Step-by-step scenario description:
  1. Install storage card in Smartphone.

  2. Connect via USB cable to computer running Windows Vista SP2.

  3. Open Windows Media Player.

  4. Click Sync.

  5. Verify that the device main storage appears in upper right corner.

  6. Verify that the Smartphone’s storage card appears and that you can sync content to it.

Expected results:
The Smartphone’s storage card appears and you can sync content to it.

Exceptions:
Sync content to device’s main storage.

Scenario 2 - Move a large number of files/folders on the same volume

Goal:
Improve performance when moving files/folders on the same volume.

Prerequisites or specific configuration for the scenario:
The user should have a folder containing 20000 or more files/folders.

Applicability:
Client

Step-by-step scenario description:
  1. Select a folder that contains a large number of items.

  2. Move the folder to another folder on the same volume.

Expected results:
Files/folders are moved nearly instantaneously.

Exceptions:
  • Move files/folders from the Desktop (not Desktop Folder).

  • Move files/folders from and to the drive’s root (for example, C:\ ).

RPC

Quality Improvements in RPC

Remote Procedure Calls (RPC) now enables number of methods on COM to be greater than 1024. Changes have been made to make RPC more reliable.

Key Scenarios

Scenario 1 – Callback Scenario

Goal:
User can use callbacks in multiple scenarios.

Prerequisites or specific configuration for the scenario:
None

Applicability:
Server & Client

Step-by-step scenario description:
  1. Create RPC interface with multiple callback functions.

  2. Run a code path that makes multiple callbacks (e.g., Server -> Client -> Server -> Client).

Expected results:
Callbacks complete as expected; no memory leaks seen in the application.

Exceptions:
None

Scenario 2 – Large COM interface

Goal:
User can use COM interface with large number of methods on 64-bit systems.

Prerequisites or specific configuration for the scenario:
64-bit system.

Applicability:
Server & Client

Scenario description:
Create COM interface with large number of methods (>1024).

Expected results:
Calls to any method in the interface complete as expected.

Exceptions:
None

Windows Media & Media Centre

Quality Improvements in Windows Media & Media Centre

Windows Media fixed issues to improve experience with media files embedded in Web pages. Media Centre has fixed various issues to improve overall experience with Windows TV.

Key Scenarios

Scenario 1 – Play media embedded files in Internet Explorer

Goal:
Play/Refresh Internet Explorer media embedded files.

Prerequisites or specific configuration for the scenario:
Have various .html/.htm files embedded with Movie/Sound.

Applicability:
Client

Step-by-step scenario description:
  1. Open the page in Internet Explorer.

  2. Keep pressing Refresh/F5 very fast.

Expected results:
No crash in IE.

Exceptions:
None

Scenario 2 – Living room scenario

Goal:
Use media center to watch TV, schedule TV programs, and play with all the media controls on the computer and through the extender from the living room while the computer is in the den.

Prerequisites or specific configuration for the scenario:
Windows Vista SP2 set up with TV tuner hooked up to the cable connection.

Applicability:
Media Centre Client

Scenario description:
Change the TV channels, change the media center window focus, watch/record content protected channels, record different series of programming and playback of those recordings should work fine.

Expected results:
All the above features should work fine.

Exceptions:
None

WMI

What’s Changed in WMI?

Event Log entries are returned by WMI provider in ascending order (newest to oldest), same as default ordering in the event viewer. Before SP2, unlike Windows XP/Server 2003, the results were returned oldest to newest. Reliability issues when WMI calls were made in Setup and operating system update programs have been fixed.

Key Scenarios

Scenario 1 – Event log entries are returned in proper order by WMI provider as event viewer default ordering

Goal:
Check that event log entries are coming in proper order and scripts extracting data from WMI nteventlog provider working properly on Windows Server 2003/XP are working fine.

Prerequisites or specific configuration for the scenario:
There should be at least 2 records in the System Event Log.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Retrieve event log entries using WMI event log provider.

  2. Compare returned results with default ordering in the default event viewer of system.

Expected results:
  • Check all the records returned by the script in command window. Record Number field should decrease from top to bottom.

  • Verify against the top 5 events in the Event viewer also. These should match.

Exceptions:
None

Supporting script:
  1. Save following scripts in a VBS file (say, TESTSP2EventLog.vbs).

    strComputer = "."
    Set objWMIService = GetObject("winmgmts:" _
        & "{impersonationLevel=impersonate}!\\" _
        & strComputer & "\root\cimv2")
    
    Set colLoggedEvents = objWMIService.ExecQuery _
        ("Select * from Win32_NTLogEvent " _
            & "Where Logfile = 'System'")
    
    i=0
    
    For Each objEvent in colLoggedEvents
        Wscript.Echo "Event Code: " & objEvent.EventCode & VBNewLine _
        & "Source Name: " & objEvent.SourceName & VBNewLine _
        & "Message: " & objEvent.Message & VBNewLine _
        & "Category: " & objEvent.Category & VBNewLine _
        & "Record Number: " & objEvent.RecordNumber & VBNewLine _
        & "Time Written: " & objEvent.TimeWritten & VBNewLine _
       
        i = i+1
        if (i>=5) then Exit For
    Next
    
    
  2. Open command prompt.

  3. Run this script from any SP2 machine using the command “cscript TESTSP2EventLog.vbs”.

Scenario 2 – Avoiding deadlock when using chained WMI methods during the OOB operating system installations

Goal:
No deadlocks observed during setup which can be attributed to WMI failures.

Prerequisites or specific configuration for the scenario:
Applicable for setup scripts/programs.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Add setup scripts as part of full operating system installation.

  2. Install full operating system using Windows Deployment Services.

Expected results:
System should not hang during installation, which would require a system restart and potential loss of data.

Exceptions:
None

Scenario 3 – Operating system update is not failing randomly and returning back to the previous version

Goal:
Operating system updates are not failing due to hung WM.

Prerequisites or specific configuration for the scenario:
None

Applicability:
Server & Client

Scenario description:
Install Windows Vista/Windows Server 2008 SP2 using update method.

Expected results:
Update should not fail.

Exceptions:
None

Scenario 4 – SNMP Event log Extension agent initialization

Goal:
No Errors are logged when initializing SNMP Event log extension post Update or upgrade.

Prerequisites or specific configuration for the scenario:
SNMP feature is installed before update/upgrade.

Applicability:
Server & Client

Step-by-step scenario description:
  1. Install Windows Vista SP2 / Windows Server 2008 SP2 and enable SNMP feature.

  2. Verify no specified Error Event regarding EventAgent in Application Event Log after restart.

  3. Install SP2 using update/upgrade method and restart.

Expected results:
No new event log error entries with Event ID 3003, 2019, 1020 identifying SNMP Event log extension as source of event.

Exceptions:
None

Scenario 5 – Memory leak in WMI Hi-Perf providers using IWbemRefresher::Refresh

Goal:
No memory leaks are observed in the Hi-Perf providers the interface IWbemRefresher::Refresh.

Prerequisites or specific configuration for the scenario:
None

Applicability:
Server & Client

Step-by-step scenario description:
  1. Create a WMI Hi-Perf provider which will use the interface IWbemRefresher::Refresh. (Check http://go.microsoft.com/fwlink/?LinkId=128728 for guidance.)

  2. Let the provider run on the system continuously. For success, multiple copies can be run at once.

  3. Check memory utilization (Private Bytes) of the process using performance monitor.

Expected results:
There should not be much change in the memory utilization of the process over period of time, say 1 hour.

Exceptions:
None

Scenario 6 – Memory leak when queries are fired against large domains

Goal:
No memory leaks are observed when running WMI queries against large domains.

Prerequisites or specific configuration for the scenario:
Need a large domain deployment with at least 1000 accounts and 100s of groups.

Applicability:
Server

Step-by-step scenario description:
  1. On big domain based deployment, run these queries from WMI on a domain-joined machine:

    SELECT * FROM Win32_UserAccount
    SELECT Domain, Name, SidType FROM Win32_Group
    
    
  2. Observe memory utilization of the process WMIPRVSE.exe.

Expected results:
Check memory utilization of all WMIPRVSE.exe processes using TaskMgr or any other tool. It should not increase appreciably over a period of time.

Supporting script:
  1. Save the following scripts in a VBS file (say, TESTSP2MemLeak.vbs).

    wbemFlagReturnImmediately = 16
    Dim oWMI, nCnt, IFlags, obj, objs
    IFlags = wbemFlagReturnImmediately
    Set oWMI = GetObject("winmgmts:\root\cimv2")
    
    Wscript.Echo "Waiting for maximum 10000 records..."
    
    Set objs = oWMI.ExecQuery ("SELECT * FROM Win32_UserAccount",,IFlags)
    For Each obj in objs
        nCnt = nCnt + 1
        Wscript.Echo "#" & nCnt & ": " & obj.FullName
        if nCnt=10000 then exit for
    Next
    
    Set obj = nothing
    Set objs = nothing
    nCnt=0 
    Wscript.Echo "Waiting for maximum 10000 records..."
    Set objs = oWMI.ExecQuery ("Select Domain, Name, SidType from Win32_Group",,IFlags)
    For Each obj in objs
        nCnt = nCnt + 1
        Wscript.Echo "#" & nCnt & ": " & obj.Domain & "\\" & obj.Name & "- SidType: " & obj.SidType
        if nCnt=10000 then exit for
    Next
    
    Set obj = nothing
    Set objs = nothing
    Set oWMI = nothing
    
    
  2. Open a command prompt.

  3. Run this script from domain joined machine using the command “cscript TESTSP2MemLeak.vbs”.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.