Skip to main content

VirtFsService.Registry file in Windows\Temp and grow to a large size

Lukasz Mikosz
  • Created:
  • Updated:

Problem:

VirtFs.Service.Registry file in Windows\Temp and grow to a large size

Symptoms:  

This can happen on physical (persistent) machines running DIA where when windows updates, user installed applications, vMware, Citrix or SCCM applications are installed/uninstalled during session. These will continually query the Windows registry for values and where we are doing session isolation and logging these requests in the VirtFsService.Registry.log or VirtFsService.Registry.txt file.

Resolution:

Step 1 What file to modify and how:

Create a backup:

C:\Program Files\ProfileUnity\FlexApp\ContainerService\(x64 and x86)\VirtFsService.exe.config.

A) Turn Off Debug Logging.

Modify: C:\Program Files\ProfileUnity\FlexApp\ContainerService\x64 (or x86)\VirtFsService.exe.config.

Find this section inside the file:

<log4net>
    <logger name="AppstreamLogger" additivity="false">
      <level value="INFO" />
      <appender-ref ref="RollingFileAppender" />
    </logger>
    <root>
      <level value="ALL" />
      <appender-ref ref="ServiceAppender" />
    </root>

Than Replace "ALL" with " FATAL" 

Save the file.

How to update the environment and propagate the changes you performed above:

Option 1) Manual change on RDSH/Citrix Server/Gold/Master Image:

  • Stop the Liquidware Labs container service
  • Restart the machine/server, recompose

Option 2) On Persistent Environment: 

Change via new install from Lwl.ProfileUnity.Client.Startup.exe or lwl.ProfileUnity.Client.Update.exe (never versions of PU) that runs at computer startup:

  • On the netlogon or share where client tools are installed, extract the flexapp.zip
  • Modify (above) flexapp.zip\ContainerService\x64 (or x86)\VirtFsService.exe.config.
  • Zip up the full file set as flexapp.zip again
  • Modify: lwl.ProfileUnity.Client.Startup.exe.config or lwl.ProfileUnity.Client.Update.exe.config (Depending what client version is installed)
  • Look for <setting name="ClientVersion" serializeAs="String"> 
    • <value>6.7.6411-4701d59</value>
  • Change value and increment (example): <value>6.7.9411-4701d59</value>

When machines reboot they will run the Lwl.ProfileUnity.Client.Startup.exe which will run lwl.profileunity.client.update.exe and detect the higher number of build and update the files on the persistent machines.  

 

 

Also see installing ProfileUnity on Gold image.  https://www.liquidware.com/support/articles/210630623-Installation-of-ProfileUnity-onto-a-Base-Image-gold-image-  

 

Product: ProfileUnity-FlexApp

Product Version:  6.7.6+

 

Related articles