it_medcomp
asked on
Server 2016 default printers issue in RDS
I am running a 2016 RDS, deploying IBM Client Access Solutions, for the console application. We use remoteapp to deploy this as an RDP shortcut, but that is most likely irrelevant, because I can duplicate the problem logged in as an Administrator to a full desktop session. When I use the program, I can go into Printer Setup on the File menu, and it lists printers. I want it to print to my Windows Default printer on the client computer. I currently have a small number of GPO's set, but I don't think the issue lies there, because I don't have the problem on a 2012R2 server setup identically in the same OU.I think the issue is the software looking at the wrong registry key... but IBM doesn't seem to be that concerned with my opinion on how they design core products... so I'm going to assume I cannot solve it like that. The next option would be to write a script on the RDS that duplicates the correct registry into the legacy location key and runs at login. In case it makes a difference, the printer that the IBM software sees is either the XPS printer or the Microsoft Print to PDF printer. We have this problem on Windows 10 x64 and Windows 7 x64 clients- there was never a deployment of any OS's at our firm in between. Since the problem appears to be the IBM software, I am working on an upgrade, but it will take time to set it up and test it properly. I tried the script approach but it did not work- Here's the script I attempted to use:
I have worked in PS before, but not with the registry, so I have no idea how to approach this.... Any ideas?
Thanks!
$key = 'HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\SessionDefaultDevices'
$keyproperty = Get-ChildItem -path $key | Select-Object Name
$keyenv = $keyproperty.Name
Copy-ItemProperty -path Registry::$keyenv -destination 'HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\' -Name Device
I have worked in PS before, but not with the registry, so I have no idea how to approach this.... Any ideas?
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Vendor accepted fault on this one!
Then log on to the RD environment and the default printer should be set correctly.
No manipulation of anything beyond the above should ever be needed.
Occasionally, one needs to clean out the user's PrinterPorts registry key as some legacy Win32 apps start choking when there's more than 15 to 20 TS Session Printers listed there.