Ferry fstelte

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) Because I have RES WM also running in my Lab i was quite easy to do troubleshooting on what was causing the slower logon times.

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.

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.

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). 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.

Recently I have been working on a performance scan for a customer. The customer wanted to have a newly built XenApp 7.6 environment validated. Ofcourse I used Login VSI to do the task at hand. While starting the validation, the customer expected to reach about 80 concurrent users on one physical host (with 3 virtual XenApp servers on it). After getting VSI to run in the environment I started a first small test, with 30 users to see what the enviroment did.

Workplace and profiles Working with Citrix XenApp, Microsoft Remote Desktop Services, or other types of workplace can be challenging when it comes to managing profiles. Most of the times mandatory profiles are used in these types of environments, but every time a user logs off their settings are flushed. Users are keen on there settings so there comes user profile visualization in to play. Tools that can virtualize user settings are Microsoft UEV, Appsense, VMWare UEM and RES Workspace Manager.

Create a Lab environment Currently I am creating and deleting AD pretty often, because I am trying out stuff in my Lab environment. Too reproduce the same enviroment I created the same OU’s, users and groups everytime, by hand. This post is about how I create a lab environment. So I created a powershell script to create the Lab environment Also created a powershell script to delete the entire environment from an existing AD and leave the rest intact, just if you need a “Lab environment” in an existing AD and want to delete afterwards.

At a customer we are using App-V 5.0 and RES Workspace Manager on XenApp 7.6 with Windows Server 2012 R2. For App-V the full infrastructure is in use. We wanted to make it possible for users to do an publishing refresh App-V applications without having them enter powershell commands or having them to logoff and logon. After the publishing refresh the script will initiate a workspace refresh. I created an application with the following Settings:

In my lab I have two App-V 5 publishing servers. I use them both to do publishing refreshes. I have a netscaler in my lab, so I figured, why not load balance the publishing servers? This article describes how to enable load balancing for App-V publishing with Netscaler 10.5. After login go to Traffic Management > Load Balancing > Servers Click on Add and add the App-V publishing servers. After adding the Servers, go to Traffic Management > Load Balancing > Service Groups and click Add After Add you will see the following screen.

In the previous part of this serie of blogs I wrote resource sharing. Also discussed the different kind of technologies, in this article I want to go into the load test I have performed at the customer. All tests are performed with the officeworker workload, 150 sessions, 60 second launch interval. The following test are performed: Baseline office worker (DFSS/RES WM on (default)) DFSS on RES WM off DFSS off RES WM on (default) DFSS off RES WM on (85%) DFSS off RES WM off Below is a chart that represents the test results in % relative to the first (baseline) test.