vROPS 7.0 launched with a feature called Business Intent which controls workload placement based on vSphere tags Announcement. This feature tackles several use cases one being controlling the host placement of workloads which have physical licencing requirements. Business Intent settings are configured at the data centre (or custom datacenter) level within vROPS 7.0 and can be configured at the per cluster or per host level. For the scope of this post, I am going to cover a customer use case to combine clusters, increaseing availability for some workloads while maintaining licencing compliance for others.

I recently updated my Ubuntu install from 17.04 to 17.10, which meant the kernel was updated to 4.13. As a result, I was no longer able to run VMs with VMware Workstation. I found some posts regarding the error and that it was due to a change in the way the Linux kernel handles paging. To resolve the issue I needed to replace the vmmon modules. I didn’;t take down the entire error message, but this post references the same error.

VMwares Hands on Labs (HOL) are a great way to explore products and features, without needing to have your own lab. When you launch a lab, the environment is spun up, when you exit it is torn down. An entire lab is built in a built in a matter of minutes, sometimes less. Each lab has an intended objective, with a manual on the right to guide you through. Going through the a lab and following the designated steps is great, but that doesn’;t mean you have to stay on track.

SSO is an integral part of providing access rights to your Vcentre server. You can assign permissions to people based on their user account, group memberships and link it with various authentication methods. After installing Vcentre for the first time log onto the Web Client with the username administrator@vsphere.local and the password you used during the install. The address for the Web Client will be https://Server Name:9443/web-client Though if you selected a different port to 9443 during the installation then use that.

While testing out a Server 2012 install on ESXi 5.5 I noticed that when copying files between it and any other server I would get a PSOD. The main section of the PSOD that got my attention was E1000PollRxRring@vmkernel After a bit of searching around I found that there seems to be a common issue with Server 2012 and Server 2012 R2 using the E1000 NIC. Standard solution seems to be remove your current E1000 NIC from the guest machine and add a NIC running as VMXNET3.