[ms office - 2019] Deploying Office 2019

[Koldov]

Out of idle curiosity ('training' day today) I decided to toy with the idea of getting our estate on to Office 2019 (currently Office 2016).

 

I thought I'd jump on MVLSC and download the MSI to give it a quick blast on a test machine....

 

Well, that escalated quickly and now I find myself in a world of 'Click-to-Run', Deployment XMLs, Office Deployment Tools and the Office Content Delivery Network (CDN)...

 

What the actual heck is going on here....? I feel like an old man having been transported to 2259 and also like a deer in the headlights of an oncoming car at the same time.

 

As usual, my research has left me with more questions than answers, not helped by the usual MS 'help' docs being less then helpful!

 

From reading this:

 

https://docs.microsoft.com/en-us/DeployOffice/office2019/deploy

 

 

I gather that apart from being 'Click-to-Run' (whatever that means - per user license?), I can't deploy it by the usual MSI or manual methods or type in a serial key (MAK) to activate it, or use WSUS to control updates to it... it has to get install files and updates from the CDN (although I can create more work and download them to the network - what happens if they click to run whilst at home?) and I have to get all the above set-up before I can even deploy it to one machine to test it...

 

However, MVLSC does have an ISO available (and the ODT):

 

 

Also WSUS does have the product listed:

 

 

