Hello,
I'm a new WAPT user and I'm having some trouble creating an Office Standard 2016 package.
I've scoured all the forums that dealt with the subject and none of the proposed methods have been successful.
The procedure I tried to follow is: http://reseaux85.fr/index.php?title=Dep ... oft_Office
Is there anyone here who has a more detailed method for creating this package? (I feel like there are missing steps or I haven't understood everything...)
So far, here's my process:
- creation of my .MSP file (named "config.msp" which I place in the root of the Office installation folder)
- creation of the template (using the command `wapt-get make-template`)
- copying the "Office" folder into the newly created project folder
- editing and modifying the .py file (this might be where my mistake is)
- retrieving the .xml file (from "standard.ww" and cutting/pasting it into the project root, renaming it "silent.xml")
- modifying the .xml file (probably another point of error, but I'm not sure)
- Creating the package (using the `build-package` command).
If anyone has the configuration files to modify/create and the paths to place them, I'd appreciate it...
Thank you in advance for your help.
[SOLVED] Creating Office Standard 2016 package
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
Last edited by admgautier on 21 Nov 2018 - 09:51, edited 1 time.
- dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Admgautier,
https://store.wapt.fr/package_details?p ... D_all.wapt
Sincerely,
Denis
Have you looked at the "skeleton" msoffice package on store.wapt.fr?admgautier wrote: ↑24 Sep 2018 - 17:28 As a new WAPT user, I'm having some trouble creating an Office Standard 2016 package.
I've scoured all the forums that dealt with the subject and none of the proposed methods have been conclusive.
The procedure I tried to follow is: http://reseaux85.fr/index.php?title=Dep ... oft_Office
Is there anyone here who has a more detailed method for creating this package? (I feel like there are missing steps or I haven't understood everything...)
So far, here's my process:
- creation of my .MSP file (named "config.msp" which I place in the root of the Office installation folder)
- creation of the template (using the command `wapt-get make-template`)
- copying the "Office" folder into the newly created project folder
- editing and modifying the .py file (this might be where my mistake is)
- retrieving the .xml file (from "standard.ww" and cutting/pasting it into the project root, renaming it "silent.xml")
- modifying the .xml file (probably another point of error, but I'm not sure)
- Creating the package (using the `build-package` command).
If anyone has the configuration files to modify/create and the paths to place them, I'd appreciate it...
Thank you in advance for your help.
https://store.wapt.fr/package_details?p ... D_all.wapt
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
Hi Denis,
Yes, I did try to use the "skeleton" package (marked "MUST BE EDIT"), but I don't know where the problem lies... in my settings?
Basically, I'm just trying to install Office in the most basic way possible... without an activation key, and I'm tearing my hair out trying to create my package...
I think I've missed some parts of the creation process, but where...?
Thanks for your quick response,
Yannick
Yes, I did try to use the "skeleton" package (marked "MUST BE EDIT"), but I don't know where the problem lies... in my settings?
Basically, I'm just trying to install Office in the most basic way possible... without an activation key, and I'm tearing my hair out trying to create my package...
I think I've missed some parts of the creation process, but where...?
Thanks for your quick response,
Yannick
Last edited by admgautier on 21 Nov 2018 - 09:51, edited 1 time.
Hello,
Before creating the WAPT package, please ensure your silent installation method for Office is correct.
The method described in the package skeleton is only valid for Microsoft Office 2016 Pro Plus.
If you plan to deploy Microsoft Office 2016 Home & Small Business or Microsoft Office 365, you will need to use a different deployment method: https://docs.microsoft.com/fr-fr/deploy ... yment-tool
Once you have validated a silent installation using the correct method, you can confidently proceed with creating the appropriate WAPT package.
Alexandre
Before creating the WAPT package, please ensure your silent installation method for Office is correct.
The method described in the package skeleton is only valid for Microsoft Office 2016 Pro Plus.
If you plan to deploy Microsoft Office 2016 Home & Small Business or Microsoft Office 365, you will need to use a different deployment method: https://docs.microsoft.com/fr-fr/deploy ... yment-tool
Once you have validated a silent installation using the correct method, you can confidently proceed with creating the appropriate WAPT package.
Alexandre
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
Hello Alexandre,
Thank you for your reply.
I tested the silent installation using the .msp file (path\setup.exe /adminfile file.msp): the installation was successful.
Based on this, I then tried to recreate the package by modifying the .py file with the one provided in the procedure described here:http://reseaux85.fr/index.php?title=Dep ... oft_Office (changing the version name: ProPlus -> Standard, the .xml file name: silent.xml -> config.xml, and therefore modifying my config.xml file located in the standard.WW folder).
When deploying the newly created package, I received an error message stating: AttributeError: 'module' object has no attribute 'uninstallkey'.
I don't see where my mistake is, since there is indeed an "uninstallstring" in my .py file...
Thank you for your help (or that of other contributors!!).
Have a good day,
Yannick
Thank you for your reply.
I tested the silent installation using the .msp file (path\setup.exe /adminfile file.msp): the installation was successful.
Based on this, I then tried to recreate the package by modifying the .py file with the one provided in the procedure described here:http://reseaux85.fr/index.php?title=Dep ... oft_Office (changing the version name: ProPlus -> Standard, the .xml file name: silent.xml -> config.xml, and therefore modifying my config.xml file located in the standard.WW folder).
When deploying the newly created package, I received an error message stating: AttributeError: 'module' object has no attribute 'uninstallkey'.
I don't see where my mistake is, since there is indeed an "uninstallstring" in my .py file...
Thank you for your help (or that of other contributors!!).
Have a good day,
Yannick
Last edited by admgautier on 21 Nov 2018 - 09:51, edited 1 time.
- dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Yannick,
Sincerely,
Denis
You need to add the line `uninstallkey = []` before or after `uninstallstring`. Defining the `uninstallstring` variable is optional, but defining `uninstallkey` is mandatory (and has been for quite some time). The reseau85 wiki page will need to be updated.admgautier wrote: ↑Sep 26, 2018 - 12:07 PM Thank you for your reply.
I tested the silent installation using the .msp file (path\setup.exe /adminfile file.msp): the installation was successful.
Based on this, I then tried to recreate the package by modifying the .py file with the one provided in the procedure described here:http://reseaux85.fr/index.php?title=Dep ... oft_Office (changing the version name: ProPlus -> Standard, the .xml file name: silent.xml -> config.xml, and therefore modifying my config.xml file located in the standard.WW folder).
When deploying the newly created package, I received an error message stating: AttributeError: 'module' object has no attribute 'uninstallkey'.
I don't see where my mistake is, since there is indeed an "uninstallstring" present in my .py file...
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
Hello Denis,
Thank you for your reply.
I added the line `uninstallkey= []` and recreated the package.
The error now displayed (during deployment) is:
Office Standard 2016 Installation
CalledProcessErrorOutput: Command 'setup.exe /adminfile config.msp' returned non-zero exit status 1.
Output: 'setup.exe' is not recognized as an internal
or external command, operable program or batch file.
It seems that the `setup.exe` command is not accepted as such. Is this a problem with the relative path of the command in the .py file?
Have a good day,
Yannick
Thank you for your reply.
I added the line `uninstallkey= []` and recreated the package.
The error now displayed (during deployment) is:
Office Standard 2016 Installation
CalledProcessErrorOutput: Command 'setup.exe /adminfile config.msp' returned non-zero exit status 1.
Output: 'setup.exe' is not recognized as an internal
or external command, operable program or batch file.
It seems that the `setup.exe` command is not accepted as such. Is this a problem with the relative path of the command in the .py file?
Have a good day,
Yannick
Last edited by admgautier on 21 Nov 2018 - 09:51, edited 1 time.
- dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Yannick,
Sincerely,
Denis
I recommend you read https://www.wapt.fr/fr/doc/CreationPaqu ... index.html This should solve your problem. If not, please post your setup.py file and your package directory structure.admgautier wrote: ↑Sep 26, 2018 - 4:24 PM Thank you for your reply.
I added the line uninstallkey= [] and recreated the package.
The error that now appears (during deployment) is:
Office Standard 2016 Installation
CalledProcessErrorOutput: Command 'setup.exe /adminfile config.msp' returned non-zero exit status 1.
Output: 'setup.exe' is not recognized as an internal
or external command, operable program or batch file.
It seems that the setup.exe command is not accepted as such; is this a problem with the relative path of the command in the .py file?
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
Hello,
I followed the procedure you indicated, but without success.
As kindly offered, you will find below the link to my .py and .xml files.
https://wetransfer.com/downloads/ece078 ... 327/0b8649
The structure of my package is as follows:
- setup.py is in the project root directory
- config.msp is in ~\wpatdev\monpaquet\ISO_office\config.msp
- the xml file is in ~\wpatdev\monpaquet\ISO_office\standard.ww\config.xml
If you see anything wrong... (I'm starting to tear my hair out...
)
Thank you. Have
a good day.
I followed the procedure you indicated, but without success.
As kindly offered, you will find below the link to my .py and .xml files.
https://wetransfer.com/downloads/ece078 ... 327/0b8649
The structure of my package is as follows:
- setup.py is in the project root directory
- config.msp is in ~\wpatdev\monpaquet\ISO_office\config.msp
- the xml file is in ~\wpatdev\monpaquet\ISO_office\standard.ww\config.xml
If you see anything wrong... (I'm starting to tear my hair out...
Thank you. Have
a good day.
Last edited by admgautier on 21 Nov 2018 - 09:52, edited 1 time.
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Code: Select all
if not check_installed_out:
cmd = 'ISO_office\setup.exe /adminfile ISO_office\config.msp'
else:
cmd = 'msiexec.exe /p ISO_office\config.msp'
