IT Core Blog

Microsoft has released the Windows Storage Server 2008 R2 for MSDN/TechNet subscribers this new version includes Microsoft iSCSI Software Target 3.3 that includes Windows PowerShell cmdlets and differencing virtual hard disk support for HPC boot scenarios.

Read more at:
Windows Storage Server
and
Jose Barreto’s Blog
PowerShell cmdlets for the Microsoft iSCSI Target 3.3 (included in Windows Storage Server 2008 R2)

From KB:980054
This article describes the hotfixes and updates that we recommend that you install on each node of a Windows Server 2008 R2-based failover cluster. When you update your Windows Server 2008 R2-based failover cluster, you help reduce downtime. You also help decrease the number of errors, failed print jobs, and other support issues that you experience.

We recommend that you install the following hotfixes if you plan to install the failover clustering feature on Windows Server 2008 R2 Core:
KB978309: IPv6 transition technologies, such as ISATAP, 6to4 and Teredo do not work on a computer that is running Windows Server 2008 R2 Server Core
KB976571: Stability update for Windows Server 2008 R2 Failover Print Clusters

For additional information about Network related issues and Hyper-V check my previous post at:
Hyper-V Fixes for Network Connectivity related issues

This article describes an update rollup package that resolves some issues for the Hyper-V role on a computer that is running Windows Server 2008 R2 and that is dated August 24, 2010.

Issue 1
When a computer has one or more Intel CPUs code-named Nehalem installed, you receive the following Stop error message:

0×00000101 ( parameter1 , 0000000000000000, parameter3 , 000000000000000c) CLOCK_WATCHDOG_TIMEOUT
Note The Nehalem CPU for a server is from the Intel Xeon processor 5500 series and for a client computer is from the Intel Core-i processor series.

Issue 2
Consider the following scenario:
You run a virtual machine (VM) on the computer.
You use a network adapter on the VM to access a network.
You establish many concurrent network connections. Or, there is heavy outgoing network traffic.
In this scenario, the network connection on the VM may be lost. Additionally, the network adapter is disabled.

Note You have to restart the VM to recover from this issue.

Issue 3
When a computer has an Intel Westmere processor, you receive an error message that resembles the following:
STOP: 0x0000001a ( Parameter1 , Parameter2 , Parameter3 , Parameter4 ) MEMORY_MANAGEMENT

Source: KB2264080

From Virtual PC Guy’s Blog, here’s a documentation list for Dynamic Memory included in in the Windows Server 2008 R2 SP1 beta release:

Dynamic Memory Technical Overview whitepaper
This paper talks about what dynamic memory is, what it does and how it does it.  It is a good read for those curious to understand what is happening under the covers.
http://download.microsoft.com/download/E/0/5/E05DF049-8220-4AEE-818B-786ADD9B434E/Implementing_and_Configuring_Dynamic_Memory.docx

Hyper-V Dynamic Memory Evaluation Guide
This article steps you through the process of setting up SP1 and enabling dynamic memory.  It also gives you some good tips on configuration and troubleshooting.
http://technet.microsoft.com/en-us/library/ff817651(WS.10).aspx

Windows Server 2008 R2 Service Pack 1 – TechNet Center
For all things “Windows Server 2008 R2 Service Pack 1” related – the TechNet Center has you covered.
http://technet.microsoft.com/en-us/library/ff817647(WS.10).aspx

Hyper-V: Dynamic Memory Survival Guide
The TechNet Wiki also has a “Dynamic Memory Survival Guide” article with some extra links.
http://social.technet.microsoft.com/wiki/contents/articles/hyper-v-dynamic-memory-survival-guide.aspx

Thanks Ben

Acording with Ben Armstrong and KB982210 - The startup time increases every time after you back up the data on all the disks of the computer in Windows Server 2008 R2 if the computer runs some virtual machines.

Note: the KB982210 applies to Windows Server 2008 R2 (not Windows Server 2008).

Additional Errors:

Log Name: System
Source: PlugPlayManager
Date: date time
Event ID: 12
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: computer name
Description:
The device ‘MSFT Virtual HD SCSI Disk Device’ (SCSI\Disk&Ven_MSFT&Prod_Virtual_HD\ GUID ) disappeared from the system without first being prepared for removal.

Short description by Ben Armstrong:
Whenever we backup a virtual machine using VSS, we momentarily connect the backup copy of the virtual machines virtual hard disks to the parent partition in order to clean them up after backup.  Unfortunately with Windows Server 2008 R2 a new plug-and-play entry would get created in the Windows registry each time that we did this.  Over time this would cause the registry to get larger and larger, which would in turn slow down the Windows boot process.

Here’s some interesting sessions for virtualization from TechEd.

Networking and Windows Server 2008 R2 Hyper-V: Deployment Considerations

Microsoft System Center Virtual Machine Manager 2008 R2: Advanced Virtualization Management

The Microsoft System Center Operations Manager Top 20 Must-Have Customizations

Microsoft System Center Operations Manager and Virtual Machine Manager: Monitoring the Service Stack

