Virtual Hardware (VMX) Template configuration
||Number of virtual sockets: 1
Number of cores per socket: 2
||Number of video displays: 1
Total video memory: 5 MB (1280×1024)
|SCSI Controller 0
Hard disk 1
|LSI Logic SAS, bus sharing: none
40 GB, Thick Provision Eager Zeroed (<—best performance)
|CD/DVD Drive 1
|Floppy Drive 1
|Network Adapter 1
||VMXNET3, network: VM Network with DHCP (for joining domain)
||OS: Microsoft Windows Server 2012 R2 (64-bit)
||Advanced: Check and upgrade Tools during power cycling
|Virtual Machine Version
||8 (not 9 because you only can edit version 9 via vSphere web-client)
|Advanced > General
Virtual Machine BIOS configuration
|Boot-time Diagnostics Screen
Categories: Hyper-V, Microsoft, VMware Advanced Configuration, BIOS, Favorite, How-To, Hyper-V, Microsoft, Performance, Template, VMware, vSphere, Windows 2012R2
Last week I added a new vSphere host in my homelab, after I configured and started my backup job in the Backup & Replication 7.0 patch 4 environment I received this error messages:
Processing ‘DC01′ Error: Client error: NFC storage connection is unavailable. Storage: [stg:datastore-12,nfchost:host-10,conn:vce01.vmpros.local]. Storage display name: [ESX01_VMFS02].
Failed to create NFC download stream. NFC path: [nfc://conn:vce01.vmpros.local,nfchost:host-10,stg:datastore-12@DC01/DC01.vmx].
When you look at the Backup Job log file you can see the details, logfile location: C:\ProgramData\Veeam\Backup\VMpros_-_Backup_01
In my case Veeam Backup could resolve my VMware vCenter 5.5 server but when he try to contact the vSphere host with some local datastores the backup failed. I tried to ping the hosts and couldn’t resolve the hostname of my vSphere host.
Make sure you have:
- Added the vSphere host in DNS, create a A record in your DNS server
Optionally: Add the vSphere hostsname(s) and IP-address(es) in the hostfile at your Veeam Backup server
More information: Veeam
Today I was installing VMware vCenter Operations 126.96.36.199 in my vSphere 5.5 update 1 homelab, during deployment I received this warning message:
The OVF package is invalid and cannot be deployed.
This operation is not supported on the object.
vRealize Operations Manager vApp 5.x can only deploy to a host inside a cluster if DRS is enabled.
My homelab is running a VMware vCenter 60 day trial version, after I enabled DRS in my cluster with 2 hosts I was able to deploy vCO 5.8
More information: VMware
VMware vCloud Automation Center (vCAC) product updates address a critical vulnerability in the vCAC VMware Remote Console (VMRC) function which could lead to a remote privilege escalation.
vCloud Automation Center 6.x without patch
Problem Description: VMware vCloud Automation Center remote privilege escalation
VMware vCloud Automation Center has a remote privilege escalation vulnerability. This issue may allow an authenticated vCAC user to obtain administrative access to vCenter Server.
This issue is present in environments that use the "Connect (by) Using VMRC" function in vCAC to connect directly to vCenter Server. Environments that exclusively use vCloud Director (vCD) as a proxy to connect to vCenter Server are not affected.
At this time the issue is remediated by removing the "Connect (by) Using VMRC" functionality for directly connecting to vCenter Server. Deploying the provided patch will remove this functionality.
VMware is working on a secure solution that will restore this functionality. Customers may continue to use the "Connect (by) Using RDP" or "Connect (by) Using SSH" options for remote desktop management as they are not affected by this issue.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the identifier CVE-2014-8373 to this issue.
Column 4 of the following table lists the action required to remediate the vulnerability in each release, if a solution is available.
Please review the patch/release notes for your product and version and verify the checksum of your downloaded file.
vCloud Automation Center 6.x
Downloads and Documentation:
More information: VMware
After upgrading a Terminal Server or Terminal Server-based Citrix XenApp virtual machine to VMware Tools 5.x, you experience these symptoms:
In the Windows Application Event log, you see this error reported multiple times in quick succession (log spew):
[ warning] [vmusr:vmusr] Error in the RPC receive loop: RpcIn: Unable to send.
This issue occurs when the VMware Tools daemon (vmtoolsd) handles more than two Terminal Sessions. When a user connects to a Windows virtual machine, each terminal session should have one vmtoolsd running; however, vmtoolsd is limited to only two sessions running simultaneously. Thus the Windows Application Event log fills up with warning messages similar to this until the total connection count is >2 per session:
[vmusr:vmusr] Error in the RPC receive loop: RpcIn: Unable to send
This is correct:
To work around this issue, disable VMware Tools logging to the Event Log and general virtual machine logging to the vmware.log file for the virtual machine.
To disable VMware Tools application event logging:
- Open the tools.conf file using a text editor. The tools.conf file is located at:
- Windows XP and Windows Server 2000/2003:
C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\
- Windows Vista, Windows 7, and Windows Server 2008:
- Add this section to the tools.conf file:[logging]
vmusr.level = error
vmsvc.level = error
- Save and close the file.
- Restart the VMTools service (Administrative Tools > Services).
Note: If there are users logged in to more than one session, restarting the VMTools service may not be sufficient. You may have to kill the vmtoolsd.exe process for all instances.
More information: VMware
- Some Citrix NetScaler virtual machine appliance running the guest Operating System with e1000 vNIC driver loses network connectivity
- And also cannot access the console after applying the patches released with ESXi 5.5 Update 2 build 2143827
This issue occurs when the NetScaler virtual machine driver resets TDT to 0 after 511 while the TX ring size is shown as 1024.
This is a known issue affecting Citrix NetScaler virtual machine appliance running on ESXi 5.5 Update 2 build 2143827.
Currently, there is no resolution.
To work around this issue, add the line hw.em.txd=512 in loader.conf file.
To add the line hw.em.txd=512 in loader.conf file:
- Log in to the Citrix NetScaler virtual machine appliance as root
- Locate the loader.conf file on the Netscaler virtual machine appliance by running this command:
find / -name loader.conf
Note: There are two loader.conf files. The two files are ./flash/boot/defaults/loader.conf and ./flash/boot/loader.conf. Modify the first one and ensure to take a backup of the file prior to making the changes.
- Add this line in the loader.conf file
- Save the changes
- Restart the NetScaler virtual machine appliance
VMware & Citrix
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.
- 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.
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.“
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
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.
More info: Citrix
KB ID: 1891
Products: Veeam Backup & Replication
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.