Nested MSI(WPS)
Hi All,
I have an MSI that needs to run after another custom action during Execute Deferred.
I've been reading this article on Altiris https://kb.altiris.com/display/1/articleDirect/index.asp?aid=2955&r=2.338809E-02 which suggests calling the MSI druing Execute Immediate. I was a little thrown off by this as best practice articles have always suggested running anything that "changes the system" in Execute Deferred.
Because the custom action the MSI depends on is actually under deferred, I created a custom action "Install MSI from Installation" to run the MSI immediately after the CA it depends on. When I ran this, I got an error 2723 (CA is unsupported type). Why is it an unsupported type?
After reading this http://support.microsoft.com/kb/306439, I went into the CustomAction table and set the value of Type to "7." This seemed to actually run the MSI however I am concerned about when it's actually executing because in the MSI Script view of the install editor, the line where my If statement is disappeared after changing the CA type.
I have an MSI that needs to run after another custom action during Execute Deferred.
I've been reading this article on Altiris https://kb.altiris.com/display/1/articleDirect/index.asp?aid=2955&r=2.338809E-02 which suggests calling the MSI druing Execute Immediate. I was a little thrown off by this as best practice articles have always suggested running anything that "changes the system" in Execute Deferred.
Because the custom action the MSI depends on is actually under deferred, I created a custom action "Install MSI from Installation" to run the MSI immediately after the CA it depends on. When I ran this, I got an error 2723 (CA is unsupported type). Why is it an unsupported type?
After reading this http://support.microsoft.com/kb/306439, I went into the CustomAction table and set the value of Type to "7." This seemed to actually run the MSI however I am concerned about when it's actually executing because in the MSI Script view of the install editor, the line where my If statement is disappeared after changing the CA type.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
turbokitty
15 years ago
There are approximately 47,000 posts on this topic already. Please use "search".
Posted by:
anonymous_9363
15 years ago
Indeed use 'Search' but the point you may miss is that nested MSIs are now, by common consent, considered to be A Bad Thing, owing to potential issues with uninstall, patches and upgrades.
Windows Installer > v4.5 now has the capability built in (install chaining), but upgrading the engine isn't really a job for a package. For now, you should package to the lowest common denominator.
Windows Installer > v4.5 now has the capability built in (install chaining), but upgrading the engine isn't really a job for a package. For now, you should package to the lowest common denominator.
Posted by:
turbokitty
15 years ago
Yup, it's a deprecated feature. This is why you have a deployment tool. It should do the chaining.
And the
So if you're running anything prior to XP SP2, you're out of luck.
Has anyone tried using the 4.5 chainer? It's a neat idea.
And the
Windows Installer 4.5 redistributable can be installed on Windows XP Service Pack 2, Windows XP Service Pack 3, Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2, Windows Vista, Windows Vista Service Pack 1, and Windows Server 2008 in X86, X64 and IA64 flavors.
So if you're running anything prior to XP SP2, you're out of luck.
Has anyone tried using the 4.5 chainer? It's a neat idea.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
