An excerpt from Justin Zarb’s article on his ‘Virtual World’ site. Michael Michael is the tops in SCVMM. If he took the time to create these videos you can bet they are worth viewing.

Managing with Windows PowerShell

http://blogs.technet.com/virtualworld/archive/2007/10/18/quick-start-from-nothing-to-scvmm.aspx

Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization,windows,powershell

From the Microsoft TechNet SCVMM TechCenter

Article URL: http://technet.microsoft.com/en-us/library/bb740860.aspx

(Don't forget the VMMCA tool. This should always be top in your troubleshooting list. More info here.)

The table below works as a quick reference for why you may be experiencing connectivity issues. This will at least get you off and running in the right troubleshooting direction!

You can use Host Properties dialog box to check the overall status of a host, the status of the agent that is installed on the host, and the status of the virtualization software that is installed on the host. These are important indicators of the operational state of a host. Should a host status indicate a need for attention, see the Troubleshooting Guide for System Center Virtual Machine Manager (VMM)

(http://go.microsoft.com/fwlink/?LinkId=83589 [ http://go.microsoft.com/fwlink/?LinkId=83589 ] ).

The following table describes the host status types and values.

To view the status values of a host  

1.     In Hosts view, navigate to the host group that contains the host, and then, in the results pane, double-click the host.

2.     In the Host Properties dialog box, click the Status tab.

Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization,windows

There are many updates for SCVMM and Hyper-V. Some are required just following product install, others are provided to offer greater functionality. Some updates/hotfixes address issues that may constitute a headache for you down the road. I'll list everything I know and provide recommendations. This post will change over time as new updates and issues arise. If you find a hotfix or update that you think should be posted here, please let me know. Include the environment conditions (Windows version, etc) and what the update addresses. Here's to being proactive!

Article Ratings  

     A – Required by product to operate correctly

     B – Resolves known issues

     C – Adds Functionality

     JJ – Get it. This is on my short list when working with customers.

A – SCVMM – Hyper-V

956589  Description of the Hyper-V update for issues that may occur when you manage the Hyper-V role on the 64-bit editions of Windows Server 2008 by using SCVMM

http://support.microsoft.com/default.aspx?scid=kb;EN-US;956589

A – SCVMM | BITS

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

http://support.microsoft.com/default.aspx?scid=kb;EN-US;956774

B – JJ – SCVMM | WMI

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

http://support.microsoft.com/default.aspx?scid=kb;EN-US;958124

B – JJ – SCVMM | WMI

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

http://support.microsoft.com/default.aspx?scid=kb;EN-US;954563

B – JJ – SCVMM - WMI

955805  Certain applications become very slow on a Windows Server 2008-based or Windows Vista SP1-based computer when a certificate with SIA extension is installed

http://support.microsoft.com/default.aspx?scid=kb;EN-US;955805

B – JJ – SCVMM | P2V

959596  Description of the System Center Virtual Machine Manager 2008 update to address physical to virtual (P2V) issues

http://support.microsoft.com/default.aspx?scid=kb;EN-US;959596

B – JJ – Hyper-V | VSS

956697  Windows Server 2008 Hyper-V VSS writer is not used during a backup job because of corrupted or invalid virtual machine configuration files

http://support.microsoft.com/default.aspx?scid=kb;EN-US;956697

B – Hyper-V | VSS

959978  Error message when you back up a Windows Server 2003-based virtual machine on a Windows Server 2008 Hyper-V-based computer: "GetWriterStatus FAILED for Selected writer [Microsoft Hyper-V VSS Writer], writer is in state [9] [VSS_WS_FAILED_AT_FREEZE]"

http://support.microsoft.com/default.aspx?scid=kb;EN-US;959978

B – Hyper-V |SCVMM

957967  Stop error message on a Windows Server 2008-based computer that has the Hyper-V role installed: "STOP 0x0000001A"

http://support.microsoft.com/default.aspx?scid=kb;EN-US;957967

B – Cluster | Hyper-V

957311  Recommended hotfixes for Windows Server 2008-based server clusters

http://support.microsoft.com/default.aspx?scid=kb;EN-US;957311

B – JJ - Hyper-V | Drive Letters

958184  Virtual machine backup operations fail in Windows Server 2008 when Hyper-V virtual machine files are saved on a volume that is mounted on a failover cluster by using a volume GUID

http://support.microsoft.com/default.aspx?scid=kb;EN-US;958184

B – Hyper-V | Cluster

958065  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

http://support.microsoft.com/default.aspx?scid=kb;EN-US;958065

C – Hyper-V | Cluster

951308  Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role

http://support.microsoft.com/default.aspx?scid=kb;EN-US;951308

Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization,windows

Mike Briggs put this article together for one of his customers who was having a bit of difficulty installing SCVMM correctly. The SCVMM install process is well designed and easy to follow, but it helps if you read the directions... Needless to say, some people have a hard time putting on the brakes and reading the few pre-requisites required. I suggest you use this document as a reference point and mark it up for your own internal use. The professional formatting of this document took a bit of a beating  when converted to HTML below, so download the attachment for use.

mbriggs@microsoft.com 

___________________________________________

Installation Prerequisites

The following section discusses the hardware, Operating System, Software and Infrastructure Prerequisites to be considered before installing System Center Virtual Machine Manager.

Prerequisites are also provided for the individually installable SCVMM Components, VMM Server, Administrator Console, Self-Service Portal.

Hardware Requirements

Hardware Prerequisites are classified by the number of hosts and the associated virtual machines that will be managed by the SCVMM server.

The following table contains recommended and minimum requirements for managing up to 150 hosts.

Operating System Prerequisites

SCVMM 2008 will install only on Microsoft Windows Server 2008 (x64) edition.

Additional Software Prerequisites

Installation Steps:

1. Select VMM Server under SETUP on the main screen.

Note: When you install the VMM server, only the domain account that you are logged on with is automatically added to the VMM Administrator user role.

2. Accept the license.

3. Join the Customer Experience Improvement Program (CEIP).

4. Enter Product Registration information.

5. Execute the Prerequisites Check and make sure it completes successfully. If not, correct the problems and re-run the check.

6. Select an Installation location on the local machine.

7. Configure SQL Server settings.

8. Create a new library share on the VMM server or select a pre-configured share. As a 'best practice', you may want to consider using another volume on the VMM Server for better performance and storage capacity.

9. After setup is complete, you cannot remove or relocate the default library share, so give careful consideration to its location before installing the VMM server. You can specify an existing share on the VMM Server in place of the default location; however it must reside on the VMM Server. Additional Library Shares and Servers can be added in the future.

10. Specify ports to support SCVMM communications and designate a domain account to use for the VMM Service Account (Default is to use local system). If the Self- Service portal is being hosted on the VMM server, Port 80 will already be taken by the Default Website. You will either need to change the port in IIS Services Manager or set a different one for VMM communications.

11. Specify Local system or a domain account to use for the VMM Service Account (Default is to use local system).

12. Verify all the selections before selecting Install

13. Provided no issues are encountered, the install will complete and you will be able to check for Virtual Machine updates on the Microsoft website.

Note: When you install the VMM server, all accounts in the local Administrators security group are automatically added to the VMM Administrator user role.

VMM Administration Console

For ease of administration it is recommended that you install a Virtual Machine Manager Administrator Console on the same computer as the SCVMM server. You can install additional VMM Administrator Consoles on other computers to remotely access and manage the SCVMM server. When you install the VMM Administrator Console, the Setup Wizard also installs Windows PowerShell — Virtual Machine Manager Command shell. Additionally, if installing the VMM Administrator Console on another supported platform the .NET Framework version 2.0 is required.

If you plan to use the reporting feature of VMM, you must install a VMM Administrator Console on the same computer as the VMM server. The reporting feature of VMM relies upon System Center Operations Manager 2007 (OpsMgr), and for OpsMgr administrators to perform tasks on hosts and virtual machines from within the Server Virtualization Management Pack requires that the Windows PowerShell — Virtual Machine Manager command shell be installed on the VMM server.

Installation Steps:

1. In the setup menu select Administrator Console

2. Accept the License Terms

3. Review customer Experience Improvement program (CEIP) information

4. Execute the Prerequisites Check and make sure it completes successfully. If not, correct the problems and re-run the check.

5. Select an Installation location on the local machine.

6. Verify the Port Assignment.

The default port is 8100.

7. Verify all the selections before selecting Install.

Provided no issues are encountered, the install will complete and you will be able to check for Virtual Machine updates on the Microsoft website.

9. By default, a shortcut to the VMM Administrator Console will be placed on the desktop. Double-click on the shortcut and verify the Administrator console does open.

10. The first time you open the VMM Administrator Console, the Connect to Server dialog box opens. In the Connect to Server dialog box, do one of the following:

· If you installed the VMM Administrator Console on the same computer as the VMM server, click Connect to connect to the local VMM server (localhost) using the port that you assigned during the installation of the VMM server.

· If you want to use the VMM Administrator Console to connect to the VMM server on the different computer, in the Server name box, type the name of the computer where the VMM server is installed, followed by a colon and the port that you assigned during the installation of the VMM server.

Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization

Technorati Tags: microsoft,scvmm,hyper-v review,virtual,virtualization,windows,app-v,med-v

You find yourself with one of the following situations

1.     Deployment or migration of data utilizing LAN (not SAN Transfer) is very slow in general

2.     BITS is slow in one direction only: Fast from Host01 to Host02, but slow from Host02 to  Host01 for example

3.     Host reports in SCVMM Admin Console "Host not responding" or "Needs attention"

4.     Under 'Status' of the Host the following may show "Not Responding"
    - Connection status
    - Agent Status

All of these issues can be related to networking components. Three common tasks can be performed to address this

1.     Test for BITS errors

2.     Verify GPO settings

3.     Correct vendor specific and Windows system settings for ‘Task Offloading’ (This item will likely have the greatest effect)

Additional Items that just make sense

Verify all network settings on all involved SCVMM and Hyper-V systems. Set the network speed on the NICs and switches. Do not leave as auto negotiate. Also, remove all NIC teaming software. Network Card drivers currently do not always play nice with virtualization technologies. (Uninstall the teaming software. Disabling will not prevent drivers from loading at startup). If you cannot remove your teaming software at this time, at least make sure the namespace is available by typing ‘wmic nic’ at an elevated command prompt. If you get a screen full of data, you may be ok. If you get any kind of error, yank teaming software now and reboot.

1 - BITS Errors
Determine if BITS (Background Intelligent Transfer Service) is encountering errors. Attempt a P2V/Migration/Deployment transfer with SCVMM. While the transfer is occurring between servers, run the following commands on both servers:
Bitsadmin /list /allusers /verbose >bitsadmin.txt

Example BITS output below shows how long the transfer lasted (MODIFICATION TIME minus CREATED TIME). Retry delay shows that there were no errors. This is a clean run. If there are errors review the system and application event logs for errors that are BITS related. Involve your network team as well for a trace.

Example output…

BITSADMIN version 1.0 [ 5.1.2600.0 ]
BITS administration utility.
(C) Copyright 2000-2001 Microsoft Corp.

GUID: {BA568D81-B234-47F2-9BA3-686743F89794} DISPLAY:
https://cotoso.com:443/8272f226d8b8cd818406b28de9b6ad0f012b9a55/C:A5cProgramDataA5cM
icrosoftA5cWindowsA5cHyperVA5calbtest1A5cvmguest.iso/E:A5cVirtualMachinesA5calbtest
1A5cvmguest.iso
TYPE: UNKNOWN STATE: TRANSFERRED OWNER: NT AUTHORITY\SYSTEM
PRIORITY: FOREGROUND FILES: 1 / 1 BYTES: 42948608 / 42948608
CREATION TIME: 12/3/2008 9:04:48 AM MODIFICATION TIME: 12/3/2008 9:16:44 AM
COMPLETION TIME: 12/3/2008 9:16:44 AM
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 60 NO PROGRESS TIMEOUT: 0 ERROR COUNT: 0
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
DESCRIPTION: VMM LAN Transfer Job
JOB FILES:
42948608 / 42948608 WORKING
https://contoso.com:443/8272f226d8b8cd818406b28de9b6ad0f012b9a55/C:A5cProgramDataA5c
MicrosoftA5cWindowsA5cHyperVA5calbtest1A5cvmguest.iso/E:A5cVirtualMachinesA5calbtes
t1A5cvmguest.iso -> E:\VirtualMachines\albtest1\vmguest.iso

2 - Verify GPO settings
By default, BITS transfers are wide open, not throttled down. Follow the MDSN article and look for the following settings in case they have been changed from default values.
     - Any setting with 'Peercache' in the name is not relevant
     - The rest of the settings should be set to 'Not Configured' or 'Disabled' to ensure that BITS is not being throttled at all. 'Maximum network bandwidth for BITS background transfers' is most important to be set to 'Not Configured' or 'Disabled'

BITS uses the following Group Policies to configure BITS
http://msdn.microsoft.com/en-us/library/aa362844(VS.85).aspx

The group policies for BITS are located in the registry here…

HKLM\Software\Policies\Microsoft\Windows\BITS

(Note that only those policies that are configured are listed in the registry.)

REMEMBER: Run ‘gpupdate /force’ following any changes from an elevated command prompt

3 - Disable Task Offloading
This work can be done easily on a non-Core server by disabling all properties on the 'Advanced' tab of all NICs. You should then follow the manual directions below to verify the rest of the Offload related settings for the NICs, and to disable this feature in Windows.

If working with a core server you may want to connect via remote registry and make these changes.
This MDSN article lists all values available.

Using Registry Values to Enable and Disable Task Offloading
http://msdn.microsoft.com/en-us/library/aa938424.aspx

All values should be set to '0' EXCEPT for the last one which is related to IPSEC, and thus Kerberos. Leave this one alone. 'HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Ipsec\EnabledOffload'  

A. Locate all physical NICs in the registry under:
'HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}'

B. There will be folders with four digits, starting with '0000'. Locate the ones that show the physical NIC names on the right. Look for the 'DriverDesc' value on the right; this should have the name of a NIC such as 'HP NC360T PCIe Gigabit Server Adapter.' For each of these, make the changes below.

C. Disable All Vendor specific Offloading
Set values for any entries below that include the word 'Offload' to '0' (Disabled)
*FlowControl

     No description available

*IPChecksumOffloadIPv4
     Describes whether the device enabled or disabled the calculation of IPv4
checksums.
*TCPChecksumOffloadIPv4
     Describes whether the device enabled or disabled the calculation of TCP Checksum
over IPv4 packets.
*TCPChecksumOffloadIPv6
     Describes whether the device enabled or disabled the calculation of TCP checksum
over IPv6 packets.
*UDPChecksumOffloadIPv4
     Describes whether the device enabled or disabled the calculation of UDP Checksum
over IPv4 packets.
*UDPChecksumOffloadIPv6
     Describes whether the device enabled or disabled the calculation of UDP Checksum
over IPv6 packets.
*LsoV1IPv4
     Describes whether the device enabled or disabled the segmentation of large TCP
packets over IPv4 for large send offload version 1 (LSOv1).
*LsoV2IPv4
     Describes whether the device enabled or disabled the segmentation of large TCP
packets over IPv4 for large send offload version 2 (LSOv2).
*LsoV2IPv6
     Describes whether the device enabled or disabled the segmentation of large TCP
packets over IPv6 for large send offload version 2 (LSOv2).
*IPsecOffloadV1IPv4
     Describes whether the device enabled or disabled the calculation of IPsec headers
over IPv4.
*IPsecOffloadV2
     Describes whether the device enabled or disabled IPsec offload version 2
(IPsecOV2). IPsecOV2 provides support for additional crypto-algorithms, IPv6, and
co-existence with large send offload version 2 (LSOv2).
*IPsecOffloadV2IPv4
     Describes whether the device enabled or disabled IPsecOV2 for IPv4 only.
*RSS
     Receive side scaling
*TCPUDPChecksumOffloadIPv4
     Describes whether the device enabled or disabled the calculation of TCP or UDP
checksum over IPv4.
*TCPUDPChecksumOffloadIPv6
     Describes whether the device enabled or disabled the calculation of TCP or UDP
checksum over IPv6.

D. Disable Offloading in Windows.
Use the following registry values to enable or disable task offloading for the TCP/IP protocol:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters\DisableTaskOffload

Setting this DWORD value to ‘1’ disables all of the task offloads from the TCP/IP transport. Setting this value to zero enables all of the task offloads.

Related Links
Network Issues with Windows Server 2008 RDP and VS/Hyper-V on Dell Servers
http://www.petri.co.il/network-issues-with-windows-server-2008-rdp-on-dell-servers.htm

Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization,windows

When the P2V process fails there can be a number of issues to identify. A number of situations are discussed below. The machine being virtualized is referred to as the Source machine. The location where the virtualized machine is being copied is the Destination Host.

Use this article as your main reference for all P2V issues
     P2V: Converting Physical Computers to Virtual Machines in VMM
     http://technet.microsoft.com/en-us/library/cc764232.aspx

Requirements for the Source Machine
To perform a P2V conversion, your source computer:
- Must have at least 512 MB of RAM.
- Must have an Advanced Configuration and Power Interface (ACPI) BIOS - Vista WinPE will not install on a non-ACPI BIOS.
- Must be accessible by VMM and by the host computer.
- Cannot be in a perimeter network (also known as a DMZ, demilitarized zone, and screened subnet) where the firewalls or IPsec settings prohibit communication.
- Must contain one of the following supported operating systems:
- Windows Server 2008 (32-bit)
- Windows Server 2008 (64-bit)
- Windows Server 2003 (32-bit) SP1 or later
- Windows Server 2003 (64-bit) SP1 or later
- Windows 2000 Server SP4 or later (Offline P2V only)
- Windows 2000 Advanced Server SP4 or later (Offline P2V only)
- Windows XP Professional (32-bit) SP2 or later
- Windows XP Professional (64-bit) SP2 or later
- Windows Vista (32-bit) SP1 or later
- Windows Vista (64-bit) SP1 or later

Errors and Resolutions
- Third party applications can lead to failures
     - Disable all antivirus using MSCONFIG and reboot
     - Disable all monitoring software such as Insight Manager (optional)
- Disable IIS on the source machine if running

Network Related - Source machine
Make sure that when rebooted into WinPE there is an IP address. There is a command prompt on the console. Type 'ipconfig /all' and verify with the customer that all IP settings are correct and match that of the SCVMM Server and Destination Host

If the IP starts with 169.254.x.x this is an auto-configed IP. This means there is no DHCP serve to provide an IP address or there are problems with the NIC drivers.  It is preferable that the source and destination host are on the same subnet. If not test all routing by pinging…
     - Ping the SCVMM and Host SCVMM servers by DNS name, not IP. If they do not resolve, correct DNS
     - Ping the IP address of the default gateway and DNS servers. If they do not reply, correct IP settings
     - If IP information needs to be set manually in WinPE, at a command prompt type:
‘netsh interface ipv4 set address "Local Area Connection" static 10.241.0.7  255.255.0.0    10.241.0.2    1’
     Where:
‘netsh interface ipv4 set address "Local Area Connection" static %ipaddr% %subnet% %dns server% 1’

Network Related - Source and SCVMM machines
On Windows 2003 machines follow the 'Workaround' in this article (disregard the fact that it is a SQL KB. It is correct). This will disable TCP Offloading in Windows 2003 SP2, which can lead to a number of networking issues.

     942861 Error message when an application connects to SQL Server on a server that is running Windows Server 2003:
     "General Network error," "Communication link failure," or "A transport-level error"
     http://support.microsoft.com/default.aspx?scid=kb;EN-US;942861

WMI and 'Access Denied' errors
Follow the article on this site ‘WMI Errors and SCVMM’

During 'Scan System' operation
Example Error
VMM does not have appropriate permissions to access the resource on the <destination_computer> server. Ensure that Virtual Machine Manager has the appropriate rights to perform this action.
ID: 2910
Details: Access is denied (0x80070005)

Resolution #1
- Make sure the computer object for the SCVMM server is in the Administrators group on the source machine
- Make sure the account specified in the SCVMM Admin Console is a member of the Administrators group on the source machine.
- SCVMM 2008 - If the machine is in a workgroup, make sure the Domain specified along with the Account and Password is actually the name of the source machine, not the domain of the SCVMM server

Resolution #2
Ensure that the following services are not set to 'Disabled,' and that you can start them successfully on the source machine
     - WMI
     - Background Intelligent Transfer Service (BITS)
     - HTTP SSL
     - RPC

Resolution #3
Enable auditing of object access to determine if the account specified in SCVMM or the SCVMM computer object are failing to access the source machine as required. Look for 'Failure' in the security log once configured and tested.

- Follow the first section of the article below 'For the local computer'
     325898 How to set up and manage operation-based auditing for Windows Server 2003, Enterprise Edition
     http://support.microsoft.com/default.aspx?scid=kb;EN-US;325898

- Record any settings under 'Audit Policy' that are already configured
- Change configure all Policies to record Success and Failure
- If any Policies have an icon of gray servers instead of blue 0's and 1's you will not be able to make this change and must involve the customer's Group Policy administrator
- Back at a command prompt type 'gpupdate /force'
- Try the scan again, then check the Security log for ’Failure’ audits
- Set all Policies back to the state you recorded them as before making changes

Resolution #4
Make sure the DCOM (DCOMLaunch) service is set to Automatic and running. (Thanks to Pramod for this tip)

Non-ACPI HAL
If the source machine has a non ACPI HAL P2V cannot be performed.

P2V: Converting Physical Computers to Virtual Machines in VMM
http://technet.microsoft.com/en-us/library/cc764232.aspx

309283 HAL options after Windows XP or Windows Server 2003 Setup
http://support.microsoft.com/default.aspx?scid=kb;EN-US;309283

249694 How to move a Windows installation to different hardware
http://support.microsoft.com/default.aspx?scid=kb;EN-US;249694

Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization,windows,P2V

There are many errors that may appear, based on events in SCVMM, to be WMI related. An understandable response would be to troubleshoot WMI. On the other hand, many ‘Access Denied’ errors, while pointing to WMI in no way, are actually the result of WMI issues. Below are a number of error examples that in one way or another are related to WMI. The best way to deal with these errors is divide and conquer. First, determine if WMI itself is responding correctly. By this I mean that we test WMI functionality alone, not in combination with SCVMM which has its own detached namespace. Second, with no fundamental problems found with WMI due to NIC teaming or otherwise, there are three updates that may very well resolve your issue. These should be installed on all Windows 2008 servers that hold SCVMM components. The updates are at the bottom of this post. Good luck!

_____ERRORS_____

SCVMM Admin Console typical errors for Hosts
     'Connection Status: Not responding'
     'Virtualization service status: unknown"

WMI typical errors
Example #1
Log Name: Application
Source: Microsoft-Windows-WMI
Event ID: 10
Task Category: none
Description:
Event filter with query "select * from __instancemodificationevent within 30 where
targetinstance isa 'Win32_PerfFormattedData_PerfOS_Processor' and
targetinstance.PercentProcessorTime > 99 and targetinstance.Name != '_Total'" could
not be reactivated in namespace "//./root/CIMV2" because of error 0x80041010.
Events cannot be delivered through this filter until the problem is corrected.

Example #2
Log Name: Application
Source: Application Error
Event ID: 1000
Task Category: (100)
Description:
Faulting application wmiprvse.exe, version 6.0.6001.18000, time stamp 0x4791950f,
faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791adec, exception
code 0xc0000005, fault offset 0x000000000003e39c, process id 0x944, application
start time 0x01c95ba1faa603ce.

Jobs list errors in SCVMM Admin Console
Example #1

Error (2911)
Insufficient resources are available to complete this operation on the
server.contoso.com server.
(Not enough storage is available to complete this operation (0x8007000E))
Recommended Action
Ensure that the virtual machine host has sufficient memory and disk space to
perform this action. Try the operation again.

Example #2

Warning (10803)
Unable to refresh \\server.contoso.com\ISOS$\WinPE_X86_with_HyperV_ICs.iso because
the file is in use by another process.
Recommended Action
Wait for the next automatic library refresh, or manually refresh the library share
after the process completes.

Example #3
Error (2912)
An internal error has occurred trying to contact an agent on the server.contoso.com
server.
(No more threads can be created in the system (0x800700A4))
Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is
installed and running, then restart the agent.

Example #4
Error (2912)
An internal error has occurred trying to contact an agent on the
ephypv01.constrution.enet server. (The paging file is too small for this operation
to complete (0x800705AF)
 

_____TEST_____ 
Verify that various WMI namespaces can be connected to, then update WMI on all involved Windows 2008 machines

Using wbemtest
- Click the 'Start' button
- Start> Run> wbemtest
     - Click 'Connect' and enter 'root\cimv2' then click 'Connect' again. This should not prompt with an error
     - Click 'Connect' and enter 'root\default' then click 'Connect' again. This should not prompt with an error
On a Hyper-V server, this should also work
     - Click 'Connect' and enter 'root\virtualization' then click 'Connect' again. This should not prompt with an error.

On an SCVMM Server (Host) this should also work
     - Click 'Connect' and enter 'root\scvmm' then click 'Connect' again. This should not prompt with an error
     - Close 'wbemtest'

Using command line
- From an elevated command prompt type 'wmic nic' and press Enter
- This should return information, not an error. If there is an error, and all other tests work, this is likely due to NIC TEAMING. Uninstall all NIC Teaming software, reboot and try again
- From an elevated command prompt type 'wmic diskdrive list brief' and press Enter
- This should return information, not an error

_____UPDATE_____

Install WMI Updates and Hotfixes
Each requires a reboot

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
http://support.microsoft.com/default.aspx?scid=kb;EN-US;954563

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
http://support.microsoft.com/default.aspx?scid=kb;EN-US;958124

955805 Certain applications become very slow on a Windows Server 2008-based or Windows Vista SP1-based computer when a certificate with SIA extension is installed

http://support.microsoft.com/kb/955805

Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization,windows

Need to add a Host? Click 'To add hosts'. Want to configure a SAN environment for VMM? There's a button for that too. This screen capture shows a few of the options available in the decision flow designed to take you to the right content for the job at hand.

Here's the link: http://technet.microsoft.com/en-us/scvmm/cc835256.aspx

Content below is the table version of the interactive decision flow located here:

http://technet.microsoft.com/en-us/scvmm/cc835256.aspx

Below is an excerpt from Justin Zarb’s article on his ‘Virtual World’ site.

Quick Start from Nothing to SCVMM

http://blogs.technet.com/virtualworld/archive/2007/10/18/quick-start-from-nothing-to-scvmm.aspx

So I have been chatting to more and more people around System Center Virtual Machine Manager (SCVMM) and this product is great! Compared to other virtualization management tools that I have used in the past (prior to myself joining MS) this product really stands up and stands proud! If you have not played with SCVMM it is soooo simple and sooooooo easy to get up and running and communicating to your virtualized estate. I strongly recommend you all to give it a try.

Anyway so whilst reading some of the techcenter articles I came across these for SCVMM. There is a range of how to video's that are here to set you on your way and get you going! Click on one of the links below and start getting SCVMM underway.......  

Getting Started

Setup

Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization,windows,P2V,V2V