One of the screens I find myself spending a lot of time in, especially when troubleshooting View 5 issues is the Events Monitoring Screen. Unfortunately it’s not created for you as part of the View 5 install. Instead, you have to realize its not created, and then go about creating it and logging the issues. Again, the unfortunate part of this process is you rarely realize you need this, or that its not logging, until you actually need to troubleshoot something !! DOH!! This is a quick blog on everything you need to setup your View 5 Events database.
By the way, this blog part is in addition to the original blog post on “How to install, configure and deploy VMware View 5 on vSphere 5”
My recommendation is to setup a separate View 5 Events Database in your SQL 2008 R2 instance we setup as part of the original View 5 install guide. I’ll take you through the short process of setting up the new database, and then how to get it added into your View 5 Configuration and then we can test to make sure everything is logging correctly.
1. First things first, lets RDP into our SQL 2008 R2 Server and setup a new Database.
2. Lets connect into our Database.
3. Right click on Database and select “New Database”
4. I’m using View5EventDB for the database name.
5. Let’s click on Options – and change Recovery Mode to Simple and then click okay and we are done !!
6. Just to double check, lets verify our new database is setup.
Now, lets head over to our View 5 Admin page and setup event monitoring.
1. Click On Event Configuration in the dashboard (under View Configuration)
2. Click on Edit and enter in the info we used to setup our database – then click OK.
3. Your Event Configuration page should look like this:
4. Now lets go see if we are collecting information. Go to Monitoring and click on Events. Go ahead and log into a desktop to kick off some events.
5. Once you click on Events – you should see information populating. In this case, I just logged into a virtual desktop and that logged some info.
There ya go – Easy Peasy !!