Non-admin users get JRE not found while running OWB on Windows 11 VDI

Products

• Clarity PPM On Premise

Issue/Introduction

We are encountering an issue with the OWB (Open Workbench) software. After a silent installation of OWB including schedule connect (SC) on Windows 11 VDI, and launching OWB from clarity UI we receive a “JRE missing” error message. This only occurs when the user is not a local administrator on the machine, which applies to 99% of our users.

Environment

Clarity 16.4.0

Resolution

• File System Permissions (Installation Directory)
  
  Issue: 
  VDI users running OWB part of local "Users" group which did not have access to the Directories where OWB, SC and JRE is installed 
  

  OWB
  C:\Program Files (x86)\Open Workbench\

  SC
  C:\Program Files (x86)\Clarity\ScheduleConnect\

  JRE 
  C:\Program Files (x86)\Clarity\ScheduleConnect\jre\bin

  Fix:
  Directories (for example: C:\Program Files (x86)\Clarity) selected for OWB and SC install has write permissions for the non-admin VDI users. 
  
  
• Registry Permissions (JRE Issue)
  

  Issue:
  Non-admin users were unable to initialize the JRE properly because they lacked permissions on the Clarity registry key.

  Fix:
  Silent installation script modified to grant Read/Write (Full Control) permissions to the local "Users" group on the following key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Niku

• Proxy Configuration (Connection Issue)

  Issue:
  OWB application not picking up the expected system network route.

  Fix:
  
  Modify net.properties file from OWB workstation java.net.useSystemProxies=false
  
  Note: default property value is java.net.useSystemProxies=true