This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Setup /a does not digitally sign msi file
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 22, 2008
09:16 AM
Setup /a does not digitally sign msi file
I am creating a CD-ROM compressed installation with InstallShield 2009 Express. I have digitally signed the exe, dll, setup.exe & msi files. On the cd image these (and the cab file) are all signed correctly.
However if I subequently use "setup.exe /a" for an administrator install to a server folder the setup installs correctly but the msi file on the server is NOT digitally signed (all the exe and dll files are)
Anyone have an idea how I can get the msi on the server to be signed as this is the msi that will be used for all network client installations, many of which are Vista?
John
However if I subequently use "setup.exe /a" for an administrator install to a server folder the setup installs correctly but the msi file on the server is NOT digitally signed (all the exe and dll files are)
Anyone have an idea how I can get the msi on the server to be signed as this is the msi that will be used for all network client installations, many of which are Vista?
John
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 22, 2008
10:24 AM
When you perform an administrative install, the .msi file changes size, therefore, loses digital watermark. I would recommend building an uncompressed release and sign the .msi file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 22, 2008
10:47 AM
Thanks for the suggestion. I have tried building the release uncompressed this but unfortunately it results in the same problem.
The msi is signed in the CD image but not when installed with setup /a. The file sizes of these two msi files are the same to the nearest KB but the timestamps are different.
The msi is signed in the CD image but not when installed with setup /a. The file sizes of these two msi files are the same to the nearest KB but the timestamps are different.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 22, 2008
10:57 AM
I suppose I could just manually copy the uncompressed CD image to the server folder but wouldn't that defeat the idea of an administrative install? I thought the advantage of an administrative install was that it ran with the privileges of the user that ran the setup /a rather than the client user.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 22, 2008
12:31 PM
The latter sounds more like an advertised install which, outside of group policy or other deployment, must be run on each machine. An administrative install is run once and just creates an uncompressed copy of the files that can be more easily accessed e.g. for a network share from which each machine can launch the install (or advertise it).
Going from compressed to uncompressed, the administrative install has to modify the Media table of the MSI; I'm not sure what exactly changes it for the uncompressed to uncompressed case, but it's all behavior of Windows Installer itself.
Going from compressed to uncompressed, the administrative install has to modify the Media table of the MSI; I'm not sure what exactly changes it for the uncompressed to uncompressed case, but it's all behavior of Windows Installer itself.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 23, 2008
02:48 AM
Thanks for everyone's help.
Yes Michael, my aim is to be able to install to network client pcs from the server folder, either through group policy or direct client action but when that client is running Vista I don't want it to receive a message that it is running software from an unknown publisher.
This is not actually a problem within our own organization but we are a software development company and I am currently writing a customer installation guide for our customers and need to detail for them how to achieve a trouble-free installation, or at least flag up any potential problems and document a work around.
I think I understand the setup process better now.
John
Yes Michael, my aim is to be able to install to network client pcs from the server folder, either through group policy or direct client action but when that client is running Vista I don't want it to receive a message that it is running software from an unknown publisher.
This is not actually a problem within our own organization but we are a software development company and I am currently writing a customer installation guide for our customers and need to detail for them how to achieve a trouble-free installation, or at least flag up any potential problems and document a work around.
I think I understand the setup process better now.
John
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 23, 2008
03:32 AM
I just found this Microsoft article that confirms Michael's comment that this is a Windows Installer "feature".
http://msdn.microsoft.com/en-us/library/aa368289(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa368289(VS.85).aspx
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)