Forum Discussion
Keep the current Office Version instead of updating - RDS W2k2R2
StephanGeeYes, using "target version" might be the option in your case..
Have you seen this article ? https://docs.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date
It states version 2002 will be supportet until September 14, 2021, so this gives you some time to work on new updated RDS environment.
HiStephanGee ,
Of course the best way would be to move to a supported Windows server version. Have you tested or considered running in-place upgrade to Win2016 ?
In case in place upgrade is not an option, you could consider disabling CDN updates (UpdatesEnabled in registry/GPO), so that you don't get version upgraded to 2005. Though, you would be running unpatched office software then and you never know when some features in O365 "cloudy part" would present you issues on unpatched software suite, let alone increased security risk..
Another alternative to test or consider is Office 2019 perpetual through volume licensing. That one is on version "1808", but officially requires Windows Server 2019 OS, so not the ideal solution either..
I don't think there are any easy solutions to this 🙂 Regards, Ruslan
I tried inplace update in my lab (SureBackup from Veeam) but it always failed.
Not updating with security patches is not an option.
Then i will go with the option to specify the "target version" in GPO - every 5 days after update deployment
StephanGeeYes, using "target version" might be the option in your case..
Have you seen this article ? https://docs.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date
It states version 2002 will be supportet until September 14, 2021, so this gives you some time to work on new updated RDS environment.
Yes is saw that - was just wondering if there is an easier way to do this 😉
Thanks for your help
