APPNOTE: Setting up Pronto for Windows for use by a restricted user

Article ID: 010509sab
Last Reviewed: Jan 04, 2012

The information in this article applies to:

  • Pronto for Windows 32 bit releases 5.04 and later on Windows 7, Vista, XP 2000 and NT4 (does not apply to Windows 95/98 and ME).

Target Audience.

This article is aimed at:

  • IT System Administrators.
  • Technical support staff.

Summary.

The default Pronto for Windows installation assumes that users of Pronto have read and write access both to the directory in which the application resides and to the registry key under which profile information is saved.

These two assumptions may not be the case for a restricted user. This application note describes the process that a Power User or System administrator must perform before Pronto for Windows will run under a restricted user account.

Registry access for a restricted user.

Pronto for Windows can be configured so that all users share the same profile settings or so that each user has their own settings.
For Pronto Releases 5.56 and earlier the installation program configures Pronto so these settings are stored in the common area in the system registry under HKEY_LOCAL_MACHINE.
For Pronto Releases 5.57 and later the installation program configures Pronto so these settings are stored on a per user basis under HKEY_CURRENT_USER.

On Windows 7, Vista, XP, 2000 and NT4.0 a restricted user can read settings under HKEY_LOCAL_MACHINE but cannot change them.

Registry Access Option 1 (recommended) : give each user their own set of profile settings.

This will already be the case for systems where Pronto 5.57 or later was the first installed version.

Option 1: Precautions.

Performing the steps below will result in each user who logs into a machine having separate settings. This will cause the following effects.

  • All settings for all users of Pronto for Windows will reset to their defaults.
  • Any Scheduled Events created before this change will be lost.
  • After this change a Scheduled Event created by one user will not be run unless the same user is logged in and Pronto is running.
  • A restricted user will not be able to set-up Pronto passwords under the Tools – Passwords – Define menu.

Option 1: Procedure.

Perform the following steps while logged into the computer as a Power user or Administrator.

  • If Pronto for Windows is not already installed then install it using the installation disks.
  • Start Pronto for Windows.
  • Close Pronto for Windows.
  • Finally using REGEDIT.EXE find the key:
    “HKEY_LOCAL_MACHINE\Software\Ranger\Pronto for Windows\User Info\ProfilePerUser”
    and change the value for this key from 0 to 1.

Registry Access Option 2: Allow users full access to a shared set of profile settings.

Restricted users of Pronto For Windows can share the same settings, if they are given full access to the appropriate registry key.

Option 2: Procedure.

Perform the following steps while logged into the computer as a Power user or Administrator.

  1. Using REGEDIT.EXE or REGEDT32.EXE find the key
    “HKEY_LOCAL_MACHINE\Software\Ranger\Pronto for Windows”
    and set the permissions to allow any restricted users full access.
  2. Finally find the key
    “HKEY_LOCAL_MACHINE\Software\Ranger\Pronto for Windows\User Info\ProfilePerUser”
    and ensure that this value is set to 0.

User data file access for a restricted user.

Pronto for Windows creates subdirectories below the application directory to save files created by a user or downloaded from a Logger. If a user does not have write access to the application directory then Pronto is unable to create subdirectories below it.

File Access Option 1 (recommended) : Change the location where Pronto creates and stores user data files.

In an installation where each user has their own configuration settings this must be done for each user.

Option 1: Procedure.

  1. With Pronto running select the Tools – Options menu item, then click on the General tab.
  2. Click on the button marked File Locations.
  3. Change the file locations individually or you may click on Set Root and set the directory below which Pronto will create all other directories.
  4. Click on OK to save changes.

File Access Option 2: Allow restricted users access to the application directory.

Option 2: Procedure.

  1. Using Windows Explorer browse to the location where the application was installed.
  2. Right click on the folder and click Properties from the pop up menu.
  3. Click on the tab marked Security (Note: this tab is not present on FAT or FAT32 formatted drives).
  4. Set the access permissions to allow those users that require it full access.
  5. Click on OK to save changes.

Support files access for a restricted user.

Pronto for Windows requires write access to the following support files, installed, by default, to the application directory:

  1. Pronto.abk, this is the Logger Address Book.
  2. PMacros.ini, this stores Pronto Macros created using the Tools – Macros menu item.
  3. Normal.pdt, this is the template used for new projects, if this file is read only then the Project Fields tab under Tools – Options will not work.

When Pronto requires access to one of these support files, if the file is no longer in the application directory, Pronto presents a dialog allowing the user to browse to the new location. This location is then stored in the registry for the next time access is required.

Support Files Option 1: Move support files to a shared location.

Using Windows Explorer or your prefered file utility simply move each of the files to a location all users have access to.
for example:
“c:documents and settingsall usersapplication datarangerpronto4w”.
or (for Windows 7 or Vista)
“c:usersall usersapplication datarangerpronto4w”.

Support Files Option 2: Give each user their own copy of the support files.

This is only possible if each user has their own configuration settings. Bear in mind that each user will have to browse for the location of each of their support files the first time they run Pronto, unless you preset the entry in the registry for each file.

Using Windows Explorer or your prefered file utility simply move each of the files to a location each user has access to.
for example:
“c:documents and settingsJohn Doeapplication datarangerpronto4w”.
or
“c:documents and settingsJohn DoeMy Documentspronto4w”.

Support Files Option3: Allow restricted users access to the application directory.

See Option 2 under user data file access.