Windows Server 2008 R2 and Windows 7 Service
Pack 1 Test Focus Guide
Microsoft Corporation
Published: March 2010
Author: Srini Puvvada & Qunshu Zhang
Abstract
This document focuses on key changes introduced with SP1 on both Windows Server 2008 R2
(“Server”) and Windows 7 (“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.
Such prerequisites are also mentioned for each scenario.
Copyright Information
Information in this document, including URL and other Internet Web site references, is subject
to change without notice. Unless otherwise noted, the companies, organizations, products,
domain names, e-mail addresses, logos, people, places, and events depicted in examples herein
are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred. Complying with all
applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval
system, or transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), or for any purpose, without the express written permission of
Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you
any license to these patents, trademarks, copyrights, or other intellectual property.
© 2010 Microsoft Corporation. All rights reserved.
Active Directory, Microsoft, MS-DOS, Visual Basic, Visual Studio, Windows, Windows NT,
Windows Vista, Windows 7 and Windows Server are trademarks of the Microsoft group of
companies.
All other trademarks are property of their respective owners.
Contents
Windows 7 SP1 / Windows Server 2008 R2 SP1 Test Focus Guide ................................................. 5
Scope of This Document .............................................................................................................. 5
Providing Feedback ...................................................................................................................... 5
Major Changed Components ....................................................................................................... 6
SP1 Beta Test Guidance for IHV ................................................................................................... 8
Test Environment & Setup........................................................................................................ 8
Test Scenarios ........................................................................................................................... 8
Test Result Reporting.............................................................................................................. 13
Server Roles & Priorities ............................................................................................................ 14
Networking................................................................................................................................. 15
DHCP ....................................................................................................................................... 15
Quality Improvements in DHCP........................................................................................... 15
Key Scenarios....................................................................................................................... 15
Network Load Balance ............................................................................................................ 19
Quality Improvements in NLB ............................................................................................. 19
Key Scenarios....................................................................................................................... 19
Branch Cache .......................................................................................................................... 22
What is Branch Cache.......................................................................................................... 22
Key Scenarios....................................................................................................................... 22
Storage ....................................................................................................................................... 24
File Server Resource Management ......................................................................................... 24
Quality Improvements in File Service.................................................................................. 24
Key Scenarios....................................................................................................................... 24
Server Technologies ................................................................................................................... 27
DNS ......................................................................................................................................... 27
Quality Improvements in DNS Server.................................................................................. 27
Key Scenarios....................................................................................................................... 27
Remote Desktop Services (aka. Terminal Services) ................................................................ 29
Quality Improvements in Remote Desktop Services........................................................... 29
Key Scenarios....................................................................................................................... 29
Directory Services ................................................................................................................... 33
Quality Improvements in Directory Services....................................................................... 33
Key Scenarios....................................................................................................................... 33
Internet Information Services (IIS) ......................................................................................... 38
Quality Improvements in IIS ................................................................................................ 38
Key Scenarios....................................................................................................................... 38
Clustering and High Availability .............................................................................................. 39
Quality Improvements in Clustering and High Availability ................................................. 39
Key Scenarios....................................................................................................................... 40
ADFS ........................................................................................................................................ 41
What is ADFS? ..................................................................................................................... 41
Key Scenarios....................................................................................................................... 41
RMS ......................................................................................................................................... 44
Quality Improvements in RMS ............................................................................................ 44
Key Scenarios....................................................................................................................... 44
NAP ......................................................................................................................................... 49
What is NAP? ....................................................................................................................... 49
Key Scenarios....................................................................................................................... 50
Distributed File System/Replication ....................................................................................... 53
What is Distributed File System/Replication? ..................................................................... 53
Key Scenarios....................................................................................................................... 53
Windows Data Access Components - WDAC .......................................................................... 54
Quality Improvements in WDAC ......................................................................................... 54
Key Scenarios....................................................................................................................... 54
Client Technologies (Applicable to both Server & Client) .......................................................... 57
Print ........................................................................................................................................ 57
Quality Improvements in Print ............................................................................................ 57
Key Scenarios....................................................................................................................... 57
RemoteFX for Remote Desktop Virtual Host .......................................................................... 60
What is RemoteFX for Remote Desktop Virtual Host ......................................................... 60
Key Scenarios....................................................................................................................... 61
Miscellaneous ............................................................................................................................ 62
Dynamic Memory ................................................................................................................... 62
What is Dynamic Memory? ................................................................................................. 62
Key Scenarios....................................................................................................................... 65
SQL Server............................................................................................................................... 67
Quality Improvements in SQL Server .................................................................................. 67
Key Scenarios....................................................................................................................... 67
Windows 7 SP1 / Windows Server 2008 R2 SP1 Test
Focus Guide
Microsoft continuously improves Windows 7® and Windows Server® 2008 R2 by providing
ongoing updates while working with software and hardware vendors to deliver application
compatibility and hardware compatibility improvements. Service Pack 1 (SP1) is another vehicle
through which Microsoft provides operating system improvements to customers.
SP1 is an update to both Windows 7 and Windows Server 2008 R2 that, along with
improvements delivered to users via other channels, addresses feedback from our customers.
As with previously released updates, SP1 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. SP1 also continues to improve upon the IT
administration experience. SP1 is not intended to be a vehicle for releasing new features;
however, some existing components do gain slightly enhanced functionality in SP1.
Scope of This Document
This document focuses on key changes introduced with SP1 on both Windows Server 2008 R2
(“Server”) and Windows 7 (“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.
Such prerequisites are also mentioned for each scenario.
Providing Feedback
Please use your Connect account to provide suggestions or file bugs regarding this content.
Important
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:
5
1. Log onto your Connect account.
2. Open and fill out a bug submission form.
a. Run the Data Grabber tool.
b. 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
Emulation Layer
File Systems (Local)
HAL
Kernel
Plug and Play
Power Management
Client Technologies
Client Platform
Date And Time
Desktop Shell
Graphics Infrastructure
Internet Explorer
Logon
Computer Management
Automated Tasks
Core Virtualization
Hypervisor (HV)
Virtual Devices
Data Services
Data Access Components
6
Area
Changed Major Subareas
Drivers
1394
PCI
Printers
Secure Digital (SD)
USB Core
Multimedia
Audio/Video Core
Codecs & DSP
Media Center
Media Center Extender
Media Foundation
Networking
DHCP
IPsec
Network Driver Interface Specification (NDIS)
RRAS
TCP/IP
Windows Filtering Platform (WFP)
Wireless Services
Security
Authentication
Crypto
PKI
Server Technologies
ADFS
Clustering and High Availability
Directory Services
DNS Server
File Systems (Remote)
7
Area
Changed Major Subareas
Internet Information Services (IIS)
Right Management Server
Remote Desktop Service
Windows Data Access Component
Storage
Core Storage
Personal Storage
SP1 Beta 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 RTM 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 7 and Windows Server 2008 R2 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 7 SP1 installs
fine on Windows 7 RTM or Windows Server 2008 R2 SP1
8
Categories
Test ID
Test Variations
installs on Windows Server 2008 R2 RTM.
2. SP Uninstall: Ensure that all devices continue to work after
a service pack is uninstalled, for example after SP1 is
uninstalled from Windows 7 or Windows Server 2008 R2.
3. Ensure that there is no crash or other issues while installing
or uninstalling SP1
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 Management
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 SP1.
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
1. Record video images or photos on peripheral devices,
9
Categories
Test ID
Video
Test Variations
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.
Netwo 1. Copy large files to/from network using wired/wireless
rking
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 7 SP1 installs fine on Windows 7 RTM or
Windows Server 2008 R2 SP1 installs on Windows
Server 2008 RTM.
3. Ensure that all optional components are intact.
4. Disable all optional components.
10
Categories
Test ID
Test Variations
5. Ensure that all optional components are disabled
successfully.
Basic scenario for
DISM.exe and Disk
Cleanup Utility
Note
Ensure your
offline
environment
provides SP1
binaries since
the
SPScavenge
functionality
will be
introduced in
SP1, it’s
absent in
RTM;
SP1 cannot
be uninstalled
after running
the DISM
command.
S1
1. SP Install: Ensure that SP installed successfully, for example
Windows 7 SP1 installs fine on Windows 7 RTM or
Windows Server 2008 R2 SP1 installs on Windows
Server 2008 R2.
2. Capture the installed components state by running the
following command:
Run dir “%windir%\” /b/s/a:d>files_before.txt
3. Run dism.exe in an elevated command prompt to remove
the staged components superseded by SP install
(Otherwise the execution fails
ERROR_ELEVATION_REQUIRED):
%windir%\system32\dism.exe /Image:C:\test\o
ffline /Cleanup-Image /spsuperseded
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 dism.exe.
6. Ensure that SP1 can’t be uninstalled from Software
Explorer.
11
Categories
Test ID
Test Variations
S2
1. SP Install: Ensure that SP installed successfully, for example
Windows 7 SP1 installs fine on Windows 7 RTM or
Windows Server 2008 R2 SP1 installs on Windows Server
2008 R2.
2. Capture the installed components state by running the
following command:
dir “%windir%\” /b/s/a:-d>files_before.txt
3. Run cleanmgr.exe to access the Disk Cleanup application:
Run cleanmgr.exe
4. Click “Clean up system files” to list system files for cleanup.
5. Select the item “Backup files required to uninstall service
pack” and unselect all the other items.
6. Press OK, and then confirm the operation.
7. Capture the installed components state by running the
following command:
Run dir “%windir%\” /b/s/a:-d>files_after.txt
8. The difference between files_before.txt and files_after.txt
is the list of items that were removed by dism.exe.
9. Ensure that SP1 can’t be uninstalled from Software
Explorer.
C1
1. SP Install over Client: Ensure that SP installed successfully,
for example Windows 7 SP1 installs fine on Windows 7
RTM Client.
2. Create a restore point A using system restore.
3. Capture the installed components state by running the
following command:
Run dir “%windir%\” /b/s/a:-d>files_before.txt
4. Run dism.exe in an elevated command prompt to remove
the staged components superseded by SP install:
Run %windir%\system32\dism.exe /Image:C:\test\offline
12
Categories
Test ID
Test Variations
/Cleanup-Image /Spsuperseded
5. Capture the installed components state by running the
following command:
Run dir “%windir%\” /b/s/a:-d>files_after.txt
6. The difference between files_before.txt and files_after.txt
is the list of items that were removed by dism.exe.
7. Ensure that SP1 can’t be uninstalled from Software
Explorer.
8. Restore back to restore point A using system restore.
9. Ensure that SP1 can be uninstalled from Software Explorer.
Unexpected Results
 Bug checks
 Crash
 Loss of functionality
 Unusable system after update to SP1
Test Result Reporting
Driver Name & Version:
PNP ID:
Operating System / Platform:
Test ID
Result
T1
Pass
T2
..
..
..
13
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 R2.
S No
Role Priority
Server Roles
1
P0
Hyper-V
2
P0
Terminal Services
3
P0
Active Directory Rights
Management Services
4
P0
Print Services
5
P0
Cluster
6
P0
File Services
7
P0
RRAS
8
P0
Active Directory Domain Services
14
S No
Role Priority
Server Roles
9
P1
DNS Server
10
P1
Active Directory Lightweight
Directory Services
11
P1
Active Directory Certificate
Services
12
P1
Network Policy And Access
Services (NAP)
Networking
DHCP
Quality Improvements in DHCP
Windows Server 2008 R2 SP1 DHCP has improved the functionality, reliability in
the IP lease, IP scope features.
Key Scenarios
Scenario 1 – MAC Based Filtering
Goal:
Verify that the client can get the leases from DHCP server properly.
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1, DHCP Server
Applicability:
Server
Step-by-step scenario description:
1. Connect WS08 R2 SP1 DHCP server with various windows clients.
15
2. Add filters to DHCP server via netsh or UI.
3. If there is an allow list, only the clients in allow list should get leases. All
clients in deny list must not get leases.
4. If there is no allow list all clients except those in the deny list should get
leases.
5. More information about the guideline can be found at
http://technet.microsoft.com/enus/library/ee405265%28WS.10%29.aspx.
Expected results:
The client can get leases depends on the configuration of the DHCP server.
Exceptions:
None
Scenario 2 – Split Scope
Goal:
Verify the DHCP scope split feature.
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1, two DHCP Servers.
Applicability:
Server
Step-by-step scenario description:
1. Setup two DHCP servers on the same network.
2. The admin should create a working scope on one of them (or he may use
a pre- configured one). He can then use the split scope wizard to extend
this scope to another DHCP server on the same network.
3. More information about the guideline can be found at
16
http://technet.microsoft.com/enus/library/ee405264%28WS.10%29.aspx.
Expected results:
The feature will automatically setup a scope and required exclusions on the
other server.
Exceptions:
None
Scenario 3 – DHCID
Goal:
Verify the DHCP DHCID feature.
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1, DHCP Servers.
Applicability:
Server
Step-by-step scenario description:
1. One WS08 R2 SP1 DHCP server configured to do A/AAAA registrations for
clients and configured to use this feature.
2. The DNS server address should be set on the DHCP server and the DNS
server should be reachable through the DHCP server. There should be
some non windows clients (ex. Linux) trying to acquire lease from the
DHCP server.
3. The DHCP server should register these clients on the DNS server if and
only if no other client having the same FQDN name is registered in the
DNS server.
4. More information about the guideline can be found at
http://technet.microsoft.com/en17
us/library/ee404786%28WS.10%29.aspx.
Expected results:
The clients can be registered in the DNS server by the DHCP properly.
Exceptions:
None
Scenario 4 – Information Refresh Time Option (Option 32)
Goal:
Verify the Information Refresh Time Option (option 32).
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1, DHCP Servers.
Applicability:
Server
Step-by-step scenario description:
1. One WS08 R2 DHCP server configured with V6 scopes connected to
various V6 clients. The clients under test should be in stateless mode (in a
windows client this would mean the M flag to be 0 and O flag to be 1).
2. These clients would acquire only other configuration parameters through
the DHCP server where as they will auto configure their ipv6 addresses.
The clients should try to reacquire the options from the DHCPv6 server
based on the value of Information Refresh Time Option. Hence any
change in the acquired options done in the DHCP server between the
option acquisition and refresh of the client would be reflected in the client
after the refresh.
3. More information about the guideline can be found at
http://technet.microsoft.com/en-us/library/cc722532.aspx.
18
Expected results:
Any change in the acquired options done in the DHCP server between the
option acquisition and refresh of the client would be reflected in the client
after the refresh.
Exceptions:
None
Network Load Balance
Quality Improvements in NLB
Windows Server 2008 R2 SP1 NLB has improved the functionality, reliability in
the Extended Affinity.
Key Scenarios
Scenario 1 – Scalable Shopping Cart Web Application
Goal:
Verify extended affinity improvement.
Prerequisites or specific configuration for the scenario:
3 nodes cluster with IIS installed.
Applicability:
Server
Step-by-step scenario description:
In this scenario, the same web application is installed on two machines.
These two machines are joined together in an NLB cluster so that when
client traffic arrives to the cluster IP address, it will be load balanced
between the two machines. This will result in faster response rates for
clients accessing the web application. Start with a 2 node cluster, and under
heavy client traffic, add another node to the cluster. With extended affinity
enabled, we can guarantee that the client state information will be
managed by only one server in the cluster. This scenario can be applied to
19
any web application that requires client state to be preserved on the server.
More information about the guideline can be found at
http://blogs.msdn.com/clustering/archive/2009/10/21/9910338.aspx.
Expected results:
The client state information will be managed by only one server in the
cluster.
Exceptions:
None
Scenario 2 – Split brain with two-way extended affinity
Goal:
Verify extended affinity improvement.
Prerequisites or specific configuration for the scenario:
2 node cluster and 1 client, with SP1 installed.
Applicability:
Server
Step-by-step scenario description:
Create 2 node NLB cluster. Freeze one of the nodes (say: node2). Send a
connection from client to NLB Cluster. Now Node1 has extended affinity for
Client. Freeze Node1 and resume Node2. Send a connection from client to
NLB Cluster. Now Node2 has extended affinity for Client. Resume Node1.
Make sure that NLB Cluster converges and client has extended affinity to
only one node. More information about the guideline can be found at
http://technet.microsoft.com/en-us/library/cc754833(WS.10).aspx.
Expected results:
NLB Cluster converges and client has extended affinity to only one node.
20
Exceptions:
None
Scenario 3 – TMG server with integrated NLB
Goal:
Verify the integration between TMG server and NLB.
Prerequisites or specific configuration for the scenario:
4+ node cluster with TMG (former ISA) server.
Applicability:
Server
Step-by-step scenario description:
Configure an array of TMG servers to protect the internal network. Enable
integrated NLB on the array of TMG servers. The inbound/outbound traffic
is load balanced between the TMG servers and no split brain occurs during
cluster operation. More information about the guideline can be found at
http://technet.microsoft.com/en-us/library/bb794741.aspx.
Expected results:
The inbound/outbound traffic is load balanced between the TMG servers
and no split brain occurs during cluster operation.
Exceptions:
None
21
Branch Cache
What is Branch Cache
BranchCache reduces WAN link utilization and improves application responsiveness for branch
office workers when accessing servers over slow, congested connections. Clients retrieve data
from a cache within the branch office instead of from remote servers. The cache may be
distributed amongst the clients in the branch (Distributed Cache mode) or may reside on a local
server (Hosted Cache mode).
BranchCache only works between Windows 7 clients and Windows Server 2008
R2 servers hosting content accessible using the HTTP, SMB and BITS protocols.
BranchCache is disabled by default on clients and must be installed on servers.
Key Scenarios
Scenario 1 – Deploy a branch office in hosted cache mode
Goal:
Verify the functionality of the branch office in the hosted cache mode.
Prerequisites or specific configuration for the scenario:
2 clients and 2 servers with SP1 installed.
Applicability:
Server, Client
Step-by-step scenario description:
In hosted cache mode, branch office clients rely on a locally deployed server when storing
or retrieving cacheable content. To test this scenario two clients and two servers are
needed. One server provides content using one of the BranchCache enabled protocols
(HTTP or SMB) and the other acts as a hosted cache server that will store and serve content.
In this scenario, the first client downloads data from the content server and provides it to
the hosted cache. The second client attempts to download the same content, and retrieves
it from the hosted cache server instead of the content server.
More information about the guideline can be found at
http://technet.microsoft.com/library/ee649232(WS.10).aspx.
22
Expected results:
In this scenario, the first client downloads data from the content server and
provides it to the hosted cache. The second client attempts to download the
same content, and retrieves it from the hosted cache server instead of the
content server.
Exceptions:
None
Scenario 2 – Deploy a branch office in distributed cache mode
Goal:
Verify the distributed cache mode for Branch office.
Prerequisites or specific configuration for the scenario:
2 clients and 1 server with SP1 installed.
Applicability:
Server, Client
Step-by-step scenario description:
In distributed cache mode, branch office clients cache content locally and provide it to each
other on demand. To test this scenario two clients and one servers are needed. The server
provides content using one of the BranchCache enabled protocols (HTTP or SMB). In this
scenario, the first client downloads data from the content server and caches it locally. The
second client attempts to download the same content, and retrieves it its peer instead of
the content server.
More information about the guideline can be found at
http://technet.microsoft.com/library/ee649232(WS.10).aspx
Expected results:
In this scenario, the first client downloads data from the content server and
caches it locally. The second client attempts to download the same
content, and retrieves it its peer instead of the content server.
23
Exceptions:
None
Storage
File Server Resource Management
Quality Improvements in File Service
Windows Server 2008 R2 SP1 File Server Resource Management has improved
the scalability, reliability in the File Classification Infrastructure.
Key Scenarios
Scenario 1 – Using Content Classifier on a large set of files
Goal:
Classify a variety of files (such as text file, office documents, etc) with FSRM
built-in Content Classifier using Regular Expressions.
Prerequisites or specific configuration for the scenario:
Installation of File Server Resource Management (FSRM) feature in windows
Server 2008 R2 SP1.
Applicability:
Server
Step-by-step scenario description:
1. Configure a FSRM classification property, such as Business Impact:
HBI/MBI/LBI
2. Create a new classification rule to govern over local folder or a mount
point. FCI (File Classification Infrastructure) is capable of handling a
large number of files.
3. Configure this classification rule to classify files based on its content.
Use Content Classifier as the classifier, and then configure the content
classifier to use Regular expressions.
4. Run Classification right away, or configure automatic classification
schedule to make it run periodically. Note that classification can be
24
configured to run at specific hours (such as non-peak hours). If
classification couldn’t be finished on one scheduled time slot, it will
resume in the next one.
5. Configure some File Management Tasks to act on the classification
results. This is done by the settings in Condition tab when
creating/editing the File Management Task. One example of such task is
to apply encryption to files that are classified as HBI of its Business
Impact property.
Read More:
http://blogs.technet.com/filecab/archive/2009/05/11/classifying-filesbased-on-location-and-content-using-the-file-classification-infrastructurefci-in-windows-server-2008-r2.aspx
Expected results:
 Files should be classified based on its contents correctly, regardless of
the size or the amount of files at the location configured in the
classification rule
 For office documents, the classification property set by FSRM can be
read by inspecting the properties of the file when they are opened in
Microsoft Office
 File Management Tasks performed specified actions (such as file
encryption) on schedule and on the right set of files specified by the
user
 Files residing on mounted volume should be classified and auctioned
upon with no differences than any other files
 Files that are read-only should be skipped in the automatic classification
 Since FSRM classification is incremental (unless configured otherwise by
user), a second classifications over the same set of file should take
much less time to complete.
Exceptions:
None
Scenario 2 – Use FCI in conjunction with other FSRM features in a cluster environment
Goal:
Verify the FCI functionality in the cluster environment.
25
Prerequisites or specific configuration for the scenario:
Multiple server machines; Installation of File Server Resource Management
(FSRM) feature; Installation of Cluster feature.
Applicability:
Server
Step-by-step scenario description:
1. Configure a Quota (FSRM Quota, not NTFS Disk quota) over a folder on
the cluster volume; for example, a hard limit of maximally 1G data is
allowed in that folder;
2. Configure a File Screening of the files in that folder; for example,
prohibiting any Mp3/Avi file to be placed in that folder;
3. Configure a File classification for the files in that folder; for example, all
files that have word ‘Confidential’ in its content should be classified as
HBI (high business impact);
4. Run classification on the folder;
5. Move the corresponding file server resource to other nodes in the
cluster.
Expected results:
 All FSRM features should expect to work normally when they are jointly
affecting any folder on a cluster volume
 Whenever a resource move or fail over happens, FSRM settings should
be moved to the corresponding node intact, and work on the new node
as before
Exceptions:
None
26
Server Technologies
DNS
Quality Improvements in DNS Server



On an Internet facing DNS server, all internal and external (Internet facing names) can be
resolved.
AD integration and forest recovery Mechanism.
DNSSEC was designed to protect the Internet from certain attacks, such as DNS cache
poisoning [0]. It is a set of extensions to DNS, which provide: a) origin authentication of DNS
data, b) data integrity, and c) authenticated denial of existence. These mechanisms require
changes to the DNS protocol. DNSSEC adds four new resource record types: Resource
Record Signature (RRSIG), DNS Public Key (DNSKEY), Delegation Signer (DS), and Next Secure
(NSEC). These new RRs are described in detail in RFC 4034.
Key Scenarios
Scenario 1 – EDNS probe and name resolution
Goal:
On an Internet facing DNS server, make sure that all internal and external
(Internet facing names) are resolved.
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1
Applicability:
Server
Step-by-step scenario description:
1. On machine with both forwarding and Internet facing server, install
Windows Server 2008 R2 SP1.
2. Enable EDNS (dnscmd /config /EnableEDnsProbes 1)
3. Also make sure that DNS servers behind routers and firewalls are able to
resolve names post the SP1 installation.
27
4. Make sure that all internal and external names are resolved.
Expected results:
All internal and external (Internet facing names) are resolved.
Exceptions:
None
Scenario 2 – Active Directory Integration and Forest recovery
Goal:
To ensure the DNS active directory integration and forest recovery
mechanism work.
Prerequisites or specific configuration for the scenario:
DNS servers hosting AD integrated zones and with SP1 installed
Applicability:
Server
Step-by-step scenario description:
1. Install SP1 on DNS servers hosting AD integrated zones
2. Try Forest recovery using MS White paper http://www.microsoft.com/downloads/details.aspx? displaylang=en&FamilyID=326c8a7adcad-4333-9050-a6303ff3155c.
3. For AD integrated zones, attempt zone transfers and make sure that we don’t have any
increase in memory consumption post upgrade.
Expected results:
No increases in memory consumption post upgrade when doing the zone
transferring.
Exceptions:
None
28
Scenario 3 – DNSSEC
Goal:
To catch and fix any deployment blocker issues in signing static zones, Trust anchor
configuration and Key Roll-over.
Prerequisites or specific configuration for the scenario:
Windows Server 2008 R2 SP1
Applicability:
Server
Step-by-step scenario description:
The deployment guideline is
http://www.microsoft.com/downloads/details.aspx?FamilyID=7a005a14-f740-4689-8c439952b5c3d36f&DisplayLang=en.
Expected results:
 There should not be any performance or functionality changes from RTM for DNSSEC
