VMware Horizon records events like administrator actions, end-user actions, system failures and errors etc. You can either leverage Microsoft SQL or Oracle Database for recording events. Before proceeding to configure VMware Horizon to log events database is required to be created and configured.
In this post, I will be covering the steps to configure Event Database in VMware Horizon 7.
Login to VMware Horizon Admin Console
Click on No Events database configured.
Click on Edit
Provide Database server details
This concludes the configuration of SQL server database as a VMware Horizon Event database. Hope this would be informative for you. Thanks for Reading!!!. Be social and share if you find worth sharing it.
VMware Horizon records events like administrator actions, end-user actions, system failures and errors etc. You can either leverage Microsoft SQL or Oracle Database for recording events. Before proceeding to configure VMware Horizon to log events, In this post, we will be covering the steps to create a Microsoft SQL database. You do not need to create an ODBC data source for this database.
Install SQL Server & SQL Server Management Studio in Mixed Mode authentication
Login to SQL Server Management Studio. Click on New Database
Give the database name and click on OK.
Create a new login account and assign DB Owner permission to the new database
Select “SQL Server Authentication” & Uncheck “User must change password at next login” & Click OK.
Click on User Mapping. Select new database & check db_owner.
Start “SQL Server configuration manager”. Go to “SQL Server Network configuration” then protocols for SQLEXPRESS. Enable TCP/IP if disabled. Click on Properties.
Restart the SQL Services
This concludes the steps required to create and configure SQL Server database before configuring it as VMware Horizon Event Database. Hope this will be informative for you. Thanks for Reading!!!. Be social and share if you find worth reading it.
Post installation of VMware App Volumes Manager, install the App Volumes agent on the provisioning computer and target desktops. You don’t need to install on the server where you have App Volumes Manager installed. You need to deploy App Volumes Agents on desktops that will be accessing AppStacks and writable volumes, as well as on provisioning machines, and RDSH hosts. Provisioning machines will be the machines used to capture applications for AppStacks.
The account used to install Agent should have local administrator privileges on the target computer.
App Volumes Manager IP Address.
Although it is not strictly required, as a best practice it is recommends to use the same Windows OS version for the provisioning machine that an AppStack will be attached to. For example, use a Windows 10 provisioning machine for AppStacks that will be attached to Windows 10 desktops, and a Windows Server 2012 R2 provisioning machine for AppStacks that will be attached to a Windows Server 2012 R2 RDSH host.
On provisioning host, you should disable any agents that will perform any type of updates like Windows Update and virus definitions.
On provisioning host, disable agents like antivirus agents, Horizon Agents, etc
This video demonstrates you the installation of VMware App Volumes Agent. You can choose to install App Volume agent to communicate on port 80 or 443. By default, Agent will communicate with App Volume manager on port 443.
This concludes the installation of VMware App Volumes agent on provisioning host. You can follow the same process to install App Volumes agent on the desktop where app stack to be attached. Next step is to create an app stack which will be further used for delivering the application in real time on to virtual desktops. Hope this will be informative for you. Thanks for Reading!!!. Be social and share if you find worth sharing it.
In most recent release of VMware Horizon 7,4, VMware came up with lot of great new features like
Session Collaboration, where users on their virtual desktops can collaborate with peers for reviews, interactive design and training.
Instant Clone support for Linux
vGPU support for RDSH Instant-Clone Farms
Enhancement of Virtualisation Pack for Skype for Business.
Enhancements in user experience for RDSH published applications in Horizon 7
Session collaboration with peers is especially useful in areas of engineering, design, healthcare, and education. Session collaboration gets more important especially in high-end graphics scenarios, where user working on a design can invite its peers to review & modify the design by passing control over to the other users.
A user can send session collaboration invitations to up to five domain users either by:
E-Mail (E-Mail application must be installed & configured)
IM Invitation (Skype for business must be installed & configured)
Sharing link to the user
Session Collaboration Feature Prerequisite
Horizon Client 4.7 or later for Windows, Mac, or Linux installed on the client system or must use HTML Access 4.7 or later.
Horizon Agent 7.4 or later must be installed in the virtual desktop or RDS host.
Session collaboration must be enabled at the desktop pool or farm level.
Horizon 7.4 Connection Server
Horizon 7 Enterprise Edition license.
VMware Blast Extreme as display protocol
Session Collaboration Feature limitation
Only primary monitor will be shown to session collaborators in case of multip monitors
PCoIP & RDP Session are not supported
H.264 hardware encoding is not supported.
Anonymous collaboration is not supported.
Session Collaboration feature cannot be used to share published application sessions.
Enabling Session Collaboration
To allow users to collaborate, Horizon administrator must have to enable Session collaboration on Desktop Pool, RDS Farm (to allow RDS users to collaborate). To allow users to collaborate with the users from other pods, you must have to enable the Session Collaboration feature for the global desktop entitlement that contains the desktop pool. You can also configure Session Collaboration on remote desktops using collaboration group policy settings in the VMware View Agent Configuration ADMX template file (vdm_agent.admx).
Configuring Session Collaboration using Group Policy
You can configure below group policy settings to enable session collaboration using Group Policies
Session Collaboration Policy Settings
Allow inviting collaborators by e-mail
Allow inviting collaborators by IM
Separator used for multiple e-mail addresses in mailto: links
Server URLs to include in invitation message
Turn off collaboration
Maximum number of invited collaborators.
Configuring Session Collaboration on Desktop Pool
To allow Desktop Pool users to collaborate with other users you have to enable session collaboration on Desktop Pool
Configuring Session Collaboration on RDS Farm
To allow RDS Pool users to collaborate with other users you have to enable session collaboration on RDS Farm.
Session collaboration provides users a great flexibility to collaborate with team members. Session collaboration gets more important especially in high-end graphics scenarios, where user working on a design can invite its peers to review & modify. Hope this will be informative for you. Thanks for Reading!! Be social and share if you find worth sharing it.