Configure SoftLINK to write to the Local Machine rather than to the Current Users profile

You are here:
  • KB Home
  • SoftLINK
  • Configure SoftLINK to write to the Local Machine rather than to the Current Users profile

Download PDF:  KB0130

Summary
In SoftLINK 9.00 and above the location of where the Tutor Configuration is stored in the registry was changed. This change was made for Environments where Users would not have rights to write to the Local Machine, but would have rights to write to their logged on users Profile. From SoftLINK 9.02.003 and above a registry setting has been added that can be set to revert SoftLINK to write to the HKEY_LOCAL_MACHINE rather than to HKEY_CURRENT_USER.

Reverting the Tutor to write its configuration to the local machine will ensure that the same configuration is then applied to any user that logs onto this machine.

Details

For 32 bit Operating Systems please follow the below Steps:

Delete the following registry setting if present:
Registry location: HKLM\Software\Productive Computer Insight\PCICTL\
ValueName: NSSregkey
Value: hklm
ValueType: String

Add the following registry setting:
Registry location: HKLM\Software\Productive Computer Insight\PCICTL\
ValueName: NSSUseHKLM
Value: 1
ValueType: String

For 64 bit Operating Systems please follow the below Steps:

Delete the following registry setting if present:
Registry location:HKEY_LOCAL_MACHINE\Software\Wow6432Node\Productive Computer Insight\PCICTL\
ValueName: NSSregkey
Value: hklm
ValueType: String

Add the following registry setting:
Registry location: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Productive Computer Insight\PCICTL\
ValueName: NSSUseHKLM
Value: 1
ValueType: String

Note: Once this value has been added to a SoftLINK 9.02.0003 installation the registry settings will be stored in the central location.

Was this article helpful?
Dislike 0
Views: 18
Previous: Cannot deploy SoftLINK to a Windows XP or Windows 2000 workstation from a Windows 7 workstation in a workgroup environment
Next: SoftLINK reports that client no longer responds