VMpros.nll
new1234.jpg

Hyper-V: Microsoft Virtual Machine Converter 3.0 released

October 14th, 2014 No comments

Microsoft® Virtual Machine Converter (MVMC) is a Microsoft-supported, stand-alone solution for the information technology (IT) pro or solution provider who wants to convert virtual machines and disks from VMware hosts to Hyper-V® hosts and Windows Azure™ or alternatively convert a physical computer running Windows Server 2008 or above server operating systems or Windows Vista or above client operating systems to a virtual machine running on Hyper-V host

MVMC can be deployed with minimal dependencies. Because MVMC provides native support for Windows PowerShell®, it enables scripting and integration with data center automation workflows such as those authored and run within Microsoft System Center Orchestrator 2012 R2. It can also be invoked through the Windows PowerShell® command-line interface. The solution is simple to download, install, and use. In addition to the Windows PowerShell capability, MVMC provides a wizard-driven GUI to facilitate virtual machine conversion.

New Features in MVMC 3.0
The 3.0 release of MVMC adds the ability to convert a physical computer running Windows Server 2008 or above server operating systems or Windows Vista or above client operating systems to a virtual machine running on Hyper-V host.

Standard Features

  • Converts virtual disks that are attached to a VMware virtual machine to virtual hard disks (VHDs) that can be uploaded to Microsoft Azure.
  • Provides native Windows PowerShell capability that enables scripting and integration into IT automation workflows.
    Note The command-line interface (CLI) in MVMC 1.0 has been replaced by Windows PowerShell in MVMC 2.0.
  • Supports conversion and provisioning of Linux-based guest operating systems from VMware hosts to Hyper-V hosts.
  • Supports conversion of offline virtual machines.
  • Supports the new virtual hard disk format (VHDX) when converting and provisioning in Hyper-V in Windows Server® 2012 R2 and Windows Server 2012.
  • Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.1, and VMware vSphere 4.1 hosts Hyper-V virtual machines.
  • Supports Windows Server® 2012 R2, Windows Server® 2012, and Windows® 8 as guest operating systems that you can select for conversion.
  • Converts and deploys virtual machines from VMware hosts to Hyper-V hosts on any of the following operating systems:
  • Windows Server® 2012 R2
  • Windows Server® 2012
  • Windows Server 2008 R2 SP1
  • Converts VMware virtual machines, virtual disks, and configurations for memory, virtual processor, and other virtual computing resources from the source to Hyper-V.
  • Adds virtual network interface cards (NICs) to the converted virtual machine on Hyper-V.
  • Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.0, and VMware vSphere 4.1 hosts to Hyper-V.
  • Has a wizard-driven GUI, which simplifies performing virtual machine conversions.
  • Uninstalls VMware Tools before online conversion (online only) to provide a clean way to migrate VMware-based virtual machines to Hyper-V.
    Important MVMC takes a snapshot of the virtual machine that you are converting before you uninstall VMware Tools, and then shuts down the source machine to preserve state during conversion. The virtual machine is restored to its previous state after the source disks that are attached to the virtual machine are successfully copied to the machine where the conversion process is run. At that point, the source machine in VMware can be turned on, if required.
    Important MVMC does not uninstall VMware Tools in an offline conversion. Instead, it disables VMware services, drivers, and programs only for Windows Server guest operating systems. For file conversions with Linux guest operating systems, VMware Tools are not disabled or uninstalled. We highly recommend that you manually uninstall VMware Tools when you convert an offline virtual machine.
  • Supports Windows Server and Linux guest operating system conversion. For more details, see the section “Supported Configurations for Virtual Machine Conversion” in this guide.
  • Includes Windows PowerShell capability for offline conversions of VMware-based virtual hard disks (VMDK) to a Hyper-V–based virtual hard disk file format (.vhd file).
    Note The offline disk conversion does not include driver fixes.

Source: Microsoft

Citrix: Using the default VMware vCenter server certificate in XenDesktop – Hosting

October 10th, 2014 No comments

When integrating XenDesktop with vSphere or vCenter respectively, you might encounter the following error message:

„Cannot connect to the vCenter server due to a certificate error. Make sure that the appropriate certificates are installed on the vCenter server, and install the appropriate certificates on the same machine that contains all instances of the host service.“

image

 

Solution:

