How to set up terminal access to 1C?

Question

1C

Question to experts 1C. Task: to ensure the operation of 1C on a terminal server, where accountants will remotely connect to work in it. There is a legal copy of 1C and a hardware USB key (hasp). 1C on windows server from under the local user saw the usb key and started, but there were problems when starting 1C from under the user of the RDP terminal (remote desktop). As far as I understand, HASP does not allow work from under the terminal? Raised a virtual machine on the server, set up a local network, forwarded a USB device there, installed the hasp driver and license manager there. In the nethasp.ini 1C configuration on the server, I registered the values

NH_TCPIP = Enabled
NH_SERVER_ADDR=192.168.0.2 (virtual machine address)
NH_USE_BROADCAST=Disabled

1C still does not see the hardware key:

License not found. The application protection key or received software license was not found!
due to:
License search on client:
local key not available: Status=-10, ORGL8 Local, not installed
Software license file not found
local key not available: Status=-10, ORG8A Local, not installed
local key not available: Status=-10, ORG8B Local, nethasp.ini not installed
: C:/Program Files (x86)/1cv8/conf/nethasp.ini, read successfully, error connecting to license manager: Net Status=0, System Error=0, Warning=142, ORGL8 Network, not installed
nethasp.ini: C:/Program Files (x86)/1cv8/conf/nethasp.ini, read successfully, error connecting to license manager: Net Status=0, System Error=0, Warning=142, ORG8A Network, nethasp not
installed .ini: C:/Program Files (x86)/1cv8/conf/nethasp.ini, read successfully, error connecting to license manager: Net Status=0, System Error=0, Warning=142, ORG8B Network, not installed
Configuration not is basic

Answer 1

Our 1C hardware keys work on several terminal servers without problems. You need to configure it in the network distribution mode, install the key driver (SafeNet) and the Hasp License Manager (HaspLM) program. You may need to open port 475 on TCP and UDP in the firewall.

Answer 2

I have the same problem with keys when working via RDP - I don't see the key. For now, the solution is to work through VPN + VNC.

Answer 3

Could it be that the key is installed in the virtual machine? Try, for the sake of experiment, to install it on a physical computer, you can even on a regular workstation.
PS Is this the only key on the network?

Answer 4

If the client key is single-user (purple with ORGL8 marking), then it should not work via RDP. It makes no sense to prescribe any parameters in nethasp.ini in this case, because HASP LM does not work with single-user keys and cannot distribute them.