petben Posted January 25, 2023 Posted January 25, 2023 I have created our Office365 install, it works fine when running the command when logged in: Start-Process "\\domain\MSI\Office\Office365\Deployment\setup.exe" -ArgumentList '/configure "\\Domain\MSI\Office\Office365\Deployment\Office365Config.xml"' -Wait but as soon as I put the command in startup script it start, the progress bar gets to about 50% then it hangs forever. Permissions are the same as all other folders the MSI folder and all other MSI's (including our old Office2019) work fine at startup. Ideas..? Is there something funny about O365? I am using a local install source rather than CDN.
petben Posted January 25, 2023 Author Posted January 25, 2023 We have found the offending error in the Office install log but what we can do about it...? This is on a freshly imaged up to date Win10 x64 machine with no software installed, we have already set the install (using the config tool) to not uninstall any previous versions. We are already using the Enterprise CDN. "ErrorCode": 0, "ErrorType": "", "AppVErrorSource": "", "ErrorMessage": "", "ErrorDetails": "", "ContextData": "{"message":"Failed to use PowerShell deprovision Appx package","Error":"Remove-AppxProvisionedPackage : Cannot bind argument to parameter 'PackageName' because it is null."}"} Ideas? Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now