Terminal Server & Citrix Host - Revision history

Regify at 10:07, 7 October 2025

2025-10-07T10:07:01Z

Regify at 09:51, 6 October 2025

2025-10-06T09:51:45Z

Regify at 09:24, 6 June 2023

2023-06-06T09:24:26Z

Regify at 09:47, 27 November 2020

2020-11-27T09:47:18Z

Regify at 09:46, 27 November 2020

2020-11-27T09:46:19Z

Regify at 09:45, 27 November 2020

2020-11-27T09:45:40Z

Regify at 12:56, 9 July 2020

2020-07-09T12:56:29Z

Regify at 07:56, 11 March 2020

2020-03-11T07:56:48Z

Regify: 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..."

2020-01-28T15:54:15Z

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..."

New page

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 specific host (eg load-balancing). So you either log-in to the one or the other host and therefore, hardware changes.

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.

@@ Line 3: / Line 3: @@
 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.
   HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\MSLicensing\Parameters\regifykey
-It must be of type ''REG_SZ'' (String) 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.
-'''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 ==
 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.

@@ Line 7: / Line 7: @@
   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, 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:
   Windows Registry Editor Version 5.00

@@ 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. 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:
@@ Line 18: / Line 18: @@
 == 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.

@@ Line 7: / Line 7: @@
   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 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'' 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:
   Windows Registry Editor Version 5.00

← Older revision		Revision as of 09:46, 27 November 2020
Line 15:		Line 15:

	'''Please replace the above example key with some other password.'''		'''Please replace the above example key with some other password.'''
		+
		+	== 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 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.

← Older revision		Revision as of 07:56, 11 March 2020
Line 1:		Line 1:
−	~~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 specific~~ host ~~(eg load-balancing)~~. ~~So you either log-in to~~ the ~~one or the other host~~ and ~~therefore,~~ hardware ~~changes~~.	+	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: