Recipe : Devolutions RemoteDesktopManager

A lot of IT departments use RemoteDesktopManager of Devolutions. Its a license product for your remotedesktop sessions. The product has several addons. For example: Dropbox, Hyper-V and many more.

Virtualizing this application isnt a straitforward job. The licensekey is stored inside the %appdata% and contains serveral hardcodepaths of the user who configures the application. In the following blog i have described the workaround to these issues.

Start the installation of Remote Desktop Manager




Select : Typical


Deselect Desktop and Quick Launch toolbar to remove these from the package





Select “I accept the terms in the license agreement”



Click Install


Click Finish


Fill in your license information and click op OK

2018-03-25 18_10_22-image12

Click on Ok


Open File


Go to Options


Go to General > Applicaiton Start  and deselect “Enable check for updates” and “Check for Add-on update at startup”

Click OK


Close the application



Go to %appdata%\Devolutions\RemotedesktopManager

Edit RemoteDesktopManager.cfg

Remove “EncryptedDataSources” tag

Change FirsTimeOpening tag to “True”


Add “<ShowWelcomePage>false</ShowWelcomePage>”  Tag


Remove the files, see screenshot and leave RemoteDesktopManager.cfg and Addoninfo60.xml.


Close and save the application!

Goodluck and happy packaging!


Recipe: Greenshot

This blog will guide packagers to virtualize Greenshot.


Greenshot is a free screenshot tool with a nice screenshot editor. I have been using Greenshot for years and running virtualized with App-V 5. The application could be configured through a default template, fixed settings or leaving de config in %appdata%\Greenshot. I should suggest to use a combination between Greenshot-default.ini and Greenshot-fixed.ini, see Greenshot Website for more information.

You can download greenshot from the website

Start to sequence with default settings.

Install the downloaded version of Greenshot

2018-03-25 16_08_33- - Remote Desktop Connection

Trying to avoid integration issues i tend to install compact version of greenshot. I am not interrested in these addons.

2018-03-25 16_10_46- - Remote Desktop Connection

Open de preferences after installing the applications. Richt click on the greenshot icon in the icontray > click on preferences..

2018-03-25 16_11_53- - Remote Desktop Connection

By setting the “Update check interval in days” to 0, the application will not prompt for updates.

2018-03-25 16_12_06- - Remote Desktop Connection

If you are packaging for VDI or RDSH environments, you might consider the “Make some optimizations for usage with remote desktop”.

2018-03-25 16_12_19- - Remote Desktop Connection

After editing, the settings are saved in %appdata%\greenshot\greenshot.ini. The default en fixed settings are used for default settings or force settings. You can reuse the current Greenshot.ini and remove all unwanted settings.

My example for Greenshot-Defaults.ini

2018-03-25 16_15_24- - Remote Desktop Connection

My example for Greenshot-Fixed.ini

2018-03-25 16_15_31- - Remote Desktop Connection

You need to copy these settings to C:\Program files\Greenshot\

2018-03-25 16_15_48- - Remote Desktop Connection2018-03-25 16_16_24- - Remote Desktop Connection

For best practice, close the running application.

2018-03-25 16_16_33- - Remote Desktop Connection

Remove greenshot from %appdata%\Greenshot

Application configuration

2018-03-25 16_16_54- - Remote Desktop Connection

Remove greenshot from %localappdata%\Greenshot

Application logs

2018-03-25 16_17_06- - Remote Desktop Connection

The application is ready and you can stop monitoring the application.

All the registry settings should be deleted

2018-03-25 16_19_42- - Remote Desktop Connection

All the files should be deleted, except for the greenshot directory.2018-03-25 16_20_52- - Remote Desktop Connection

Beware, the application does not need write access to the program files. To force the settings of “Greenshot-fixed.ini” users shouldnt have write or delete access on programfiles. Keep de “Allow Virtual Applications full write permissions to the virtual file system” unchecked.2018-03-25 16_21_01- - Remote Desktop Connection

The default setting of Greenshot is startup at userlogin. This setting is configured through RUN registry and is ignored by App-V 5. You could create a shortcut in \Programs\StartUp if you want this feature.

2018-03-25 16_21_29- - Remote Desktop Connection


Goodluck and happy packaging!


Recipe: App-V 5 Workpace 5.0.3

Wellnomics Workpace 5.03

The application workpace is used to monitor the behaviour and advice the users to reduce RSI (Repetitive strain injury) Through videos and popups the user is informed to exercise or to take a break

This application is supplied with an administrative guide, “Wellnomics WorkPace 5.0.3 IT Administrators Guide.pdf”. You can configure the first run and even force configuration.