deployment.
 DNSSEC signed zones should be able to be deployed without significant processing
penalty side-by-side with regular DNS Server Deployment.
Exceptions:
None
Remote Desktop Services (aka. Terminal Services)
Quality Improvements in Remote Desktop Services
Windows Server 2008 R2 SP1 Remote Desktop Services (aka. 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.
29
Prerequisites or specific configuration for the scenario:
Both client and server machine should be Windows 7 SP1 or Windows
Server 2008 R2 SP1.
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 – Large scale Remote Desktop Services deployment
Goal:
User can do remote desktop connection without any functionality errors.
Prerequisites or specific configuration for the scenario:
Server machine should be Windows Server 2008 R2 SP1.
Applicability:
Server
Step-by-step scenario description:
Install Remote Desktop Session Host on WS08R2 SP1 server machines by this
Step-by-Step Guide. Install the Remote Desktop WebAccess Role Services as
30
well. Enable all client experience features including device redirection,
multiple monitor, etc.
Expected results:
Users should be able to TS to their work PC through tsgateway or RAS. Users
will connect from Win7/Vista/XP/Win2K3 and various network configurations.
Exceptions:
None
Scenario 3 – Remote Desktop Virtualization
Goal:
Enable you to publish virtual resources to the users in your organization. RDV
is aimed squarely not only at consolidation of the resources but also on the
discovery mechanism of these virtualized resources.
Prerequisites or specific configuration for the scenario:
Set up a Connection Broker and a Remote Desktop WebAccess Server and 4
Remote Desktop Virtualization Hosts (instructions). The server should be
Windows Server 2008 R2 SP1.
Applicability:
Server
Step-by-step scenario description:
1. Set up 4 Remote Desktop Virtualization Hosts (instructions).
2. Deploy a VM Pool (instructions) of at least 4 VMs and Configure 4
Personal Virtual Desktops (instructions).
3. You will also need to deploy a Connection Broker and a Remote Desktop
WebAccess Server.
31
Expected results:
The RDV can work well. The virtual resource can be published.
Exceptions:
None
Scenario 4 – Remote Desktop Session Host Farm with Clustered Connection Broker
Goal:
To verify the RDSH Farm managed properly by Broker.
Prerequisites or specific configuration for the scenario:
6 servers with Windows Server 2008 R2 SP1 installed.
Applicability:
Server
Step-by-step scenario description:
1. Install RDSH role on WS08R2 SP1 on 6 servers.
2. Setup a Fail over clustering for Connection Broker role with two nodes
(instructions).
3. Setup a Remote Desktop WebAccess Server.
4. Join the 6 RDSH servers to the farm (instructions).
Expected results:
The availability of the RDSH resource is improved.
Exceptions:
None
32
Directory Services
Quality Improvements in Directory Services
Windows Server 2008 R2 SP1 directory service has fixed issues to improve the functionality,
reliability.
Key Scenarios
Scenario 1 – Disjoint Namespace
Goal:
This is to verify the disjoint namespace.
Prerequisites or specific configuration for the scenario:
2 Existing domains. Servers are installed with Windows Server 2008 R2 SP1.
Applicability:
Server
Step-by-step scenario description:
1. Create two different Domains.
2. Following the guideline: http://technet.microsoft.com/enus/library/cc773264(WS.10).aspx
Expected results:
The disjoint namespace feature can work when one or more domain member
computers have a primary Domain Name Service (DNS) suffix that does not
match the DNS name of the Active Directory domain of which the computers
are members.
Exceptions:
None
33
Scenario 2 – Active Directory in the DMZ (AKA Perimeter Network)
Goal:
Verify the Active Directory can work well in the DMZ.
Prerequisites or specific configuration for the scenario:
Existing domain. Servers are installed with Windows Server 2008 R2 SP1.
Applicability:
Server
Scenario description:
The deployment guideline is http://technet.microsoft.com/enus/library/dd728034(WS.10).aspx.
Expected results:
No functionality failure with the active directory in DMZ environment.
Exceptions:
None
Scenario 3 – Active Directory Lag Sites
Goal:
To verify the functionality of the lag site.
Prerequisites or specific configuration for the scenario:
Existing domain, with SP1 installed
Applicability:
Server
34
Scenario description:
The deployment guideline is
http://blogs.technet.com/askds/archive/2008/10/20/lag-site-or-hot-site-akadelayed-replication-for-active-directory-disaster-recovery-support.aspx.
Expected results:
Active directory lag site can be used as a quick way to recover accidentally
deleted objects without having to resort to finding the most recent successful
backup within the tombstone lifetime of the domain that has the data.
Exceptions:
None
Scenario 4 – Domain Controllers in Hyper-V
Goal:
To verify the virtualized domain controller can work well.
Prerequisites or specific configuration for the scenario:
Windows Server 2008 R2 SP1 (Standard, Enterprise, Foundation, Datacenter)
Applicability:
Server
Step-by-step scenario description:
The deployment guideline is http://technet.microsoft.com/enus/library/dd363553(WS.10).aspx.
Expected results:
The virtualized domain controller can perform a physical domain controller.
Exceptions:
None
35
Scenario 5 – Certificate-based Authentication Infrastructure
Goal:
Verify the functionality of the Certificate-based authentication infrastructure.
Prerequisites or specific configuration for the scenario:
See the requirement in http://technet.microsoft.com/enus/library/cc730847(WS.10).aspx.
Applicability:
Server
Scenario description:
When a certificate-based logon method (for example, smart-card logon) is
used, and authentication mechanism assurance is enabled, an additional
group membership is added to the user’s access token during logon. The
deployment guideline is http://technet.microsoft.com/enus/library/cc730847(WS.10).aspx.
Expected results:
The certificate-based authentication infrastructure can working well in the AD
environment.
Exceptions:
None
Scenario 6 – Branch Office Topology
Goal:
Verify the topology and functionality of the Branch Office.
Prerequisites or specific configuration for the scenario:
Existing Read only domain controller, with SP1 installed.
36
Applicability:
Server
Scenario description:
In an ideal strategy, branch offices have the benefit of data and service
locality without the costs of securing and administering the information
technology (IT) infrastructure. Read-only domain controllers (RODCs) map
well to that strategy because they can cache the data that the branch office
needs, and they provide delegation for specific management tasks. The
deployment guideline is http://technet.microsoft.com/enus/library/dd734758(WS.10).aspx.
Expected results:
The read only domain controller is working well in the existing environment.
Exceptions:
None
Scenario 7 – Managed Service Accounts
Goal:
Verify the topology and functionality of the Branch Office.
Prerequisites or specific configuration for the scenario:
None.
Applicability:
Server
Scenario description:
Managed service accounts are used to run various services for applications that are operating
in your domain environment. More details: http://technet.microsoft.com/enus/library/dd378925(WS.10).aspx .
Expected results:
Services for applications running in the branch office work well with Managed Service
Accounts.
37
Exceptions:
None
Scenario 8 – Offline domain join
Goal:
Verify the topology and functionality of the Branch Office.
Prerequisites or specific configuration for the scenario:
None.
Applicability:
Server
Scenario description:
You can use offline domain join to join computers to a domain without contacting a domain
controller over the network. You can join computers to the domain when they first start up
after an operating system installation. No additional restart is necessary to complete the
domain join. This helps reduce the time and effort required to complete a large-scale
computer deployment in places such as datacenters. More details:
http://technet.microsoft.com/en-us/library/dd391977(WS.10).aspx.
Expected results:
Deployment of computers in the branch office should work with no access to
a domain controller.
Exceptions:
None
Internet Information Services (IIS)
Quality Improvements in IIS
IIS has improved the publishing functionality in the SP1 for FTP.
Key Scenarios
Scenario 1 – FTP site publishing and configuration
Goal:
Verify the publishing functionality for FTP.
38
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
1. Create a new FTP site: http://go.microsoft.com/fwlink/?LinkId=89115
2. Add FTP publishing to an existing Web site: http://go.microsoft.com/fwlink/?LinkId=89116
3. Configure FTP over SSL: http://go.microsoft.com/fwlink/?LinkId=89117
4. Configure FTP user isolation: http://go.microsoft.com/fwlink/?LinkId=89118
5. Configure FTP virtual host names: http://go.microsoft.com/fwlink/?LinkId=89119
6. Configure FTP firewall settings: http://go.microsoft.com/fwlink/?LinkId=100090
7. Configure folder quotas for use with FTP: http://go.microsoft.com/fwlink/?LinkId=100092
8. Configure IIS Manager Authentication for FTP:
http://go.microsoft.com/fwlink/?LinkId=100142
Expected results:
The FTP site can be published well.
Exceptions:
None
Clustering and High Availability
Quality Improvements in Clustering and High Availability
Cluster service has been improved the support for complex MPIO configurations in CVT. The
changes enabled the Failover service (clssvc) and UI (cluadmin) under VM-Scale.
39
Key Scenarios
Scenario 1: Failover Service (clssvc) and UI (cluadmin) under VM-Scale
Goal:
Verify that virtual machines running on Hyper-V can use the dynamic memory
well.
Prerequisites or specific configuration for the scenario:
Windows Server 2008 R2 SP1
Applicability:
Server
Step-by-step scenario description:
1. Create 64 VMs per node. Each VM should be configured to use dynamic
memory. Each VM should have some load which causes memory
allocations and de-allocations.
2.
Cluster all VMs. Guideline: http://technet.microsoft.com/enus/library/dd197477(WS.10).aspx.
3.
Verify the following scenarios: LiveMigration (use cluadmin),
QuickMigration (use cluadmin), Failover (use cluadmin), Machine disaster
(expected restart, unexpected restart).
Expected results:
The failover service in VM-scale functions well.
The dynamic memory management mechanism functions well.
Exceptions:
None.
Scenario 2 – CVT in complex MPIO setup
Goal:
To verify the CVT works fine in complex MPIO setup.
40
Prerequisites or specific configuration for the scenario:
Windows Server 2008 R2 SP1.
Applicability:
Server
Step-by-step scenario description:
1. Configure a cluster setup with 8+ nodes with each node having 8+ MPIO
paths to disk. The guideline is http://technet.microsoft.com/enus/library/dd197477(WS.10).aspx.
2.
Run CVT (Cluster Validation Test).
Expected results:
All disk related cluster validation tests pass.
Exceptions:
None
ADFS
What is ADFS?
Active Directory Federation Services (AD FS) is a server role in Windows Server 2008 R2 that
provides Web single-sign-on (SSO) technologies to authenticate a user to multiple Web
applications over the life of a single online session.
For more information about ADFS, please see the following TechNet article:
http://technet.microsoft.com/en-us/library/dd391937(WS.10).aspx.
Key Scenarios
Scenario 1 – Classic Two Forests federated web SSO scenario
Goal:
Verify that the SAML security token can be cleaned after sign out.
41
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
The deployment guideline is http://technet.microsoft.com/enus/library/cc757344(WS.10).aspx.
Expected results:
After Use sign-out, the SAML security token can also be used to access
resources.
Exceptions:
None
Scenario 2 – Two Forests ADFS Scenario with one way Forest Trust
Goal:
Verify that two Forests ADFS with one way Forest Trust can function well.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
The deployment guideline is http://technet.microsoft.com/enus/library/dd378921(WS.10).aspx.
42
Expected results:
Two Forests ADFS with one way Forest Trust can function well.
Exceptions:
None
Scenario 3 – Interoperation with 3rd party Federation Service
Goal:
Verify that the ADFS can interop well with 3rd party Federation service.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
The deployment guideline is http://technet.microsoft.com/enus/library/dd378921(WS.10).aspx.
Expected results:
Both ADFS and 3rd party federation service can work well.
Exceptions:
None
Scenario 4 – Interoperation with Down-level ADFS
Goal:
Verify that the ADFS can interop well with the down level ADFS.
Prerequisites or specific configuration for the scenario:
43
None
Applicability:
Server
Step-by-step scenario description:
The ADFS deployment guideline is http://technet.microsoft.com/enus/library/dd378921(WS.10).aspx.
Expected results:
Both Windows Server 2008 R2 SP1 ADFS and Windows Server 2003/2008
ADFS can work well.
Exceptions:
None
RMS
Quality Improvements in RMS
1. 3rd party federation support: ADRMS Support for 3rd party Federation server
2. Mac Office support: Enable RMS Server to support Mac Office RMS features
3. Authentication Update: Enables integration with the Microsoft Federation Gateway to
enable authentication to work across Organizational Boundaries
Key Scenarios
Scenario 1 – Federated Group Expansion
Goal:
Verify the federated group expansion.
Prerequisites or specific configuration for the scenario:
None
44
Applicability:
Server
Step-by-step scenario description:
1. Group expansion on federated environment;
2. Publish documents from resource domain and restrict the permission
to a group in account domain.
Expected results:
The user in the account domain group can open the document as
expected.
Exceptions:
None
Scenario 2 – SQM support
Goal:
Verify the RMS feature will be not impacted by the SQM.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
Switch on CEIP on RM Server.
Expected results:
The functionality will not be impacted by SQM.
Exceptions:
45
None
Scenario 3 – Power shell for RMS Admin
Goal:
Verify the Power shell can be used to configure the RMS settings.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
1. Setup RMS;
2. Using Power shell to configure the RMS server: Server settings,
policy settings, federal settings
Expected results:
The RMS server can be configured by using Power shell.
Exceptions:
None
Scenario 4 – Power shell for RMS Setup
Goal:
Verify the RMS can be set up by using the power shell.
Prerequisites or specific configuration for the scenario:
None
46
Applicability:
Server
Step-by-step scenario description:
Using Power shell to setup and provision RMS.
Expected results:
The RMS should be set up successfully.
Exceptions:
None
Scenario 5 – Federated Support for 3rd party FS
Goal:
Verify the ADRMS can support the 3rd party Federation server.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
1. Setup RMS server.
2. Setup 3rd party federation server.
3. Verify the RMS server can work with 3rd party federation server.
Expected results:
47
The RMS can work well with the 3rd party federation server.
Exceptions:
None
Scenario 6 – Mac Office Support
Goal:
Verify the Mac Office RMS feature.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
1. Setup RMS server.
2. Setup Mac Office.
3. Verify the RMS server can support the Mac office.
Expected results:
The RMS can work well with the Mac office.
Exceptions:
None
Scenario 7 – Authentication Update
Goal:
Verify the integration between the RMS server and Microsoft Federation
48
Gateway.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
Setup the RMS server and integrate with the Microsoft Federation
Gateway.
Expected results:
The authentication should work well across the Organizational
Boundaries.
Exceptions:
None
NAP
What is NAP?
Network Access Protection (NAP) is a new platform and solution that controls access to network
resources based on a client computer’s identity and compliance with corporate governance
policy. NAP allows network administrators to define granular levels of network access based on
who a client is, the groups to which the client belongs, and the degree to which that client is
compliant with corporate governance policy. If a client is not compliant, NAP provides a
mechanism to automatically bring the client back into compliance and then dynamically increase
its level of network access.
For more information about NAP, please see the following TechNet article:
http://technet.microsoft.com/en-us/network/bb545879.aspx.
49
Key Scenarios
Scenario 1 – NAP with IPSec Enforcement
Goal:
Verify NAP functions well in the IPSec enforcement scenario.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
1. Deploy a NAP CA.
2. Deploy an HRA server.
3. Deploy a NAP Health Policy Server.
4. Configure Policies for IPsec enforcement.
5. Deploy NAP Client settings.
6. Deploy IPsec policies for NAP.
7. For detail information, the deployment guideline is
http://www.microsoft.com/downloads/details.aspx?FamilyID=298ff9561e6c-4d97-a3ed-7e7ffc4bed32&displaylang=en.
Expected results:
After deployment, the NAP platform can work well in the IPSec environment.
Exceptions:
None
Scenario 2 – NAP with DHCP Enforcement NAP
Goal:
50
Verify NAP functions well in the DHCP enforcement scenario.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
The deployment guideline is
http://www.microsoft.com/downloads/details.aspx?FamilyID=ac38e5bb18ce-40cb-8e59-188f7a198897&displaylang=en.
Expected results:
After deployment, the NAP platform can work well in the DHCP environment.
Exceptions:
None
Scenario 3 – NAP with VPN Enforcement
Goal:
In this scenario, NAP will use the VPN enforcement method. NAP with VPN
enforcement can be used to enforce organizational compliance policies on
remote clients.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
51
Step-by-step scenario description:
The deployment guideline is
http://www.microsoft.com/downloads/details.aspx?FamilyID=729bba0
0-55ad-4199-b441-378cc3d900a7&displaylang=en.
Expected results:
After deployment, the NAP platform can work well in the VPN environment.
Exceptions:
None
Scenario 4 – NAP with 802.1X Enforcement
Goal:
Verify NAP functions well in the 802.1x enforcement scenario.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
Step-by-step scenario description:
The deployment guideline is
http://www.microsoft.com/downloads/details.aspx?FamilyID=8a0925
ee-ee06-4dfb-bba2-07605eff0608&displaylang=en.
Expected results:
After deployment, the NAP platform can work well in the 802.1x
environment.
Exceptions:
None
52
Distributed File System/Replication
What is Distributed File System/Replication?
The DFS Replication service is a distributed multi master file replication service. It has been
designed to be a replacement for the NT File Replication Service and is typically used by
customers for the following purposes:
a) Replication of files and folders between file servers so as to achieve the following:

