AWS Workspace failed to map local printer

I try the following when the Teradici virtual printer driver on a WorkSpace is not seeing a printer on the local machine.

Disconnect from the WorkSpace and reconnect.

If still not seeing the printer restart the WorkSpace and reconnect.

If still not seeing the printer restart the local machine and reconnect to the WorkSpace.

Doing that has solved it for me. Also if the printer is a shared printer from someone else's local PC or a print server try to connect your local machine to it directly instead (either USB or wired/wireless network).

Edited by: mglennjp on Jan 7, 2018 8:41 PM

Can you provide a bit more information about your problem and diagnosis?
One of the first steps in analysing a problem is to compare the failing case (yours) to the working case (your colleague) and see what is different between the two, looking at the differences one by one to determine the problem.

One big difference is the local PC. Not just the OS, but the whole PC is different--you have yours and your colleague has his. Is the locally attached printer the same, or is it a different model between the two? Can you confirm that your locally attached printer works? It's not clear from your posting how your PC differs from your colleague's so forgive the questions if they seem rather basic.

As an experiment, try connecting to your AWS Workspace (you'll need to switch profiles in the AWS client) from your colleague's PC machine. Once you connect, see if your colleague's local printer shows up. If it does, that means the problem is with the configuration on your PC (and not your AWS Workspace).
If it does not, that implies it's a problem with your AWS Workspace

Likewise, ask your colleague to connect to his AWS Workspace from your PC. See if he can access the local printer. If he can't, it means there's a problem with your local PC. If he can, it means there's a problem with your AWS Workspace.

We need to perform the above to narrow down the problem. Statistically speaking, the problem is most likely with your local PC configuration, but we need to methodically test each possibility to narrow down the issue.

Hi

Thanks for your reply.

I have attempted to use my account logging into two local PCs, which my account is able to map local printers on both local PCs for sure, but my colleague's account not.

So I don't think it is necessary to give more detail of what differs are between local PCs.

To best describe the issue, I would still say: AWS workspace failed to map local printers.

Some discussion re this issue suggests to change Group Policy in Domain controller, as the issue could be caused by "Administration Control". However, I have attempted to make the change on Group Policy, but it won't make any changes for this issue. I did check local Group Policy list, which I'm not able to find any features/settings that would change printer mapping function at all.

Happy to accept any suggestions from you further.

BTW, I don't think local printer with cable connection or network connection would cause this issue in this scenario anyway.

Cheers,
James

Edited by: RichFieldTechnology on Jan 17, 2018 9:12 PM

Edited by: RichFieldTechnology on Jan 17, 2018 9:13 PM

RichFieldTechnology wrote:
Hi

Thanks for your reply.

I have attempted to use my account logging into two local PCs, which my account is able to map local printers on both local PCs for sure, but my colleague's account not.

Sorry, I didn't really understand your description. When you say "my account", do you mean your Windows account, or do you mean you logged onto your AWS workspaces account from two different PCs? Previously you mentioned your colleague's account worked, but now you mention that it doesn't.

So I don't think it is necessary to give more detail of what differs are between local PCs.

To best describe the issue, I would still say: AWS workspace failed to map local printers.
I didn't really understand from your description how you arrived at this conclusion, but okay, we'll assume that the problem is not on your local PC

Some discussion re this issue suggests to change Group Policy in Domain controller, as the issue could be caused by "Administration Control". However, I have attempted to make the change on Group Policy, but it won't make any changes for this issue. I did check local Group Policy list, which I'm not able to find any features/settings that would change printer mapping function at all.

Happy to accept any suggestions from you further.

Yes, looking into the GPO settings is a good place to start.
You will not see the PCoIP options via gpedit.msc until you load the PCoIP configuration file.
On your workspace, run gpedit.msc and from the administrative template add the template in C:\Program Files (x86)\Teradici\PCoIP Agent\configuration\pcoip.adm

See {message:id=701842} for the general idea.

If you just want to view the settings, you can of course just use gpresult or rsop
https://deployhappiness.com/gpresult-or-rsop/

BTW, I don't think local printer with cable connection or network connection would cause this issue in this scenario anyway.

Well, if the printer was not showing up locally on the PC, then it wouldn't show up on the AWS Workspace, so I was just trying to make sure that that was not the case.

Hi,

Thanks for the reply again.

After looked at more places in the system for further troubleshooting, and I say straightly, the answer is "Teradici PCoIP Printing Service" which is disabled in services list. This is the reason to cause printers from local PC that cannot map into AWS workspace, or AWS workspace cannot find printers from local PC.

The solution is:

Right Click-on Windows Button, go to "Run" --> "Service.msc", find "Teradici PCoIP Printing Service", right click-on "Properties", ensure the Startup Type is "Automatic", and click on "start" button to run the service.

Thanks,
James

Edited by: RichFieldTechnology on Jan 24, 2018 4:47 PM

Yes, that would explain it. Very odd that the service was in that state since when it is installed its service is configured to start automatically.
Oh well, as long as it's working for you now, that's all that matters.