Setting up LoginVSI is quite easy and fun to do. But when you get into the mix with for-instance RES Workspace Manager, where several options (includig managed applications) are enabled, it will take a while to be able to run a successfull test.
To make life a little easier, I created building blocks for the most commenly used components run from LoginVSI. When importing these building blocks only thing you need to do, is change the access control, so that you target your LoginVSI users.
Basic steps you need to do:
Create a variable called VSISHARE and give it the value of \\<servername>\<vsisharename>
Import the building blocks attached to this post and edit the Logon script to be applied to the LoginVSI group
Edit the authorized files (the admin note has LoginVSI in it) to be targeted on the LoginVSI group.
Once you are done with this, your environment is set to run the VSI tests.
A while ago I updated my SBC servers and installed IE11 on Server 2008R2. Having WM2014 on my lab servers to maintain my user settings across the SBC servers, I started to notice that my cookies aren't being roamed. Until recently I saw a posting on twitter that the issue is supposed to be solved with a solution at RESguru.
It comes down to the following:
Since IE10 the webcacheV01.dat file is introduced (located at localappdata\microsoft\windows\WebCache), this file needs to be saved, included with the cookie files, cookies are stored in appdata\microsoft\Windows\Cookies on Server 2008R2 and Windows 7. On Win8/server 2012R2 and up cookies are stored in localappdata\microsoft\windows\INetCookies.
Both the cookies and webcacheV01 file have to roam with the user and that is where the solution on RESguru comes in. All credits go to mr Rob Aarts for the solution, the whole deal is explained in the posting on RESguru.