Problem As a follow up to one of my previous posts: Upgrading from VMware Horizon View 6.0.1 to 6.2.1 causes connections to throw the error: “Unable to connect to desktop: There is no available gateway
Problem You attempt to upgrade your existing VMware Horizon View 6.0.1 infrastructure to 6.2.1 but noticed that after upgrading your View Connection and Security servers you receive the following error message when connecting to a
Problem You’ve created a new pool of virtual desktops in your VMware Horizon View environment but noticed that while the virtual machines get created, they never get past the customizing status: After waiting 10 minutes
I recently ran into an interesting issue where I went through a series of troubleshooting steps that eventually led me to reinstalling the VMware Horizon View Agent on a master image but quickly realized I
Problem While reviewing the Hard disk configuration of VMware Horizon View ioVDI enabled virtual desktops, you notice that there are several disposable disks assigned to the VDI: Note the Disk File path: 18/disp0/18disp0.vmdk Note the
Problem You’ve updated your linked-clone pool’s master image and attempt to reassign the Default Image Snapshot but while you are able to assign the new snapshot, you receive the following error when you try to
Before I begin, it’s important to note that I am not an expert with the SanDisk Fusion-io ioVDI product and the only exposure I’ve had was with a client who had another consulting company implement
Problem You have installed Office 2010 directly onto your base virtual machine master image then continue to create two separate AppStacks in VMware App Volumes. With the AppStacks created, you proceed with assigning Microsoft Project
Problem You’ve recently renewed the certificate issued by a public CA for your VMware Horizon View Security server that secures external incoming traffic. Windows desktops continue to connect without any issues but users with iPads
I’ve noticed that one of the most common questions I’ve been asked over the past year and a half is whether I had written a blog post to demonstrate how to configure Microsoft Lync 2013
