ThinApp VMware vCenter Server Myth or A Reality?
August 10, 2010 
Sean Crookston 
Why ThinApp VMware vCenter? Because it’s cool.
In reality though the question itself is not specific to this application and the thinking process of the possibilities of being to virtualize applications like this is more important. The future of application virtualization could allow for much further consolidation and as we approach the limits of consolidation with server virtualization, application virtualization could further allow us to consolidate the number of virtual servers we run but placing applications that can’t run together on the same server, together on the same server.
Recently a coworker of my mentioned that he had heard that someone had created a ThinApp package for vCenter Server. Looking quickly at the limitations of ThinApp and knowing that it is possible to Thinapp Microsoft’s SQL Express and personally creating ThinApp packages for several applications that had running services, I see no real reason why it would not be.
I attempted a few things with this package including breaking out the SQL application. I then created an odbc connection manually and connected to the external SQL server. Additionally I thought it best to change the service accounts to run a domain accounts so no matter what machine the application was run on the accounts would exist with the same password for starting up to limit any troubleshooting.
I’m able to get the web services of vCenter to start but the vCenter service itself does not. One idea I had that I will try in the near future is creating an entry point to the services so that I can start them manually. I am still not sure of the best way of doing this so I am open to ideas from anyone who may have one.
To date this is the best resource I could find on these services. http://blogs.vmware.com/thinapp/2009/07/thinapp-services.html
Is it really possible to ThinApp VMware’s own vCenter? I would say yes, even though part of how to do it has not quite been figured out yet.
Tags: 
There are 2 simple ways to start the service manager inside the virtual environment:
1) Enable the cmd.exe entry point, build the package, launch the virtual cmd.exe and at the prompt type “services.msc”
2) Create an entry point for the service manager:
[service_manager.exe]
Shortcut=
Source=%SystemSystem%\services.msc
Thanks for taking the time to reply. That is a very easy possible solution to my issues and I will let you know how I make out.
An additional question for you. I misread the first part of your message and I have in fact tried the first method you mentioned above by running services.msc under the virtual cmd.exe context.
My assumption is there is not any difference between doing this and creating an entry point for services.msc, but is that correct?
Yes, that’s correct.