RDP + usb printers + Barcode FR

Question

Seal

Got serv2008 standard and clients with XP3.
By rdp we connect to the server, there we launch 1c and print to “our” printer and fiscal (stroke).
It turns out that there should be port forwarding from the client machine to the server.
I go into printers - server properties - there are ports, and I see that yes, he forwarded the ports himself: TS003-TS010 blah blah. And he sees, and the fiscal officer, I put firewood on the printer. Well, everything is super - the "golden" works.
and now two glitches have degenerated:
1. So he assigned the TS003 port to COMP_USER: usb001 (to the printer). The server itself created the printer.
The user is disconnected due to idle session. Or just closes the connection, without leaving the user.
Returns and what do we see? The server has already assigned another port to usb001 - TS004!
As a result, the old printer is not deleted, it writes that it cannot find the port and blah blah. Even under the administrator kicks.
And he does not want to create a new printer, on a new port!
2. Forwarded ports disappear.
Well, it follows from (1). I'm back for the session. And I see that he does not see the ports at all. Empty, only your local ones. I'm waiting for a couple of minutes. Hop, one port appeared. some more time later. and eventually they all showed up. But they are not active, do not want to use them. I reconnect again - and everything works!
How can you rigidly, directly with BDSM elements, prescribe these ports and that he did not change them?

PS.
and the long press is still in progress.
even just a text from a notebook with two letters, sometimes it prints 5-6 minutes.
And sent it to print. I open the print queue, and it shows there that it is downloading a document, on average it weighs about 400kb. But as soon as he finished downloading, he downloads another document. slightly less weight. As if collecting a file. And then hangs, thinks. And it prints in 4-5 minutes.
Network - 256kb.

Answer 1

Create a 'printer' and share it on the client side. As little as possible, use Microsoft's tools for automatically registering printers in RDP from Microsoft, which problems I didn’t pick up there at one time, the same with balls. To avoid problems, someone (server / program) should be responsible for the devices, independent of the terminal sessions.