Jump to content

Recommended Posts

Posted (edited)

This might be of use to someone in the future.

 

Office 2021 LTSC cannot be directly installed/upgraded from Office 2019 using the click-to-run.

The process requires an uninstall 2019 and install of 2021 which I was hoping to achieve from 1 config XML file but I haven't had much joy with this.

 

In short - Create a config XML to uninstall Office and then another to install 2021 and deploy together in sequence, no reboot needed in between.

**Note: First load of any Office application after the above process shows the splash screen of the product as 2019 and the UI of the application doesn't look like its changed but the about section of the product shows 2021 LTSC. Close the app and re-open and both the splash screen and UI change to that of the 2021 format. #Shrug

Edited by Tefters
  • Thanks 2
  • 5 weeks later...
Posted
Im starting to look at upgrading a few guinea pigs from 2019 to 2021. What did you do with your configuration GPOS? Any "gotchas" you have found so far?
Posted

I have managed to get this working, uninstalling Office 2019 using the Remove Element and then installing Office 2021 using configuration.xml

 

Using a batch script running the following

cmd /c "setup.exe /configure uninstall.xml"  & cmd /c "setup.exe /configure configuration.xml"

The xml to uninstall






 

Install the new 2021 Office volume licence pack here on the KMS server and the KMS key from the VLSC

https://www.microsoft.com/download/details.aspx?id=103446

Seems easy now, I wished Microsoft would save us time and give us a simple how to!

Enjoy :)

  • Thanks 1
  • 2 weeks later...
Posted

Ah thank you I've been tearing what little hair I have left out with this, I thought the ODT could uninstall any previous version but what do I know.

 

Am trying your trick now @dazza007 hopefully it will sort it.

Posted
I have managed to get this working, uninstalling Office 2019 using the Remove Element and then installing Office 2021 using configuration.xml

 

Using a batch script running the following

cmd /c "setup.exe /configure uninstall.xml"  & cmd /c "setup.exe /configure configuration.xml"

The xml to uninstall






 

Install the new 2021 Office volume licence pack here on the KMS server and the KMS key from the VLSC

https://www.microsoft.com/download/details.aspx?id=103446

Seems easy now, I wished Microsoft would save us time and give us a simple how to!

Enjoy :)

 

This worked perfectly thank you @dazza007

Posted (edited)

Actually am now struggling, I've pushed this out to a set of laptops that has 2019 on and it's failing again with the same error. It's like the uninstaller can't find 2019 to uninstall?!

 

Am doubting if it uninstalled the previous at all and I tested on a laptop without Office on?!

 

I'll take another look tomorrow.

Edited by mullet_man
Posted
I've been using the offscrub vbs script and that appears to work every time

 

https://silentinstallhq.com/microsoft-office-2019-click-to-run-c2r-uninstall-offscrub-vbs-script/

 

Yeah I think the issue am having is the uninstall bit is set to uninstall all versions of Office so it's taking ages to work it's way through scanning for every version of Office to uninstall. I think if I changed the uninstall XML is specifically uninstall Office 2019 ProPlus it would speed things up.

  • 4 weeks later...
Posted

Just upgraded from 19 to 21 on my Desktop and Laptop and, AFAICT, it seems to have removed 2019 by just adding after the remove MSI line. Don't know if setting it to device based licensing had anything to do with that.

 

 
 
 
 

  • 1 year later...
Posted (edited)
I have managed to get this working, uninstalling Office 2019 using the Remove Element and then installing Office 2021 using configuration.xml

 

Using a batch script running the following

cmd /c "setup.exe /configure uninstall.xml"  & cmd /c "setup.exe /configure configuration.xml"

The xml to uninstall






 

Install the new 2021 Office volume licence pack here on the KMS server and the KMS key from the VLSC

https://www.microsoft.com/download/details.aspx?id=103446

Seems easy now, I wished Microsoft would save us time and give us a simple how to!

Enjoy :)

 

How do you run this .bat inside a sccm application.?

All this office uninstall has been driving me crazy the last 2 weeks.

The .bat works by itself, but i can't get it to work as a application.!

 

Nevermind is working now :)

Thank you :)

Edited by denmyos
Posted
I've just been looking at Office 2021 as we are all on 2019. I believe it's being rebranded as Microsoft 365 this year, is it the same deployment process?
Posted
I've just been looking at Office 2021 as we are all on 2019. I believe it's being rebranded as Microsoft 365 this year, is it the same deployment process?

 

took me 2 weeks to get working.

 

our problem was that our office 2019 was a package, so i couldn't supersedence it.

I use the batch in this thread:

cmd /c "setup.exe /configure uninstall.xml" & cmd /c "setup.exe /configure configuration.xml"

and placed it in the source folder, and then made a new application as a "manully specify the ....." and then pointed it to the batch file.

Thank you @dazza007 :)

 

remember the detection rules is for the new office, not the old Office 2019, as i thought.

 

If you have futher question just, :)

Posted

You just setup a batch file and the config in the same folder and run as a script.

If you set it as available and not required staff can run this from software center and then when they ignore your emails to do it force the app as required. The problem is the install kills all office apps to run and staff can lose work.

Posted
Installed 365 easily enough as its similar to 2021 but just found out A1 licences don't allow shared computers, only A3 and above.. This is straying from the original query but thought it was something mention.
  • Thanks 1
Posted
You just setup a batch file and the config in the same folder and run as a script.

If you set it as available and not required staff can run this from software center and then when they ignore your emails to do it force the app as required. The problem is the install kills all office apps to run and staff can lose work.

 

yes, it was quiet easy when i first got my head around it.

Good point with making it Available, instead of Required. :)

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...