LoginPi Real world performance insight – part 1
LoginPI Real world performance insight
- Login PI server
- Target Environment
- Active directory
- Database configuration
- AD configuration
Next step is the AD wizard, it will create an base OU and two user accounts to use with Login PI. If you have more than one user to run you can specify that here, the script you will run later on will create those user accounts.
- Citrix Storefront
- Citrix Web interface
- Citrix XenApp
- Direct Desktop
- Microsoft RDP
- VMware Horizon View 5.x or 6.x
After you created a profile you will setup a workload setting. There are two types of workloads you can configure. You need to configure the office language, the office version and the operating system language.
When you choose Default workload – Standard Windows apps you have the option to specify which applications you want to start. This is handy when you want to prevent that one certain application is used in the test.
With the Office workload you could specify if for instance outlook needs to be started, outlook needs configuration that perhaps is not possible automatically.
The next one is the connection, here I need to setup a connection with Storefront. Mind you that you configure Login PI to talk to the store and not to the storeweb site. It doesn’t matter if you configured Storefront with a default user domain or not after you configure the domain here Login PI handles it fine.
To the connection you have to add a users that will logon as an actual user. There is a button at the end of the connection you just added, click there and type the username and password to add the user.
In the beginning I wrote that you had to share the folder of Login PI on the server, at this point of the configuration you will see the reason why. When you didn’t configure the share you will get an error here. The dataserver is a share on the Login PI server that will be accessed from the target server.
The same goes for the webserver, from the target server the share is accessed and therefore needs to be available.
You need to configure the launchers that will start the sessions, here I configured only one launcher just to see the working of the product. It’s the host name that is needed when you add a launcher.
Now the configuration is ready and you create a job so that the show can begin.
In the main screen you will see an overview of the jobs configured and if they are running or idle.
I zoomed in a bit so that you see the job stats screen more in detail, this is where the configuration stops and the launcher takes over.
The launcher starts the session and the user you configured is logged on to the XenApp server. When the user logs on the logon script is launched.
for more info on the product take a look at : http://www.loginvsi.com/products/login-pi