Hi! We did a deployment of an upgrade to 190 sites. Each of our sites has as scheduled task set up on the Updater page of advanced installer to be run as NT AUTHORITY. The scheduled task calls the updater program with the extension of "/silentall -nofreqcheck -nogui HKLM\SOFTWARE\WOW6432Node\Company\Id" Of those sites 61 did not upgrade this morning.
We had remote access to 36 of those 61 sites.
19 sites had an error 0xE000000E. I ran the scheduled task manually at two sites that encountered the error and it ran successfully. I've currently left the others alone to avoid interfering with the business's operations.
7 ran the updater, which showed as "0x0 The operation completed successfully in task scheduler", but never downloaded or ran the installer to the updates directory. Again I've currently left the others alone to avoid interfering with operations.
10 of the sites had miscellaneous errors (2 had 0x2EF3, 1 had 0x2F19, 2 had 0x2EFD, 3 had no internet at the time, 1 was installing a windows update, 1 was missing the uninstallation msi file)
I know the error 0xE000000E is supposed to indicate "The signature of the updates configuration file is missing or is invalid", but at the two sites where I ran the scheduled task again manually the updater ran correctly and the upgrader was downloaded and run. Is a configuration file really causing this issue? If so, what is the updates configuration file referred to? Is it the ini file stored on the client, or the file with aiu tag hosted remotely? How can we avoid this error?
Also what happened at the 7 sites that reported completion? What can we do to avoid this scenario from occurring again?
Going forward we plan to deploy our solution to more and more sites which we do not have remote access to, and it is also not feasible to manually address the growing number of customers that we can access. What steps can we take to ensure that the updater program will make the upgrade take place?