this post was submitted on 02 Apr 2024
12 points (92.9% liked)
techsupport
2469 readers
20 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Seconded. ODT is the way to go, used to use it a lot back in my sysadmin days to generate specific builds.
Thanks, this looks like the answer. Any idea what the version string should be in the ODT config file for build 17328.20184? It looks like they want a major version number first, so Office 2016 was v16.0.xxxxx.xxxxxx. Is 2019 v17 or v19?
This page is your friend, bookmark it cause you'll be referring to it multiple times ;) : https://learn.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date
In saying that, all Office versions since 2016 have been called v16 - so that first bit won't change (unless MS pull another stunt like Windows 11).
Also worth taking a look at this page: https://learn.microsoft.com/en-us/deployoffice/office-deployment-tool-configuration-options