This guide includes basic troubleshooting steps, issues observed in the process of composer installation or composer uninstall process, and finally operational issues. At the bottom of the KB there is a long list of related KBs that are also of interest if View composer problems are encountered.
We want to highlight some mitigation techniques and a handy KB article today for those of you managing Horizon View desktops. We’re talking about those occasions when no desktop can be created or recomposed in your vdi environment and no tasks submitted from Connection Brokers are acted upon by Virtual Center server.
This KB contains several main steps, the first one of which is collecting the bundled logs from all connection brokers in the vdi environment and recording the time this issue was first observed. Steps 2 to 6 are basic steps that can potentially help address the issue but if issues persist, then step 7 requests opening a support case and submitting the collected bundle logs in step 1 alongside the recorded time when the issue was first observed. You might also include any other useful information, such as whether any recent changes were made to the environment.
When opening your support case, please note this KB article number in the description the case. That helps us get right on point ASAP.
Step 8 is what should address this issue without any connection broker reboot as it causes the stoppage of all View services in all View connection brokers and then restarting them.
If step 8 does not resolve your issue, then the last step (9) involves reboot of all connection serves and this has always addressed the issue in our experience.
Starting November 1st 2015, public Certificate Authorities (CA) will no longer issue certificates with a subjectAltName extension or Subject commonName field containing a Reserved IP Address or Internal Name.
Effective October 1st 2016, CAs shall revoke all unexpired Certificates whose subjectAlternativeName extension or Subject commonName field contains a Reserved IP Address or Internal Name.
While this change is not VMware specific, VMware Administrators still need to be aware of the this change and understand if they are impacted. For this reason, we have created the following KB article, and urge you to familiarize yourself with it-
Today we bring you a video which demonstrates downgrading from VMware Workstation Pro 12.x to VMware Workstation 11.x including changing the virtual hardware of your virtual machines.
VMware Workstation Pro 12.x and VMware Workstation 11.x use different virtual machine hardware compatibility. When downgrading Workstation, you must change the virtual machine hardware compatibility version of your virtual machine to Workstation 11.0.