Release date: January 4th 2019
Welcome to my VMware Horizon series. In this session I will describe how I did the preparations for the Events Database used by VMware Horizon Connection Server. I have, after I created this session, moved my SQL database to a SQL AlwaysOn Cluster, covered here: VMware Horizon – Move Events DB to AlwaysOn Sql Cluster
For this database-setup I will be using my existing MS SQL Database server.
I login to the db-server, start “SQL Management Studio”. Right-click on SQL Server on the top, choose “Properties”
From the “Security”-page, choose “SQL Server and Windows Authentication Mode”, OK
Right-click Databases – New Database
Give the database a name, in this case this will be the Events-database for the Connection-server, so I’ll call it EventsDB
The new database is now present under Databases-folder.
Now we will setup sql-permissions for the EventsDB-database, right-click Logins – New Login…
I will create a sql-user: viewadmin, be sure to uncheck “Enforce password policy”
The Server Role “Public” will be sufficient for my viewadmin-user
I map my user to my newly created EventsDB-database and give the user db_owner membership for this database.
Be sure to grant permission to connect and login to database is selected.
Recommended reading:
Paolo Valsecchi has written an excellent write-up about this topic, posted here:
https://nolabnoparty.com/en/vmware-horizon-7-view-event-database-configuration/
VMware Horizon planning, deployment etc.
Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.
bjosoren's IT-Tech blog 