Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 232413

Re: Registry Isolation...

$
0
0

MarcBouchard wrote:

 

I created an empty package (no files, no registry keys) to have entry points for the natively installed Office 2010 in order to enable using multiple virtualized plugins using appsync.

 

I deleted the HKEY*.txt files as all I want is for office to act as if natively installed.

 

I added:

[Isolation]

DirectoryIsolationMode=Merged

RegistryIsolationMode=Merged

 

to my package.ini file.

 

I **assumed** that this would basically run any entry point natively (since there is no customization and I merge everything).

 

Setting the isolation mode for directories and registry to "merged" will only authorize the program to write to the native computer.

The following parameters might be what you are looking for:

 

ChildProcessEnvironmentDefault Parameter

 

The ChildProcessEnvironmentDefault parameter determines whether ThinApp runs all child processes in the

 

virtual environment.

 

ThinApp creates all child processes in the virtual environment. If the processes are slow, you might want to

 

move child processes to the physical environment. As a child process, Microsoft Outlook might affect

 

performance when it copies the whole mailbox to the virtual environment.

 

You can create specific exceptions with the ChildProcessEnvironmentExceptions parameter.

 

See “ChildProcessEnvironmentExceptions Parameter,” on page 45.

 

Example: Create Child Processes in the Physical Environment

 

If you do not want the child process to operate in or slow down the virtual environment, you can modify the

 

ChildProcessEnvironmentDefault parameter to create child processes in the physical environment.

 

[BuildOptions]

 

ChildProcessEnvironmentDefault=External

 

ChildProcessEnvironmentExceptions Parameter

 

The ChildProcessEnvironmentExceptions parameter notes exceptions to the

 

ChildProcessEnvironmentDefault parameter when you want to specify child processes.

 

When you set the ChildProcessEnvironmentDefault parameter to Virtual, the

 

ChildProcessEnvironmentExceptions parameter lists the applications that run outside of the virtual

 

environment. When you set the ChildProcessEnvironmentDefault parameter to External, the

 

ChildProcessEnvironmentExceptions parameter lists the applications that run in the virtual environment.

 

Example: Specifying Exceptions to Running Child Processes in the Virtual

 

Environment

 

You can specify exceptions to running child processes in the virtual environment. When the virtual application

 

starts a notepad.exe child process, the child process runs outside the virtual environment.

 

[BuildOptions]

 

ChildProcessEnvironmentExceptions=AcroRd.exe;notepad.exe

 

ChildProcessEnvironmentDefault=Virtual

(from the document thinapp473_packageini_reference.pdf)

 

Common scenarios:

http://blogs.vmware.com/thinapp/2011/01/locally-installed-applications-and-integration-with-virtualized-internet-explorer.html


Viewing all articles
Browse latest Browse all 232413

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>