See the Largest Mission Critical Deployment of Microsoft SQL Server around the World

Check the Latest Videos from TechEd North America

Have Fun

Important (recommended updates) fixes that were Recently released by Microsoft that you should consider for installation in Windows 2008 R2 and Windows 7 Systems.

KB979782: An update rollup package for the Validate a Configuration Wizard of the Failover Clustering feature is available for Windows Server 2008 R2

KB981314: The “Win32_Service” WMI class leaks memory in Windows Server 2008 R2 and in Windows 7

KB981577: The “Invoke-WmiMethod” cmdlet dispatches incorrect results on a computer that is running Windows 7 or Windows Server 2008 R2

KB982293: The Svchost.exe process that has the WMI service crashes in Windows Server 2008 R2 or in Windows 7

KB982383: You encounter a decrease in I/O performance under a heavy disk I/O load on a Windows Server 2008 R2-based or Windows 7-based computer

KB983289: The “ZwAllocateVirtualMemory” function fails together with a STATUS_INSUFFICIENT_RESOURCES error randomly when you have sufficient memory in Windows 7 or in Windows Server 2008 R2

KB983551: Windows 7 or Windows Server 2008 R2 stops responding at the “Please wait” screen before you are requested to press Ctrl+ALT+DEL

From TechNet’s Channel 9

One of the very cool new features coming in Windows Server 2008 R2 SP1 is dynamic memory provisioning for virtual machines. In this interview, Vijay Tewari explains how this model works, and gave me a demo of it in action.

From Arlindo’s blog here’s some helpful articles to help you Managing and deploying Windows 7~

Wouldn’t it be handy to have one place on the web where you could find an updated list of ALL the AV exclusions you might want to configure? This wiki stub topic is meant to be that list. Feel free to add to the list, it is the wiki way!  

  

Windows:
KB822158 Virus scanning recommendations for Enterprise computers that are running currently supported versions of Windows

Windows / Active Directory: 
http://support.microsoft.com/kb/822158
http://support.microsoft.com/kb/837932
http://support.microsoft.com/kb/943556

Cluster:
http://support.microsoft.com/kb/250355

Forefront: Considerations when using antivirus software on FF Edge
Products
http://support.microsoft.com/kb/943620
http://technet.microsoft.com/en-us/library/cc707727.aspx

FRS:
http://support.microsoft.com/kb/815263

SQL:
http://support.microsoft.com/kb/309422

IIS:
http://support.microsoft.com/kb/821749
http://support.microsoft.com/kb/817442

DHCP:
http://support.microsoft.com/kb/927059

SCOM / MOM:
http://support.microsoft.com/kb/975931

Hyper-V:
http://support.microsoft.com/default.aspx/kb/961804

Exchange:
Exchange 2010: http://technet.microsoft.com/en-us/library/bb332342.aspx
Exchange 2007: http://technet.microsoft.com/en-us/library/bb332342(EXCHG.80).aspx
http://support.microsoft.com/kb/328841
http://support.microsoft.com/kb/823166
http://support.microsoft.com/kb/245822
http://technet.microsoft.com/en-us/library/bb332342(EXCHG.80).aspx
http://technet.microsoft.com/en-us/library/bb332342.aspx

SharePoint:
http://support.microsoft.com/kb/952167
http://support.microsoft.com/kb/320111
http://support.microsoft.com/kb/322941

SMS:
http://support.microsoft.com/kb/327453

ISA:
http://support.microsoft.com/kb/887311

WSUS:
http://support.microsoft.com/kb/900638

SBS:
http://support.microsoft.com/kb/885685

 Med-V
Recommended Anti-Virus exclusions for MED-V client and workspace installations

System Center:
Recommendations for antivirus exclusions in MOM 2005 and Operations Manager 2007

Error:
Virtual Machine Manager failed to connect to the virtual machine because of a socket connection error. Check the firewall and network settings, and then try to connect again.

Cause:
This issue may occur because the SCVMM 2008 Administrator Console tries to establish a Remote Desktop connection by not using a VMConnect connection to the Hyper-V host on the 2179 TCP port. Instead, the SCVMM 2008 Administrator Console tries to establish a Remote Desktop connection directly with the operating system of the VM on the 3389 TCP port.

Note: The SCVMM 2008 Administrator Console works as expected on a computer that is running a supported version of Windows XP, of Windows Vista, or of Windows Server 2008.

Resolution:
To resolve this issue on a computer that is running Windows 7 or Windows Server 2008 R2, you must use Microsoft System Center Virtual Machine Manager (SCVMM) 2008 R2. Additionally, you must use SCVMM 2008 R2 to manage Windows Server 2008 R2 Hyper-V hosts.

Taken from:
KB983253-SCVMM 2008 Administrator Console cannot connect to a Windows Server 2008 Hyper-V-hosted VM in Windows 7 or in Windows Server 2008 R2

Important Hyper-V Network issues related (Recommended Updates):
KB974909 - The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer
KB981836 - Network connectivity for a Windows Server 2003-based Hyper-V virtual machine is lost temporarily in Windows Server 2008 R2.
KB978309 - IPv6 transition technologies, such as ISATAP, 6to4 and Teredo do not work on a computer that is running Windows Server 2008 R2 Server core.