1. Connect to your vCenter server and browse to „C:\ProgramData\VMware\VMware VirtualCenter\SSL“

2. Copy the cacert.pem file to your XenDesktop Broker (to the C:\Temp directory for example)

3. Open a Microsoft Management Console (by running the mmc.exe command) as an Administrator

4. Add the Certificates Snap-In and select to manage certificates for the local computer account.

5. Browse to „Trusted Root Certification Authorities“ and select Import

image

6. Import the cacert.pem file. (You need to select „All Files“ from the dropdown menu in the lower right hand corner, to be able to see it)

7. Now you should be able to see the vCenter certificate in the list of trusted certificates and XenDesktop should connect to vCenter without any error message.

 

Result:

image  image 

More info: Citrix

Veeam: Installing patch 4 Veeam Backup & Replication 7.0

August 29th, 2014 No comments

 

KB ID: 1891
Products: Veeam Backup & Replication
Version: 7.0.0.871
Published: 2014-06-05
Created: 2014-05-30
Last Modified: 2014-06-05

New Features and Enhancements

VMware Virtual SAN (VSAN)

  • In addition to adding basic support (as provided by other vendors), the intelligent load-balancing engine was enhanced to account for VSAN specifics. As the result, for each VM the job will pick backup proxy running on VSAN cluster node with most of the virtual disks’ data available locally. This significantly reduces backup traffic on VSAN cluster network, resulting in minimum possible impact on production environment from backup activities.

Microsoft SQL Server 2014

  • Added support for Microsoft SQL Server 2014 both as the protected guest workload (including application-aware processing functionality), and the back-end database for backup and Enterprise Manager servers.

License key auto update

  • Added automated license key update option to the License Information dialog. With auto-update enabled, the product will check Veeam licensing server periodically for an updated license key, and download and install the key automatically as soon as it becomes available. This feature is particularly useful to the Service Providers and subscription-based customers, and it removes the need to download and install the license key manually each time when the license extension is purchased.

Read more…

VMware: Nesting Hyper-V 2012 R2 on vSphere ESXi 5.5

August 28th, 2014 No comments

In my test environment I configured tree Hyper-V 2012R2 servers nested on vSphere 5.5,  the configuration was very easy, here some details:

1. Deploy a Windows 2012R2 server, use GuestOS Windows 2012 (64-bit)

2. Upgrade hardware level to version 10

3. Remove the virtual machine from the vCenter inventory

4. Download and edit the .vmx file, add the following lines:

vhv.enable = “TRUE”
hypervisor.cpuid.v0 = “FALSE”
mce.enable = “TRUE”

 image

5. Upload and re-add the .vmx file to the vCenter inventory

6. Edit the virtual machine hardware > CPU > Hardware virtualization> select: Expose hardware assisted virtualization to the guest OS

*Note: you need to upgrade to HW level 10, otherwise the hardware virtualization tab is grayed out.

 image

7. Power on the virtual machine

8. Now you are able to select the Hyper-V role, finish the setup

image

 

Ejoy!

VMware: Unable to remove an inaccessible NFS datastore

August 27th, 2014 No comments

The backend storage volume corresponding to the datastore has been removed and the datastore appears as Inactive, when I want to remove (via vSphere Client connected to vCenter server) the NFS datastore I receive this error message:

Unmounting the datastore in vCenter Server fails with the error:
‘Call “HostDatastoreSystem.RemoveDatastore” form object “datastoreSystem-28″ on vCenter Server “xxxx” failed. CannotRemove datastore ‘datastore_name’ because Storage I/O control is enabled on it. Correct it and re-try the operation

image

 

Solution:

To resolve this issue, log in directly to each ESXi host that has access to the inactive datastore and manually remove it.

- Connect to the vSphere ESXi host using SSH

- Run this command to list the mounted datastores:

esxcli storage nfs list

image

- Run this command to unmount the NFS datastore:

esxcli storage nfs remove –v datastorename

image

The inactive NFS datastore has been removed

Note: if your datastore display name have some spaces, please use quotes

 

More information: VMware

VMware: Update or recover “root” password using Host Profiles

August 26th, 2014 No comments

Start Profile Wizard after you have entered Maintenance Mode

image

- Select: Create Profile from existing host

 

image

- Select host (in maintenance mode)

image

- Profile details: Reset root password

image

- Finish the host profile creation
On the left pane select your new host profile and right-click and select edit profile:

