/build/static/layout/Breadcrumb_cap_w.png

How to find out MSI properties and values?

I'm new to editing MSI files. I'm trying to deploy ScanSoft OmniForm 5.0 through Group Policy. I tried it without modifying the MSI and it did not install, probably because the installer did not have the serial number. How do I specify my serial number in the MSI? I have Orca, but I don't know what to do other than editing values. How do you all learn what properties and values to edit, generally speaking?

0 Comments   [ + ] Show comments

Answers (8)

Posted by: slay_u 14 years ago
Orange Belt
0
I have Orca, but I don't know what to do

you mean to say that your client / organisation has not provided you proper packaging tools and you just use Orca for everything (Its not impossible to do it with Orca, however as someone said that using Orca is like coding the whole MS website using Notepad). I suggest you use Wise Package Studio or Flexera Installshield (or any other decent packaging tool as it will help you out and will save you lotta time).

I'm new to editing MSI files
ona different note, its not a good idea to directly edit the vendor msi, instead you need to create a transform to add your SERIALNUMBER/LICENSEKEY properties into the Property Table.
Posted by: anonymous_9363 14 years ago
Red Belt
0
Pull down a copy of Phil Wilson's ouvre, The Definitive Guide to Windows Installer. That's a good starter.If you search AppDeploy for that title, you'll turn up other posts which contain useful links, such as John McFadyen's Windows Live blog and Ed Tippelt's articles.
Posted by: northben 14 years ago
Yellow Belt
0
Someone recommended WPKG. Is it worth using? We are a small business, and I'm the only IT person. Nearly everything is self-learned, so I appreciate the guidance. I will read the resources you listed and post back with more questions. So should I not attempt to learn or use Orca at all? Thank you both.
Posted by: anonymous_9363 14 years ago
Red Belt
0
I don't know WPKG, other than that it's an open source deployment tool. As such, support will likely be patchy to non-existent. For deployment, you would probably be better off using Group Policy. It's free and well documented, plus there is a dedicated GP forum here on AppDeploy if you have questions on its usage.
Posted by: riversidekid 13 years ago
Senior Yellow Belt
0
We had pushed OmniForms out via GPO, it worked fine until we migrated all our workstations to a new domain and that killed all functionality for OmniForms. I found that it modified the permissions on required registry entries, files and folders. In order to get it working again i have had to delete ALL "OmniForm" entries in the registry and file system before attempting a manual re-install.

The registry entries are not removed when the software is uninstalled, so removing the software for the migration also did not help.

I still have a number of Windows XP computers to 'repair' with this old software. I am still open to alternatives! :)
Posted by: kardock 13 years ago
Second Degree Green Belt
0
wth? why are you replying to a post more than a year old? do you have a question?

if so, create a new post.
Posted by: anonymous_9363 13 years ago
Red Belt
0
it modified the permissions on required registry entries, files and foldersEr...why not simply remove the permissions it had applied and apply new ones? A simple script running SetACL would suffice.
Posted by: riversidekid 13 years ago
Senior Yellow Belt
0
No question, just didn't look at the date. Wanted to offer up my experience in case it helped the original situation. sorry to confuse.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