Plain Virtualization

Recently done a few Horizon Proof of Concept and encounter a connection issue with App Volumes. Here is how I resolve the error message from App Volume agent "Virtualization is disabled". Do note that this is based on version 2.12. This error message encounter when your App Volumes agent is not able to communicate with App Volumes Manager. During installation for the agent and manager, you can choose whether secure or not connection. You MUST choose the same type of connection. However if you have done this incorrectly, this is the problem that is often the problem. Here will show you how you can first confirm the type of the connection are the same between the manager and agent, and change it if it is not. Agent To check if the SSL is enabled on the agent, head over to the VM that has agent installed, follow the instruction stated here . Manager For App Volumes manager, this is not as straightforward. Refer to this document . If you want ...

In my previous posts on Horizon Mirage, Installation on Mirage 3.6 What's New in Horizon Mirage 4.2 What's New in Horizon Mirage 4.3 You would have find some of the things like e.g. leaving blank for SQL server entry if you are using the default instance name. Also Best Practice to upgrade Horizon Mirage can be found in a KB here . In Horizon Mirage 4.4, you will enter the SQL server name without the SQL instance name if you have use the default instance name e.g. MSSQLSERVER (in this case it's call unnamed instance not sure why).  This is required as shown during installation of Horizon Mirage Management Server and Horizon Mirage Server as shown below:   In Horizon Mirage there are a few changes.   The main new added is the Edge server.  Now instead of placing your Mirage Server in the DMZ and be compromise with security attacks or require a need of using VPN, now you have a Edge server to handle that piece just like what in Horizon View Security s...