Jonathan's Virtual Blog : WinRM

WinRM (Windows Remote Management) Troubleshooting

Jonathan — Sat, 10 Jan 2009 01:44:00 GMT

What is WinRM?

New in Windows Vista, Windows Server 2003 R2, Windows Server 2008 (and Server 2008 Core) are WinRM & WinRS. Windows Remote Management (known as WinRM) is a handy new remote management service. WinRM is the “server” component of this remote management application and WinRS (Windows Remote Shell) is the “client” for WinRM, which runs on the remote computer attempting to remotely manage the WinRM server. However, I should note that BOTH computers must have WinRM installed and enabled on them for WinRS to work and retrieve information from the remote system.

While WinRM listens on port 80 by default, it doesn't mean traffic is unencrypted. Traffic by default is only accepted by WinRM when it is encrypted using the Negotiate or Kerberos SSP. WinRM uses HTTP (TCP 80) or HTTPS (TCP 443). WinRM also includes helper code that lets the WinRM listener to share port 80 with IIS or any other application that may need to use that port.

WinRM with SCVMM uses Kerberos for authentication, and does not support fall-back to NTLM. There will be an error instead. If no credentials are specified, then the logged-on credentials are used to authenticate against the remote machine. This allows for a single sign-on experience.

What is WinRS?

Remote Shell, (WinRS) is used to execute a program on a remote host. Similar in operation to the former Sysinternals tool PSExec, WinRS leverages Windows Remote Management to let you launch processes on remote machines. For example, if you want to perform a directory listing on the system drive on a remote machine, you can remotely launch ‘dir’ using this syntax:

winrs -r:machinename dir

Another handy use of WinRS can be when installing software on remote systems. If you want to quietly install an application using an MSI file onto a remote machine, use the following syntax. This syntax assumes the MSI file has already been deposited into the C:\ folder.

winrs -r:machinename msiexec.exe /i c:\install.msi /quiet

When specifying the remote machine, the following are valid:

· Localhost

· NetBIOS name

· Fully Qualified Domain Name (FQDN)

· IP address

How to install WinRM

The WinRM is not dependent on any other service except WinHttp. If the IIS Admin Service is installed on the same computer, you may see messages that indicate WinRM cannot be loaded before Interent Information Services (IIS). However, WinRM does not actually depend on IIS: these messages occur because the load order ensures that the IIS service starts before the HTTP service. WinRM does require that WinHTTP.dll be registered.

(Stated simply: WinRM service should be set to Automatic (Delayed Start) on Windows Vista and Server 2008)

· The WinRM service starts automatically on Windows Server 2008.

· On Windows Vista, the service must be started manually.

· UPDATE! Windows 2003 requires an update for WinRM

936059 An update is available for the Windows Remote Management feature in Windows Server 2003 and in Windows XP

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

How to configure WinRM

To set the default configuration type:

winrm quickconfig (or the abbreviated version, winrm qc)

‘winrm qc’ performs the following operations:

1. Starts the WinRM service and sets the service startup type to auto-start.

2. Configures a listener for the ports that send and receive WS-Management protocol messages using either HTTP or HTTPS on any IP address.

3. Defines ICF exceptions for the WinRM service and opens the ports for HTTP and HTTPS.

(Note: Winrm quickconfig also configures Winrs default settings)

If ‘winrm qc’ throws an error:

If the firewall is disabled the quick config command will fail. The firewall can either be started in Services long enough to run ‘winrm qc’ or the commands below can be run:

sc config "WinRM" start= auto

net start WinRM

winrm create winrm/config/listener?Address=*+Transport=HTTP

netsh firewall add portopening TCP 80 "Windows Remote Management"

Group Policy configuration:

WinRM can be configured by group policies.

1. Type gpedit at a command prompt. The Group Policy Object Editor window opens.

2. Look for the Windows Remote Management and Windows Remote Shell Group Policy Objects (GPO) under Administrative Templates and Windows Components.

Troubleshoot WinRM

Common Issues:

1. If the ISA2004 firewall client is installed on the computer, it can cause a Web Services for Management (WS-Management) client to stop responding. To avoid this issue, install ISA2004 Firewall SP1.

