When adding Project/Visio fails with ConfigureOfficeApps, the script should fail out

[brmcmill]

Hey Team -- have a customer who has seen this twice now where Project/Visio did not successfully install, the script continues as if the build is successful. They find out after deploy an image, Project and Visio did not successfully install. Looking at the customization log:

Noticed this with currently and previous versions of ConfigureOfficeApps: https://github.com/Azure/RDS-Templates/blob/master/CustomImageTemplateScripts/CustomImageTemplateScripts_2024-03-27/ConfigureOfficeApps.ps1

Errors seen in the customization.log packer file:

azure-arm:  Error 404 - Not Found
[c82a1b56-f812-4848-8d36-8e9c404ed9e7] PACKER 2024/12/23 16:27:00 ui:     azure-arm: <div class="
[c82a1b56-f812-4848-8d36-8e9c404ed9e7] PACKER 2024/12/23 16:27:00 ui:     azure-arm: At C:\Windows\Temp\script-6769876b-e65a-c0b7-31be-c4de644d310c.ps1:1 char:1
[c82a1b56-f812-4848-8d36-8e9c404ed9e7] PACKER 2024/12/23 16:27:00 ui:     azure-arm: + C:\AVDImage\OfficeApps.ps1 -Type "Add" -Applications "Visio","Project ...
[c82a1b56-f812-4848-8d36-8e9c404ed9e7] PACKER 2024/12/23 16:27:00 ui:     azure-arm: + 
[c82a1b56-f812-4848-8d36-8e9c404ed9e7] PACKER 2024/12/23 16:27:00 ui:     azure-arm:     + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [OfficeApps.ps1], WebExcept
[c82a1b56-f812-4848-8d36-8e9c404ed9e7] PACKER 2024/12/23 16:27:00 ui:     azure-arm:    ion
[c82a1b56-f812-4848-8d36-8e9c404ed9e7] PACKER 2024/12/23 16:27:00 ui:     azure-arm:     + FullyQualifiedErrorId : WebCmdletWebResponseException,OfficeApps.ps1

[brmcmill]

Update to this -- the Built-In option to add Project/Visio is not working and there's no way of knowing it's not working until you try to deploy a VM with the captured image. The script should fail if it does not install it correctly; however, there seems to be an issue with this script. I've had to revert to using a custom script with the OCT as an alternative and it works.

[Korton-TAS-1]

Something has changed with the download location of the Office Deployment Toolkit (ODT), so the download doesn't work anymore. See: https://www.reddit.com/r/microsoft/comments/1had789/odt_download_link_always_newest_version/

[brmcmill]

@Korton-TAS-1 -- you're spot on, good find. Line 217 - https://www.microsoft.com/en-us/download/confirmation.aspx?id=49117 -- 404 error.

[Korton-TAS-1]

After changing download URL to:

$ODTDownloadUrl = 'https://go.microsoft.com/fwlink/p/?LinkID=626065'

It works again!

[SirBeredan]

Suggestion, Would it possibly not be better to use https://officecdn.microsoft.com/pr/wsus/setup.exe as this should be kept up to date?

[marshalexander99]

Suggestion, Would it possibly not be better to use https://officecdn.microsoft.com/pr/wsus/setup.exe as this should be kept up to date?

This script can definitely be simplified. I'm not sure what actually the ODT.exe is doing here apart from being extracted to get setup.exe, which would be easier to download directly from the above as the script itself generates the XML used to configure office

[SirBeredan]

Suggestion, Would it possibly not be better to use https://officecdn.microsoft.com/pr/wsus/setup.exe as this should be kept up to date?

This script can definitely be simplified. I'm not sure what actually the ODT.exe is doing here apart from being extracted to get setup.exe, which would be easier to download directly from the above as the script itself generates the XML used to configure office

It's what I did in my fork, it works well.