IT Core Blog

This paper describes the best practices for implementing a Microsoft virtualized solution for SAP applications on a Microsoft® Windows Server® 2008 platform. It introduces the technologies and architecture used, describes the available options for Hyper-V™ infrastructure planning, and discusses possible performance optimizations. This paper also discusses lifecycle management and provides information about using the System Center Virtual Machine Manager to manage the Hyper-V infrastructure. Windows Server 2008 R2 enhancements as they apply to an SAP environment are also discussed. This paper is written for developers, technical consultants, and solution architects. Readers are expected to have administrator level SAP knowledge, and a basic understanding of Hyper-V and SQL Server.

This white paper describes the advantages of deploying Microsoft® SQL Server® database application workloads to a virtualization environment using Microsoft Windows® Server® 2008 R2 Hyper-V™. It demonstrates that Hyper-V provides the performance and scalability needed to run complex SQL Server workloads in certain scenarios. It also shows how Hyper-V can improve performance when used in conjunction with advanced processor technologies. This paper assumes that the reader has a working knowledge of virtualization, Windows Server Hyper-V, SQL Server, Microsoft System Center concepts and features.

Here’s an interesting one
You try to install the Hyper-V Integration Services (Drivers) in a VM with Windows 2003 and you get the following error:
“An error has occurred: Internal Error“

Hum…
No errors in the event log we decided to start by installing the latest updates for that VM. Unfortunately not all updates were able to install properly, in fact most of the updates were failing to install as well…
 Ok, Back to the Integration Components setup, it was time to check the log. Under %Windir% directory we check the installation log “vmguest.log”:

Hyper-V Integration Services Installer version 6.1.7600.16385
MUI file loaded
Parsing command line…
Command line parsing complete
Application Directory = D:\support\x86
ServicingMode = 0
##### START: VERIFY SYSTEM ENVIRONMENT
OS Version      = 5.2
OS SP Level     = 2
OS Platform ID  = 2
OS Product Type = 3
Edition ID      = 0×0
Processor Arch  = 0
Processor Count = 2
System Language = en-us (ENU)
Windows Dir     = C:\WINDOWS
System Dir      = C:\WINDOWS\system32
Drivers Dir     = C:\WINDOWS\system32\drivers
System MUI Dir  = C:\WINDOWS\system32\en-us
Drivers MUI Dir = C:\WINDOWS\system32\drivers\en-us
##### END: VERIFY SYSTEM ENVIRONMENT – Exit code = 0×0
Starting the restart dialog killer thread
RestartDialogCaption = System Settings Change
Restart dialog handler ready
Creating progress dialog
Dialog created
ProgressMessage = 49305
Creating worker thread
Worker thread created
Waiting for worker thread
##### START: UPDATE HAL
HAL found at C:\WINDOWS\inf\hal.inf
##### END: UPDATE HAL – Error code = 0×0
##### START: INSTALL KMDF
About to load DLL D:\support\x86\WdfCoInstaller01007.dll
About to call preinstall
Preinstall failed with error 0000F00D
##### END: INSTALL KMDF – Error code = 0xF00D
Detected worker thread exit
Worker thread error code = 0000F00D
Exit code = 0xEA60

After identifying which component fail, we proceed to the respective log “Wdf01007Inst.log” under the same directory “%WinDir%”. Inside this log, between other errors, we found this one:
“Failed to copy spupdsvc.exe“

So we decided to analyze the “%Windir%\System32\ spupdsvc.exe“. After checking the ” spupdsvc.exe” we discover that “spupdsvc.exe” did not appear to be a original Microsoft exe file, we were able to confirm this checking the “spupdsvc.exe” properties and its digital signature which didn’t exist at all.

Solution:
The Solution was to delete the “spupdsvc.exe”, run a Malware remover tool in the system (this may be need as the antivirus may not be able to detect the malware or remove it), then copy the “spupdsvc.exe” from a healthy system to the problematic one.
After this the Integration components were successfully installed and the updates that were also ALL installed successfully.

Windows Server 2008 R2: Hyper-V Component Architecture pdf available for download.

