Difference between revisions of "Terminal Server & Citrix Host"

From regify WIKI
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
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.
 
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. The host usually switches depending on load or availability of host machines. Thus, the hosting hardware is changing and you may get permanent error regarding '''"hardware has changed"''' .  
+
Running regify software on Terminal Server or Citrix environments with multiple hosts means to likely run on a different host machine after login. The host usually switches depending on load or availability of host machines. Thus, the hosting 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 or Citrix host machines:
+
To get rid of the problem, you need to provide a registry key that is on all Terminal Server or Citrix host machines.
 +
 
 +
To solve that '''without manual registry entries''':
 +
 
 +
# Open notepad and paste the following:<pre>Windows Registry Editor Version 5.00&#10;&#10;[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSLicensing\Parameters]&#10; "regifykey"="Nup2w,Eq4qe16u"</pre>
 +
# Change the value "Nup2w,Eq4qe16u" to be another random key. We suggest to write down this key!
 +
# Save as file '''regify.reg''' to desktop.
 +
# Double click that file and let it write to the registry.
 +
# Copy this file to the other hosts and also doubleclick to let it write the registry key.
 +
 
 +
 
 +
 
 +
If you prefer to '''create the registry key manually''', you have to create this key:
  
 
  HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\MSLicensing\Parameters\regifykey
 
  HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\MSLicensing\Parameters\regifykey
  
It must be of type ''REG_SZ'' and, for example "Nupew,Eqaqe967" as value (without quotation marks). It '''must be the same on all your Terminal Server or Citrix hosts''', so every regify software is always getting this key (no matter which host machine the user is associated during login). 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:
+
It must be of type ''REG_SZ'' (String) and a random key as value.  
 
 
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.'''
+
'''IMPORTANT:''' The key '''must be the same on all your Terminal Server or Citrix hosts''', so every regify software is always getting this key (no matter which host machine the user is associated during login). The trick is that it must be the same on all host machines.
  
 
== If you already configured your software before the keys were entered ==
 
== If you already configured your software before the keys were entered ==
  
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.
+
Upon the registry 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.

Latest revision as of 11:07, 7 October 2025

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 with multiple hosts means to likely run on a different host machine after login. The host usually switches depending on load or availability of host machines. Thus, the hosting 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 or Citrix host machines.

To solve that without manual registry entries:

  1. Open notepad and paste the following:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSLicensing\Parameters]
     "regifykey"="Nup2w,Eq4qe16u"
  2. Change the value "Nup2w,Eq4qe16u" to be another random key. We suggest to write down this key!
  3. Save as file regify.reg to desktop.
  4. Double click that file and let it write to the registry.
  5. Copy this file to the other hosts and also doubleclick to let it write the registry key.


If you prefer to create the registry key manually, you have to create this key:

HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\MSLicensing\Parameters\regifykey

It must be of type REG_SZ (String) and a random key as value.

IMPORTANT: The key must be the same on all your Terminal Server or Citrix hosts, so every regify software is always getting this key (no matter which host machine the user is associated during login). The trick is that it must be the same on all host machines.

If you already configured your software before the keys were entered

Upon the registry 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.