• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1029
  • Last Modified:

App-V 5.0 - Trying to make a virtual printer installed locally - Communicate with a virtual application

I am attempting to use APP-V (ThinAPP is available to me as well.) To virtualize Hyland's Unity Client, to connect to Onbase (ECM tool).

The application installs a virtual printer - that outputs images that are automatically picked up by the application, and an Upload window appears.

I realize that Printer cannot be virtualized, so I have it being installed via GPO at machine creation (We're running Non-persistent desktops in Vmware View 5.3).

So what I am looking for - is any ideas on how to make the Virtual Application's Virtual Printer listener (provided via a .DLL) either listen to a non virtualized folder - or to get it to listen to a folder internal to the application, being that I can modify the spooling Folder.

So far it appears that the spooling works correctly, but the application seems to be unaware of it, whereas in a local physical install, it works great.

Happy to clarify.
0
PemcoIT
Asked:
PemcoIT
  • 3
  • 2
1 Solution
 
Squidly_ManCommented:
With ThinApp, you can define a folder within a virtualized app to use what is called MERGED isolation. Doing so would allow the virtualized app to write out the native drive on the same path.

For a good explanation of ThinApp isolation modes, see Peter Björk's blog / KB posting on the topic.

http://blogs.vmware.com/kb/2011/04/understanding-isolation-modes-in-vmware-thinapp.html
0
 
PemcoITAuthor Commented:
Thanks - I am aware of the Isolation modes within ThinAPP, although this particular App hasn't been very easy to virtualize in ThinAPP - Whereas APPV has been much more accomodating. I'll try again in thinAPP, and see if I can get it working.
0
 
PemcoITAuthor Commented:
It ended up being related to the COM objects being able to communicate. Once I enabled that, it picked it up no problem.
0
 
Squidly_ManCommented:
Ahh, yes.  With ThinApp that is done by using the VirtualizeExternalOutOfProcessCOM=0 setting in the PACKAGE.INI file.

For anyone else reading this after the fact, see the ThinApp Package.INI Reference Guide for more information.
0
 
PemcoITAuthor Commented:
Ended up being COM objects - Which I eventually figured out.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now