Problem You’ve completed a new greenfield deployment or successfully migrated from Lync Server 2010 to Lync Server 2013 with Windows Server 2012 servers as the base operating system but noticed that your Lync Edge servers
Problem You attempt to remove a virtual machine from the VMware View administration console: … but you notice that VMware View is unable to delete the virtual desktop and the follow error is logged in
Update: Please see my latest update blog post: Updated: Starting Google Earth on Citrix XenDesktop 5.6 virtual desktop prompts the message: ‘DirectX’ mode not supported https://blog.terenceluk.com/updated-starting-google-earth-on-citrix/ Problem You’ve followed the instructions provided by the following
As demonstrated in one of my previous posts for VMware Horizon View 5.2: Using PowerCLI to create new role and assign service account used by VMware Horizon View 5.2 (View Manager & View Composer) permissions
As demonstrated in one of my previous posts: Using PowerCLI to create new role and assign service account used by VMware View Manager 5.1 permissions for vCenter Server https://blog.terenceluk.com/using-powercli-to-create-new-role-and/ … you can use PowerCLI to
I was recently asked by a colleague whether I had prewritten scripts to reverse the configuration changes that the VMware View Optimization Guide for Windows 7 performed on a master image and while I didn’t
I’ve been meaning to blog about an issue I noticed in environments with disparate namespaces (internal domain name is different than external) where no matter how I configured the DNS for the internal or public
As some administrators may have noticed, VMware has made quite a few changes to vSphere 5.1 and I was a bit thrown off by the change to the layout of permissions while I configured the
Problem Ran into an issue the other day where I would have no problems logging into a Citrix XenApp 6.5 environment published with a Citrix Access Gateway VPX 50 (NS10.0: Build 73.5.nc) but noticed that
As some administrators may have noticed, VMware has made quite a few changes to vSphere 5.1 and I was thrown off by the change to the layout of permissions while I configured the role for
