Office 2021 Install via GPO

[Julian]

I believe that your batch file failed as Cmd.exe does not like UNC's! However Powershell can process UNC's

 

After a Google search I have used the following PowerShell script, to Uninstall Office 2019, and install Office 2021, This is a computer start-up script.

 

#Check for Office 2021 installation

$officeInstall = Get-ItemPropertyValue 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' 'ProductReleaseIds'

 

if($officeInstall -eq "ProPlus2021Volume"){

Exit

}

 

if($officeInstall -eq "ProPlus2019Volume"){

#Uninstall 2019

$now = Get-Date -format "dd-MMM-yyy HH:mm:ss"

Write-Output $now "Office 2019 found, uninstalling" >> c:\Office2021.log

 

\\joa-app01\Repository\Office2019\setup.exe /configure \\joa-app01\Repository\Office2019\Remove2019.xml

}

 

#install office 2021

$now = Get-Date -format "dd-MMM-yyy HH:mm:ss"

Write-Output $now "Installing Office 2021" >> c:\Office2021.log

\\joa-app01\Repository\Office2021\setup.exe /configure \\joa-app01\Repository\Office2021\Config2021.xml

[CrispyJay]

I believe that your batch file failed as Cmd.exe does not like UNC's! However Powershell can process UNC's

 

After a Google search I have used the following PowerShell script, to Uninstall Office 2019, and install Office 2021, This is a computer start-up script.

 

#Check for Office 2021 installation

$officeInstall = Get-ItemPropertyValue 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' 'ProductReleaseIds'

 

if($officeInstall -eq "ProPlus2021Volume"){

Exit

}

 

if($officeInstall -eq "ProPlus2019Volume"){

#Uninstall 2019

$now = Get-Date -format "dd-MMM-yyy HH:mm:ss"

Write-Output $now "Office 2019 found, uninstalling" >> c:\Office2021.log

 

\\joa-app01\Repository\Office2019\setup.exe /configure \\joa-app01\Repository\Office2019\Remove2019.xml

}

 

#install office 2021

$now = Get-Date -format "dd-MMM-yyy HH:mm:ss"

Write-Output $now "Installing Office 2021" >> c:\Office2021.log

\\joa-app01\Repository\Office2021\setup.exe /configure \\joa-app01\Repository\Office2021\Config2021.xml

To be honest I didnt factor in removing office 2019 as we'll only be using fresh images. Thanks for including that

 

I've managed to use cmd's/bat's for other software so I carried on with that approach. It just wasn't working in this instance. It is now though 😁😁

[Lensytink]

Setting up Office 2021 via GPO can be quite the puzzle—I've navigated similar challenges with deployment scripts in the past. When I upgraded to Microsoft Office Professional, I encountered some script frustrations too. What eventually worked for me was diving deep into the configuration file and double-checking network permissions. Sometimes, it's the smallest detail causing the hiccup! Hang in there, and hopefully, someone here can chime in with a solution that clicks perfectly for your setup. It can be a bit of trial and error, but once it's up and running smoothly, it's a game-changer for productivity!

[LeMarchand]

Setting up Office 2021 via GPO can be quite the puzzle—I've navigated similar challenges with deployment scripts in the past. When I upgraded to Microsoft Office Professional, I encountered some script frustrations too. What eventually worked for me was diving deep into the configuration file and double-checking network permissions. Sometimes, it's the smallest detail causing the hiccup! Hang in there, and hopefully, someone here can chime in with a solution that clicks perfectly for your setup. It can be a bit of trial and error, but once it's up and running smoothly, it's a game-changer for productivity!

 

Thank you for your insightful input on this. From your post, I see that the best solution is to check the configuration file for network solutions or there may be hiccups. I have found that a good way to fix hiccups is to take some Andrews.

[Lensytink]

Setting up Office 2021 via GPO can be quite the puzzle—I've navigated similar challenges with deployment scripts in the past. When I upgraded to Microsoft Office Professional Plus 2021, I encountered some script frustrations too. What eventually worked for me was diving deep into the configuration file and double-checking network permissions. Sometimes, it's the smallest detail causing the hiccup! Hang in there, and hopefully, someone here can chime in with a solution that clicks perfectly for your setup. It can be a bit of trial and error, but once it's up and running smoothly, it's a game-changer for productivity!

Thank you for your insightful input on this. From your post, I see that the best solution is to check the configuration file for network solutions or there may be hiccups. I have found that a good way to fix hiccups is to take some Andrews.

 

Thanks for your input! I agree that checking the configuration file and network permissions is crucial. In my experience, ensuring that all settings align perfectly can really smooth out the deployment process. I also found that keeping a detailed log helps track any issues that come up. Let's hope for a quick resolution!