SOLVED

Keep the current Office Version instead of updating - RDS W2k2R2

%3CLINGO-SUB%20id%3D%22lingo-sub-1554902%22%20slang%3D%22en-US%22%3EKeep%20the%20current%20Office%20Version%20instead%20of%20updating%20-%20RDS%20W2k2R2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1554902%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Emaybe%20i%20do%20not%20use%20the%20right%20search%20terms%20but%20what%20is%20the%20best%20practice%20to%20keep%20the%20current%20semi%20annual%20version%202002%20until%20the%20end%20of%20it's%20%22supported%20end%20date%22%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20need%20to%20perform%20this%20setting%20because%20of%20the%20%22Major%20Change%22%20coming%20up%3A%3C%2FP%3E%3CP%3E%3CSPAN%3EIn%20particular%2C%20any%20Microsoft%20365%20Apps%20updated%20%3CSTRONG%3E%3CSTRONG%3Eto%20version%202005%20or%20later%3C%2FSTRONG%3E%3C%2FSTRONG%3E%20will%20result%20in%20functionality%20and%20stability%20issues%20for%20Office%20applications%20due%20to%20innovations%20that%20are%20not%20compatible%20with%20Windows%208%20and%20Windows%20Server%202012.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20know%20that%20best%20practice%20would%20be%20to%20switch%20to%20Windows%202019%20or%20Virtual%20Desktop.%20But%20we%20do%20not%20have%20the%20resources%20to%20perform%20this%20change%20at%20the%20moment.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EBoth%20installations%20i%20have%20are%20set%20to%20semi%20annual.%20Which%20is%20fine%20for%20the%20moment.%20Until%20the%20next%20update%20of%20the%20semi%20annual%20version%20in%20September.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDo%20i%20have%20to%20work%20with%20Target%20Version%20or%20Prevent%20Office%20from%20being%20updated%3F%20Or%20is%20there%20a%20easier%20way%20that%20does%20not%20need%20manual%20work%20every%20month%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%20in%20advance%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EStephan%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1554902%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1555746%22%20slang%3D%22en-US%22%3ERe%3A%20Keep%20the%20current%20Office%20Version%20instead%20of%20updating%20-%20RDS%20W2k2R2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1555746%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F533323%22%20target%3D%22_blank%22%3E%40StephanGee%3C%2FA%3E%20%2C%3C%2FP%3E%3CP%3EOf%20course%20the%20best%20way%20would%20be%20to%20move%20to%20a%20supported%20Windows%20server%20version.%20Have%20you%20tested%20or%20considered%20running%20in-place%20upgrade%20to%20Win2016%20%3F%3C%2FP%3E%3CP%3EIn%20case%20in%20place%20upgrade%20is%20not%20an%20option%2C%20you%20could%20consider%20disabling%20CDN%20updates%20(UpdatesEnabled%20in%20registry%2FGPO)%2C%20so%20that%20you%20don't%20get%20version%20upgraded%20to%202005.%20Though%2C%20you%20would%20be%20running%20unpatched%20office%20software%20then%20and%20you%20never%20know%20when%20some%20features%20in%20O365%20%22cloudy%20part%22%20would%20present%20you%20issues%20on%20unpatched%20software%20suite%2C%20let%20alone%20increased%20security%20risk..%3C%2FP%3E%3CP%3EAnother%20alternative%20to%20test%20or%20consider%20is%20Office%202019%20perpetual%20through%20volume%20licensing.%20That%20one%20is%20on%20version%20%221808%22%2C%20but%20officially%20requires%20Windows%20Server%202019%20OS%2C%20so%20not%20the%20ideal%20solution%20either..%3C%2FP%3E%3CP%3EI%20don't%20think%20there%20are%20any%20easy%20solutions%20to%20this%20%3A)%3C%2Fimg%3E%20Regards%2C%20Ruslan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1555788%22%20slang%3D%22en-US%22%3ERe%3A%20Keep%20the%20current%20Office%20Version%20instead%20of%20updating%20-%20RDS%20W2k2R2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1555788%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F366140%22%20target%3D%22_blank%22%3E%40RNalivaika%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20inplace%20update%20in%20my%20lab%20(SureBackup%20from%20Veeam)%20but%20it%20always%20failed.%3C%2FP%3E%3CP%3ENot%20updating%20with%20security%20patches%20is%20not%20an%20option.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20i%20will%20go%20with%20the%20option%20to%20specify%20the%20%22target%20version%22%20in%20GPO%20-%20every%205%20days%20after%20update%20deployment%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1557986%22%20slang%3D%22en-US%22%3ERe%3A%20Keep%20the%20current%20Office%20Version%20instead%20of%20updating%20-%20RDS%20W2k2R2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1557986%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F533323%22%20target%3D%22_blank%22%3E%40StephanGee%3C%2FA%3EYes%2C%20using%20%22target%20version%22%20might%20be%20the%20option%20in%20your%20case..%3C%2FP%3E%3CP%3EHave%20you%20seen%20this%20article%20%3F%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fofficeupdates%2Fupdate-history-microsoft365-apps-by-date%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fofficeupdates%2Fupdate-history-microsoft365-apps-by-date%3C%2FA%3E%3C%2FP%3E%3CP%3EIt%20states%20version%202002%20will%20be%20supportet%20until%20September%2014%2C%202021%2C%20so%20this%20gives%20you%20some%20time%20to%20work%20on%20new%20updated%20RDS%20environment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1560258%22%20slang%3D%22en-US%22%3ERe%3A%20Keep%20the%20current%20Office%20Version%20instead%20of%20updating%20-%20RDS%20W2k2R2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1560258%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F366140%22%20target%3D%22_blank%22%3E%40RNalivaika%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20is%20saw%20that%20-%20was%20just%20wondering%20if%20there%20is%20an%20easier%20way%20to%20do%20this%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3CP%3EThanks%20for%20your%20help%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

Hi everyone,

 

maybe i do not use the right search terms but what is the best practice to keep the current semi annual version 2002 until the end of it's "supported end date"?

 

I need to perform this setting because of the "Major Change" coming up:

In particular, any Microsoft 365 Apps updated to version 2005 or later will result in functionality and stability issues for Office applications due to innovations that are not compatible with Windows 8 and Windows Server 2012.

 

I know that best practice would be to switch to Windows 2019 or Virtual Desktop. But we do not have the resources to perform this change at the moment.

 

Both installations i have are set to semi annual. Which is fine for the moment. Until the next update of the semi annual version in September.

 

Do i have to work with Target Version or Prevent Office from being updated? Or is there a easier way that does not need manual work every month?

 

Thanks in advance

Stephan

 

4 Replies

Hi@StephanGee ,

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

@RNalivaika 

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

best response confirmed by StephanGee (Frequent Contributor)
Solution

@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.

@RNalivaika 

Yes is saw that - was just wondering if there is an easier way to do this ;)

Thanks for your help