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

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

How to P2V with Virtual Machine Manager 2008 and 2008 R2 Part 2

with one comment

If you miss part 1 of this series, please check it here.

Now that we already know the minimum requirements to run P2V conversions, let’s check what additional steps we need to perform in order to get our physical computer converted to virtual.

I recommend that you run the VMMCA (Virtual Machine Manager 2008 and 2008 R2 Configuration Analyzer) before starting the process, this diagnostic tool will determine important pre-installation or post-installation configuration settings for computers that either might serve or are serving Virtual Machine Manager (VMM) roles or other VMM functions. You should use this version of the VMMCA with VMM 2008 and VMM 2008 R2 only. All steps performed by VMMCA are described in detail here.

After you run the scan, the output should be similar to:

Now that we run the VMMCA and the output report shows “No configuration issues found” is time to open the Virtual Machine Manager Administrator Console, in the Actions pane in any view, click Convert physical server to open the Convert Physical Server Wizard.

On the following screen enter the computer name or IP address, an Account with local Administrator rights in the source computer. If the computer account that you’re using is a local account, then change the “Domain or computer name” to the machine’s name and click Next.

On the next screen enter the Virtual Machine Name and the proper owner, additionally you may enter some words for description for the new VM, then click Next.

On the next screen “System Information“, click “Scan System”  and the P2V agent is installed on the remote physical system with the credentials provided before and gathers the source computer’s hardware and software configuration (You can consult detailed information for this process here). After that, hit the Next button.

The Volume Configuration page will allow you to define the disk size (cannot be smaller than the existing one), the VHD type (Dynamic or Fixed), the controller channel and type (IDE or SCSI). Under conversion options you can choose between Online and Offline conversions, you can also decide either to shutdown or not the source computer after finishing the P2V process. In this scenario I’ll choose the Offline Conversion type. Make your required modifications and then click Next.

On the Offline Conversion Options page (assuming that you choose Offline Conversion), You’ll have to decide if you want to use DHCP or a Fixed IP Address. If using DHCP, make sure that the SCVMM can solve the DNS name of the source computer to the correct IP provided by the DHCP server. Make your required modifications and then click Next.

On the next screen “Virtual Machine Configuration” you can modify the settings for vCPU and Memoryto be configured in the final VM. For a Windows 2000 server, remember that only a single processor configuration is supported. Make your required modifications and then click Next.

On the Select Host page, select between the available hosts which are ranked based on performance and available capacity for this virtual machine. The hosts are ranked using a star ranking with the recommended host at the top of the list. Select the Hyper-V host or the Virtual Server where you want to place the new virtual machine and then click Next.

On the Select Path page, select an available drive with sufficient space to allocate the new VHD, also consider future snapshots and additional growth for additional VHD files if required. The host that I selected is a Hyper-V R2 node member of a Hyper-V R2 cluster with CSV enabled, in this scenario I’ll need to select the mount point that is created under C:\ClusterStorage\Volume(x). Select your drive and then click Next.

On the Select Networks page, select an available VSwitch that was previously created in the Hyper-V or Virtual Server Host Server. If you’re converting a Domain Controller you may want to check Not Connected in order to prevent unwanted network communications until you have verified everything is working correctly. Make your required modifications and then click Next.

On the Additional Properties page, select the Automatic Stop and Start actions you prefer and then click Next.

On the Conversion Information page, Confirm that the message No issues detected appears. If any issues are reported by the wizard those must be address before the conversion can continue. Each issue in the list explains how to resolve the issue. After resolving all issues, click Check Again to check for additional issues. When no issues are detected, click Next to continue.

On the Summary page, review the configuration settings. To change settings, click Previous. Optionally, click View Script to view (and copy) the Windows PowerShell script that runs this wizard and performs the conversion. All administrative tasks in VMM can be scripted or performed at the command line. For more information, see Scripting. Optionally, select the Start the virtual machine after deploying it on the host check box. Click Create to create the virtual machine.

The end Result should be similar to this:

Great job 🙂

DONE!!!

Written by IT Core

December 20, 2009 at 7:23 PM

How to P2V with Virtual Machine Manager 2008 and 2008 R2 Part 1

with one comment

As you may know Microsoft System Center Virtual Machine Manager (SCVMM) allows you to convert existing physical computers into virtual machines using P2V (physical-to-virtual). Most of the times the task-based wizard will be used because automates much of the conversion process, but since the P2V process is completely scriptable, you can take advantage of it to initiate large scale P2V conversions using Windows Power Shell  (in this post we’ll look at P2V using the GUI).

Let’s look at both (Online & Offline) conversions type and their differences:

Online P2V: This type of conversion runs with the source computer online and no reboot is required. During the conversion process the P2V agent acts like an backup requester using the VSS (Shadow Copy Service) for volumes and applications VSS aware. This process also ensures that the physical computer doesn’t “suffer” regarding to resources consumption with the P2V task, the computer continues to perform the tasks that it is expected to perform during normal operations.

