Service Not getting captured...ideas?
I am doing a recapture of a software called SOFTMAR, using ISRepackager.
The software is a *.MSI in a EXE wrapper (yes, I know its a bad idea to repackage a MSI, but in this specific case I had no choice due to settings that have to be configured by hand BEFORE and AFTER installation).
The MSI I created works fine, EXCEPT that the SOFTMAR Update Agent which is a Windows service does not appear. The update file is installed where it should be, but for some reason my capture is unable to recognize this as a Windows service and thus when the msi is installed, the PC doesnt realize that it is a windows service.
I have even left all "noise" and enabled the "MAP NT SERVICE events to the ServiceControl table" tickbox within ISRepackager.
The update service is works normally using the original MSI, so its not an issue with the source.
The software is a *.MSI in a EXE wrapper (yes, I know its a bad idea to repackage a MSI, but in this specific case I had no choice due to settings that have to be configured by hand BEFORE and AFTER installation).
The MSI I created works fine, EXCEPT that the SOFTMAR Update Agent which is a Windows service does not appear. The update file is installed where it should be, but for some reason my capture is unable to recognize this as a Windows service and thus when the msi is installed, the PC doesnt realize that it is a windows service.
I have even left all "noise" and enabled the "MAP NT SERVICE events to the ServiceControl table" tickbox within ISRepackager.
The update service is works normally using the original MSI, so its not an issue with the source.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
I had no choice due to settings that have to be configured by hand BEFORE and AFTER installationWhat settings? If they're held in a file or files and/or registry (and what else COULD be involved?), they could go in the MSI, surely? If you've re-packaged, then by definition they CAN be included in an MSI, or else how do they end up in your capture?
What you SHOULD do is:
- run the extracted MSI
- use a lightweight snapshot tool to take a 'Before' snapshot
- rename the product's entry in the 'Uninstall' registry branch (to fool the next run that the product isn't installed)
- run the set-up stub
- take an 'After' snapshot
- incorporate any relevant changes in a transform to be applied to the MSI.
Posted by:
spartacus
13 years ago
ORIGINAL: mmarsh
The MSI I created works fine, EXCEPT that the SOFTMAR Update Agent which is a Windows service does not appear.
Just an additional thought, what does the 'SOFTMAR Update Agent' do exactly?
Hopefully it doesnt check for, and download updates to the application itself ? If it does, then generally speaking it is something you would want to disable anyway (in order to keep the target estate consistent as regards version / revision level of the application).
Regards,
Spartacus
Posted by:
mmarsh
13 years ago
Spartacus
Yes it does exactly that, and you are 100% correct its not something we would normally allow. But the user is adamant about it so I am afraid we got overruled.
Yes it does exactly that, and you are 100% correct its not something we would normally allow. But the user is adamant about it so I am afraid we got overruled.
Posted by:
anonymous_9363
13 years ago
Presumably you got him/her to sign a waiver that says you're off the hook when an update hoses the PC?
Posted by:
jmcfadyen
13 years ago
you may find it is an old school proprietary service utilising regkeys.
Have a look in here for a culprit on the capture box.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
Have a look in here for a culprit on the capture box.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.