IT Core Blog

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

Posts Tagged ‘P2V

SCVMM P2V fails with Error 2910 (0x80070005) Access Denied

leave a comment »

Symptom

When using Microsoft System Center Virtual Machine Manager 2008 to perform a Physical-to-Virtual conversion (P2V), the following error message appears during the Scan System phase.
Error (2910)
VMM does not have appropriate permissions to access the resource on the %server.
Access is denied (0x80070005)
Recommended Action
Ensure that Virtual Machine Manager has the appropriate rights to perform this action.
Additional Information: The Source computer is the machine intended to be virtualized in the P2V conversion.

 Cause

This failure is typically caused by either of the following conditions:

•  The credentials provided during the P2V wizard is not a member of the local ‘Administrators’ group on the Source computer.
•  The Source computer does not allow remote WMI calls to the CIMV2 namespace for the credentials entered during the P2V wizard.

Resolution
To resolve the problem, follow these steps:

  1. Make sure that the account used during the P2V wizard is a member of the local ‘Administrators’ group on the Source computer. Note Pay particular attention to this if the SCVMM server and Source computer are in different domains.
  2. During the Scan System phase of the P2V conversion, SCVMM makes WMI calls to the CIMV2 namespace on the Source computer to pull basic system information. If these WMI calls fail, then the P2V conversion will also fail. To verify WMI connectivity to the CIMV2 namespace on the Source computer, perform the following actions from the SCVMM server:
  3. Click Start , point to Run and type ” WBEMtest” (without the quotes) in the Open box and click OK . This will open the WBEMtest window.
  4. Click Connect in the upper right hand corner.
  5. Now, connect to the CIMV2 namespace on the Source computer.

Example: \\Source\ROOT\CIMV2

                Note Be sure to use the name of your Source computer.

  1. Then click Connect to complete the connection. This should connect without any errors displayed.
  2. Just to confirm access to a sample object, select Open Class and type Win32_PhysicalMemory
  3. You should see objects populate in the Object Editor window. The actual content returned is not as important as the fact that a remote connection to the CIMV2 namespace was established.
  4. Open wmimgmt.msc and verify connectivity to the Local computer and also check the ‘Remote Enable’ permissions.
    1. Click Start , point to Run and type wmimgmt.msc and click OK . This will open the WMI Control (Local).
    2. Right click on the WMI Control (Local) node and select Properties .
    3. Select the Security tab, highlight Root and then open security by clicking the Security button in the lower right.
    4. Select “Remote Enable” permission for Everyone or the specific user account that you want to grant this permission to.
    5. This action does not require a reboot.
    6. Open dcomcnfg and verify that DCOM is running and also check the ‘Remote Activation’ permission.
      1. Click Start , point to Run and type dcomcnfg and click OK . This will open the Component Services snap-in.|
      2. Expand Component Service , then Computers , then My Computer . If My Computer has a red down arrow mark, it means that the service is not running. It will need to be started.
      3. Right click on My Computer and select Properties and select the COM Security tab.
      4. Click Edit Limits under the Launch and Activation Permissions section.
      5. For the Everyone user give the “Remote Activation” permission or add the specific user account that you want to grant this permission to.

Note The following error message may occur if the appropriate WMI permission is not granted to the user:
Access Denied” with Error Code: 0x80041003

  1. This problem can also occur if the OLE registry key is missing or has the incorrect value on the Source computer.
    1. Start Registry Editor.
    2. Locate the following path:
      HKLM\SOFTWARE\Microsoft\OLE
    3. This key should have a REG_SZ value EnableDCOM and a value of Y
Advertisements

Written by IT Core

November 23, 2010 at 9:17 PM

KB2465160: Add Host or other action fails with (2916) 0x80338126 in System Center Virtual Machine Manager 2008

leave a comment »

From Microsoft , KB2465160.

Symptoms
Adding a Host to System Center Virtual Machine Manager 2008 (SCVMM 2008) fails with a variation of Error (2916):

Error (2916)
VMM is unable to complete the request. The connection to the agent ServerA.contoso.com was lost.
(The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. (0x80338126))

Recommended Action:
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic. If the error persists; reboot ServerA.contoso.com and then try the operation again.

Cause
Specific content is being filtered by a non-Windows firewall. The firewall could be software installed on either the SCVMM 2008 Server or the Host that is being added. More likely, there is a hardware appliance firewall on the network between the two communicating servers.

Resolution
Test multiple communication protocols between the two systems; the SCVMM 2008 Server and Host in this example. Some firewalls can have content filtering enabled despite showing that it is not. Remove all non-Windows software firewalls and bypass all hardware appliance firewalls entirely long enough to perform testing to verify whether or not they are contributing to the problem.

The following tests are examples of protocols that should always succeed. Test both directions always:

Ping by DNS name in both directions (NETBIOS and FQDN). The IP address returned must match.
Access to ‘\\ServerA.contoso.com\admin$’ from the ‘Run’ command in both directions. This must succeed.
From Server B: \\ServerA.contoso.com\admin$
From Server A: \\ServerB.contoso.com\admin$
WinRM basic connectivity in both directions. This must succeed. If it does not, execute ‘winrm qc’ on both servers, accepting all prompts, then test again.
Remote NETBIOS test: winrm id -r:remoteserver
Remote FQDN test: winrm id -r:remoteserver.contoso.com
WinRM successful reply example:

C:\>winrm id -r:ServerA
IdentifyResponse
    ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
    ProductVendor = Microsoft Corporation
    ProductVersion = OS: 6.1.7600 SP: 0.0 Stack: 2.0

More Information
Recently a firewall appliance sold by a major vendor showed content filtering disabled and not licensed to be turned on, yet was still filtering specific content. This was discovered through examination of network traces. Do not assume content, protocols or traffic are not being blocked. Perform tests to verify.

Written by IT Core

November 23, 2010 at 9:12 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

Image to Virtual Hard Disk (WIM2VHD) Converter

leave a comment »

You can use WIM2VHD to quickly create a VHD from a WIM file, e.g. the install.wim file in the Vista/Windows7/Server 2008/Server 2008 R2 installation media, and then attach that VHD to a Hyper-V virtual machine.

Mikael Nystrom blogged about WIM2VHD.

Sometimes you need a fast way to create a reference image. You know, suddenly you need to have a VHD file of Windows Server 2008 R2 and a Windows 7 machine, like NOW. It always seem to be NOW or yesterday that things need to be done, wonder why…

Anyway, you need the following:

WAIK (Well, you only need Imagex, but if you have WAIK installed you have that)
WIM2VHD, and that’s just a small download
The OS (You only need the Install.wim, but I’ll guess you already have the DVD somewhere anyway)
WIM2VHD
This tools i really nice actually, but it only supports Windows 7 and Windows Server 2008 R2. The command line to create a VHD file is quite simple:

cscript WIM2VHD.wsf /wim:g:\sources\install.wim /sku:1

That will create a 40gb dynamic VHD file in less than 3 minutes (Yes, I do have a SSD disk), but it also have a bunch of other commands that could be used to make it more fun 🙂

Required parameters:

  /wim: Path to the .wim file
  /sku: Sku number or sku name

Some Optional parameters:

  /vhd: Name and path to the VHD file you would like to have
  /size: Size (default is 40960 mb)
  /disktype: Dynamic, Fixed or FastFixed (FastFixed requires VHDTOOL)
  /unattend: Path and name of an unattended XML file
  /qfe: A comma-seperated list of .MSU files that you would like to have in the image
  /mergefolder: Names of folders that you would like to have in the image

I use it from time to time when a need a fast solution and i don’t have time to do it the “real” way and in this case the real way is using MDT of course.

Nice work 🙂

Written by IT Core

August 26, 2010 at 12:00 AM

Posted in Tools, Virtualization

Tagged with ,

FREE tool remove the HP Proliant Support Pack from Virtualized Servers

leave a comment »

Guillermo Musumeci has written a good tool for removing HP Proliant Support Pack, this tool is a nice tool to use before p2v migrations )you must remove all driver software before you start p2v).

 

Download: Here

Written by IT Core

July 7, 2010 at 11:00 PM

Linux P2V – Vmware and Hyper-V

leave a comment »

Although you can P2V Windows machines using System Center Virtual Machine Manager, the same functionality is not available for Linux computers (Note:  You can V2V a Linux VM).

VMware vCenter Converter is a free tool that allows you to convert Linux physical machines into VMs. The process will create a vmdk disk file.  The problem is that it appears that the target must be VMware ESX, ESXi, Workstation or Player.

If you need to move that machine to Hyper-V, you can, in theory, use a tool like VMDK2VHD to convert that vmdk to a vhd file. If you’re using System Center Virtual Machine Manager to mange VMware vCenter Server you can do a direct V2V from VMWare ESX to Hyper-V hosts. After migration process, you’ll need to install integration components which are supported on RHEL and SLES.

Written by IT Core

February 24, 2010 at 12:00 AM

P2V – Disk2vhd v1.4

leave a comment »

Disk2vhd is a utility that creates VHD (Virtual Hard Disk – Microsoft’s Virtual Machine disk format) versions of physical disks for use in Microsoft Virtual PC or Microsoft Hyper-V virtual machines (VMs). The difference between Disk2vhd and other physical-to-virtual tools is that you can run Disk2vhd on a system that’s online. Disk2vhd uses Windows’ Volume Snapshot capability, introduced in Windows XP, to create consistent point-in-time snapshots of the volumes you want to include in a conversion. You can even have Disk2vhd create the VHDs on local volumes, even ones being converted (though performance is better when the VHD is on a disk different than ones being converted).

Get it Now

🙂

Written by IT Core

January 2, 2010 at 11:01 PM