KB950050
Description: Hyper-V RTM
Date: June 26, 2008
Mandatory?: Yes
File Name: Windows6.0-KB950050-x64.msu
On Windows Update?: Yes
--------------------------------------------------------------------------------------------------
KB956710
Description: Hyper-V update : 24 proc and 192 VM possible
Date: Sept 23, 2008
Mandatory?: Yes, if host has > 16 Logical processors
File Name: Windows6.0-KB956710-v2-x64.msu
On Windows Update?: No
-------------------------------------------------------------------------------------------------
KB956589
Description: Resolve potential issues when you manage Hyper-V with SCVMM
Date: Sept 23, 2008
Mandatory?: Yes if SCVMM 2008 is used to manage environment
File Name: Windows6.0-KB956589-x64.msu
On Windows Update?: No
-------------------------------------------------------------------------------------------------
KB956774
Description: Resolve the scenario where a BITS client cannot handle files that have paths that contain the volume GUID in Windows Server 2008.
Date: Sept 23, 2008
Mandatory?: Yes if GUIDs are used to access instead of drive letter or mount point
File Name: Windows6.0-KB956774-x64.msu
On Windows Update?: No
---------------------------------------------------------------------------------------------------
KB956697
Description: Resolve an issue in which the Hyper-V Volume Shadow Copy Service (VSS) does not back up virtual machines properly
Date: Sept 8, 2008
Mandatory?: Yes, any time VSS is utilized for backups
File Name: Windows6.0-KB956697-x64.msu
On Windows Update?: Yes
----------------------------------------------------------------------------------------------------
KB951308
Description: Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role
Date: Sept 11, 2008
Mandatory?: Yes, for Failover Clustering
File Name: Windows6.0-KB951308-v2-x64.msu
On Windows Update?: No
-----------------------------------------------------------------------------------------------------
KB953828
Description: The NLB host does not converge as expected on Windows Server 2008 Hyper-V virtual machines
Date: June 25, 2008
Mandatory?: Yes if NLB is in use
File Name: Windows6.0-KB953828-x64.msu
On Windows Update?: No
-------------------------------------------------------------------------------------------------------
KB953585
Description: Error message when you try to start a Hyper-V virtual machine on a Windows Server 2008 computer that uses the NUMA architecture.
Date; Sept 4, 2008
Mandatory?: Yes if NUMA hosts are in use
File Name: Windows6.0-KB953585-x64.msu
On Windows Update?: No
-------------------------------------------------------------------------------------------------------
KB950182
Description: A computer that is running an x86-based version of Windows Server 2008 or an x86-based version of Windows Vista may use fewer processors than expected if the number of cores on a socket is not a power of 2
Date: April 11, 2008
Mandatory?: Yes, if you wish to start a Windows Server 2008 x86-based virtual machine on a computer that uses a 6-core processor.
File Name: Windows6.0-KB950182-x86.msu
On Windows Update?: No
-------------------------------------------------------------------------------------------------------
KB957967

Description: Stop error message on a Windows Server 2008-based computer that has the Hyper-V role installed: "STOP 0x0000001A"
Date: October 8, 2008
Mandatory?: No
File Name: Varies
On Windows Update?: No
----------------------------------------------------------------------------------------------------------

KB958065

Description: You cannot configure a Hyper-V virtual machine by using Windows Server 2008 Failover Clustering when the virtual machine uses a storage device that is managed by a third-party clustered file system or a third-party replication solution
Date: November 3, 2008
Mandatory?: Yes, if you use 3d-party clustered file systems to store few VMs per LUN, running on different hosts.
File Name: Varies
On Windows Update?: No
----------------------------------------------------------------------------------------------------------

KB957967

Description: Stop error message on a Windows Server 2008-based computer that has the Hyper-V role installed: "STOP 0x0000001A"
Date: October 8, 2008
Mandatory?: No, apply this hotfix only to systems that are experiencing this specific problem.

File Name: Vid.sys
On Windows Update?: No

Note: The process is tested only on MOM 2005, newer versions may have different procedures. Always use ip-address instead of hostname with http, I experienced that using hostname doesn't work with IIS authentication for some reasons.

1. Export the MOM reports by using the Report Utility (RptUtil.exe) command-line tool. This tool is located in the following folder: %Program File%\Microsoft System Center Re\porting\Reporting
2. Use the command line as rptutil /URL:http://ip-address of the Report Server/ReportServer and by default it will dump the reports as MOMReports.xml under C:\
3. Uninstall MOM 2005 Reporting on the standby server first and then perform the un-installation on the primary node
4. Detach the SystemCenterReporting database using the SQL Server 2005 Management Studio
5. Install MOM 2005 Reporting on the destination computer which will automatically create the SystemCenterReporting database on the SQL server.
6. On the destination computer, detach and then remove the SystemCenterReporting database that is automatically created in Step 5 by the installation performed in Step 5
7. Replace the database that you removed with the original MOM 2005 reporting database that you detached in Step 4
8. Move the membership of both groups (SC DW Reader, SC DW DTS)
9. Use the rptutil.exe to import the MOM reports that you exported in step 1 using command-line rptutil /action:import /file:path\MOMReports.XML /URL:http://ip-addressof the server/ReportServer

Moving Reporting Services database from a SQL cluster to another computer running SQL Server & Reporting Services

Operations on the Source Server
1. Open SQL Server management studio, and then connect to the instance of SQL Server 2005
2. Back up the ReportServer database and the ReportServerTempDB
3. Back up the encryption key by using the reporting services configuration manager.
Backing up the symmetric key is a process that writes the key to a file that you specify, and then scrambles the key using a password that you provide. The symmetric key can never be stored in an unencrypted state so you must provide a password to scramble the key when you save it to disk. After the file is created, you must store it in a secure location and remember the password that is used to unlock the file. To backup the symmetric key, you can use either the Reporting Services Configuration tool or the rskeymgmt utility.
Since the reporting services configuration tool is more user friendly, let's look at the steps to backup the key
Star the Reporting Services Configuration Tool, and then connect to the report server instance you want to configure.
* Click Encryption Keys, and then click Back Up.
* Type a strong password
* Specify a file to contain the stored key. Reporting Services appends a .snk file extension to the file. Click OK.
* Copy the backup database files and the backup encryption key you performed in step 2 and 3 to the destination server

Operations on the Destination Server
1. Stop IIS service by running the iisreset /stop command at the command prompt.
2. Open the Reporting Services Configuration Manager, and then connect to the instance of SQL Server 2005 Reporting Services
3. Stop Reporting Services by clicking on "Server Status" and then click Stop on the Report Server Status Page.
4. Open SQL Server management studio, and then connect to the instance of SQL Server 2005
5. Back up the ReportServer database and the ReportServerTempDB database if they exist
6. Detach the ReportServer database and the ReportServerTempDB database
7. Restore the backup databases from the source server
8. In the Reporting Services Configuration Manager, make sure that the configurations in the following pages are identical to those in the source server:
a. Configurations in Report Server Virtual Directory
b. Configurations in Report Manager Virtual Directory
c. Type of service account configuration in Windows Service Identity
d. The Report Server configuration and the Report Manager configuration in Web Service Identity
9. Start reporting services by clicking on the Server Status in the Reporting Services Configuration Page
10. Start IIS service by running the iisreset /start at the command prompt
11. In the Reporting Services Configuration Manager, click the Encryption Keys, and then click Restore.
12. In the Encryption Key Information window, type the password you use to back up the encryption key from the source server, locate the backup encryption key from the folder on the destination server you performed in step earlier steps on the source server