When this issue occurs, one or both of the following events are logged in the System log on the VM:
Event Type: Warning
Event Source: netvsc
Event Category: None
Event ID: 5
Date: <date>
Time: <time>
User: N/A
Computer: <computer name>
Description: The miniport ‘<network adapter name>’ hung.

Event Type: Warning
Event Source: netvsc
Event Category: None
Event ID: 4
Date: <date>
Time: <time>
User: N/A
Computer: <computer name>
Description: The miniport ‘<network adapter name>’ reset.

Notes:
KB979409 is to be installed in the Hyper-V servers.
KB981836 is to be installed on the Hyper-V server which will create a new set of Integration Components and then the new Integration Components will need to be updated in the Windows 2003 VMs.

KB978309 - Check Related Issues in the following posts:
IP Helper Service – IpHlpSvc Consume more than expected %CPU
“Unable to add additional node to Hyper-V Cluster”
“Windows 2008 R2 problems with HP Drivers”
“Windows 2008 R2 problems with HP Drivers Again…“

Additional Updates At:
Hyper-V Update List for Windows Server 2008 R2
Hyper-V Update List for Windows Server 2008

Many “Recommended” updates are available for SCVMM and the technologies it manages, staying up to date can be hard, fortunately there is a tool called VMMCA that will check the configuration and updates installed on the SCVMM Server and any Hosts specified and produce a simple report.

What about all updates that have been released since the VMMCA was last released?
Here’s a list of all of the updates the VMMCA checks and another one that you will have to verify on your own.

Updates the VMMCA verifies
Install on the SCVMM Server
961983
971244
Install on SCVMM Hosts
950050
956589
956774
958124
954563
955805
Hyper-V updates for SCVMM Hosts
952247
956697
957967
958184
959978
971677
Failover Cluster Management updates for SCVMM Hosts
951308
958065

New updates, not verified by the VMMCA
WinRM-Win2003
936059 An update is available for the Windows Remote Management feature in Windows Server 2003 and in Windows XP
WMI – Win2008, SP2
968936 Memory corruption may occur with the Windows Management Instrumentation (WMI) service on a computer that is running Windows Server 2008 or Windows Vista Service Pack 1
WMI – Win2008, SP2
971403 A rollup hotfix package for Windows Server 2008 Failover Clustering WMI provider
WMI – Win2008, SP2
970520 The Wmiprvse.exe process creates a memory leak on a computer that is running Windows Server 2008 if you remotely monitor this process by using the WMI interface on a computer that is running Windows Server 2003 or Windows XP
WMI – Win2008R2
974930 An application or service that queries information about a failover cluster by using the WMI provider may experience low performance or a time-out exception
WMI – Win2008R2
981314 The “Win32_Service” WMI class leaks memory in Windows Server 2008 R2 and in Windows 7
Hyper-V – Win2008R2
981618 The computer stops responding or restarts during the Hyper-V Live Migration process in Windows Server 2008 R2
P2V – Win2000
834010 A deadlock occurs when a program that uses WMI calls the LoadLibrary() or the FreeLibrary() function in Windows 2000
P2V – Win2000, 2003
892294 A WMI event notification query does not detect a user permissions change on Windows 2000 or Windows Server 2003
P2V – Win2000
843527 The Win32_SCSIController WMI class cannot obtain SCSI controller information after you install the MS04-011 security update
P2V – SCVMM2008
959596 Description of the System Center Virtual Machine Manager 2008 update to address physical to virtual (P2V) issues
P2V – SCVMM2008
971816 Using P2V together with System Center Virtual Machine Manager 2008 may fail with error 3154 (0x8099319E) or error 13252 (0x809933C4)
VMM Rollup – SCVMM 2008R2
976244 Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: November 10, 2009
VMM Rollup – SCVMM 2008R2
978560 Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: February 9, 2010
Other – SCVMM2008R2
976246 When you remove a virtual hard disk from a virtual machine in System Center Virtual Machine Manager 2008 R2, the .vhd file on the Hyper-V server is deleted without warning

From App-V Team Blog.

“On Windows 7 and Windows Server 2008 R2, there is a great troubleshooting tool called the Problem Steps Recorder (PSR). The PSR allows screenshots and details of actions to be automatically recorded and saved in a .MHT file that is automatically zipped. A user can send this file to Microsoft Support to provide an accurate account of steps to reproduce and issue. There is a short video on TechNet that gives a demonstration of the Problem steps recorder.

We can appropriate this tool and turn it into a Sequencing Steps Recorder to document “recipes” for sequencing applications. Other App-V blog articles have demonstrated how to use video to document sequencing. The Problem Steps Recorder just provides another alternative, especially for those users that like to read from a printout.

The PSR can be easily be found on Windows 7 or Server 2008 just by clicking on the Windows Logo and typing “steps” ,“record”, or “PSR.exe” in the search bar”

Read more at: “Document Sequencing on Windows 7 with the Problem Steps Recorder“