First up is placing the license file where it needs to be.
Copy the license file in the _VSI_Configuration folder of the VSI Share we created in Part 1.
Starting the Management Console
After starting the VSI Management Console (VSI MMC from here), you are presented with this screen where you need to point to the VSI Share
Now that we are in the VSI MMC, it’s configuration time!
If we want to put some load on our VTARGET machine we need to configure a LAUNCHER.
Click the LAUNCHER button on top and rightclick to add a launcher
THIS IS AN IMPORTANT STEP!!!!!:
Assign the launcher, the NAME of the MACHINE from which you will be RUNNING the load test (VLAUNCHER in my case)
Then choose the amount of “load-testers” we will be putting inside the launcher. (the express edition has 50 so we’ll go with that)
Choose Finish and you’re done!
Choosing a Test Configuration
With a Launcher in the tube we can now Create a Test configuration
You can keep the default or change the “Auto logoff timeout” in order to give the session more time to end the session.
The first time you run the test it is recommended to check the “Create Profiles” option so that user profiles are created on the Target. This has a slight impact on the measurements.
After you’ve configured this you are ready to start the test but before you do this, make sure you’ve started the VSI Agent
Now, go ahead and start the test
Let VSI do its thing and after a while you’ll be notified that the testing has been completed:
Analyzing the results
After all that hard work, we can finally enjoy the fruits of our labor:
Start the Analyzer, the first run wizard will show the following
If all goes well you should see the logs from the tests that were completed
Select a test en click Open
Select VSIMax Dynamic en hit the OK button
and voilà, we’ve gathered our first benchmark!
First off, I think VSI Express is a great tool to get statistics on what a TS/VDI machine can handle before performance goes south.
The installation process is relatively easy but has room for improvement (manual installation of the MS Chart section for example).
What the tool does not provide is insight in WHY the performance goes south (if you want to find out why your server is maxing out on X amount of users you will need to get down and dirty with Windows Performance Monitor). Even though its primary use cases are benchmarking and change impact analysis, we all know what the next question from the IT Manager will be: “Why is the server doing that..? “ So we will add this functionality to the “VSI-Wish-list”.
All in all, it’s a great tool to have on your belt. Every admin/consultant should consider using VSI when starting a new project to whip up some baseline statistics before deploying a new environment.
If this post helped you out, help me out keeping this site alive and visit some of my sponsors on the left or right.. Thanks..!
Tags: Login VSI, Installation, How-to, Part 3