Hello. This is Sam Hancock, Support engineer at Dell. I'm going to be throwing the spotlight on vWorkspace version 8's new feature, enabling diagnostics. We're on a Windows 7 machine at the minute. A user has specified that they have an error, and you've been asked to look into it.
The error may not be recognizable to you, however the good news is in vWorkspace 8, we have enabled one application to grab all the necessary vWorkspace logs for you and store it in one location. So on the local machine if you browse the C drive, Program Files x86, Quest Software, vWorkspace client, there will be a folder called Diagnostics.
Under this folder you will have Diagnostics application, which if you're running UAC, you will have to run as the administrator. This will then pop up the PN diagnostics tray. You can right click this tray to enable the diagnostics. And then replicate the error. In order to cease the capture, hit the iconic again. Choose to enable diagnostics, and it will prompt for a folder. Location
Each individual diagnostic zip file will have a time and date stamp attached to it. Within the file, you will see logs associated with the vWorkspace components that are specifically installed on that machine. In this particular example, it looks like the problem was session host. So we can switch the session host and run the same process again. Get to the local C drive, open the Program Files. Quest Software.
This time, vWorkspace folder. The same Diagnostics folder, and the same PN diagnostics tray application. Run through the same process as we did before. This being a session host, there will be a data collector service running. So when we save the zip file to the desktop, we'll see data collector service logs. Using the diagnostics logs, we can start to understand where the problem may lie.
So we switch back to our desktop. And unfortunately, still the same problem. So undeterred, we'll use the diagnostics tool again. And grab a new set of logs. Here you'll notice the usefulness of the time stamp. You'll also see that another vWorkspace component, the Windows Connectors, has been invoked. Therefore, this has also provided logs.
The diagnostic logging is all driven by a diagnostics.xml. Here you'll see all the different vWorkspace components. Thanks to the ease and usefulness of the diagnostic logging, the error was identified and quickly corrected. For more information about vWorkspace, visit quest.com/vworkspace.