2. Antivirus software can prevent proper WinRM communication. Disable antivirus software and reboot the machine if the Antivirus software is known to scan processes and protocols, or if there is any doubt about the software.

Test WinRM communication on the local and remote machines

This section addresses how to test whether WinRM is working on the local system, and whether it can communicate with the remote system. Test remote communication in both directions between machines.

Local communication:

Locate listeners and addresses: (No output means WinRM is not installed)

winrm e winrm/config/listener

Localhost Ping:

(Successfully completing this step pretty much insure complete access to WSMan on the local system)

Winrm id

Further:

Check state of configuration settings:

winrm get winrm/config

Check the state of WinRM service:

winrm get wmicimv2/Win32_Service?Name=WinRM

Remote communication:

Locate listeners and addresses:

winrm e winrm/config/listener

Remote Ping:

(Successfully completing this step pretty much insure complete access to WSMan on the remote system)

Winrm id –r:machinename

Further:

Check state of configuration settings:

winrm get winrm/config -r:machinename

Check the state of WinRM service:

winrm get wmicimv2/Win32_Service?Name=WinRM -r:machinename

Sample Commands

Here are some sample commands to play with. If you cannot get the ‘Test WS-Man...' step to work, none of the steps following will work either (you're probably not using the right credentials to access the remote machine). One more caveat, the remote commands work best on domain joined machines. For workgroup machines, the WinRM service needs additional configuration.

Description	Command
Run from an Elevated* Command prompt*
Quickly configure the WS-Man service	winrm QuickConfig
Quickly delete the WS-Man listener	winrm invoke Restore winrm/Config @{}
Run from an standard* Command prompt*
Display your machine's basic hardware info	winrm enumerate wmicimv2/Win32_ComputerSystem
Display your operating system properties	winrm get wmicimv2/Win32_OperatingSystem
Output your OS info in XML	winrm get wmicimv2/Win32_OperatingSystem -format:pretty
Test WS-Man access to a remote machine**	winrm id -remote:<some machine>
Grab a remote machine's WS-Man config	winrm get winrm/Config -r:<some machine>
Grab a remote machine's CPU load	winrm g wmicimv2/Win32_Processor?DeviceID=CPU0 -fragment:LoadPercentage -r:<some computer>
Grab a remote machine's free memory	winrm g wmicimv2/Win32_OperatingSystem -fragment:FreePhysicalMemory -r:<some computer>
Stop a service on a remote machine	winrm invoke stopservice wmicimv2/Win32_Service?name=w32time -r:<some computer>
Start a service on a remote machine	winrm invoke startservice wmicimv2/Win32_Service?name=w32time -r:<some computer>
Reboot a remote machine	winrm invoke reboot wmicimv2/Win32_OperatingSystem -r:<some computer>
Run a command on a remote machine (this uses winrS, not winrM)	winrs -r:<some computer> ipconfig /all
Run from PowerShell
Use PowerShell to grab the WS-Man Win32_OperatingSystem XML output	[xml]$osInfo = winrm get wmicimv2/Win32_OperatingSystem /format:pretty
Display the OS version property	$osInfo.Win32_OperatingSystem.Version
Display the last boot time	$osInfo.Win32_OperatingSystem.LastBootupTime.DateTime
Put free memory metric into an XML variable	[xml]$freemem = cmd /c "winrm get wmicimv2/Win32_OperatingSystem -fragment:FreePhysicalMemory -f:pretty -r:<some computer>"
Display the free memory value	$freemem.XMLFragment.FreePhysicalMemory

**Note: This step verifies that you have good connectivity to the remote machine, WS-Man is running and properly configured on the remote machine, AND you have the correct permissions to fully leverage WS-Man on the remote machine. If this step fails, it's probably a permissions issue.

Advanced Concepts

URI Aliases

URI aliases can simplify the Winrm command line. The following URI aliases are supported:

wmi = http://schemas.microsoft.com/wsman/2005/06/wmi

wsman = wsman:microsoft.com/wsman/2005/06/

cimv2.9 = http://schemas.dmtf.org/wsman/2005/06/cimv2.9