Note: You need to force “OptionSuspendInRemoteSession=Locked:N” setting inside C:\Installationdirectory\system\default.ini for VDI and RDS.

App-V 5 Recipe

My colleague Randy von Bannisseht started packaging “Workpace”. This application is usually an easy package. We didn’t expect any problems with this application. The main shortcut works without any issues. The shortcut “WorkPace Training” gave errors. It started with “Directory Player Error” with message “Unable to load movie playlist. …”


The sequencer informed us of about excluded files of the %TEMP% directory. Our first step was removing the exclusions %LOCALAPPDATA%\TEMP and %LOCALAPPDATA%. We solved the “Director Player Error” but we received an “Application Error” with the message “The application cannot start as it cannot create needed files. There may not be enough free disk space”.


After this error message we tried to write into all the parts of the VFS (%ProgramFiles% and %TEMP%). We were able to successful write to the VFS.


The solution was found by trail and error. The application shouldn’t be started during the monitoring fase and the application needs to be installed to the PVAD. The installation didn’t change for creating the App-V package. Removing the %TEMP% directory from the exclusion list is not needed.

Microsoft App-V 5 Connectiongroups and errors

Edit: The issue is solved in App-V 5 SP2. The connectiongroups can’t be added with these conflicting settings

Microsoft App-V 5 Connectiongroups and errors

Error: This may be due to a network failure

After importing App-V 5 packages and setting up connectiongroups I was experiencing problems with starting up the applications. I got several errors:the may be due to a network failure

Error: this may be due to a network failure

Error code: 0x8e90060a-003000F

On a Windows 2008 R2 server i got a additional error.

error: MSVCR100.dll

MSVCR100.DLL missing from the system

The following error is in the eventviewer:

failed to start due to Virtual COM subsystem failure

Process 2744 failed to start due to Virtual COM subsystem failure. Package ID {715f39d8-1b48-4b9a-95e6-d33370564b33}. Version ID {9cdf46f3-6716-43d3-b533-5c697878f51f}. Error: 0x8E90060A-0x3000F


With troubleshooting these errors i didn’t find a solution on the internet. There are some similar errors around with different solutions. My problem wasn’t about local rights, because I tried local administrator account and domain admin account. The application would startup correctly after removing the connectiongroup.

The connectiongroup was giving the problem with these applications. A new connectiongroup with different applications worked fine. My suspicion instantly went to “allow all named objects to interact with the local system” and “Allow all COM objects to interact with the local system”. In Microsoft App-V 4.* this settings was “ALLOW LOCAL INTERACTION”.

Testing my suspicion

For my test I created two new applications:

  • A Link to notepad without any registry or files
  • A Link to odbcad32 without any registry or files with BOTH Com and Named objects allowed

Both applications worked fine as a single App-V package. I connected both App-V packages through a connectiongroup.


The connectiongroup imported without any errors or warnings. After the creation of the connectiongroup the applications started with the errors again.


The connectiongroups aren’t able to handle a choice between using or not using “allow all named objects to interact with the local system” and “Allow all COM objects to interact with the local system”. The Microsoft App-V 5 client will generate several errors with startup, because it can’t make a choice between them.

App-V 5 Shared Content Store SCS


In my first blog i want to talk about App-V 5 Share Content Store. At my work we are developing a App-V 5 training for our customers. In my lab i have tried to use Shared Content Store (SCS). With SCS in App-V 5 we are able to keep the footprint of the cache application to a minimal. Because the application inst fully downloaded at run-time.

The use of SCS could be useful for VDI infrastructure, to spare on the storage usages.

I have noticed my test account was able to download his own applications. Because the test user downloaded all his applicationcache, the use of SCS is nullified. Microsoft has fixed this issue during beta. Soo i was surprised of this option.

Other people aren’t having the same problem as my lab. Why is my lab having this option for the users?

I have tried out three options:

Situation A:

Installing App-V 5 Client with the correct paramenters  “appv_client_setup.exe SHAREDCONTENTSTOREMODE=1 /q” and rebooting and setting all the settings through GPO

Situation B:

Installing App-V 5 Client with the installer gui and rebooting and setting all the settings through GPO

Situation C:

Working after situation B, but removing all the cache through powershell “Get-AppvClientPackage -All | Stop-AppvClientPackage | Remove-AppvClientPackage”  and rebooting and setting all the settings through GPO

The results,

With the situation A en C the test user wasnt able to cache the applications

Although Situation B the test user was able to cache the applications.

Conclusion: Install App-V 5 with unattented installation through or rebuild your local cache through Powershell.