It’s been a while since I’ve worked with Windows XP virtual desktops but recently had to create a small linked-clone pool in VMware Horizon View 5.3 because a client had an application that was only compatible with IE 6. I proceeded to do as I
I ran into an interesting problem the other day while trying to assign an updated snapshot to a linked clone pool after upgrading an environment from VMware View 5.1.2 to VMware Horizon View 5.3 where I would receive the following error after assigning the new
While the problem outlined in this post isn’t specific or caused by VMware View but rather Microsoft Windows Server 2008 R2, it was an issue I encountered today that threw me off for a few minutes until I was able to determine the cause. Problem
Problem You’ve just added a new existing virtual machine into a VMware View pool and attempt to connect to it via the VMware View client but the following black screen: What you notice is that if you restore the size of the VMware View client
To follow up on one of my previous posts I wrote earlier in the year in February: Manually deleting orphaned and/or stale virtual desktops in VMware View Manager poolshttps://blog.terenceluk.com/2013/02/manually-deleting-orphaned-andor-stale.html … I finally got fed up when I had to clean up more than 40 orphaned
I ran into an issue last night after receiving a call from the same client who had an issue with their View 4.6 environment a few days ago that desktops are no longer being refreshed and all of desktops who have had users logged off
I was called by a client today asking me to to have a look at their VMware View 4.6 for their VDI infrastructure that was reporting vCenter was down. Fixing vCenter wasn’t too difficult as a few reboot and re-initialization of VMware Heartbeat got the
Problem You’ve received a complaint that when a user attempts to log onto their desktop, they immediate get kicked off. Logging onto the desktop with another account appears to be fine and the following errors are found in the event logs: Event ID 1532: Windows
One of the common issues I’ve come across over the past few months for clients was when I was asked to identify which replicas belonged to which virtual desktops in VMware View environments because a lot of my clients suspected that they had orphaned replicas
I’ve recently been asked quite a few times in over the last few months on how to properly request and issue certificates for VMware View servers ever since the later versions of 5.x began throwing warnings when servers are using their default self-signed certificates and