cimv2 = http://schemas.microsoft.com/wsman/2005/06/wmi/root/cimv2

For example, the following command:

winrm get http://schemas.microsoft.com/wsman/2005/06/wmi/root/cimv2/Win32_Service?Name=WSMan

Gets replaced with:

winrm get wmi/root/cimv2/Win32_Service?Name=WinRM

Performing an Invoke Operation

‘Invoke’ initiates commands

winrm invoke StartService wmicimv2/Win32_Service?Name=WinRM -r:machinename @{}

This will likely return ‘ReturnValue = 10’ on a remote system where WinRM is running

WS-Man (WinRM) Architecture

The following diagram shows a high-level overview of the WS-Man (WinRM) architecture. In the diagram the 'Client' is querying the 'Server' for WS-Man information. Note that HTTP.sys and WinHTTP support the HTTP(s) transport for WS-Man, not IIS. In addition, IIS (or another web publishing service) can co-exist with WS-Man and share port 80.

Remember:

WinHTTP = Client

HTTP.SYS = Server

The Windows Remote Management architecture consists of components on the client and server computers. The following illustration shows the components on both computers, how the components interact with other components, and the protocol that is used to communicate between the computers.

Requesting Client

The following WinRM components reside on the computer that is running the script that requests data.

· WinRM application

