In vCenter Server 5.x the embedded SQL Express database supports a maximum of 5 hosts and 50 Virtual Machines. With vCenter Server 6 the embedded database is changes from SQL Express to a vPostgress database. The vPostgres database supports a maximum of 20 hosts and 200 VMs. In comparison the vPostgres database on the vCenter Server Appliance (VCSA) 6 supports 1000 hosts and 10000. When upgrading or fresh installing vCenter Server 6 make sure to note the following items:
- When upgrading to vCenter Server 6.0, the Microsoft SQL Express database is migrated to a vPostgres database.
- Oracle, SQL Standard and Enterprise database editions will not be migrated to vPostgres.
- It is possible to upgrade without migrating the SQL database to vPostgres. Make sure you have a supported SQL database before upgrading. More information can be found here, link.
- When uninstalling vCenter Server 6 the embedded VMware vPostgres database will be removed with all the data! More information can be found here, link.
- How to backup and restore the vPostgres database there is a Python script available. This script can be found here, link.
- VMware vSphere Update Manager can’t use the embedded vPostgres database! For VMware vSphere Update Manager you need a Microsoft SQL (Express) database. When combining the vCenter Server, PSC and VUM on one server, two different databases engines are used. This looks like this:
PowerCLI 6.0 R1 is released with some cool new features. One thing I missed in this announcement is improvements in the PowerCLI support for VMware Horizon View. The latest release of VMware Horizon View 6.1 still has NO PowerCLI improvements! This is a huge bummer because PowerCLI is very limited in VMware Horizon View.
Each new release tends to have several features or enhancements that have been asked for by YOU, our customers. These new features come to us by way of interaction at events like VMworld, Partner Exchange, VMUG Conferences, Twitter, Email, and customer visits. What better way to show our customers that we listen then by adding in features they ask for? This release does not disappoint! Thank you to all who provide feedback and help us continue to improve this great tool.
- Ability to run from remote systems
- Creating and exporting desktop pools with all the settings available as in the GUI (Horizon View Administrator)
- Available as module
- Getting the Health overview as in the VMware Horizon View Administrator
- Filter on the desktop status such as problem desktops, agent unreachable, deleting, missing, disconnected, available etc.
- Filter pools and display the amount of desktops that are used, available desktops, headroom and total desktops.
- Check the ADAM replication between the Connection Servers
- Search and filter the Event database on error and warnings
- Add or remove a VM to a manual pool
- Send messages to desktops
Here are some tips for installing System Center 2012 R2 Virtual Machine Manager Update Rollup (UR5):
- UR5 is available from Microsoft Update or by manual download. If you are not installing UR5 through Microsoft Update (e.g. you’re downloading the update and then installing it), you must install using elevated privileges. If you do not do this the update may fail silently.
- During the UR5 installion the System Center Virtual Machine Manager & Agent will be stopped
- After the SCVMM UR5 server component, reboot the VMM server before installing the UR5 console
- Before Update Rollup 5, you had to manually update the System Center Virtual Machine Manager DHCP Server (x64) component. As of Update Rollup 5, this is no longer required. When updating the agent on the server the DHCP server components is updated too.
- The new SCVMM UR5 agent build version is: 3.2.7895.0
- The Microsoft System Center Virtual Machine Manager DHCP Server (x64) build version is still 3.2.7768.0
- Make sure to update the agent on all the infrastructure servers such as the Update Server and library server. In VMM click on Fabric- Server for a complete overview
- Refresh the cluster after updating the agents
- When starting the VMM console the following error appears:
- This error is permission related. To solve this error add the “Authenticated Users” group to the AddInPipeline directory and assign read and execute rights. The installation of VMM can be found under: <Driveletter>:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin\AddInPipeline.
- Update 24-02-2015: Microsoft released a hotfix for UR5 that addresses replica and smb shares issues. The link to the KB can be found here, link.
For all the details on SCVMM 2012 R2 UR5, see the following:
- KB3023195 – Description of the security update for Update Rollup 5 for System Center 2012 R2 Virtual Machine Manager, link
Sometimes you are unable to remove linked clones or stale desktop entries from the VMware Horizon View Administrator. In this example we have a missing VM in the VMware Horizon View Administrator.
When trying to remove the VM from the VMware Horizon View Administrator the following error is generated:
Failed to remove VM…… from the View Composer Inventory
To remove the orphaned missing VM, you need to manually remove the orphaned records from the ADAM and composer database, AD and vCenter Server. The process is described in the following KB:
- Manually deleting linked clones or stale virtual desktop entires KB, link
Executing the procedure described in the KB can be a risky. VMware has released a new tool (fling) called “ViewDBChk”. The ViewDBChk tool allows administrators to scan and fix provisioning errors that can not be addressed using the VMware Horizon View Administrator. This tool is supported on VMware Horizon View 5.3 and 6.0. Fling tools are not supported by VMware!
Fling ViewDbChk can be found here, link
What’s new in the vCenter Server Appliance (vCSA) 6.0:
- ISO with an easy guided Installer
- Different deployment options possible during the guided installer such as:
- Install vCenter Server
- Install Platform Services Controller
- Install vCenter Server with an Embedded Platform Controller (default)
- Scripted install. Values can be specified in a template file
- Embedded vPostgres database. As external database Oracle is supported.
- IPv6 Support
- Enhanced Linked mode support
- VMware Data Protection (VDP) support for backup and recovery
- Based on a hardened Suse Linux Enterprise 11 SP3 (64-bit)
- The minimum (Up to 20 hosts and 400 VMs) appliance requirements for the VCSA are:
- 2 vCPU
- 8 GB memory
- ~ 100 GB diskspace
- Is has the same feature parity as vCenter Windows:
What are we missing:
- Still no Microsoft SQL database support.
- Possibility to separate roles of the vCenter
- VMware Update Manager is not included in the appliance. Still need an additional Windows Server for VMware Update Manager (VUM)
- Clustering of the vCenter Server Appliance