/build/static/layout/Breadcrumb_cap_w.png

How to create Visio2003 standard MSI

I have Visio2003 standard CD, and I found the VISSTD.MSI file in the root of CD, I copy the setup.ini file from D:\files\setup folder, and I modify the ini file as following:

MSI=VISSTD.MSI
USERNAME:Customer
COMPANAYNAME= my company
INSTALLLOCATION:=C:\Program Files\MyApps
PIDKEY="XXXXXXXXXXXXXXXXXXXXXXXXX"

So the command I have is
msiexec.exe /i visstd.msi
but it keep ask me my production code:
where I can specify the productioncode?
I even put into
[Product]
ProductCode={XXXXX-XXXXX-XXXXX-XXXXX-XXXXX}
ProductName=Microsoft Office Visio Standard 2003
ProductVersion=11.0.3216.5614
Recache=1

but still not work, need help

Thanks.

Lillian

0 Comments   [ + ] Show comments

Answers (4)

Posted by: darkfang 14 years ago
Blue Belt
0
Why don't you use the .msi alone instead of the setup.exe ?

msiexec /i visstd.msi PIDKEY=ProductionCodeWithoutDash
Posted by: cygan 14 years ago
Fifth Degree Brown Belt
0
to make things easy for you

you will need to create an admin install running setup.exe this will then ask for the serial key

then you can customize and create mst with ork
Posted by: llian 14 years ago
Orange Senior Belt
0
I use this command, it work, but how you specify quiet mode, I use /qb! but not working

msiexec /i visstd.msi PIDKEY=XXXXXXXXXXXXXXXXXXXX /qb!

need help

Thanks.

Lillian
Posted by: anonymous_9363 14 years ago
Red Belt
0
It depends on what you mean by 'quiet'. The switch you have, '/QB!' means "Basic interface, with no 'Cancel' button". For a completely "silent" install, i.e., with no UI at all, you need to use '/QN'.
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