IT Core Blog

Never stop questioning. Curiosity has its own reason for existing…

Archive for September 2010

Windows Storage Server 2008 R2 and the Microsoft iSCSI Software Target 3.3 available on MSDN/TechNet

leave a comment »

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)

Written by IT Core

September 29, 2010 at 9:08 PM

Virtual Machine Servicing Tool (VMST) 3.0

leave a comment »

This release of the Virtual Machine Servicing Tool (VMST) 3.0 completely replaces the Offline Virtual Machine Servicing Tool version 2.1.

Version 3.0 of the tool works with System Center Virtual Machine Manager 2008 R2, System Center Configuration Manager 2007 SP2, and Windows Server Update Services 3.0 SP2. The tool also supports updating the Windows® 7 and Windows Server® 2008 R2 operating systems.

To Download the Virtual Machine Servicing Tool 3.0 click here.

Some highlights include:
 
•    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.

Written by IT Core

September 28, 2010 at 12:00 AM

KB2413735: Mouse and screen resolution issues when managing a virtual machine using the Hyper-V

leave a comment »

From KB2413735

Windows Server 2008 or Windows Server 2008 R2, you may experience one of the following symptoms when you connect to a Hyper-V virtual machine using the Hyper-V Manager console or the System Center Virtual Machine Manager Administrator Console:
· The mouse cursor is frozen or has disappeared
· The screen resolution has reverted to the default size
If you connect to the virtual machine using a Remote Desktop Connection (RDP), the symptoms listed above are not exhibited.

This issue can occur after a new Hyper-V VMMS certificate is generated.
Note: The following event will be logged in the Hyper-VMMS event log when a new VMMS certificate is generated:

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Event ID: 12520
Level: Warning
Description:
Auto-generating a self-signed certificate for server authentication.

To resolve this issue, perform one of the following steps on the Hyper-V server:
·Place the virtual machines in a saved state and then resume the virtual machines.
or
·Restart the virtual machines.

The self-signed certificate that is generated by the Hyper-V Virtual Machine Management service is valid for one year.

To create a self-signed certificate that doesn’t expire for several years, perform the following steps:
1.
Copy the PowerShell script from the following Microsoft Web site:
http://gallery.technet.microsoft.com/ScriptCenter/en-us/be2da634-978b-48d7-b3ab-01c593c9d177 (http://gallery.technet.microsoft.com/ScriptCenter/en-us/be2da634-978b-48d7-b3ab-01c593c9d177)
2. Paste the script into notepad, and then save the file as Cert.ps1. 
3. Copy Makecert.exe to the same directory as the Cert.ps1 file.
For more information on how to obtain Makecert.exe, please visit the following Microsoft web site: http://msdn.microsoft.com/en-us/library/aa386968(VS.85).aspx (http://msdn.microsoft.com/en-us/library/aa386968(VS.85).aspx)
4. Open an elevated Windows PowerShell command prompt. 
5. Run the Cert.ps1 script.

🙂

Written by IT Core

September 23, 2010 at 12:14 PM

KB2308590: System Center Virtual Machine Manager 2008 R2 hotfix rollup package

leave a comment »

KB2308590: System Center Virtual Machine Manager 2008 R2 hotfix rollup package

List of issues that are resolved
Issue 1
Duplicate virtual machines (VMs) may appear in the SCVMM Administrator Console window after a Hyper-V VM in a cluster fails over to another cluster node. Additionally, the status for one of the duplicate VMs is set to Missing. If you try to remove the missing VM from the SCVMM Administrator Console window, the VM is not removed.
Issue 2
Consider the following scenario:
You install the Hyper-V role on a computer that is running Windows Server 2008 R2.
You configure the computer to start from a virtual hard disk.
The computer is part of a Hyper-V failover cluster. The cluster is configured to use cluster shared volumes.
You try to create a VM on a cluster shared volume by using SCVMM 2008 R2.
In this scenario, the operation fails together with the 2912 (0x8004232C) error code.
Issue 3
The Virtual Machine Manager service (Vmmservice.exe) crashes if the following conditions are true:

System Center Operations Manager 2007 integration is enabled.
A Performance and Resource Optimization (PRO) feature-enabled management pack is imported into Operations Manager.
The PRO settings for a host group are changed on the SCVMM server.

KB2308590: System Center Virtual Machine Manager 2008 R2 hotfix rollup package

Written by IT Core

September 21, 2010 at 10:11 PM

Hyper-V R2 Cluster CSV stops working when NTLM is disabled in cluster with Hyper-V Enabled

leave a comment »


Hyper-V R2 Cluster CSV stops working when NTLM is disabled in cluster with Hyper-V Enabled

ID: 5121
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Symbolic Name: DCM_VOLUME_NO_DIRECT_IO_DUE_TO_FAILURE
Message: Cluster Shared Volume ‘%1′ (’%2′) is no longer directly accessible from this cluster node