Anyone got a really simple way to explain all this (otherwise I'm sticking to 2016 until 2025)?

 

EDIT: Just to note we don't have SCCM or anything like that for deployment...

Edited April 19, 2022 by Koldov

[tmoon-mint]

You will need to generate an XML file for your install. Config.office.com will be your friend for this combined with the click to run installer that I suspect you have already downloaded.

 

Edit: Just to add, Office 2021 LTSC is the latest version if you want to go down that route instead.

 

The click to run versions of Office update by themselves and dont use WSUS or Windows update.

Edited April 19, 2022 by tmoon-mint

[jhothersall]

Just make sure it is Office 2019 and not Office 365, Sims.net will not support Office 365. We use SCCM to deploy and then Windows update for business for updates

[DrCheese]

Just make sure it is Office 2019 and not Office 365, Sims.net will not support Office 365. We use SCCM to deploy and then Windows update for business for updates

 

I would question this - We've ran the 365 version of office for over 3 years now without any issues with SIMS. If they ever did complain during a support call I'd just roll down a few machines for testing (They haven't) The advantages of the 365 version are numerous and I wouldn't want to be held back due to SIMS.

[TwistedHelixis]

We've ran the 365 version of office for over 3 years now without any issues with SIMS

Sorry to jump in, am I right in thinking that 365 office doesn't support shared devices? We still have some schools that use Year3 as a login for all year 3 pupils.

[Koldov]

You will need to generate an XML file for your install. Config.office.com will be your friend for this combined with the click to run installer that I suspect you have already downloaded.

 

Actually looking at it I'm not exactly sure what I've downloaded It says it is 'SW_DVD5_Office_Professional_Plus_64Bit_English_-6_OfficeOnlineSvr_MLF_X21-90444.ISO'.... Office Online Server? Where am I supposed to install that, on a server share? Who is doing the 'Click-to-Run' part...? The user?

 

The click to run versions of Office update by themselves and dont use WSUS or Windows update.

 

We use SCCM to deploy and then Windows update for business for updates

 

It was my initial understanding that it uses its own 'special' internet channel for updates (or you can configure a share and manage them manually), but again there is the WSUS entry (so what exactly does that do?) and apparently WUfB so...?

[CHiLL]

Actually looking at it I'm not exactly sure what I've downloaded It says it is 'SW_DVD5_Office_Professional_Plus_64Bit_English_-6_OfficeOnlineSvr_MLF_X21-90444.ISO'.... Office Online Server? Where am I supposed to install that, on a server share? Who is doing the 'Click-to-Run' part...? The user?

That configused me at first, but you don't download anything from VLSC for Office 365. You need to download the Office 365 Deployment Tool: https://www.microsoft.com/en-us/download/details.aspx?id=49117. Run/extract the contents, which will contain setup.exe and some sample XML. You can go to https://config.office.com/ to create a cutsom XML file with your requirements of how Office is configured and download it.

 

Once you have your customised XML file, you can download Office by running the following command (which will download Office 365 into a sub folder of that folder structure):

\\server\share$\O365\setup.exe /download \\server\share$\O365\config.xml

 

To then deploy Office, run the following command:

\\server\share$\O365\setup.exe /configure \\server\share$\O365\config.xml

Edited April 20, 2022 by CHiLL

[3s-gtech]

You don’t want Office Online Server, that’s an integration tool for local Sharepoint and Skype for Business/Exchange. Right pain to get working too!

 

You’ll need to run the setup process that pulls down the install. It ends up working similar to Office 2016 once you’ve done this - for instance, 2019 is available in my WDS task sequence to deploy to clients and I have a script that installs it when run locally.

[Koldov]

That configused me at first, but you don't download anything from VLSC for Office 365.

 

This is for Office 2019 though not O365, still the same process?

 

You don’t want Office Online Server, that’s an integration tool for local Sharepoint and Skype for Business/Exchange. Right pain to get working too!

 

Thanks, that saved me a fair amount of potentially wasted time wondering why it wasn't working!

 

WOW! Well done MS, this all seems so much simpler and easier than downloading and deploying an MSi...

[CHiLL]

This is for Office 2019 though not O365, still the same process?

Yeah, starting with Office 2019, Microsoft did away with the old MSI deployments and it all went purely C2R.

[Koldov]

Sorry to jump in, am I right in thinking that 365 office doesn't support shared devices? We still have some schools that use Year3 as a login for all year 3 pupils.

 

Interested in this too...

 

Just gone to create my deployment configuration xml on the Office Customisation Tool website and it will not let me choose 'Device Based Activation'... in fact it is greyed out!

 

 

I guess I can edit the config.xml but why won't it let me choose it in the tool, what am I missing here?

Edited April 20, 2022 by Koldov

[Steve21]

Interested in this too...

 

Just gone to create my deployment configuration xml on the Office Customisation Tool website and it will not let me choose 'Device Based Activation'... in fact it is greyed out!

 

[ATTACH=CONFIG]65269[/ATTACH]

 

I guess I can edit the config.xml but why won't it let me choose it in the tool, what am I missing here?

 

Not sure if you’re doing what I did originally but there are two config tools

 

One won’t let you pick it as it’s not for volume licensing etc

 

If you go to https://config.office.com sign in and go to device configuration and create new configuration you get all the options (with a huge licensing disclaimer warning on the device based licensing )

 

Steve

[Koldov]

Unfortunately it doesn't seem to work that way....

 

However, I have found that I might be overthinking it (or MS have made a complete hash of explaining it and have written a tool that doesn't actually make sense)!

 

It seems that the only way I can get the other two options to be selectable is if I choose the 'Product' Office Suite - 'Microsoft 365 Apps for Enterprise' this is the only time I can change to Device Based or Shared Computer... this possibly makes sense as this is when you WOULD need to specify depending on your use case scenario and licensing of M365 apps (but I don't want to install M365 apps, I want Office 2019).....

 

If however you are installing Office 2019, it should automatically activate with the key provided AND be licenced to the 'computer' and not a 'user'... I guess my confusion here stems from the fact that if I have chosen Office Pro Plus 2019 as the 'product' then it should automatically grey out ALL of those choices as there is no need to make a choice there....

 

EDIT: I also noticed the line which I guess must take the included MAK key and activate and hopefully ignore the other lines about 'shared computer' or 'device based' licensing as it isn't a O365/M365 apps install and they only pertain to that... or maybe I can just remove those lines from the XML in that case?

Edited April 20, 2022 by Koldov

[CHiLL]

Unfortunately it doesn't seem to work that way....

 

However, I have found that I might be overthinking it (or MS have made a complete hash of explaining it and have written a tool that doesn't actually make sense)!

 

It seems that the only way I can get the other two options to be selectable is if I choose the 'Product' Office Suite - 'Microsoft 365 Apps for Enterprise' this is the only time I can change to Device Based or Shared Computer... this possibly makes sense as this is when you WOULD need to specify depending on your use case scenario and licensing of M365 apps (but I don't want to install M365 apps, I want Office 2019).....

 

If however you are installing Office 2019, it should automatically activate with the key provided AND be licenced to the 'computer' and not a 'user'... I guess my confusion here stems from the fact that if I have chosen Office Pro Plus 2019 as the 'product' then it should automatically grey out ALL of those choices as there is no need to make a choice there....

I don't think you need to worry about shared licensing in regards to DBL for Office 2019. I had mine deployed since 2019 and looking at my config XML in config.office.com, it only has User Based selected. However, if I check my actual deployed XML file, I have added:

I think Device Based Licensing only applies to Microsoft 365 (formerly Office 365) apps.

Edited April 20, 2022 by CHiLL

[CHiLL]

EDIT: I also noticed the line which I guess must take the included MAK key and activate and hopefully ignore the other lines about 'shared computer' or 'device based' licensing as it isn't a O365/M365 apps install and they only pertain to that...

I have mine activated via KMS, which I obtained the key for from our VLSC. Install the key on your KMS server/AD activation method and use the standard KMS client key on all your clients (same key for everyone, specified in the config XML). I don't use MAK keys. Using AUTOACTIVATE will tell Office to go look for a valid license, usually via KMS. Once KMS grants it, Office is automatically activated.

 

Note: KMS activations only last 180 days, then they request a new activation. So if a device is off the network for more than 6 months (staff laptop without a VPN for example), then it will limit Office's functionaliity until it's activated again. Usually it's automatic once the device re-joins the network (and may Word or something is opened).

Edited April 20, 2022 by CHiLL

[Koldov]

Thanks for that, good to have some reassurance!

 

I was editing my post when you replied, but I think I had already convinced myself that it wasn't going to apply to the Office 2019 licensing/install (in fact I now don't think either of those lines apply).

 

Pity MS couldn't have made that clearer by greying out that section if you choose an install product that doesn't require those in the XML...

 

EDIT: We don't use KMS and I chose MAK in the XML generator, so I'm hoping there is a line in there that explains that to the install and it goes off to activate on the internet (although I can't see one)...

Edited April 20, 2022 by Koldov

[Koldov]

OK, so a little bit further and more issues...

 

Got the Office Deployment Tools to extract the setup.exe and example XMLs on a share on the server. Sorted out the XML I want to use and did the CMD to download the install files... ERROR! Tried on my own PC and.... ERROR!

 

 

Went through the XML trying to see what could be stopping it removing a line and retrying and found out that if you specify a 'Source Path' location (network or local) for the deployment install files in the XML it stops the download... Made a copy of the XML called 'download' removing that and it download on my PC, so I tried it on the server. Unfortunately it only downloaded half the required files and... ERROR!

 

Looked through the firewall logs and it seems we are blocking "https://config.edge.skype.com" on the server IP and as this was denied something wasn't downloaded (I did try unblocking it, but it still didn't work and I couldn't be bothered to spend the rest of the day poking holes in the firewall so copied across what downloaded to my PC).

 

So, now I have deployment share with all the required files downloaded and a 'deployment' XML... just need to work out how I actually deploy it now... but I've had enough for today!

[tmoon-mint]

OK, so a little bit further and more issues...

 

Got the Office Deployment Tools to extract the setup.exe and example XMLs on a share on the server. Sorted out the XML I want to use and did the CMD to download the install files... ERROR! Tried on my own PC and.... ERROR!

 

[ATTACH=CONFIG]65284[/ATTACH]

 

Went through the XML trying to see what could be stopping it removing a line and retrying and found out that if you specify a 'Source Path' location (network or local) for the deployment install files in the XML it stops the download... Made a copy of the XML called 'download' removing that and it download on my PC, so I tried it on the server. Unfortunately it only downloaded half the required files and... ERROR!

 

Looked through the firewall logs and it seems we are blocking "https://config.edge.skype.com" on the server IP and as this was denied something wasn't downloaded (I did try unblocking it, but it still didn't work and I couldn't be bothered to spend the rest of the day poking holes in the firewall so copied across what downloaded to my PC).

 

So, now I have deployment share with all the required files downloaded and a 'deployment' XML... just need to work out how I actually deploy it now... but I've had enough for today!

 

setup /configure NAMEOFXMLFILE.xml will do the install.

[CHiLL]

OK, so a little bit further and more issues...

 

Got the Office Deployment Tools to extract the setup.exe and example XMLs on a share on the server. Sorted out the XML I want to use and did the CMD to download the install files... ERROR! Tried on my own PC and.... ERROR!

 

[ATTACH=CONFIG]65284[/ATTACH]

 

Went through the XML trying to see what could be stopping it removing a line and retrying and found out that if you specify a 'Source Path' location (network or local) for the deployment install files in the XML it stops the download... Made a copy of the XML called 'download' removing that and it download on my PC, so I tried it on the server. Unfortunately it only downloaded half the required files and... ERROR!

 

Looked through the firewall logs and it seems we are blocking "https://config.edge.skype.com" on the server IP and as this was denied something wasn't downloaded (I did try unblocking it, but it still didn't work and I couldn't be bothered to spend the rest of the day poking holes in the firewall so copied across what downloaded to my PC).

 

So, now I have deployment share with all the required files downloaded and a 'deployment' XML... just need to work out how I actually deploy it now... but I've had enough for today!

I remember having issues when I was trying to run it from a UNC path, where it would just error with a generic message. Instead, I had to copy the folder with setup.exe and the XML files to my local machine and run it from there. Once it downloaded, I copied the files back to the UNC folder for deployment.

 

Do you have SCCM? Because it can sort out a lot of that for you.

[Koldov]

setup /configure NAMEOFXMLFILE.xml will do the install.

 

Is that a batch file startup script?

 

I remember having issues when I was trying to run it from a UNC path, where it would just error with a generic message. Instead, I had to copy the folder with setup.exe and the XML files to my local machine and run it from there. Once it downloaded, I copied the files back to the UNC folder for deployment.

 

Do you have SCCM? Because it can sort out a lot of that for you.

 

Yeah, I have seen a few posts on here about issues running the deployment/install from a UNC, not so much the download though (maybe it's just 'one of those things' and everybody just got on with it and did what we ended up doing).

 

No SCCM unfortunately.

Edited April 21, 2022 by Koldov

[Koldov]

Also, if it is a startup batch file, how do you only get it to run once or use an 'if exist'...?

 

I've seen one on here that says 'If EXIST "C:\Program Files\Microsoft Office\Office16" goto :FINISHED' but we currently have Office 2016 installed so it does exist and obviously exits...

[Foresthippy]

If you're installing from a UNC path, use pushd:

 

pushd \\srvname\pathname

setup /configure nameofxml.xml

popd

[Koldov]

Well, looks like it's time to give up!

 

Seemed to be going fine, at least it managed to uninstall Office 2016 OK (which means it could see the share and read the XML)...

 

Then either this:

 

 

Or this:

 

 

Depending on which setup.exe I used, could be filtering but I can't find anything in the firewall logs that is blocked this time so...

Edited April 21, 2022 by Koldov

[Guest Guest]

Well, looks like it's time to give up!

 

Seemed to be going fine, well it managed to uninstall Office 2016 OK (which means it could see the share and read the XML)...

 

Then either this:

 

[ATTACH=CONFIG]65301[/ATTACH]

 

Or this:

 

[ATTACH=CONFIG]65302[/ATTACH]

 

Depending on which setup.exe I used, could be filtering but I can't find anything in the firewall logs that is blocked this time so...

Try selecting English US as the language and add English UK as an editing language (or whatever it's called) that resolved that for me

[Koldov]

Thanks, seems I've fixed it (well it has got further than before and looks like it's installing)...

 

Tried your trick on using en-us and en-gb (couldn't add en-gb as a proofing language if that's what you meant, only a second full language) but it still failed.

 

But it put me on the right track I hope... someone else had posted an XML that states ''

 

This could be something to do with having the English 'International' (yeah, right!) ISO downloaded for our Windows 10 installs, or the fact that it had an uninstall of a previous Office 2016...

 

Seems to have sorted it out, so thanks again!