Consolidation of data over the WAN from several branch office servers to a
datacenter to enable reliable low cost centralized backups.

To replicate patches, software, documents and other common LOB application
data to branch office file servers.
b) Replication of the contents of the SYSVOL share on domain controllers operating in
Windows Server 2008 domain functional level and above.
A lot of enterprise customers have invested heavily in cluster hardware and infrastructure so as
to provide highly available services in their enterprises. These customers would like to leverage
their significant investments to cater to their file replication needs as well. Customers would like
to operate their enterprise data center servers in a clustered environment so they can provide
“always-on” replication services to branch offices. This clustered environment needs to be
highly resilient to failures (hardware and software) of individual data center servers and thus
helps enterprises attain the stringent availability metrics in their datacenter SLAs.
Key Scenarios
Scenario 1 – RODC Sysvol replication
Goal:
Verify the new feature in the DFS Replication service that it has the ability to
configure a given replicated folder as read-only.
Prerequisites or specific configuration for the scenario:
None
Applicability:
Server
53
Step-by-step scenario description:
In Windows Server 2008 R2, one of the new features in the DFS
Replication service is the ability to configure a given replicated folder as
read-only. The contents of a read only replicated folder cannot be
modified locally. The contents of the read-only replicated folder are
however kept in sync with those on a read-write enabled replicated folder
by the DFS Replication service. It is possible to configure a replicated
folder as read-only on a particular replication member server in a given
replication group. The new read-only replicated folders design extends to
the SYSVOL replicated folder on Windows Server 2008 R2 based Read-only
Domain Controllers (RODC). Read-only Domain Controllers that are using
the DFS Replication service for replication of the SYSVOL replicated folder
will benefit from the new read-only replicated folders feature. Therefore,
it is not possible to make any modifications to the contents of the SYSVOL
share on the Read-only Domain Controller.
More information can be found here
http://blogs.technet.com/filecab/archive/2008/02/04/how-does-dfsr-function-on-readonly-domain-controllers.aspx.
Expected results:
The DFSR can configure a given replicated folder as read-only.
Exceptions:
None
Windows Data Access Components - WDAC
Quality Improvements in WDAC
Win7/WS08 R2 SP1 ADO and RDS has fixed 2 QFEs and 2 SP1 bugs to improve reliability, security
and compatibility.
Key Scenarios
Scenario 1 – ADO application retrieving connectionstring property
Goal:
ADO applications can run without memory leak.
Prerequisites or specific configuration for the scenario:
Client and server machine using Windows 7 SP1 or Windows Server 2008 R2
54
SP1.
Applicability:
Client and server
Step-by-step scenario description:
Application uses ADO at its data access layer and retrieving ADO
connectionstring property.
Expected results:
No memory leak
Exceptions:
None
Scenario 2 – ADO application batch update
Goal:
ADO applications can run without memory leak.
Prerequisites or specific configuration for the scenario:
Client and server machine using Windows 7 SP1 or Windows Server 2008 R2
SP1.
Applicability:
Client and Server
Step-by-step scenario description:
Application uses ADO at its data access layer and sends batch updates to a
SQL Server database.
Expected results:
No memory leak
Exceptions:
None
Scenario 3 – Remote Data Services (RDS)
Goal:
RDS application will not load object marked as KillBit by IE
55
Prerequisites or specific configuration for the scenario:
Client and server machine using Windows 7 SP1 or Windows Server 2008 R2
SP1.
Applicability:
Client and Server
Step-by-step scenario description:
A Web application uses RDS for remote data services, and receives a KillBit
object from a compromised server.
Expected results:
RDS will validate the received object and guarantee not loading a KillBit
object.
Exceptions:
None
Scenario 4 – ODBC Asynchronous Connection
Goal:
ODBC API introduced in Win7 ODBC Asynchronous Connection feature is
compatible with ISO by using the function ID defined in ISO 9075:2008. This
feature only introduce one new API – SQLCancelHandle.
Prerequisites or specific configuration for the scenario:
Client and server machine using Windows 7 SP1 or Windows Server 2008 R2
SP1.
Applicability:
Client and Server
Step-by-step scenario description:
Customer application uses SQLGetFunctions to query the function ID, so that
the application can know whether SQLCanCelHandle is supported by the
driver or not.
Expected results:
The customer application should query function ID 2050 (the function ID
defined in ISO 9075:2008) for the ODBC API SQLCancelHandle.
(note: in Win7/WS08 R2 RTM, SQLCancelHandle uses function ID 1022)
56
Exceptions:
none
Client Technologies (Applicable to both Server & Client)
Print
Quality Improvements in Print
Windows Server 2008 R2 SP1 Print has improved the functionality, reliability for
the print/scan management.
Key Scenarios
Scenario 1 – Print Management
Goal:
Print Management provides a central administration point for sharing printers
on a network and managing print server and network printer tasks. Verify the
print management feature.
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1 for 1 server; install Windows 7 SP1 for 1
client.
Applicability:
Server, Client
Step-by-step scenario description:
The Print Management snap-in is installed by default on computers running Windows 7, but it
is not installed on computers running Windows Server 2008 R2. Use either one of the
following methods to install the Print Management snap-in on a computer running Windows
Server 2008 R2:

To install the Print Management snap-in and configure the server to be a print server From Server Manager, use the Add Roles Wizard to install both the Print and
57
Document Services role and the Print Server role service.

To install the Print Management snap-in without configuring the server to be a print
server - From Server Manager, use the Add Features Wizard to install the Print
Services Tools option of the Remote Server Administration Tools feature.
To open Print Management on a computer running Windows 7 or Windows Server 2008 R2,
click Start, point to Administrative Tools, and then click Print Management.
The more information can be found in the deployment guideline at:
 Print Management: http://technet.microsoft.com/en-us/library/cc766474.aspx

Checklist:
Deploy
Print
us/library/cc771729.aspx

Deploying Printers and
us/library/cc770760.aspx

Managing Printers and Print Servers:
http://technet.microsoft.com/en-us/library/cc754769.aspx
Print
Servers:
Servers:
http://technet.microsoft.com/enhttp://technet.microsoft.com/en-
Expected results:
You can share printers on a network and centralize print server and network
printer management tasks using the Print Management Microsoft
Management Console (MMC) snap-in. Print Management helps you to
monitor print queues and receive notifications when print queues stop
processing print jobs. It also enables you to migrate print servers and deploy
printer connections using Group policy.
Exceptions:
None
Scenario 2 – Scan Management
Goal:
Verify the Scan management feature. Scan servers are used to communicate
with scanners that support Web Services on Devices (WSD), run scan
processes, route scanned documents, and log scan-related events. On a
computer running Windows Server 2008 R2, you first install the Print and
Document Services role and then install the Distributed Scan Server role
58
service in Server Manager. The Distributed Scan Server role service also
installs the Scan Management snap-in.
After a scan server is installed, you can use the scan server configuration
wizard to modify existing server settings.
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1 for 1 server.
Applicability:
Server
Step-by-step scenario description:
To install and configure a scan server
1. Open Server Manager.
2. In the left pane, click Roles, and do the following:
a. If the Print and Document Services role is not installed, in the right pane, click
Add Roles. Follow the instructions in the Add Roles Wizard to specify the
domain user service account, local temporary folder, SMTP mail server for emailing scanned documents, server authentication certificate, and user and
group security permissions.
b. If the Print and Document Services role is already installed, in the left pane,
click Roles, and then click Print and Document Services. Follow the
instructions in the Add Roles Services Wizard to specify the domain user
service account, local temporary folder, SMTP mail server for e-mailing
scanned documents, server authentication certificate, and user and group
security permissions.
More information about the guideline can be found at MSDN

