Thinprint - printer redirection

[wdj01]

Not sure if this one is even possible...

Within a view session, we are wanting to launch another view session, which is not ideal, although due to some internal policies this seems to be the way we are forced to go. Connection is fine, however in terms of printing, we do not seem to be able to get ThinPrint on the second view session.

The printer actually pulls through from the base desktop and ThinPrint is fine on the first view session, though when we launch another view session within our first view session, (although the printers are showing and ThinPrint is setup) we are unable to print.

[elgwhoppo]

You always have location based printing that you can use on the second level desktops, you just have to install the print drivers on the base and configure with GPO. Then just disable the automatic thinprint redirect. Not optimal, but workable. Did you try switching the protocol to RDP on the second level desktops?

On another real-world note, I'd be concerned for the supportability of your solution if you decide to go this route. Can you talk more about the policies that are driving you this way? There may be more ways to accomplish your goals than the one you've listed to address this.

[wdj01]

Thanks for that! Some progress as we managed to get some prints off! Using RDP on the second level and added a number of network printers on the base machine, which do appear on the last desktop and we can print.

The reason we are going down this route is we are being forced by internal policies to make the second view session (to third party network), from within an internal pool, although I agree that this could be a headache in terms of support, especially when a end user calls with a problem with "View" and trying to establish which pool they are having the issue in!

That is the plan for the moment although there are ongoing discussions to see about just accessing the view client from within the base desktop and not in the view session...

[elgwhoppo]

Does the third party network have public access to their View environment? Has anyone answered the question, "Why can't we just connect straight to their view environment from an onsite location? Why does it have to be View in View?"

I'm sure already that you see the manageability problem with supporting nested View sessions.

Just my 2 cents, I'd push back on what's driving this requirement. If the security requirements are legit and this truly is the only way they want you to get in, it should work for you, but it's definitely not the best way to do it.