1803 education build for summer (which office, 2016 or 2019 beta)

[chazzy2501]

I'm looking to deploy Windows 10 in the summer from our "Win8 office 2013" builds. It's somewhat irksome that I'm going to be putting office 2016 on the image. The 1803 edu 10 build now being tested and built will probably include 2016 but really I want 2019 as we're so close to its release.

 

It's not that I can or wouldn't change the office product when it arrives but a matter of "training". I like to introduce a new OS with a new Office and keep it that way as many users can't differentiate the two.

 

Previously it was Win7 and office 2010, then win8 2013, now win10 office 20?? probably should have done it a few years back

[3s-gtech]

It's worth bearing in mind that rolling out a brand new Office suite can cause you so many headaches that you'll wish you stuck with n-1 for twelve months. Examples can include SIMS or other MIS compatibility, full range of GPO support, bugs, bulk activation issues, major UI changes and HUP. Stick with 2016 IMO.

[synaesthesia]

Do you use 365 at all? Stick to the 365 client, so it'll always be 1. compatible and 2. relevant, so to speak. Currently its still 2016 based but will change and allow you to do the same easily with little interruption to users.

[chazzy2501]

3s-gtech this is the point, I'm using 2013 at the moment and spending the time with 2016 only to switch in a moment to 2019 seems like a pain.

 

we have access to office 365 but am not familiar with the 365 client. What is involved? (not federated)

[synaesthesia]

It's just the current version of Office, so at the moment it's 2016. There's 2 versions, the "full fat" one, and the click to run (which we use) - means users log in with their office 365 accounts, it's licensed to the logged on user.

You can do single sign on without any federation and it's very easy to do with lots of guides.

[Blue_Cookeh]

Do you use 365 at all? Stick to the 365 client, so it'll always be 1. compatible and 2. relevant, so to speak. Currently its still 2016 based but will change and allow you to do the same easily with little interruption to users.

 

This is the best move nowadays but you need to make sure you're licensed appropriately - I could be wrong but our licensing partners told us you must license Office365 CTR through EES/whatever specifically - the Office365 CTR licenses you get for free in Office365 are for personal devices only.

Edited June 6, 2018 by Blue_Cookeh

[chazzy2501]

urk, no KMS server for 2019 anyway so 2016 it is!

[Fazza]

You can do single sign on without any federation and it's very easy to do with lots of guides.

 

Do you have an links to the guides that need to be followed please?