Defining Entry Points as Shortcuts into the Virtual Environment

Entry points are the executable files that act as shortcuts into the virtual environment and start the virtual application.

The entry points you can choose from depend on the executable files that your captured application creates during installation.

For example, if you install Microsoft Office, you can select entry points for Microsoft Word, Microsoft Excel, and other applications that are installed during a Microsoft Office installation. If you install Firefox, you might selectMozillaFirefox.exe and MozillaFireFox (SafeMode).exe if users required safe mode access.

During the build process that occurs at the end of the Setup Capture wizard, Omnissa ThinApp generates one executable file for each selected entry point. If you deploy the application as an MSI file or use thethinreg.exe utility, the desktop and Start menu shortcuts created on user desktops point to these entry points.

Entry Points for Troubleshooting

ThinApp provides entry points to troubleshoot your environment.

Debugging an application might involve the following entry points:

• cmd.exe Starts a command prompt in a virtual context that enables you to view the virtual file system.
• regedit.exe Starts the registry editor in a virtual context that enables you to view the virtual registry.
• iexplore.exe Starts iexplore.exe in a virtual context that enables you to test virtualized ActiveX controls.

Entry points start native executable files in a virtual context. Entry points do not create virtual packages of cmd.exe, regedit.exe, or iexplore.exe.

If you cannot predict the need for debugging or troubleshooting the environment, you can use the Disabled parameter in the Package.ini file at a later time to activate these entry points.