This error may be caused because the NTLM was disabled in your Hyper-Host. Enabling a policy to disable NTLM may break CSV and cause the alert described before.

If the NTLM was disabled using GPO in your Active Directory Domain, identify the GPO with this setting and create an exception to this policy for all clustered Hyper-V computer objects. Alternatively you can create and link another GPO (GPO with “enable NTLM” setting) that applies just to the clustered hosts. 

 🙂

Written by IT Core

September 21, 2010 at 10:07 PM

Hyper-V Host may stop when VM’s Dynamic Memory use all available RAM

leave a comment »

When setting up VMs with dynamic memory remember that your hyper-v host may stop if those VMs consume (or try to) use all existing memory on the host leaving nothing for the parent partition. 

To prevent that Crete the following Registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ Virtualization
RED_DWORD value
Name = MemoryReserve
Setting = amount of MB to reserve for the parent partition.
After setting up the desired value you must reboot the host to the setting become active.

Note: if you set this value too low; VMs will be able to use too much memory and cause performance issues for you. Equally – the higher you set this the fewer VMs you can run.
For more information about memory reserve with dynamic memory check the Virtual PC Guy’s Blog

Written by IT Core

September 21, 2010 at 9:52 PM

How to manually remove a missing host from SCVMM

leave a comment »

You may see the following error when trying to remove a “dead” host from your SCVMM console.

Error (406)
Access has been denied while contacting the server <servername>. 

Recommended Action
1. Verify that the specified user account has administrative privileges on <servername>.
2. Verify that DCOM access, launch, and activation permissions are enabled on <servername> for the Administrators group. Use dcomcnfg.exe to modify permissions, and then try the operation again.

If that server is no longer online you need a way to remove it from your SCVMM. To do that you may use the PowerShell that come with the SCVMM console:

get-vmmserver <Vmm_Server_Name>
Than forcibly remove the missing host server by running:
remove-vmhost <Host_Server_Name> –force
Wait a few seconds and the host should be removed from the console.

🙂

Written by IT Core

September 21, 2010 at 8:49 PM

System Center Data Protection Manager 2010 Documentation

leave a comment »

Written by IT Core

September 21, 2010 at 8:24 PM

KB957311: Recommended hotfixes for Windows Server 2008-based server clusters

leave a comment »

 
 
If you determine that cluster nodes in your environment may be affected by the problems that an update or hotfix addresses, install the hotfix or update on each one of the cluster nodes in your environment.
 
 
 
