I'm using a "custom shell" in GPO to provide a specific and limited experience (like a kiosk) for users. The OS is hosted as a VM in the datacenter and the user side is handled with a wyse terminal (c10le). Connecting other USB devices, they are passed through without any issue. What is happening is the wyse terminal detects the printer and when RDP connects to the remote workstation, the printer does not get automatically created. Not using the custom shell, (standard explorer.exe) the printer is auto created without issue. I tried manually adding the printer and was able to see the TSXXX por and print to it without issue. The problem is, next time the computer connects, the port changes. I cannot find anything to allow me to auto create the printer for myself with vbscript, javascript or powershell so far. Perhaps there is something that explorer.exe is running when it starts that you don't see and causes the printers to auto map? I have to imagine there is a way to see all of the TSXXX ports and their description to manually create the printer even if I can't get the auto creation process to work. I'm hoping that someone has insight for this process (either way).