|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
July 30th, 2009, 02:09 AM
posted to microsoft.public.office.setup
|
|||
|
|||
Using OCT to create an MSI to automate license information
Hi there,
Is it possible to use the OCT to create an MSI file and put it in the \Update folder, so users just need to run setup.exe and the license information is automated? Thankyou in advance 
|
|
#2
August 1st, 2009, 12:20 AM
posted to microsoft.public.office.setup
|
|||
|
|||
|
Using OCT to create an MSI to automate license information
Yes; of course you're actually referring to .MSP customization file, but that
is exactly right - run Setup /admin and then in the "Licensing and User Interface" section of OCT add the Product Key in the textbox and check the box for "I accept the terms..." and then set the Display Level to Basic. Save the Custom.MSP to the \Updates folder and you're all set. Alternatively, you can use the Config.xml to do the same thing: Display Level="basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" / PIDKEY Value="eebiejeebieyaddahootchiekoo" / Office Customization Tool in the 2007 Office system http://technet.microsoft.com/en-us/l.../cc179097.aspx Config.xml file in the 2007 Office system http://technet.microsoft.com/en-us/l.../cc179195.aspx -- TXGuy [MSFT] "Joey Joe Joe" wrote: Hi there, Is it possible to use the OCT to create an MSI file and put it in the \Update folder, so users just need to run setup.exe and the license information is automated? Thankyou in advance
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