Windows Server 2008 R2: Hyper-V Component Architecture

For additional documentation check this link.

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

A Management Server that has been added to a Systems Center Operations Manager 2007 management group is able to download configuration information from the Root Management Server, but generates an error when attempting to process the configuration. The Operations Manager event log on the new management server will show the following two events every few minutes:

Source: HealthService
Event ID: 7022
Task Category: Health Service
Level: Error
Description:
The Health Service has downloaded secure configuration for management group , and processing the configuration failed with error code 0x80FF003F(0x80FF003F).

Source: HealthService
Event ID: 1220
Task Category: Health Service
Level: Error
Description:
Received configuration cannot be processed. Management group . The error is 0x80FF003F(0x80FF003F).

Check KB2027535 - New Management Server unable to get configuration in System Center Operations Manager 2007

CRITICAL UPDATE for Exchange 2010 Address List Segregation and Current Support Stances, read the Full article From Dgoldman’s WebLog

The Operations Manager Support Team Blog posted some nice report samples.

From Operations Manager Support Team Blog:

“Just in case you missed their post last week, The System Center Operations Manager team blog posted a bunch of reporting samples you could use with OpsMgr 2007, including:
- “Customer X needs to produce a report that shows the processor, memory, logical disk performance for his 100 servers and needs to see the average performance over multiple time ranges”
- “Customer X needs to produce a report showing detailed information about how long servers spent in maintenance mode and what happened during that time”
- “Customer Y is looking for physical servers in his environment that may be suitable candidates for Virtualization, he needs a report that can show overtime the most suitable servers”
and more.
You can find their original post here but they recently uploaded an newer, updated batch of files to correct some issues they saw in the first one.  You can find that here.
If you’re looking to really maximize how OpsMgr 2007 can help you save money and manage your resources more wisely then you’ll definitely want to check these out.”

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

Active Directory Federation Services 2.0 helps IT enable users to collaborate across organizational boundaries and easily access applications on-premises and in the cloud, while maintaining application security. Through a claims-based infrastructure, IT can enable a single sign-on experience for end-users to applications without requiring a separate account or password, whether applications are located in partner organizations or hosted in the cloud.

Get it Active Directory Federation Services 2.0 RTW
Read more about Federation Services

Once again Kevin Holman posted how to perform this update step by step…

The KB979257 article describes the fixes and changes and instructions
Get it from the download Center

This is not a huge hotfix rollup…. It does contain some substantial fixes however, and if impacted, you should consider applying this update. If you have not yet tested and applied CU1 to your R2 management group, then you absolutely should skip CU1 and apply CU2 as soon as possible.

The release notes in the KB article above cover the fixes that are included. The main ones I have seen in the field are the SNMP device view issue, and the Console crashing when opening multiple views. I have added it to my Recommended Hotfix page, but if you aren’t impacted by any of these issues, you can certainly pass on a cumulative update, and pick up the next one that provides a fix you need.

Read More…

As VMST 2.1, VMST 3.0 builds on the functionality of VMST 2.1 and adds some new features, which are designed to streamline the process of keeping offline virtual machines, templates and VHDs up-to-date with the latest operating system and application updates, without introducing vulnerabilities into your virtualization infrastructure.

New available features in VMST 3.0:
- Offline virtual machines in a SCVMM library.
- Stopped and saved state virtual machines on a host.
- Virtual machine templates.
- Offline virtual hard disks in a SCVMM library by injecting update packages.
- Windows Server 2008 R2 failover clusters running Hyper-V.

VMST 3.0 is designed to work with Microsoft System Center Virtual Machine Manager (SCVMM) 2008 or SCVMM 2008 R2, and with the following technologies:
- Windows Server Update Services (WSUS) 3.0 SP1 or WSUS 3.0 SP2.
- System Center Configuration Manager (SCCM) 2007 SP1, SCCM 2007 R2, or SCCM 2007 SP2.
- VMST 3.0 also provides the option to manually copy updates to service offline VHDs.
- The tool works with Windows Task Scheduler to enable scheduling the servicing job.

To sign up to the beta go to Microsoft Connect (Connect ID required).