952247  (http://support.microsoft.com/kb/952247/ ) The Cluster network name resource and the File Share Witness resource may not come
951308  (http://support.microsoft.com/kb/951308/ ) Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role
950179  (http://support.microsoft.com/kb/950179/ ) When you run the Validate a Configuration Wizard on a Windows Server 2008-based computer or on a Windows Vista-based computer, the validation does not pass
969550  (http://support.microsoft.com/kb/969550/ ) A Stop error occurs on an HP ProLiant server that has the firmware from an E200/E200i HP Smart Array SAS/SATA controller installed on any Windows Server platform
970529  (http://support.microsoft.com/kb/970529/ ) The volume GUID may unexpectedly change after a volume is extended on a Windows Server 2008 failover cluster node
953652  (http://support.microsoft.com/kb/953652/ ) A physical disk resource may unexpectedly fail or go offline when the IsAlive function is executed on a Windows Server 2008 cluster node

Written by IT Core

September 11, 2010 at 11:12 PM

Posted in MS Hotfixes

Tagged with ,

KB:980054 Recommended hotfixes and updates for Windows Server 2008 R2-based server clusters

leave a comment »

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

🙂

Written by IT Core

September 11, 2010 at 10:59 AM

KB2397711: Recommended hotfixes for System Center Virtual Machine Manager 2008 R2

leave a comment »

KB2397711: Recommended hotfixes for System Center Virtual Machine Manager 2008 R2.

Recommended updates for the Virtual Machine Manager (VMM) Server and Admin Console
982522 (http://support.microsoft.com/kb/982522)   Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: June 8, 2010
982523 (http://support.microsoft.com/kb/982523)   Description of the System Center Virtual Machine Manager 2008 R2 Admin Console hotfix rollup package: June 8, 2010

Windows Server 2008 – Recommended updates for Microsoft Hyper-V Server and for the VMM server
The following list applies only to systems that are running Windows Server 2008 Service Pack 1
954563 (http://support.microsoft.com/kb/954563)   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
955805 (http://support.microsoft.com/kb/955805)   Certain applications become very slow on a Windows Server 2008-based or Windows Vista SP1-based computer when a certificate with the SIA extension is installed
956774 (http://support.microsoft.com/kb/956774)   A Background Intelligent Transfer Service (BITS) client cannot handle files that have paths that contain the volume GUID in Windows Server 2008 or in Windows Vista
958124 (http://support.microsoft.com/kb/958124)   A wmiprvse.exe process may leak memory when a WMI notification query is used heavily on a Windows Server 2008-based or Windows Vista-based computer

The following list applies to systems that are running Windows Server 2008 Service Pack 1 or Windows Server 2008 Service Pack 2
968936 (http://support.microsoft.com/kb/968936)   A rollup hotfix package for Windows Server 2008 Failover Clustering WMI provider
970520 (http://support.microsoft.com/kb/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
971244 (http://support.microsoft.com/kb/971244)   Windows Remote Management (WinRM) does not accept HTTP authorization requests that are larger than 16 KB on a computer that is running Windows Server 2008 or Windows Vista
971403 (http://support.microsoft.com/kb/971403)   The “Win32_share” WMI class cannot enumerate file shares or create file shares on a node in a Windows Server 2008 failover cluster

To see a list of recommended Hyper-V updates for Windows Server 2008 and for Microsoft Hyper-V Server 2008, visit the following Microsoft TechNet websitehttp://technet.microsoft.com/en-us/library/dd430893(WS.10).aspx (http://technet.microsoft.com/en-us/library/dd430893(WS.10).aspx)

Windows Server 2008 – Recommended updates for Hyper-V Failover Cluster nodes
957311 (http://support.microsoft.com/kb/957311)   Recommended hotfixes for Windows Server 2008-based server clusters

Windows Server 2008 R2 – Recommended updates for Microsoft Hyper-V Server and for the VMM server
981314 (http://support.microsoft.com/kb/981314)   The “Win32_Service” WMI class leaks memory in Windows Server 2008 R2 and in Windows 7
981845 (http://support.microsoft.com/kb/981845)   The Windows Remote Management service stops responding in Windows 7 or in Windows Server 2008 R2

To see a list of recommended Hyper-V updates for Windows Server 2008 R2 and for Microsoft Hyper-V Server 2008 R2, visit the following Microsoft TechNet websitehttp://technet.microsoft.com/en-us/library/ff394763(WS.10).aspx (http://technet.microsoft.com/en-us/library/ff394763(WS.10).aspx)

Windows Server 2008 R2 – Recommended updates for Hyper-V Failover Cluster nodes
974930 (http://support.microsoft.com/kb/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
980054 (http://support.microsoft.com/kb/980054)   Recommended hotfixes and updates for Windows Server 2008 R2-based server clusters

Recommended updates for Windows Server 2003 systems that have Virtual Server installed
936059 (http://support.microsoft.com/kb/936059)   An update is available for the Windows Remote Management feature in Windows Server 2003 and in Windows XP

Recommended updates that should be applied to Windows 2000 systems before a P2V is performed
834010 (http://support.microsoft.com/kb/834010)   A deadlock occurs when a program that uses WMI calls the LoadLibrary() or the FreeLibrary() function in Windows 2000
843527 (http://support.microsoft.com/kb/843527)   The Win32_SCSIController WMI class cannot obtain SCSI controller information after you install the MS04-011 security update
892294 (http://support.microsoft.com/kb/892294)   A WMI event notification query does not detect a user permissions change on Windows 2000 or Windows Server 2003

Written by IT Core

September 8, 2010 at 11:08 PM

KB2397370: A System Center Virtual Machine Manager 2008 R2 virtual machine migrated between Failover Clusters fails with Error 12711

leave a comment »

 

From KB2397370

Migration of a virtual machine from one Microsoft Windows 2008 R2 Failover Cluster to another fails. Both Failover Clusters are managed by System Center Virtual Machine Manager 2008 R2 (SCVMM).

Error (12711)
VMM cannot complete the WMI operation on server Contoso.LOCAL because of error: [MSCluster_ResourceGroup.Name=”2068e895-4930-42be-a4c8-152ab15a28b8″] The cluster group could not be found.
 (The cluster group could not be found (0x1395))
Recommended Action
Resolve the issue and then try the operation again
.

SCVMM 2008 R2 attempts to execute an operation on the source host (of the source cluster) using the resources names and GUIDS of the destination cluster. Migration will always fail right after the BITS migration when the virtual machine is placed in a saved state.

This issue can only be reproduced under these conditions:
VM is created using Hyper-V
VM is made into an HA VM using the Failover Cluster GUI (resource name will be called something like “Virtual Machine <vmname>”)
VM is in a running state
VM is migrated to a different cluster. VMM will chose Quick Storage Migration with network migration in this case

There are two different workarounds for this issue.

1. Perform the migration when the virtual machine is in a saved state or powered down.

2. Use the Failover Cluster Manager User Interface to locate the virtual machine in “Services and Applications”. Right click the top resource group for this virtual machine and change the Resource Name from “Virtual Machine <vmname>” to “SCVMM <vmname>”. Then refresh the virtual machine in SCVMM PowerShell using the “refresh-vm -force ‘<vmname>'” cmdlet. The virtual machine can now be migrated while in a running state.

Written by IT Core

September 2, 2010 at 12:02 PM