Microsoft Office version: Difference between revisions
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
Line 4: | Line 4: | ||
Upgrading any part of MS Office can break functionality, so we need to test first whenever there might be an upgrade. | Upgrading any part of MS Office can break functionality, so we need to test first whenever there might be an upgrade. | ||
Specifically, Digital Health is upgrading our ancient Exchange (email) server from on-premise to cloud over the next few weeks, which requires modern auth and should be tested with our email automation. Also, we have a system of VBS, batch, VBA and possibly PowerShell scripts to run the beast, so we need to know things will work in the new setup. | |||
== Verified Version== | == Verified Version== | ||
Line 9: | Line 13: | ||
== Version lifecycle == | == Version lifecycle == | ||
* [https://docs.microsoft.com/en-us/lifecycle/products/microsoft-office-2019 Office 2019] | * [https://docs.microsoft.com/en-us/lifecycle/products/microsoft-office-2019 Office 2019] support ends | ||
** initially support was supposed to end 2023-10-10 | ** initially support was supposed to end 2023-10-10 | ||
** extended support was added up to 2025-10-14; | ** extended support was added up to 2025-10-14; | ||
** [https://learn.microsoft.com/en-us/office/ltsc/2021/ Office LTSC 2021] might be an option but [https://learn.microsoft.com/en-us/lifecycle/products/office-ltsc-2021 support also ends 2026-10-13] so this would only buy us 1 year | |||
{{Todo | {{Todo | ||
Line 19: | Line 24: | ||
| question = | | question = | ||
* I have been in contact with Shared Health about this; they are aware but don't have a project right now to update Office. Offered us to install the new version to test recently, but I have not had bandwidth. [[User:Ttenbergen|Ttenbergen]] 11:39, 7 August 2025 (CDT) }} | * I have been in contact with Shared Health about this; they are aware but don't have a project right now to update Office. Offered us to install the new version to test recently, but I have not had bandwidth. [[User:Ttenbergen|Ttenbergen]] 11:39, 7 August 2025 (CDT) }} | ||
== Log == | |||
2025-08-13 - secured a laptop to do testing | |||
2025-07-16 – email to Service Desk; got Request# REQ510946 | |||
2025-04-29 – emailed for follow-up; contact has no news and expects it will be a while since there really is no project just the idea of a plan… | |||
2025-04-10 – emailed a Shared Health contact to see if there are plans for MS Office replacement | |||
== Related articles == | == Related articles == |
Revision as of 20:27, 13 August 2025
Out project uses MS Access 2019 64-bit.
See Finding your version of MS Access to find out what version you have.
Upgrading any part of MS Office can break functionality, so we need to test first whenever there might be an upgrade.
Specifically, Digital Health is upgrading our ancient Exchange (email) server from on-premise to cloud over the next few weeks, which requires modern auth and should be tested with our email automation. Also, we have a system of VBS, batch, VBA and possibly PowerShell scripts to run the beast, so we need to know things will work in the new setup.
Verified Version
- TT 2025-08-07: Microsoft Access 2019 MSO (16.0.10417.20030) 64-bit
Version lifecycle
- Office 2019 support ends
- initially support was supposed to end 2023-10-10
- extended support was added up to 2025-10-14;
- Office LTSC 2021 might be an option but support also ends 2026-10-13 so this would only buy us 1 year
![]() |
|
|
Log
2025-08-13 - secured a laptop to do testing
2025-07-16 – email to Service Desk; got Request# REQ510946 2025-04-29 – emailed for follow-up; contact has no news and expects it will be a while since there really is no project just the idea of a plan… 2025-04-10 – emailed a Shared Health contact to see if there are plans for MS Office replacement
Related articles
Related articles: |