Starting and Stopping Virtual Services
When you capture and deploy a package that contains a Windows service, such as the SQL Server service, any user can run the package and start and stop the service. Unlike native applications, virtual applications do not require administrator rights for these operations.
Automatic Startup for Virtual Services
You can install a virtual service as a physical service, so that it starts when the physical machine is started. The virtual service remains in its ThinApp project package, but is registered on the physical machine and controlled using the natively installed service management tools.
After you package your service, for example Apache Server, you register it on the physical machine, using the ThinReg.exe application. The service is created as a native service, using information from the virtual registry. The service is available to all users using the virtual application. The service is not user specific.
The process is composed of the following tasks:
Create a virtual service for automatic startup
The Package.ini file opens in a text editor.
Search for the services entry.
The entry is followed by the name of the service that you captured.
By default, the entry is commented out.
Remove the semicolon (;) from the start of the line.
Save the Package.ini file.
You can now register your virtual service so that it can be managed by using the native services management tools.
Register the virtual service on a machine
Run the ThinReg.exe application.
At the command line, type C:\Program Files\VMware\VMware ThinApp\ThinReg /a *.exe.
You must use /a to register services. If you run ThinApp without this option, the service is not registered.
You can change the path, if required for your system.
From the Start menu, select Programs > Administrative Tools > Services.
Your virtual service application appears in the list of services.
You can manage the service in the same way as any natively installed service.