Deyda
Microsoft 365 Apps - install with custom XML
Hello,
I browse in NeverRed to my Custom XML file and save it.
In the scriptbox is written:
I start the script and when it comes to "Install Microsoft 365 Apps Monthly Enterprise Channel" the followed error accured.
The other software i want to install is installed successfully. I also checked the install folder, all files are there including the install.xml with the correct selections.
Thanks for your help
The script renames the Office installer .EXE based on the channel name ("$PackageName = "setup_" + "$MS365AppsChannelClear""). The channel name contains a whitespace (I´d assume this has been changed by Microsoft recently), which causes the installer to fail. As a manual workaround (until this is fixed), you could try to rename the installer so something w/o any whitespace and execute the three steps ("/download install.xml", "/configure remove.xml", "/configure install.xml").
Thanks for the info. the last time (2 Month ago) it works perfect with the scipt. I checked the nameof the installer and it has whitespaces already and the script works.
I will try now your solution. Thanks
OK, looks like the channel name did not change. Therefore, I´d assume the installer changed its behaviour regarding whitespace handling.
I have not yet fully figured out, what the root case of this problem is.
It seems that the Set-Location prior to the Start-Process (Lines 26662 ff.) for the M365-Installer ist not working as expected. It somehow does not change the location and hence the Installer doesn't find the configuration xml files.
When I navigate to the Channel-Folder on CLI and start the /download /configure commands manually, everything works as expected.
Maybe it will be a good idea to "feed" the installer with the full path of the xml-files instead of relying on the current folder location.
It has in fact something to do with the whitespaces inside the installer's file name. It does never find the config files specified on command line because it maybe doesn't take care of the whitespaces in it's own filename (treating them already as arguments).
When the setup ... exe is renamed to something wirhout whitespaces (e.g. setupmec.exe) then everything works, as ist should. (Regarding my previous commen: for convenience I had already renamed it for my CLI-Test so it wokred there already)
So as far as I can see it is a problem in the Installer itself which maybe will be resolved by MS in a future version. In the mean time you could rename the installer after download to something wirhout whitespaces:
Line 26635 ff:
$MS365OrgAppsInstaller = "setup_" + "$MS365AppsChannelClear" + ".exe"
$MS365AppsInstaller = "setupM365.exe"
rename-Item -Path "$PSScriptRoot\$Product\$MS365AppsChannelClear\$MS365OrgAppsInstaller" -NewName "$PSScriptRoot\$Product\$MS365AppsChannelClear\$MS365AppsInstaller"