Scan
Management:
us/library/dd759124.aspx

Overview of Scan Management: http://technet.microsoft.com/en-
http://technet.microsoft.com/en-
59
us/library/dd759067.aspx

Checklist: Install, Configure, and Get Started with Scan Management:
http://technet.microsoft.com/en-us/library/dd871109.aspx

Managing from a client computer: http://technet.microsoft.com/enus/library/dd871137.aspx
Expected results:
You can use Scan Management to monitor network scanners, install scan
servers, process scanned documents and route scanned documents to
network folders, to Windows SharePoint Services Web sites, and to e-mail
recipients in your domain network.
Exceptions:
None
RemoteFX for Remote Desktop Virtualization Host
What is RemoteFX for Remote Desktop Virtualization Host
RemoteFX for Remote Desktop Virtualization Host (RD Virtualization Host) enables the delivery
of a full Windows client user experience to a full range of client devices including rich clients
(e.g. Windows 7 PC), thin clients (e.g. Windows Embedded clients), and ultra thin clients (e.g.
Windows CE and Linux clients that use the RemoteFX hardware decoder) over the Remote
Desktop Procotol. RemoteFX delivers a rich user experience for Virtual Desktop Infrastructure
(VDI) by rendering content on the server by using graphics processing units (GPUs) that are
present on the server and shared across multiple virtual desktops. The RemoteFX experience
renders a range of content including DirectX and all types of multimedia and is optimized for
LAN-based networks. The target users are Knowledge Workers whose entire desktop can be
virtualized and centralized, while enabling these users to use their regular productivity
applications, Line of Business applications and media content.
Prerequisites or specific configuration for all the scenario:
· Ensure that the RD Virtualization Host server’s CPU is Intel EPT or AMD NPT or SLAT (Second
Level Address Translation) capable.
60
· Ensure that the RD Virtualization Host server has a physical GPU that is compatible with DirectX
9.0 and had a minimum of 1 GB of video RAM. Each virtual machine will consume approximately
200 MB of video RAM. The number of virtual machines that you can run on a single RD
Virtualization Host server depends on the amount of video RAM included with your video card.
Ensure that the RD Virtualization Host server only has a single GPU. Multiple GPUs installed
within a single server are not supported on this build. Only one GPU per server is supported. If
the RD Virtualization Host server has an embedded GPU card, such as an HP iLO or a Dell DRAC,
ensure that the embedded GPU is disabled in the BIOS.
· Per the Windows® 7 SP1 requirements, if you are using an x86-based virtual machine, you must
configure at least 1024 megabytes of RAM. If you are using an x64-based virtual machine, you
must configure at least 2048 megabytes of RAM.
· Ensure that there is a LAN connection between the client and the RD Virtualization Host server.
The connection should be at least 10 Mbps with a latency of less than 20 milliseconds.
Key Scenarios
Scenario description:
o
o
o
o
o
o
Server (Hyper-v Host): 1 or more RD Virtualization Host server with RemoteFX
enabled
Virtual Machine (Hyper-v Guest): 1 – 10 virtual machines per host with RemoteFX
enabled
Client: 1 or more RemoteFX client computers
Deployment guide to use: Deploying a Single RemoteFX Server Step-by-Step Guide
Description: Create up to 10 VMs per Host. Connect to the virtual machines from
RemoteFX Rich Clients and Ultra Thin Clients over LAN connections.
Expected results: Media applications, DirectX applications, Office work well.
Recommended features to test in this scenario:

Feature 1: RemoteFX LAN experience
o Description: In the Remote Desktop Connection Client UI, select Options>Experience->LAN. Connect over a high bandwidth (>10 Mbps, <20ms latency)
connection to a RemoteFX-enabled virtual machine. Use the following types of
content and compare the experience with a non RemoteFX virtual machine.
 Play streaming Flash content (e.g. youtube.com and hulu.com)
 Use Silverlight content (e.g. Bing maps)
 Use Productivity applications (e.g. MS Outlook, MS Word, Product
Studio) and verify typing responsiveness and overall responsiveness
61


o
Use DirectX applications (e.g. PowerPoint 2010, Google Earth )
Use your company’s Line of Business applications
Expected results: Media applications (Flash, Silverlight, Windows Media Player),
DirectX, WPF applications work well over the LAN.

Feature 2: Multiple Monitor support for RemoteFX
o Description: Assign multiple monitors (max 4) to some RemoteFX virtual
machines. Connect to these virtual machines from a client with the assigned
number of monitors (e.g. 2).
o Expected results: Media applications, DirectX applications, Office work well with
multiple monitors.

Feature 3: RemoteFX WAN experience
o Description: When connecting over a low bandwidth (<10 Mbps) or high latency
(>20ms) connection, in the Remote Desktop Connection Client UI, select
Options->Experience->WAN.
o Expected results: Media applications (Flash, WMP), DirectX, WPF applications
work reasonably well over the WAN.
Miscellaneous
Dynamic Memory
What is Dynamic Memory?
Dynamic memory overview
Dynamic memory allows you to configure a virtual machine so that the amount of memory
assigned to the virtual machine is adjusted while the virtual machine is running, in reaction to
the amount of memory that is actually being used by the virtual machine. This allows you to run
a higher number of virtual machines on a given physical computer. It also ensures that memory
is always distributed optimally between running virtual machines.
Before enabling dynamic memory in a virtual machine you need to ensure that the latest version
of integration services is installed in the virtual machine.
You can then enable dynamic memory for a virtual machine using the memory settings under
the virtual machine settings. Once dynamic memory is enabled there are four parameters that
you can configure:
62




