Repackaging ProSeries 2007
I'm trying to re-package and deploy Intuit's ProSeries 2007 (single client mode, as opposed to network installation mode), and I'm having one motherB of a time getting it done. I'm using AdminStudio Zenworks Edition on an XP VM.
I've tried many approaches - Installation Monitoring, Single-step Snapshot, Multiple-step Snapshot and even a response file - none of these work. I've tried rebooting in the middle of the installation - still not working. I get varying degrees of "not working" with the different methods, but the bottom line is that I have so far been unable to push it out.
Can someone please point me in the right direction?
I've tried many approaches - Installation Monitoring, Single-step Snapshot, Multiple-step Snapshot and even a response file - none of these work. I've tried rebooting in the middle of the installation - still not working. I get varying degrees of "not working" with the different methods, but the bottom line is that I have so far been unable to push it out.
Can someone please point me in the right direction?
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
Is it the deployment which isn't working, or the app once deployed?
Also, have you seen http://www.appdeploy.com/packages/detail.asp?id=1236 ?
Also, have you seen http://www.appdeploy.com/packages/detail.asp?id=1236 ?
Posted by:
Jeemo
16 years ago
Hi Scab,
Thank you for your reply. The problem is with the repackaging process, and consequently the application once deployed. And yes, I have seen the installation note that you linked. It was because of that link that I tried to reboot between the installation and the initialization/configuration, which has been at least a little helpful.
The main functionality that I have not been able to get to work is product activation/licensing. Sometimes when I do a build, both the licensing mechanism and the product update component will report that they cannot connect to the internet. The only way I can alleviate that particular problem is to do another build "as-is" after the snapshot process, but that pushes a bunch of extraneous crap along with it. When disabling reg keys and folders that I'm almost 100% sure are useless, that's when I get the connectivity problem. I took a stab at trying to narrow down exactly what is responsible for the connectivity issue, but have been unable to identify it thus far. Even when connectivity is not an issue, I still cannot programmatically run the Entitlement Client with success.
There are a couple other noteworthy things to mention:
- When trying to utilize the Installation Monitoring tool of AdminStudio for this app, it prompts me to use InstallShield Professional Logging since the ProSeries installer as provided by Intuit was detected as being originally packaged by AdminStudio (although not packaged into an MSI). For this app (and every other one for which I've gotten the same prompt), at the end of the scanning process AdminStudio throws an error. Has anyone else had this problem?
- When I've tried to build an MSI from the two-step snapshot, AdminStudio stops the build process because it said there was an error (and a couple warnings) in the compile process. It still generates an MSI though, and that MSI seems to work just fine (with the exception of the problems mentioned above). Weird stuff.
This is the only app that I've had this much trouble with. I really hope someone can help (or that I stumble upon the solution myself)!
Thanks,
Gavin
Thank you for your reply. The problem is with the repackaging process, and consequently the application once deployed. And yes, I have seen the installation note that you linked. It was because of that link that I tried to reboot between the installation and the initialization/configuration, which has been at least a little helpful.
The main functionality that I have not been able to get to work is product activation/licensing. Sometimes when I do a build, both the licensing mechanism and the product update component will report that they cannot connect to the internet. The only way I can alleviate that particular problem is to do another build "as-is" after the snapshot process, but that pushes a bunch of extraneous crap along with it. When disabling reg keys and folders that I'm almost 100% sure are useless, that's when I get the connectivity problem. I took a stab at trying to narrow down exactly what is responsible for the connectivity issue, but have been unable to identify it thus far. Even when connectivity is not an issue, I still cannot programmatically run the Entitlement Client with success.
There are a couple other noteworthy things to mention:
- When trying to utilize the Installation Monitoring tool of AdminStudio for this app, it prompts me to use InstallShield Professional Logging since the ProSeries installer as provided by Intuit was detected as being originally packaged by AdminStudio (although not packaged into an MSI). For this app (and every other one for which I've gotten the same prompt), at the end of the scanning process AdminStudio throws an error. Has anyone else had this problem?
- When I've tried to build an MSI from the two-step snapshot, AdminStudio stops the build process because it said there was an error (and a couple warnings) in the compile process. It still generates an MSI though, and that MSI seems to work just fine (with the exception of the problems mentioned above). Weird stuff.
This is the only app that I've had this much trouble with. I really hope someone can help (or that I stumble upon the solution myself)!
Thanks,
Gavin
Posted by:
anonymous_9363
16 years ago
ORIGINAL: JeemoI discovered that an app would failt to run (with a NASTY error dialog full of gibberish) if the original InstallShield 'UninstallString' key was missing from the registry, so stuff that you would routinely delete may turn out to be required by this particular app. To bang my particular gong yet again, this is where ProcMon is your friend. It will show you exactly what file & registry access is going on. You need to filter out some of the crud, sure, but that'll be obvious after the first few times of use.
When disabling reg keys and folders that I'm almost 100% sure are useless, that's when I get the connectivity problem.
I can't help you with the AdminStudio stuff, I'm afraid. I'm getting a bit rusty with that.
Posted by:
Jeemo
16 years ago
Hi Scab,
Thanks again for your reply. I have started to familiarize myself with ProcMon, but I was wondering if you might be able to rattle off a list of what you consider to be obvious crud exclusions. I have a few of my own so far, but I'm hoping you might be able to save me a couple hours of trial and error, unless you feel that doing so would deprive me of valuable learning experience. [;)]
Thank you in advance,
Gavin
Thanks again for your reply. I have started to familiarize myself with ProcMon, but I was wondering if you might be able to rattle off a list of what you consider to be obvious crud exclusions. I have a few of my own so far, but I'm hoping you might be able to save me a couple hours of trial and error, unless you feel that doing so would deprive me of valuable learning experience. [;)]
Thank you in advance,
Gavin
Posted by:
anonymous_9363
16 years ago
Forgive me, fellow members, but this is by far and away the easiest route:
Paste that into a .REG and import it.
If that should fail, the list I use is:
Process names:
VMWareService.exe
VMWareUser.exe
Explorer.exe
csrss.exe
svchost.exe
lsass.exe
rtvscan.exe (our a/v process)
services.exe
winlogon.exe
imapi.exe
userinit.exe
dwwin.exe (Dr Watson)
procmon.exe
System
Path begins with:
IRP_MJ_
FASTIO_
Path ends with
pagefile.sys
$Mft
$MftMirr
$Logfile
$Volume
$AttrDef
$Root
$Bitmap
$Boot
$BadClus
$Secure
$UpCase
$Extend
REGEDIT4
[HKEY_CURRENT_USER\Software\Sysinternals\Process Monitor]
"FilterRules"=hex:01,1e,00,00,00,75,9c,00,00,00,00,00,00,00,24,00,00,00,56,00,\
4d,00,77,00,61,00,72,00,65,00,53,00,65,00,72,00,76,00,69,00,63,00,65,00,2e,\
00,65,00,78,00,65,00,00,00,00,00,00,00,00,00,00,00,75,9c,00,00,00,00,00,00,\
00,1e,00,00,00,56,00,4d,00,77,00,61,00,72,00,65,00,55,00,73,00,65,00,72,00,\
2e,00,65,00,78,00,65,00,00,00,00,00,00,00,00,00,00,00,75,9c,00,00,00,00,00,\
00,00,1a,00,00,00,45,00,78,00,70,00,6c,00,6f,00,72,00,65,00,72,00,2e,00,45,\
00,58,00,45,00,00,00,00,00,00,00,00,00,00,00,75,9c,00,00,00,00,00,00,00,14,\
00,00,00,63,00,73,00,72,00,73,00,73,00,2e,00,65,00,78,00,65,00,00,00,00,00,\
00,00,00,00,00,00,75,9c,00,00,00,00,00,00,00,18,00,00,00,73,00,76,00,63,00,\
68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,00,00,00,00,00,00,00,00,00,\
00,75,9c,00,00,00,00,00,00,00,14,00,00,00,6c,00,73,00,61,00,73,00,73,00,2e,\
00,65,00,78,00,65,00,00,00,00,00,00,00,00,00,00,00,75,9c,00,00,00,00,00,00,\
00,18,00,00,00,52,00,74,00,76,00,73,00,63,00,61,00,6e,00,2e,00,65,00,78,00,\
65,00,00,00,00,00,00,00,00,00,00,00,75,9c,00,00,00,00,00,00,00,1a,00,00,00,\
73,00,65,00,72,00,76,00,69,00,63,00,65,00,73,00,2e,00,65,00,78,00,65,00,00,\
00,00,00,00,00,00,00,00,00,75,9c,00,00,00,00,00,00,00,1a,00,00,00,77,00,69,\
00,6e,00,6c,00,6f,00,67,00,6f,00,6e,00,2e,00,65,00,78,00,65,00,00,00,00,00,\
00,00,00,00,00,00,75,9c,00,00,00,00,00,00,00,14,00,00,00,69,00,6d,00,61,00,\
70,00,69,00,2e,00,65,00,78,00,65,00,00,00,00,00,00,00,00,00,00,00,75,9c,00,\
00,00,00,00,00,00,1a,00,00,00,75,00,73,00,65,00,72,00,69,00,6e,00,69,00,74,\
00,2e,00,65,00,78,00,65,00,00,00,00,00,00,00,00,00,00,00,75,9c,00,00,00,00,\
00,00,00,14,00,00,00,64,00,77,00,77,00,69,00,6e,00,2e,00,65,00,78,00,65,00,\
00,00,00,00,00,00,00,00,00,00,75,9c,00,00,00,00,00,00,00,18,00,00,00,50,00,\
44,00,45,00,78,00,70,00,6c,00,6f,00,2e,00,65,00,78,00,65,00,00,00,00,00,00,\
00,00,00,00,00,75,9c,00,00,00,00,00,00,00,18,00,00,00,50,00,72,00,6f,00,63,\
00,6d,00,6f,00,6e,00,2e,00,65,00,78,00,65,00,00,00,00,00,00,00,00,00,00,00,\
75,9c,00,00,00,00,00,00,00,0e,00,00,00,53,00,79,00,73,00,74,00,65,00,6d,00,\
00,00,00,00,00,00,00,00,00,00,77,9c,00,00,04,00,00,00,00,10,00,00,00,49,00,\
52,00,50,00,5f,00,4d,00,4a,00,5f,00,00,00,00,00,00,00,00,00,00,00,77,9c,00,\
00,04,00,00,00,00,10,00,00,00,46,00,41,00,53,00,54,00,49,00,4f,00,5f,00,00,\
00,00,00,00,00,00,00,00,00,87,9c,00,00,05,00,00,00,00,1a,00,00,00,70,00,61,\
00,67,00,65,00,66,00,69,00,6c,00,65,00,2e,00,73,00,79,00,73,00,00,00,00,00,\
00,00,00,00,00,00,87,9c,00,00,05,00,00,00,00,0a,00,00,00,24,00,4d,00,66,00,\
74,00,00,00,00,00,00,00,00,00,00,00,87,9c,00,00,05,00,00,00,00,12,00,00,00,\
24,00,4d,00,66,00,74,00,4d,00,69,00,72,00,72,00,00,00,00,00,00,00,00,00,00,\
00,87,9c,00,00,05,00,00,00,00,12,00,00,00,24,00,4c,00,6f,00,67,00,46,00,69,\
00,6c,00,65,00,00,00,00,00,00,00,00,00,00,00,87,9c,00,00,05,00,00,00,00,10,\
00,00,00,24,00,56,00,6f,00,6c,00,75,00,6d,00,65,00,00,00,00,00,00,00,00,00,\
00,00,87,9c,00,00,05,00,00,00,00,12,00,00,00,24,00,41,00,74,00,74,00,72,00,\
44,00,65,00,66,00,00,00,00,00,00,00,00,00,00,00,87,9c,00,00,05,00,00,00,00,\
0c,00,00,00,24,00,52,00,6f,00,6f,00,74,00,00,00,00,00,00,00,00,00,00,00,87,\
9c,00,00,05,00,00,00,00,10,00,00,00,24,00,42,00,69,00,74,00,6d,00,61,00,70,\
00,00,00,00,00,00,00,00,00,00,00,87,9c,00,00,05,00,00,00,00,0c,00,00,00,24,\
00,42,00,6f,00,6f,00,74,00,00,00,00,00,00,00,00,00,00,00,87,9c,00,00,05,00,\
00,00,00,12,00,00,00,24,00,42,00,61,00,64,00,43,00,6c,00,75,00,73,00,00,00,\
00,00,00,00,00,00,00,00,87,9c,00,00,05,00,00,00,00,10,00,00,00,24,00,53,00,\
65,00,63,00,75,00,72,00,65,00,00,00,00,00,00,00,00,00,00,00,87,9c,00,00,05,\
00,00,00,00,10,00,00,00,24,00,55,00,70,00,43,00,61,00,73,00,65,00,00,00,00,\
00,00,00,00,00,00,00,87,9c,00,00,06,00,00,00,00,10,00,00,00,24,00,45,00,78,\
00,74,00,65,00,6e,00,64,00,00,00,00,00,00,00,00,00,00,00
"FilterDialog"=hex:2c,00,00,00,00,00,00,00,01,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,\
ff,ff,ff,ff,ff,ff,ff,ff,32,00,00,00,1a,00,00,00,3d,04,00,00,ce,02,00,00
"FilterControlColumns"=hex:64,00,00,00,64,00,00,00,64,00,00,00,64,00,00,00,00,\
00,00,00,01,00,00,00,02,00,00,00,03,00,00,00
Paste that into a .REG and import it.
If that should fail, the list I use is:
Process names:
VMWareService.exe
VMWareUser.exe
Explorer.exe
csrss.exe
svchost.exe
lsass.exe
rtvscan.exe (our a/v process)
services.exe
winlogon.exe
imapi.exe
userinit.exe
dwwin.exe (Dr Watson)
procmon.exe
System
Path begins with:
IRP_MJ_
FASTIO_
Path ends with
pagefile.sys
$Mft
$MftMirr
$Logfile
$Volume
$AttrDef
$Root
$Bitmap
$Boot
$BadClus
$Secure
$UpCase
$Extend
Posted by:
Jeemo
16 years ago
All is forgiven! Thank you very much, I will give this a shot and see what happens.
Gavin
Gavin
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.