Hello

I have created an Office 2013 ProPlus package with Volume Licensing referring the link https://technet.microsoft.com/en-us/library/dn817830.aspx.

Configuration file using for /download and /Packager is as follows:
<Configuration>
 <Add SourcePath="C:\Office 2013 ODT\Office 2013 Download" OfficeClientEdition="32" >
  <Product ID="ProPlusVolume">
   <Language ID="en-us" />
  </Product>
 </Add>
</Configuration>

After installing on Windows 7 x86 machine with App-V 5.0 SP3, the package was installed correctly, however the product was not activated.

Can you please help on the activation part and also if anything was done wrongly.

Regards
Sujit J

Hi Sujit,

Did you install Office in a Domain environment? What kind of Volume Licensing method did you use? KMS or MAK?

If you use KMS to activate your Office, you have to set up KMS host, you can refer to how to set up KMS host.

If you use MAK to activate your Office, you have to specify with PIDKEY in your config file like below:

<Configuration Product="ProPlus">

<PIDKEY Value="ABC12xxxxxxxxxxxxxxx34XYZ" />

<Setting Id="AUTO_ACTIVATE" Value="1" />

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

<Logging Type="verbose" Path="%temp%" Template="Microsoft Office Pro Plus Setup(*).txt" />

</Configuration>

You can refer to this article for more information regarding MAK activation.

From what you have described, I assume you are looking for MAK activation. If I misunderstand anything, please let me know, thank you.

Hi Chloe

Thanks for the answer.

We use KMS method for activating the Office. We have used it for Office 2010 and also for Office 2013 (with the installation done from setup.exe and MSP created by OCT) also. Hence the KMS server and all other things are already setup. We had done the activation from an msi which runs ospp.vbs with the /sethst: and /act

We are now looking to have Office 2013 packaged in the App-V 5.0 format for using it with SCCM2012 hence has created the package using ODT as mentioned earlier.

But after packaging it with ODT, on installation it shows at requires activation.

Regards
Sujit J

We use KMS method for activating the Office. We have used it for Office 2010 and also for Office 2013 (with the installation done from setup.exe and MSP created by OCT) also. Hence the KMS server and all other things are already setup. We had done the activation

Hi Sutij:

Do you mean you are using KMS activation and successfully activate Office client from msi? If so, you might want refer information below.

XML Configuration Files

Next up, you will need to create two XML files, one to suppress the reboot and the other is optional but strongly advised to configure a silent uninstallation.

The first XML file will be named Config.xml and goes into the root folder of your installation source files where setup.exe resides. The contents of config.xml is below:

<Configuration Product="Standard">
< Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
< Setting Id="SETUP_REBOOT" Value="Never" />
< Setting Id="REBOOT" Value="ReallySuppress"/>
< Setting Id="AUTO_ACTIVATE" Value="1" />
< /Configuration>

If using the Professional Plus MSDN media the Configuration Product is ProPlus and if using the Retail media it will be ProPlusr.

The second XML file will be named SilentUninstallConfig.xml and goes into your [Product Code].ww folder in the root of your installation source files. The contents of SilentUninstallConfig.xml is below:

<Configuration Product="Standard">
< Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
< /Configuration>

Again, it goes without saying to update the Configuration Product value accordingly.

Above information is referred from this article.

Let me know the result, thank you.

 

Hello

I have created an Office 2013 ProPlus package with Volume Licensing referring the link https://technet.microsoft.com/en-us/library/dn817830.aspx.

Configuration file using for /download and /Packager is as follows:
<Configuration>
 <Add SourcePath="C:\Office 2013 ODT\Office 2013 Download" OfficeClientEdition="32" >
  <Product ID="ProPlusVolume">
   <Language ID="en-us" />
  </Product>
 </Add>
</Configuration>

After installing on Windows 7 x86 machine with App-V 5.0 SP3, the package was installed correctly, however the product was not activated.

Can you please help on the activation part and also if anything was done wrongly.

Did you perform "/download" and also "/packager" on x64 machine?

Create the Office 2013 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7 and Windows 8 computers.

Did you examine the logfile produced during "/packager" step, and also on the installation target client, for any issues recorded there?

We use KMS method for activating the Office. We have used it for Office 2010 and also for Office 2013 (with the installation done from setup.exe and MSP created by OCT) also. Hence the KMS server and all other things are already setup. We had done the activation

Hi Sutij:

Do you mean you are using KMS activation and successfully activate Office client from msi? If so, you might want refer information below.

XML Configuration Files

Next up, you will need to create two XML files, one to suppress the reboot and the other is optional but strongly advised to configure a silent uninstallation.

The first XML file will be named Config.xml and goes into the root folder of your installation source files where setup.exe resides. The contents of config.xml is below:

<Configuration Product="Standard">
< Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
< Setting Id="SETUP_REBOOT" Value="Never" />
< Setting Id="REBOOT" Value="ReallySuppress"/>
< Setting Id="AUTO_ACTIVATE" Value="1" />
< /Configuration>

If using the Professional Plus MSDN media the Configuration Product is ProPlus and if using the Retail media it will be ProPlusr.

The second XML file will be named SilentUninstallConfig.xml and goes into your [Product Code].ww folder in the root of your installation source files. The contents of SilentUninstallConfig.xml is below:

<Configuration Product="Standard">
< Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
< /Configuration>

Again, it goes without saying to update the Configuration Product value accordingly.

Above information is referred from this article.

Let me know the result, thank you.

 

• Marked as answer by Chloe WangMicrosoft employee, Moderator Tuesday, June 23, 2015 12:52 AM

Hi Sutij:

Did any of above suggestions help? Let me know if you need further assistant, thank you.

Add the following in the config.xml file. This is responsible for the auto activation.

< Setting Id="AUTO_ACTIVATE" Value="1" />