/build/static/layout/Breadcrumb_cap_w.png

How to create oneNote2010 MSI package

I need to know how to create MSI package for this, where is license key file at?

can I do this way?

c:\msiexec.exe\i "OneNoterww.msi" /quiet.
if I do onenoterww.msi /?, it show me [PROPERTY=ProductyValue]
is this is the product key value? if is, then how can I combined into misexec command.

Thanks

Lillian

0 Comments   [ + ] Show comments

Answers (5)

Posted by: anonymous_9363 12 years ago
Red Belt
0
Isn't OneNote part of the Office family? If so, you'll need to create an MSP for it using the '/admin' argument against SETUP.EXE, in the same way as for the other Office products.
Posted by: llian 12 years ago
Orange Senior Belt
0
I created Note.msp file include the license key,

c:\setup.exe /adminfile note.msp, install just fine, how can I make silence installation?
Thanks

Lillian
Posted by: AngelD 12 years ago
Red Belt
0
My guessing is that OneNote is like Office deployment, configure Config.xml as
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
Posted by: llian 12 years ago
Orange Senior Belt
0
In this config.xml file, do I need add PIDKEY at the end ? like this
<PIDKEY Value="xxxxxxxxxxxxxxxxxxxxxxx"/>

Thanks

Lillian
Posted by: anonymous_9363 12 years ago
Red Belt
0
There is a sample XML file alongside SETUP.EXE which contains all the various configuration options, all with explanatory comments. There is more extensive documentation on MSDN but I think you're right that it's the PIDKEY attribute you need to populate.
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