We have 50 new HP T310 zero clients running the newest version of the Teradici firmware located in a library. When first deployed about a month ago we were running View 5.1.1 and using location based printing to assign printers. This worked very well. Last week we upgraded our Broker server as well as the agent to version 5.1.2. Occasionally when a student logs into a desktop (Win7 32 bit) a printer is not assigned. Is anyone else experiencing this? Any ideas how to make this rock solid?
One thing I should mention is we are pulling the printer from a Microsoft print server so the driver gets pulled down when the printer is assigned. We do not install the driver into the base image.
We have 10 HP t310 zero clients and I had to disable the two Thinprint services from Win7 64bit virtual machines in order to have a stabile network default printer for a user. Thinprint tries to change the default printer to a local (virtual locals included) printer. Maybe this is not the issue that you are having...
Also, have tried pushing a network printer for VMs through group policy... didn't work as expected. With PCs group policy succeeded installing the driver and the printer was deployed, but with View 5.1.2 VMs it seemed the group policy does not succeed installing the driver. We have now put the drivers of our printers to the base image; don't know however which one of these is enough or are both needed; a) using pnputil -a *.inf b) taking the printers into use including driver installation and then removing those printers from the base image - this gives the drivers to the base image's (win7) Windows Print Management view. It seemed likely that the pnputil -a *.inf for the printer drivers was not enough - that was a surprising result at least with one printer model. With PCs pnputil -a *inf has worked for us ok.
Could you tell a little bit more about how you are using location based printing with these zero clients?
We are using a group policy to push the printers. Of course this is a computer policy so we have to use Group Policy loopback procesing to apply it to the users who are logged in. Below is a screen shot of our setup
There are times when a student logs in when a printer is not assigned. The only "local" printers that are part of the image are a pdf printer so that ends up being the default. We do not have the printer drivers as part of the image but that may be the next step. The printer driver is pulled from the print server down to the image. I am thinking there must be some bug in either View Broker or View Agent version 5.1.2 since all of this worked fine when we were on 5.1.1
Henderson, you just blew my mind....
I never knew you could do remote drivers on this screen.... We just build the HP UPD into our base image...
@Henderson,
Why don't you have IP's in your GPO? Your entire IP Port/ThinPrint Port column is empty.
Do not need them if the printer is being pulled from a print server, all you need is the full path to the print server share hence the entries that start with \\printserv\....
Have any of you successfully test the LBP with user/group?
I've been playing with it all day and it won't work.
If I changed it to (*) instead of an AD user/group, it will work like a charm.
The user/group must not be for an AD user/group entity?
Very interesting.
Thanks for the feedback if you guys have some.
We have the same problem. Did you find any solution?
With View 5.2 there is a bug that affects zero clients and location based printing. Printers do not always map properly when using the name of the client to direct the printer. If you use the Mac address instead, it works fine. We just upgrade to View 5.3, not sure if this bug is still there but we will be testing. This bug was verified by VMWare after I opened a ticket and send them numerous log files
I have successfully deployed LBP with View 5.3 after trial and error with the help of VMware support.
Did you have the same problem as me?
Go ahead open a new thread so we don't hijack this thread since I don't use the MAC address like HendersonD and I'll see if I can help you.
Just to be clear, we have location based printing setup in a large number of areas on campus, about 700 machines on campus get printers pushed to them this way. A repurposed desktop or laptop always gets the proper printer using the name (or wildcard character to cover a lab or library) of the machine. The zero clients get the printer about 95% of the time using name. It was the 5% of the time when a student logged in that they were not getting a printer. They could log off and right back on and the printer appeared. The only way to make the printer map properly to zero clients was to use Mac address instead of name
