Changing Extender script path

In Extender PU9 and above, users can configure where to check out the scripts. This only needs to be done if you have security issues on the %LOCALAPPDATA% folder.

Default path

Extender caches scripts at runtime in the user's temp folder:  %LOCALAPPDATA%. In most cases, this is set to c:\users. The path is also used to check out scripts.

When to change the default folder

In some cases, %LOCALAPPDATA% is set to a folder that the users don't have write access to.

For example, when using AutoSimply Barcode, AC Chat or TeamWork. Such programs run under a system user account and LOCALAPPDATA for that user is set to c:\windows\system32\config, which it doesn't have write access to. So, we need to allow the user to specify where to check out the scripts so they can set folder permissions.

You can now specify where to check scripts out by setting a registry key.

If not specified in the registry then it uses LOCALAPPDATA as before.

Detailed steps

In the Registry Editor, add a new Key called Extender and a new StringValue called ScriptPath in the Extender key.

  1. You can use either LOCAL_MACHINE or CURRENT_USER - Extender will first check for CURRENT_USER and only use LOCAL_MACHINE if CURRENT_USER is not set.

    1. Set CURRENT_USER if you want the setting to only apply to the current Windows user.

    2. Set LOCAL_MACHINE if you want the setting to apply to ALL users.

  2. Set the value to a path that all users have write access to.

 

Notes:

  1. If the WOW6432 Node exists, the registry needs to be added to the \WOW6432Node\Orchid Systems node as Windows will use that (ie it silently maps any calls to HKEY\Software\Orchid Systems to HKEY\Software\WOW6432Node\Orchid Systems).

  2. If the Orchid Systems node doesn't exist then create it.

  3. If the Extender key doesn't exist, create it.

  4. Don't use the View Extender or Orchid Extender 2024 PU12.xx existing folders

Restart IIS

Restart IIS to apply the change. This applies to running the EFT Web screens and third party applications such as AutoSimply Barcode or TeamWork.

Test that the scripts run in the Sage 300 desktop and using the other applications.