image

- Select: Root password reset > Security configuration > SSH authorized key for root user

Note: check or deselect specific host profile configurations to enable or disable them. A disabled configuration will not be applied when applying the host profile and hosts will not be checked for compliance with that configuration

Now click OK and we’ll start attaching the host of which we want to reset the password. Click ‘Attach Host/Cluster’ and select the right host, click Attach and then OK.

Voila, the root account of the host has been reconfigured and you should be able to log in again. Now the only thing left is to detach the host from the profile.

VMware: Error 2901. Could not connect to vCenter Single Sign On during install

August 26th, 2014 No comments

Today I installed a new vCenter 5.5 server in a environment without a domain and DNS server. During the deployment of vCenter Single Sign On I received this error message:

Error 29101 Could not connect to vCenter Single Sign On. Make sure that the Lookup Service URL points correctly to the vCenter Single Sign On instance you installed. If vCenter Sign On is installed with an IP address, make sure the IP address is specified in the URL.

clip_image001

 

Solution:

image

Select: “Use FQDN instead of IP address to configure vCenter Single Sign-On”

VMware: Cannot remove a License Key from VMware vCenter Server

August 23rd, 2014 No comments

Last week I upgraded a vCenter Server from version 5.1 to 5.5, I also added a 4th hosts to the cluster, so I need to upgrade the host license keys. But after upgrade I couldn’t remove the license files in vCenter Licensing section:

image

 

Solution:

To connect to the ADAM database:

  1. Log in to the vCenter Server.
  2. To open ADSI Edit, click Start > Run, type adsiedit.msc, and press Enter.
  3. Right-click ADSI Edit and click Connect to.
  4. In the Connection point section, click Select or type a Distinguished Name or Naming Context.
  5. Enter dc=virtualcenter, dc=vmware, dc=int
  6. In the Computer section, click Select or type a domain or server: (Server | Domain [:port]).
  7. Enter localhost
  8. Click OK.
  9. Drill down to DC=virtualcenter,DC=vmware,DC=int, OU=Licensing, OU=LicenseEntities.You see the CN="license key" containers.
  10. Right-click the container that shows the the serial number of the key that is negative within the vCenter Server Licensing page.
  11. Click Delete.

image

 

Result:

When you restart he vSphere client and navigate to the Licensing page the old license keys are removed and you can re-assign license keys to the hosts

image

 

More information: VMware

VMware: Service ´VMware Kdc Service’ (VMwareKdcService) failed to start

August 13th, 2014 No comments

Last week I upgraded VMware vCenter server from version 5.0 to 5.5 Update 1c, during installation of vCenter Single Sign-On 5.5 I received this warning message:

Service ‘VMware Kdc Service’ (VMwareKdcService) failed to start. Verify that you have sufficient privileges to start system services

 
image

 

The service account which I´m using for the upgrade is Domain Administrator, I tied to start the service manually but the service won’t start. The Windows Event log was clean, but in the vmkdcd.log file (located at: C:\ProgramData\VMware\CIS\logs\vmkdcd) I found this error logs:

20140812092452.000:t@0:TRACE: Vmkdcd: stop
20140812092458.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp called…
20140812092458.000:t@0:TRACE: dwError=87 errno=17
20140812092458.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp done.
20140812092458.000:t@0:TRACE: ERROR: vmkdc VmKdcInit failed (87)

20140812092458.000:t@0:TRACE: Vmkdcd: stop
20140812092503.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp called…
20140812092503.000:t@0:TRACE: dwError=87 errno=17
20140812092503.000:t@0:TRACE: VmKdcSrvOpenServicePortTcp done.
20140812092503.000:t@0:TRACE: ERROR: vmkdc VmKdcInit failed (87)
20140812092503.000:t@0:TRACE: Vmkdcd: stop

 

Solution:

To resolve this issue, ensure port 88 is available for use by the VMware Kdc Service:

  1. Use netstat from an elevated command prompt on the Windows host system to confirm port 88 is not in use. For more information on using the netstat command, see Determining if a port is in use (1003971).
  2. If another application is using port 88, reconfigure or disable the application to open port 88 for use with the VMware Kdc Service.

In my case VMware Converter Standalone Server was running and configured at port 88, I removed the installation and restarted the Single Sign-On setup.

 
More information: VMware