Initial memory.
This is the amount of memory that is required to start the virtual machine. This value
needs to be high enough to allow the guest operating system to boot, but should be as
low as possible to allow for optimal performance with dynamic memory.
The virtual machine will never be assigned less memory than the initial memory value.
Maximum memory.
The virtual machine will not be allowed to use more memory than is specified by this
value. This value can be configured anywhere from the initial memory value up to
64GB.
Memory buffer.
The memory buffer value indicates how much memory is assigned to the virtual
machine when compared to the amount of memory actually needed by the applications
and services running inside the virtual machine.
The memory buffer will not be maintained if there is not enough physical memory
available in the computer to give every virtual machine its requested memory buffer.
Memory priority.
The memory priority value reflects how memory will be distributed amongst virtual
machines if there is not enough physical memory available in the computer to give every
virtual machine its requested amount of memory.
Higher priority virtual machines will be given more memory when compared to lower
priority virtual machines with similar settings.
Supported guest operating systems
Dynamic memory is supported for the following guest operating systems:












Windows Server 2008 R2 Enterprise Edition (32-bit and 64-bit)
Windows Server 2008 R2 Datacenter Edition (32-bit and 64-bit)
Windows 7 Ultimate Edition (32-bit and 64-bit)
Windows 7 Enterprise Edition (32-bit and 64-bit)
Windows Server 2008 Enterprise Edition (32-bit and 64-bit)
Windows Server 2008 Datacenter Edition (32-bit and 64-bit)
Windows Vista Ultimate Edition (32-bit and 64-bit)
Windows Vista Enterprise Edition (32-bit and 64-bit)
Windows Server 2003 R2 Enterprise Edition (32-bit and 64-bit)
Windows Server 2003 R2 Datacenter Edition (32-bit and 64-bit)
Windows Server 2003 Enterprise Edition (32-bit and 64-bit)
Windows Server 2003 Datacenter Edition (32-bit and 64-bit)
If you enable dynamic memory for a virtual machine that is running an operating system that is
not on this list, the guest operating system will only ever be able to access the initial memory.
63
For each supported operating system you should follow the published required and
recommended memory values prior to installing the latest integration services and enabling
dynamic memory. Once dynamic memory is enabled you can use a lower initial value in order to
get the best performance out of dynamic memory. The maximum memory value should always
be greater than the required memory for the operating system that is running in the virtual
machine.
Operating System
Required
Memory
Recommended
Memory
Initial Memory (with
DM enabled)
Windows Server 2008 R2 Enterprise
Edition
512MB
N/A
512MB
Windows Server 2008 R2 Datacenter
Edition
512MB
N/A
512MB
Windows 7 Ultimate Edition
1GB
N/A
512MB
Windows 7 Enterprise Edition
1GB
N/A
512MB
Windows Server 2008 Enterprise Edition
512MB
1GB
512MB
Windows Server 2008 Datacenter
Edition
512MB
1GB
512MB
Windows Vista Ultimate Edition
512MB
1GB
512MB
Windows Vista Enterprise Edition
512MB
1GB
512MB
Windows Server 2003 R2 Enterprise
Edition
128MB
256MB
128MB
Windows Server 2003 R2 Datacenter
Edition
512MB
1GB
128MB
Windows Server 2003 Enterprise Edition
128MB
256MB
128MB
Windows Server 2003 Datacenter
Edition
512MB
1GB
128MB
Tuning dynamic memory for best performance
If you enable dynamic memory on a virtual machine and are not satisfied with the performance
that you receive from the virtual machine, there are multiple configuration changes that you can
make to potentially improve performance:
64



