VMware printing via thinprint

EE, thanks again

My question is in regards to printing via thinprint dll which registers that extra group policy setting. It's like an xml file almost and allows you to specify printers. One problem is that the client requires drivers. So if you have 300+ printers, the client will need every printers driver on the network imaginable at least when doing linked clones with thousands of machines. This is a horrible solution in my opinion.

How does everyone else deploy printers on floating linked clones who float to a new desktop every login? Do you do group policy preferences based on user configuration?

Thanks in advance.
snyderkvAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

joharderCommented:
Unless you have specifically disabled the installation of ThinPrint driver on your VM, it is installed by default.  If you look under the printer drivers (command line: printui /s), you should see the ThinPrint driver there.
snyderkvAuthor Commented:
I'm not sure you're following. I'm not concerned about the thinprint dll. I'm asking for a better way to deploy printers than using that spreadsheet via gpolicy.
snyderkvAuthor Commented:
And by thinprint dll I meant TPVMGPoACmap.dll.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

joharderCommented:
Sorry, misunderstood your question.  

While you can deploy printers via the Printers Group Policy Preference and use the second tab, Item-Level targeting (e.g., choose groups and map those printers in close proximity), the Printers GPP can be problematic.  It will map just fine, but when you need to change or delete printers, sometimes it just doesn't want to let go of them but sometimes it works just fine.  I've spent many hours trying to figure out why, but have finally just accepted that's the way it is.  

So, if you are going to use the Printers GPP, test it with a few VMs first, including changes and deletions.

If it doesn't work for you, the next best option is to use the Registry GPP.  That gets more complex because you have to find and map the specific reg keys to inject the printers.  Let's hope you don't have to go there.
snyderkvAuthor Commented:
So what are you using? Most of the locations I've been in simply used a vbs/batch logon script that mapps printers i.e. \\printserver\share or vbs to a group policy (non preference) Why should this change when deploying desktop? After all, vmware requires that every driver be installed on the machine. If you have 300 printers, each machine will require 300 drivers locally if the network is built from a single linked clone template.
snyderkvAuthor Commented:
Not only that, every time a new printer comes online (like every day) and it requires a new printer driver on the client, you'll have to install it on the base image and recompose all workstations that will use that printer. Unless I'm mistaken.
joharderCommented:
Where you can get away with vendor universal print drivers, that will cut down significantly on the number of drivers you need to install.  The downside is that some vendor universal drivers aren't as universal as you might need.  Typically, they'll get you so far as b/w, color, paper size, and maybe duplex, but for higher-end printers that include collating, stapling, and such, the native drivers will be required.
snyderkvAuthor Commented:
The whole point of VDI was centralizing desktop resources yet here is vmwares backwards evolution solution to mapping printers by requiring hundreds or even thousands of print drivers on every desktop, lame. I guess mapping printers to a network print server is still the best solution

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
snyderkvAuthor Commented:
Archived
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
VMware

From novice to tech pro — start learning today.