Microsoft 365 Package Update Script

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Answer
ddcorazon
Messages: 37
Registration: May 30, 2023 - 11:53 p.m.

January 16, 2025 - 5:58 PM

Hello everyone,

Happy New Year and Best Wishes.

I'm having a small issue with the Office365 package update. I modified the package's Configuration.xml file to switch to a Current channel (Apps for Business).

I have been using the update package for almost a year and I have not had any problems.

However, since version 18227.20162, it's impossible to upgrade. When I run the update package, it tells me I'm up to date with version 18227.20162 (a version dating from December 10th, and we've had 2 builds since then, the latest dating from January 14th (2 days ago)).

Code: Select all

*** Remote Interpreter Reinitialized ***
Command Line : update-package-sources "c:\waptdev\my-microsoft-office-365-business-64_16.0.18227.20162-26_x64_windows_10.0_PROD_fr-wapt\WAPT\.."
Using config file: C:\Users\my\AppData\Local\waptconsole\waptconsole.ini
Downloading Office with XML configuration
Software version up-to-date (16.0.18227.20162)
OfficeClientEdition: 64
Product ID: O365BusinessRetail
Language ID: fr-fr
Packages updated :
Has anyone else experienced this problem?
PS: Note that I did not modify the update package script, just the XML to change the channel to current and the product ID to O365BusinessRetail.
Another thing, when I force an update from a PC (which was installed via the WAPT package) directly in Word, I am able to get the latest version.

WAPT Server version: 2.6.0.16795 Ubuntu 20.04
WAPT Agent version: 2.6.0.16795
High
ddcorazon
Messages: 37
Registration: May 30, 2023 - 11:53 p.m.

January 24, 2025 - 11:03

Hello everyone,

the script is working again on its own.

I'll look into the problem later.
High
Answer

Return to “WAPT Packages”


  • To go further with WAPT