Offline P2V: The conversion begins after the computer is booted with WinPE, which means that the source computer to be virtualized is NOT available during the entire conversion, the advantage of it, is that a consistent image will be taken from the source computer without the need to have applications that are VSS aware nor you’ll have the need to stop services and their dependencies that’s why Offline P2V is considered the most reliable method for converting physical computers to a virtual machines without potential data loss. For offline conversions, be prepared to supply NIC and mass storage drivers that are compatible with Windows Vista. VMM will evaluate the source physical computer and compare it with the drivers included in Windows PE and provide instructions on adding drivers on the source computer.

Before starting the P2V conversions  let’s check the Hardware and Software requirements:

Source Machine:
– 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 SCVMM and by the Host computer.
– If performing Offline conversions, the P2V agent will identify any additional drivers or updates that may be needed (These drivers must be Vista compatible because the WinPE will run under Vista OS).
Cannot be in a perimeter network (DMZ, demilitarized zone, screened subnet) where the firewalls or IPSec settings prohibit communication.

Operating System VMM 2008 VMM 2008 R2
Windows NT 4 (You can use the Microsoft Virtual Server 2005 Migration Toolkit (VSMT) or third-party solutions for converting computers running Windows NT Server 4.0.) No No
Microsoft Windows 2000 Server (Standard and Advanced) with Service Pack 4 (SP4) or later (offline P2V only) Yes (Offline P2V only) Yes (Offline P2V only)
Windows XP Professional (32Bit and 64Bit) with Service Pack 2 (SP2) or later Yes Yes
Windows Server 2003 (Standard, Enterprise and Datacenter Edition-32-bit and 64 Bit) Yes (With SP1 or later) Yes (With SP2 or later)
Windows Server 2003 Web Edition Yes Yes
Windows Small Business Server 2003 Yes Yes
Windows Vista (32-bit and 64-Bit) Yes (With SP1 or later) Yes (With SP1 or later)
Windows Server 2008 (Web, Standard, Enterprise and Datacenter – 32-Bit and 64-Bit) Yes Yes
Windows 7 (32Bit and 64-Bit) No Yes
Windows Server 2008 R2 (Web, Standard, Enterprise and Datacenter) No Yes
Itanium architecture–based operating systemsBottom of Form No No

 

Requirements for the Destination Host Server:
– The destination host cannot be in a perimeter network.
– Must have sufficient memory for the new  virtual machine plus the memory reserved for the host operating system (256 MB in VMM 2008 or 512 MB in VMM 2008 R2).
– Sufficient Storage to allocate the new VHD to be created from the source.

Virtualization Software:
Virtual Server R2 SP1
Windows Server 2008 with Hyper-V
Windows Server 2008 R2 with Hyper-V 

Security Settings:
– Must have an account member of the local Administrators in the Source computer.
– Verify that no firewalls or IPSec policies prevent communication between the source computer and SCVMM on the management channel (on WMI or the SMB protocol) or between the source computer and the destination host on the data channel (TCP port 443 by default – SCVMM 2008 R2 will begin with port 40443).
– The VMM agent Windows Installer creates a firewall exception for remote administration (RemoteAdmin service) and Secure Sockets Layer (SSL) port. These exceptions are removed when the VMM agent is removed at the end of the P2V process. The HTTPS port default is TCP 443 and 40443 for SCVMM 2008 R2.

An example of P2V conversion.

 

During a P2V conversion, the participating computers communicate over the following protocols:
– Destination host and the source computer: HTTPs (443 or 40443 for VMM 2008 R2). The 40443 is initiated by default in SCVMM 2008 R2, but this is not the case for SCVMM 2008. To avoid port conflicts with P2V agent you can STOP the service that is running in port 443 in the Source machine or change the default port used by Virtual Machine Manager for P2V (create the registry DWORD key: “HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\P2VBITSTcpPort” and enter the number of the port that you want to use on the VMM server. The port number must be smaller than 32768. Restart the VMM service.)
SCVMM server and the P2V agent on the source computer: WMI
SCVMM server and the destination host: WS-Management (Windows Remote Management –  WinRM)
– Data is transferred directly between the source computer and the destination host over HTTPs. Machine configuration and P2V parameters are exchanged between the source computer and VMM over WMI.

In P2V Online conversions the source physical machine doesn’t need to be rebooted, but you should be careful with the apps that you run on that computer and make sure that they’re VSS aware, if those applications are not VSS aware you should disable or stop them before attempt to do an Online P2V.

Offline P2V is more clean regarding to data consistency, this is achieved  because the source computer data is copied while it is not in use.
Remember:  offline P2V is the only option to convert Windows 2000 Servers and computers with Non-NTFS volumes, this process is also highly recommend for domain controllers so you don’t run into USN Rollback issues.
Unlike online conversions, the user must provide any missing drivers if Windows PE does not support the source computer

In part 2 we’ll cover the P2V migration steps.

Additional related Links:
P2V: Converting Physical Computers to Virtual Machines in VMM
Frequently Asked Questions: P2V and V2V Conversions in VMM
Virtual Server 2005 Migration Toolkit

Written by IT Core

December 20, 2009 at 6:23 PM