A customer reported an issue because all PCs had the same hardware id and therefore couldn’t connect (because the orcus server rejects all clients which run on a computer that is already connected). It is hard to solve that issue, especially client PCs which are running a Window server client are hard to identify. To solve that issue, we created a possibility to salt the hardware id through a registry key. If that key exists, it is involved into the hardware id hash.
Nice to know:
By default, the hardware id is an md5 hash of the volume serial number of the first drive and the processor id.
The registry key you have to create is HKEY_CURRENT_USER\SOFTWARE\Orcus. Create a new value of type ‘string’ named HardwareIdSalt and input something random. If you now start any Orcus client, it will see that key and involves it. You can also use a .reg file:
Windows Registry Editor Version 5.00