Problem You have to deploy VMware View Client on a number of Windows XP workstations and installing the client manually is not an option because there are too many workstations in the environment. Then environment
One of the common issues that I find fellow professionals bring up when we’re talking about VMware View desktop customizations and deployments is that if the environment is trying to extend the life of their
I’m not sure why I never wrote a blog post about the items I typically go through when I have a VMware View virtual desktop deployment but as some of you may know, I’m currently
I haven’t really gotten in a chance in the past to document the process of packaging and streaming an application with VMware’s ThinApp and since I’m currently deploying a new VMware View environment and had
The client I’m currently working with is trying to extend the life of their desktops that was around since I was still attending university and slowly move to thin-clients as they require replacement and one
I’m not exactly sure why VMware specifically states that the certificate you use for View Manager and Connection server has to be PKCS#7 but I went ahead and tried to use a PKCS#12 certificate today
Note that there are many reasons why Microsoft Office 2010 on your VMware View desktops may not activate so the following is only 1 of the many out there. Problem You have just completed the
Problem You’ve just successfully configured a new Vmware View 5.0 Linked Clone pool and vCenter has completed the cloning of the replica and linked-clones but when you log onto the View Connection server administrative console
This won’t be a detailed about how to fix these errors but more of a post with specific error messages I can reference to in the future to know that I’m running into network connectivity
To follow up on one of my previous posts: Installing VMware View 4.6 – Composer Server 2.6 and Connection & Transfer Server 4.5 Installing VMware View 4.6 – Composer Server 2.6 and Connection & Transfer