This is the script or Winrm command-line tool that uses the WinRM scripting API to make calls to request data or to execute methods. For more information, see the WinRM Scripting API [ http://msdn.microsoft.com/en-us/library/aa384469(VS.85).aspx ] .

· WsmAuto.dll

The OLE automation layer that provides scripting support.

· WsmCL.dll

C API layer within the operating system.

· HTTP API

WinRM requires support for HTTP and HTTPS transport.

Responding Server

The following WinRM components reside on the responding computer.

· HTTP API

WinRM requires support for HTTP and HTTPS transport.

· WsmAuto.dll

The OLE automation layer that provides scripting support.

· WsmCL.dll

C API layer within the operating system.

· WsmSvc.dll

WinRM listener [ http://msdn.microsoft.com/en-us/library/aa384465(VS.85).aspx ] service.

· WsmProv.dll

Provider subsystem.

· WsmRes.dll

Resource file.

· WsmWmiPl.dll

WMI plug-in [ http://msdn.microsoft.com/en-us/library/aa384465(VS.85).aspx ] . This allows you to obtain WMI data through WinRM.

· Intelligent Platform Management Interface (IPMI) driver and WMI IPMI provider

These components supply any hardware data that is requested using the IPMI classes. For more information, see Intelligent Platform Management Interface (IPMI) Classes [ http://msdn.microsoft.com/en-us/library/aa390891(VS.85).aspx ] . BMC hardware must have been detected by the SMBIOS or the device created manually by loading the driver. For more information, see Installation and Configuration for Windows Remote Management [ http://msdn.microsoft.com/en-us/library/aa384372(VS.85).aspx ] .

References

Installation and Configuration for Windows Remote Management

http://msdn.microsoft.com/en-us/library/aa384372(VS.85).aspx

Windows Remote Management Command-Line Tool (Winrm.cmd)

http://technet.microsoft.com/en-us/library/cc781778.aspx

How can Windows Server 2008 WinRM & WinRS help you

http://windowsnetworking.com/articles_tutorials/How-Windows-Server-2008-WinRM-WinRS.html

The things that are better left unspoken Remotely managing your Server Core using WinRM and WinRS

http://blogs.dirteam.com/blogs/sanderberkouwer/archive/2008/02/23/remotely-managing-your-server-core-using-winrm-and-winrs.aspx

Redmond Print First Look WinRM & WinRS

http://redmondmag.com/columns/article.asp?EditorialsID=2262

Otto Helweg - Management Matters A Few Good Vista WS-Man (WinRM) Commands

http://blogs.technet.com/otto/archive/2007/02/09/sample-vista-ws-man-winrm-commands.aspx

Windows Remote Management Architecture

http://msdn.microsoft.com/en-us/library/aa384464(VS.85).aspx

How to Capture a WinRM Trace

Jonathan — Tue, 06 Jan 2009 02:04:00 GMT

When working with Microsoft Support you may be asked to capture traces to assist with issue resolution. Below are two methods for capturing WinRM traces. Following a reboot these will need to be set up again. The GUI setup is simple. The logman method allows a template with pre-populated settings to be imported. Choose the method that suits you.

Method 1 using GUI

1. Open Perfmon and navigate to Event Trace Sessions. In your case you will run this from a non-core box and connect to the core box first.

2. Right click Event Trace Sessions and choose New Data Collector Set.

3. Name it WinRM, select “Create manually” and click Next

4. Click “Add” when prompted “Which event trace providers would you like to enable?”

5. Select “Windows Remote Management Trace”.

6. Select the Keywords(Any) Property and choose edit.

7. Add the desired values. I selected all of them and clicked OK.

8. Select Level and then Edit.

9. Select the Manual option, change the value to 0x05, and click OK.

10. Click Next.

11. Change the Root Directory to the destination location for the trace log.

12. Click Finish (Repeat process for both client and server)

13. Start the trace by selecting WinRM and choosing Start (on client and server)

14. Reproduce the issue.

15. Stop the trace by selecting WinRM and choosing stop for both systems.

16. You will have a winrm.etl file in the location that was set in step 11.

Method 2 using LOGMAN

1. Rename the attached WinRMETL.txt file to WinRMETL.xml

2. Create a folder called “winrm” on the root of the C drive of the node that is having the Winrm problem, node 2 for example.

3. Copy the xml file to that folder and change into that folder

4. Enter “logman /import –n mytrace –xml c:\winrm\WinRMETL.xml” and press enter.

5. Enter “logman” and press enter and should see the “mytrace” as a Data Collector Set”

6. Repeat this for the client from where you will run the Winrm command.

7. On both systems Enter “logman start mytrace” to start the tracing.

8. On the client system enter the “winrm id -r:<targetname>

9. Stop trace by entering “logman stop mytrace” on both systems.

10. There will be a file created called winRM2.etl in the C:\winrm directory.

How to Troubleshoot Host Status - Quick Table

Jonathan — Tue, 30 Dec 2008 03:18:00 GMT

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 ] ).

Note

The host status values do not change in the VMM Administrator Console until the VMM server performs a refresh.

The following table describes the host status types and values.

Status Type

Status Value and Definition

Overall host status

· OK—no issues exist with any host status.

· Needs Attention—a problem exists with one or more host statuses.

Agent connection status

· Responding—the VMM server is able to communicate with the agent.

· Not Responding—the VMM server is unable to communicate with the agent.

· Access Denied—the agent is no longer associated with the VMM server.

Agent version status

· Current—the version of the agent is up to date.

· Needs update—the version of the agent must be upgraded to match the version of VMM server.

· Unsupported—the version of the agent is not supported for any VMM functions.

Virtual Server service status

· Running—the Virtual Server service is started.

· Stopped—the Virtual Server service is stopped.

Virtual Server version status

· Current—the version of Virtual Server is up to date.

· Needs update—the version of Virtual Server needs to be upgraded.

· Unsupported—the version of Virtual Server is not supported for any VMM functions.

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

Understanding Microsoft Virtualization Solutions - eBook download (did I mention FREE?)

Jonathan — Mon, 29 Dec 2008 22:54:00 GMT

I found this link on ‘Keith Combs' Blahg.’ Written by Mitch Tulloch with the Microsoft Virtualization team, this is THE reference for all things virtual: Hyper-V, SCVMM, App-V, Med-V, and USMT. Download and read today!

http://blogs.technet.com/keithcombs/archive/2008/12/19/thanks-for-attending-the-usa-virtualization-tour-ebook-download.aspx

Direct download link:

https://www.getvirtualnow.com/usevents/education/download/693371eBook.pdf

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

WMI Errors and SCVMM – If It’s Not Broken, Update It!

Jonathan — Mon, 29 Dec 2008 12:02:00 GMT

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

Troubleshooting and Data Collection During Offline P2V

Jonathan — Mon, 29 Dec 2008 11:36:00 GMT

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