Tranquil IT Forum

Published: **October 6, 2015 - 3:30 PM**

Hello,
I'm looking for a tutorial on creating a WAPT Office 2013 package. I'd like to know the exact steps to follow. I think there are some modifications to make to the setup.py script. There's a template script for making these changes.
Are there any other modifications, like a timeout setting or anything else?
I don't know much about scripting languages.
Any help would be greatly appreciated!
Thanks in advance.
Jonathan

Published: **October 7, 2015 - 3:41 PM**

Hello,

there was a topic on the Wapt mailing list:

"[Wapt] Microsoft Office Package"

here: http://lists.tranquil.it/pipermail/wapt ... hread.html

Simon

Published: **October 21, 2015 - 4:46 PM**

Thanks for the links!
I tried modifying my setup.py file by using a script (originally designed for standard MS-Office 2013) adapted for MS-Office 2013 Professional. I created the wapt package and uploaded it to our private repository. Then, I deployed it to a test computer. The package loads correctly, but during installation (which takes some time), it reports errors and fails to install.

I think I'm missing some elements in my script. Furthermore, I'd like to integrate a VBScript to activate KMS and the license.

Could you provide me with the necessary information (the "errors" or "missing elements") to successfully complete the installation? Thank you.
I'm attaching screenshots.
Best regards,
Jonathan, LPC2E

Published: **October 21, 2015 - 11:47 PM**

Good morning

You are missing the silent.msp repair.xml and uninstall.xml files in your package dev folder.

Create the silent.msp file using the command c:\waptdev\my-msoffice-proplus-wapt\setup.exe /admin

Add well SETUP_REBOOT Never when creating the msp file, as in this link:

http://www.adminarsenal.com/admin-arsen ... installation

The content of the XML files is as follows:

Code: Select all

<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
  <Setting Id="SETUP_REBOOT" Value="NEVER" />
</Configuration>

The product needs to be modified depending on the version

The uninstall strings are not in the correct location; the lines should be present in `def uninstall():` or in an `uninstallstring` with program files variables

The repair is not mandatory

Alternatively, you can use this example package:

http://wapt.lesfourmisduweb.org/wapt/sm ... 0_all.wapt

You will need to slightly modify the package if you wish to use a version other than the 2013 pro plus.

Simon

Published: **October 22, 2015 - 09:01**

Thank you for your quick response. I'll get to work on it.
Thanks again.
Jonathan

Published: **October 23, 2015 - 2:43 PM**

Good morning,

Having followed the steps carefully, I get an error during installation: PackageEntry "packagename" unavailable. And the interface remains frozen on the package installation screen.
I also tried retrieving the file from the link posted above, but I still encounter the same problem.

I would like to point out that I only succeeded in the installation once, by modifying the setup.py file like this:

Code: Select all

# -*- coding: utf-8 -*-
from setuphelpers import *

uninstallkey = []

def install():
    print('installing my-msoffice2013')
    run(r'"silent.msp"')

But afterwards it was impossible to get it working again.

Published: **October 23, 2015 - 6:30 PM**

Are you getting

`PackageEntry "packagename" unavailable`

in PyScripter?

Simon

Published: **October 24, 2015 - 5:47 PM**

Thank you for your quick response.
I'm getting an error on the WAPT console while monitoring the task execution.
I get the message: "installing 'package name'" for a while, without any installation taking place on the client, and then the message: "PackageEntry 'package name' unavailable" appears.

Published: **October 25, 2015 - 1:18 PM**

Could you please send a screenshot of the console as shown in the attached image?

Could you also confirm that the package appears correctly in "private repository"?

Simon

Published: **October 25, 2015 - 1:46 PM**

If it does not appear in the private repository (or at least the correct version), it is surely because there was a problem during the upload.

Indeed, uploading packages to the wapt server can cause problems when the package is of a significant size (which is often the case for Microsoft Office).

For a Linux server:

You can transfer your wapt package (it is located in c:\waptdev\my-msoffice-wapt.wapt if the package has already been built)

You can transfer it using WinSCP to /var/www/wapt

Then do the following:

Code: Select all

chown wapt:www-data /var/www/wapt/my-msoffice-wapt.wapt

Then do this:

Code: Select all

/usr/bin/python /opt/wapt/wapt-scanpackages.py /var/www/wapt

This will regenerate the file http://wapt/wapt/Packages including the packages present in the directory http://wapt/wapt

Under a Wapt Windows server:

You can transfer your wapt package (it is located in c:\waptdev\my-msoffice-wapt.wapt if the package has already been built)

You can transfer it to the server in c:\wapt\waptserver\repository\wapt

Then launch:

Code: Select all

wapt-get update-packages c:\wapt\waptserver\repository\wapt

This will regenerate the file http://wapt/wapt/Packages including the packages present in the directory http://wapt/wapt

Tranquil IT Forum

creating MS-Office 2013 package

creating MS-Office 2013 package

Re: Creating MS-Office 2013 package

Re: Creating MS-Office 2013 package

Re: Creating MS-Office 2013 package

Re: Creating MS-Office 2013 package

Re: Creating MS-Office 2013 package

Re: Creating MS-Office 2013 package

Re: Creating MS-Office 2013 package

Re: Creating MS-Office 2013 package

Re: Creating MS-Office 2013 package