Appdeploy Repackager is not creating the service
Helo Everyone!
Im getting a problem when repacking a software,
the software must create a service that is an updater, but when i create de package e install it, the service dont come up, when i look at the regedit, i see that the appdeploys is not capturing one line, that line is the .exe that get up the service.
i want to know if its possible to create .msi package by snapshoot that capture the "Services" with APPDEPLOY
Thanks
*Sry my poor english.
Im getting a problem when repacking a software,
the software must create a service that is an updater, but when i create de package e install it, the service dont come up, when i look at the regedit, i see that the appdeploys is not capturing one line, that line is the .exe that get up the service.
i want to know if its possible to create .msi package by snapshoot that capture the "Services" with APPDEPLOY
Thanks
*Sry my poor english.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Rvlieburg
11 years ago
You cannot really snapshot services, not even with AdminStudio. In AdminStudio you can define services within the Installation Designer.
This is as far as I know not possible with the AppDeploy-Repackager.
I suggest you use the command-line tool "sc"
e.g. sc create "cbVSCService11" type= own binpath= "C:\Program Files\Cobian Backup 11\cbVSCService11.exe" start= auto displayname= "Cobian Backup 11 Volume Shadow Copy Requester"
Comments:
-
I have just encountered this problem when trying to create an MSI package for the UltraVNC v1.1.8 (Nov 2012).
I do not believe, that registry configuration for a service cannot be captured, as for example with the WinINSTALL LE the MSI package was created without any problem.
On further exploration, it seems that the repackager's MSI did not create the Expandable String Value "ImagePath", which contains the path to the executable for the service - in the case of the UltraVNC it should contain the following data:
"C:\Program Files\UltraVNC\WinVNC.exe" -service
Other registry entries were created correctly, but omission of the ImagePath is (obviously) preventing the service from start. - MartinSt 11 years ago
