Page 1 of 1

Microsoft 365 Package Update Script

Published: January 16, 2025 - 5:58 PM
by ddcorazon
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

Re: Microsoft 365 Package Update Script

Published: January 24, 2025 - 11:03 AM
by ddcorazon
Hello everyone,

the script is working again on its own.

I'll look into the problem later.