Remoted Desktop with HP Officeject 8600 redirected does not work

Hello, I have a remote user that uses an application on an office PC. The remote user has a VPN connection and uses Remote Desktop to work on the system and wants to print to their local printer (redirected printer) which is an HP OfficeJet 8600.

It will not print.  We do not have an Officejet 8600 locally.

I have downloaded the drivers to the office system and performed the install up to connect later and finished the install.  I believe the driver is in the system reviewing it through printui /s /t2

Anyone have any ideas of how to resovle this issue of redirecting printers?

The users says it use to work at one time but we had other printer problems so I had to remove all drivers from the system, clear corrupt spooler files and reloaded all exisiting printers.
tucktechAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dirk KotteSECommented:
try to force the universal Printer Driver or substitute the Driver with a standard-Driver.
Somewhere is a file with a Printer-Driver-replacement-list for RDP.

Some Printers are not usable with Terminalservers. Installing and using many Drivers mostly reduce the stability of the System.
0
tucktechAuthor Commented:
I ended up downloading the driver, running it so the program would extract the drivers and I used printui /s /t2 to add the drivers.  Once I did this it worked.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tucktechAuthor Commented:
The driver needed to be loaded locally on the remote system, once I did this it worked.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.