As stated in my previous blog I also use Login PI in my lab to do research and monitoring of my desktop environment.

Recently I have updated the PDF reader in my lab environment. I was using Adobe Reader XI and updated to Adobe Reader DC. We all know that Adobe Reader isn't the quickest application to start and it has a lot of stuff included that isn't necessarily needed to do the basic PDF reading.

Write comment (0 Comments)

In my lab I have Login PI running to do research. While looking at the dashboard I noticed the following thing, normally logon and running times are around 12~14 seconds. Since an x period the Logon and running times went up to around ~60 seconds (see first pictrure, at point 1)

Picture One, depracation of logon time

Write comment (0 Comments)

Previously when running Windows 8 or hyper-v server 2012R2 it would be easy to implement Deduplication on those workstations/servers by installing the deduplication binaries found in Windows Server 2012 R2 (as I described here).

Being on Windows 10 and being a Windows Insider (in the fast ring!) I found it hard to use deduplication, there are some binaries that can be found on the internet coming from Windows Server 2016 tech preview. But receiving new build on an almost weekly basis, it is very hard to keep dedup working this way.

Write comment (0 Comments)

In older versions of NetScaler when wanting to customize the Gateway portal we did customize files etc. With NetScaler 11 there is the portal themes function, making it easy to customize to a certain amount. But you cannot go further then the standard options in the portal themes function. Recently at a customer I got the question how they could add some links under the logon portion of the Gateway.

This article describes a way of adding URL's to the Gateway, without having to edit the physical pages. We will be using rewrite rules, from within NetScaler.


From within the CLI add the following code:


add rewrite action rw_act_insert_loginfooter insert_before_all "HTTP.RES.BODY(120000).SET_TEXT_MODE(IGNORECASE)" q{""var login_footer=$(\"<div style='text-align:center;color:black;font-size:15px;'>My personal website found <a href ='' target='_blank'>here</a></div>\").appendTo(logonbox_container);""} -pattern "box_view.prepare_view();"



add rewrite policy rw_pol_insert_loginfooter "HTTP.REQ.URL.CONTAINS(\"gateway_login_view.js\")" rw_act_insert_loginfooter


From the GUI we create the following

 Rewrite Action

 Rewrite Policy


 After the Action and Policy are created we bind the Policy to the Gateway vServer.


 Binding the ReWrite policy


As a result of the Policy we will see:


As you can see, there is a link added to the standaard Gateway portal. By uisng a rewrite policy we can further cusotmize the portal, think of using different CSS styling, formatting the login box or whatever. You can use FireFox with FireBug for instance to check what elements are configured by what file and create a rewrite action and policy for this specific file(s).

Happy customizing!


Write comment (0 Comments)

Performance collection files like *.etl and *.blg files I work with on a daily basis as a performance consultant. Collecting the files is quite easy, working with them can be teadious. Especially when the log files are seperated (because you don't want logging to be the bottleneck in the performance and you schedule log creation for once in the x minutes).

working with performance collection filesXperf

Because opening the different log files can be very time constraining and not give the entire view of the timeline, I like to merge files. The two different log file types need to be merged on a different way. The ways are by Xperf (Explanation here) and by relog (Explanation here).

Merging the performance collection files

To do a merge of *.etl files do the following:

  1. Open powershell
  2. Browse to the location of the Logfiles
  3. enter: $Test=get-childitem -recurse -include *.etl
  4. after that enter: xperf -merge $test MergedETL.etl

When merging *.blg files use the following procedure:

  1. Open powershell
  2. Browse to the location of the Logfiles
  3. enter: $test=get-childitem -recurse -include *.blg
  4. After that enter: relog $test -f BIN -o mergedlogs.blg

Make sure that when merging *.blg files you do not have more then 32 files and that there are no empty (400 kb) files.

After merging the files you can go on analysing the performance collection files. You can use your own favorite tooling to do the analysis. I will spend a following blog about which tooling I use and for what cause.

If you have any questions or remarks after reading this article feel free to hit me up with your questions or remarks, I will try to get back at you as soon as possible and where possible update this blog post to corresponded with your question or remark.

Write comment (0 Comments)
feed-image RSS