Difference between revisions of "Terminal Server & Citrix Host"
(Created page with "If you get permanent error regarding "hardware has changed" and you are running on a Terminal Server or Citrix environment, your Admins very likely did not fix you on some spe...") |
|||
| Line 1: | Line 1: | ||
| − | + | All regify software for Windows, Mac and Linux is storing several settings on the local drive (.ini files in %APPDATA%). In order to protect sensitive data, passwords (login, smtp, identity-file) are encrypted using a hardware based key. | |
| + | |||
| + | Running regify software on Terminal Server or Citrix environments means to run on a different machine after login. Depending on load or availability of host machines. Thus, the hardware is changing and you may get permanent error regarding '''"hardware has changed"''' . | ||
To get rid of the problem, you need to provide a registry key that is on all Terminal Server hosts: | To get rid of the problem, you need to provide a registry key that is on all Terminal Server hosts: | ||
Revision as of 08:56, 11 March 2020
All regify software for Windows, Mac and Linux is storing several settings on the local drive (.ini files in %APPDATA%). In order to protect sensitive data, passwords (login, smtp, identity-file) are encrypted using a hardware based key.
Running regify software on Terminal Server or Citrix environments means to run on a different machine after login. Depending on load or availability of host machines. Thus, the hardware is changing and you may get permanent error regarding "hardware has changed" .
To get rid of the problem, you need to provide a registry key that is on all Terminal Server hosts:
HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\MSLicensing\Parameters\regifykey
It must be of type REG_SZ and, for example "Nupew,Eqaqe967" as value. It must be the same on all Terminal Server hosts, so every regify software is always getting this key (no matter where the user logs in). The trick is that it must be the same on all host machines. You may provide this to the servers with the help of some .reg file:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSLicensing\Parameters] "regifykey"="Nupew,Eqaqe967"
Please replace the above example key with some other password.
Upon the keys are created on all hosts, the regify software will again complain about changed hardware on next start. Now, re-enter the credentials (regify password, SMTP password and maybe you need to re-load the identity file if used). Now it will run as usual.
