Login VSI Launcher Waiting

Every now and then, I am running a couple of VDI benchmarks. Most of the time when I run a benchmark, I re-build my whole VDI environment incl. Login VSI systems on my Shuttle DS81s (I use 10 for ~100 VDI desktops). This time, I set-up 3 Login VSI Launcher VMs and 50 VDI desktops for a quick test.

When I tried to start the test, my Login VSI Launcher was stuck in the status “waiting” and I got the following error:
The current user does not have permission to enumerate and/or logoff the user sessions on the launcher

LoginVSI

 

This is not the first time that I have run into this error but I always forgot how I fixed it. Well, this time, I had a couple of minutes to take a screenshot and actually write down how to fix it for the future.

In my case, my Launcher-VMs are running Windows 7 64bit. If you run any Desktop OS, you have to enable remote RPC manually via the registry on each individual VM, or you could just create a template.

I followed these steps to get it working:

  1. Open the Registry Editor and go to HKEY_LOCAL_MACHINE -> System -> CurrentControlSet -> Control -> TerminalServerScreen Shot 2015-03-30 at 5.41.36 PM
  2. Change the decimal value of AllowRemoteRPC from “0” to “1”Screen Shot 2015-03-30 at 5.41.55 PM
  3. Try to start your Login VSI workload again. For me this did the trick and it started to work.Screen Shot 2015-03-30 at 5.44.03 PM

2 Comments|Add your own comment below

  1. Nice article Jan! The AllowRemoteRPC thing is only with Windows clients (like 7) run as a launcher. When you use Windows 2008 (R2) or Windows 2012 (R2) it works out of the box.

    I prefer to do some (performance) things on the laucher like:

    Stop Spooler
    Stop Themes
    Stop BITS
    Stop Antivirus
    Stop …

  2. I agree Manfred, this issue only occurs on desktop-like Operating Systems. Also, I use VMware OS Optimization Tool on all my VDI templates and Launcher templates.

Leave a Reply

Your email address will not be published. Required fields are marked *