Increase the size of the page file inside the guest operating system.
A larger page file inside the virtual machine allows larger amounts of memory to be
added to the running virtual machine if it is needed suddenly. It also lets the virtual
machine run better when the availability of physical memory is limited.
Increase the memory buffer configured for the virtual machine.
Increasing the memory buffer will result in more memory being assigned to the virtual
machine when compared to the amount of memory actually needed by the applications
and services running inside the virtual machine. This extra memory can then be used for
file caching purposes, and may help with the performance of IO intensive applications
and services.
Increase the initial memory for the virtual machine.
Some applications assign fixed amounts of memory based on the amount of memory
available when the application first starts. These applications will perform better with
higher values for the initial memory.
Alternatively, if you are seeing poor performance due to too much memory being
removed from the virtual machine, increasing the initial memory value can also alleviate
this problem.
It should be noted that by increasing the initial memory value, the overall flexibility and
effectiveness of dynamic memory is reduced.
Increase the virtual machine memory priority.
Increasing the virtual machine memory priority will ensure that available physical memory is
assigned to this virtual machine before being
Key Scenarios
Scenario 1 – Dynamic Memory and Hyper-V Failover clustering
Goal:
Verify that virtual machines running on Hyper-V can use the dynamic memory
well.
Prerequisites or specific configuration for the scenario:
Windows Server 2008 R2 SP1
Applicability:
Server
Step-by-step scenario description:
1. Create 64 VMs per node. Each VM should be configured to use dynamic
65
memory. Each VM should have some load which causes memory
allocations and de-allocations.
2.
Cluster all VMs. Guideline: http://technet.microsoft.com/enus/library/dd197477(WS.10).aspx.
3.
Verify the following scenarios: LiveMigration (use cluadmin),
QuickMigration (use cluadmin), Failover (use cluadmin), Machine disaster
(expected restart, unexpected restart).
By enabling dynamic memory on virtual machines in a Hyper-V failover cluster you are able to
get better utilization of your hardware. However this comes with risk that a virtual machine
may fail to start after a hardware failure if other virtual machines do not relinquish memory
when requested to do so. In order to mitigate this risk, for following guidelines should be
followed:

Calculate the amount of physical memory available in the cluster when a node has
failed (or when multiple nodes have failed if you want to be able to sustain the failure
of multiple nodes). Then ensure that:
o The sum value of all initial memory values for all virtual machines on the
cluster does not exceed this value.
o The expected performance of the virtual machines when they are limited to
this value is acceptable in your environment.
o The sum value of all maximum memory values for all virtual machines is no
more than twice this value.
Expected results:
The failover service in VM-scale functions well.
The dynamic memory management mechanism functions well.
Exceptions:
None.
66
SQL Server
Quality Improvements in SQL Server
Windows Server 2008 R2 SP1 SQL Server 2008 has improved the functionality for failover
cluster.
Key Scenarios
Scenario 1 – Basic SQL Server 2008 Failover Clustering Installation, using Create Failover
Cluster and Add Node features
Goal:
Verify the basic failover clustering installation of SQL Server 2008: Create
Failover Cluster and Add Node features.
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1, SQL server 2008
Applicability:
Server
Step-by-step scenario description:
Using the basic SQL Server failover cluster installation method, install a 2node SQL Server 2008 R2 RTM+SP1 (using SQL Server 2008 slipstream)
failover cluster instance on WS08 R2 SP1.
The installation method is http://msdn.microsoft.com/enus/library/ms179410.aspx.
Expected results:
The basic SQL Server 2008 Failover cluster installation succeeds.
Exceptions:
None
67
Scenario 2 – Advanced SQL Server 2008 Failover Clustering Installation, using Prepare Failover
Cluster and Complete Failover Cluster features
Goal:
Verify the Advanced failover clustering installation of SQL Server 2008:
Prepare Failover Cluster and Complete Failover Cluster features.
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1, SQL server 2008
Applicability:
Server
Step-by-step scenario description:
Using the advanced SQL Server failover cluster installation method, install a 2node SQL Server 2008 R2 RTM+SP1 (using SQL Server 2008 slipstream)
failover cluster instance after WS08 R2 SP1.
The installation method is http://msdn.microsoft.com/enus/library/ms179410.aspx.
Expected results:
The advanced SQL Server 2008 Failover cluster installation succeeds.
Exceptions:
None
Scenario 3 – OS Upgrade to WS08 R2 SP1 after installing SQL Server 2008
(using basic installation method) on WS08 R2
Goal:
Verify the SQL Server 2008 failover feature after the OS upgrade (Using the
basic installation method).
Prerequisites or specific configuration for the scenario:
68
Install Windows Server 2008 R2 SP1, SQL server 2008
Applicability:
Server
Step-by-step scenario description:
1. Install SQL server 2008.
2. Install the failover feature with the basic installation method.
3. Upgrade to the Windows Server 2008 R2 SP1.
The installation method is http://msdn.microsoft.com/enus/library/ms179410.aspx.
Expected results:
The SQL Server 2008 failover feature works well after the OS upgrade (Using
the basic installation method).
Exceptions:
None
Scenario 4 – OS Upgrade to WS08 R2 SP1 after installing SQL Server 2008
(using advanced installation method) on WS08 R2
Goal:
Verify the SQL Server 2008 failover feature after the OS upgrade (Using the
advanced installation method).
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1, SQL server 2008
Applicability:
Server
69
Step-by-step scenario description:
1. Install SQL server 2008.
2. Install the failover feature with the advanced installation method.
3. Upgrade to the Windows Server 2008 R2 SP1.
The installation method is http://msdn.microsoft.com/enus/library/ms179410.aspx.
Expected results:
The SQL Server 2008 failover feature works well after the OS upgrade (Using
the advanced installation method).
Exceptions:
None
Scenario 5 – Apply SQL Server 2008 SP1 CU6 after installing a 2 node SQL
Server 2008 failover cluster (using basic install method) at the RTM+SP1 level
using the slipstream method on WS08 R2. Then apply WS08 R2 SP1.
Goal:
Verify the SQL Server 2008 failover feature and SP1 CU6 after the OS
upgrade (Using the basic installation method).
Prerequisites or specific configuration for the scenario:
Install Windows Server 2008 R2 SP1, SQL server 2008
Applicability:
Server
Step-by-step scenario description:
1. Using the basic SQL Server failover cluster installation method, install a 2-node SQL
Server 2008 RTM+SP1 (using SQL Server 2008 slipstream) failover cluster instance on
WS08 R2.
2. Apply WS08 R2 SP1 after the SQL Server failover cluster installation.
3. Then apply SQL Server 2008 SP1 CU6.
70
The installation method is http://msdn.microsoft.com/enus/library/ms179410.aspx.
Expected results:
The SQL Server 2008 SP1 CU6 works well after the OS upgrade (Using the
basic installation method).
Exceptions:
None
71