WEBVTT 00:00:06.100 --> 00:00:10.700 Bradley 4csonline today to talk about some changes to Office 00:00:10.700 --> 00:00:15.800 365 proplus. The first thing is it's a name change Microsoft 00:00:15.800 --> 00:00:20.700 has decided to realign it with the Microsoft 365 platform 00:00:20.700 --> 00:00:24.900 and they're calling it Microsoft 365 apps in particular 00:00:24.900 --> 00:00:29.000 anytime. You see the phrase Microsoft 365 apps for Enterprise. 00:00:29.000 --> 00:00:32.400 That's the old Office 365 proplus name. 00:00:32.400 --> 00:00:33.500 So keep that in mind. 00:00:33.500 --> 00:00:38.500 Secondly, they realize that we need a little bit more stable 00:00:38.500 --> 00:00:42.600 release Channel and what we've had in the past and what do I mean 00:00:42.600 --> 00:00:47.200 by that if you launched any office suite right now and you click 00:00:47.200 --> 00:00:51.300 on account you'll see that you probably are on the the monthly 00:00:51.300 --> 00:00:54.000 release. What is the monthly release mean? 00:00:54.000 --> 00:00:57.600 It really doesn't mean it coming out monthly for say 00:00:58.600 --> 00:01:02.200 The multi release Channel always had once a month security 00:01:02.200 --> 00:01:06.000 updates. So on the second week of the month the security 00:01:06.000 --> 00:01:10.200 updates with dribble out the rest of the time and nearly once 00:01:10.200 --> 00:01:14.200 a week different feature updates different fixes with come out. 00:01:14.200 --> 00:01:18.300 So if all of a sudden your user started reporting an issue 00:01:18.300 --> 00:01:21.400 and you're like the way that it wasn't doing that last week, 00:01:21.400 --> 00:01:24.600 it's probably because a release came out. 00:01:24.600 --> 00:01:29.100 So for example here March 31st how to release April 14th, 00:01:29.100 --> 00:01:30.600 April 15th. 00:01:32.400 --> 00:01:37.300 April 29th, May 4th, May 12th, May 21st, 00:01:37.300 --> 00:01:38.400 so follow the sun. 00:01:38.400 --> 00:01:39.300 You went wait a sec. 00:01:39.300 --> 00:01:41.300 How come I'm getting these issues in last week. 00:01:41.300 --> 00:01:41.900 It was fine. 00:01:41.900 --> 00:01:46.000 It's because you actually got new releases every week. 00:01:46.000 --> 00:01:48.600 So clearly in Enterprise. 00:01:48.600 --> 00:01:52.400 We needed something different many of us including myself 00:01:52.400 --> 00:01:57.900 switch to the semi-annual update Channel what this meant was 00:01:57.900 --> 00:01:59.500 his only twice a year. 00:01:59.500 --> 00:02:01.400 I got feature releases. 00:02:02.400 --> 00:02:06.700 So I purposely went into my Office 365 deployment and said no 00:02:06.700 --> 00:02:09.300 instead of every month getting an update. 00:02:09.300 --> 00:02:14.700 I'm going to get these feature releases only twice a year know 00:02:14.700 --> 00:02:15.600 what that meant was. 00:02:16.700 --> 00:02:19.100 I didn't get the new stuff all the time. 00:02:19.100 --> 00:02:21.600 That's a good thing about thing. 00:02:21.600 --> 00:02:23.700 Obviously. I had a much more stable release, 00:02:23.700 --> 00:02:26.300 but then I couldn't take advantage of certain things. 00:02:26.300 --> 00:02:31.300 So Microsoft made the decision that enterprises we need to something 00:02:31.300 --> 00:02:34.900 a little more stable A Little Less weekly, 00:02:34.900 --> 00:02:38.400 but at the same time we got the future releases in a little 00:02:38.400 --> 00:02:42.400 more timely fashion and come up with something called monthly 00:02:42.400 --> 00:02:43.500 Enterprise release. 00:02:44.400 --> 00:02:48.900 With monthly Enterprise you get an update once a month and when I 00:02:48.900 --> 00:02:51.900 say once a month it dribbles out. 00:02:51.900 --> 00:02:56.000 So on that second week of the month when the second Tuesday 00:02:56.000 --> 00:02:59.900 releases come out for Windows 10 about the same time in the background 00:02:59.900 --> 00:03:02.700 the quick to run updates come out for Office 365. 00:03:02.700 --> 00:03:07.700 I shouldn't call it that anymore Microsoft 365 apps for Enterprise. 00:03:07.700 --> 00:03:12.100 So rather than get weekly monthly releases you're going to get 00:03:12.100 --> 00:03:16.400 once a month a stable Enterprise release. 00:03:16.400 --> 00:03:22.200 You'll still get future releases, but not weekly Cadence 00:03:22.200 --> 00:03:25.400 you've been getting before now in your organization. 00:03:25.400 --> 00:03:28.400 You may want to have some people on beta channel so you can test 00:03:28.400 --> 00:03:28.900 out things. 00:03:29.800 --> 00:03:31.500 I need to call The Insider Edition. 00:03:31.500 --> 00:03:36.900 You can sign up for these Office 365 / Microsoft 365 Insider 00:03:36.900 --> 00:03:41.500 editions and get these pre-release versions and actually 00:03:41.500 --> 00:03:43.200 see what's coming in in advance. 00:03:44.600 --> 00:03:47.900 You can choose your default software settings in one of two ways. 00:03:47.900 --> 00:03:51.100 If you go into the Microsoft 365 admin Center. 00:03:52.100 --> 00:03:56.300 Going to settings or settings and find the office software 00:03:56.300 --> 00:03:59.800 download settings. You can change what the default will be. 00:03:59.800 --> 00:04:02.000 And here's these new channels. 00:04:03.400 --> 00:04:06.600 So the first one is the default if you don't choose anything 00:04:06.600 --> 00:04:11.100 else monthly channel comes out several updates during the month 00:04:11.100 --> 00:04:14.900 the next the new one, which is called the monthly Enterprise 00:04:14.900 --> 00:04:18.400 Channel starts tripping out on the second Tuesday of the month. 00:04:20.000 --> 00:04:24.700 Finally, there's someone that up until now I've chosen at the 00:04:24.700 --> 00:04:28.300 semi-annual Channel where you'll still get security updates 00:04:28.300 --> 00:04:33.500 every month, but the future releases only come out twice a year, 00:04:33.500 --> 00:04:34.500 January and July. 00:04:37.000 --> 00:04:40.200 The monthly Enterprise channel is available starting May 12th, 00:04:40.200 --> 00:04:42.800 2020 on June 9th. 00:04:42.800 --> 00:04:45.600 There are several other channel attributes that can be used 00:04:45.600 --> 00:04:50.400 in deployment beta Channel, which is used to be called Insider 00:04:50.400 --> 00:04:54.700 fast current Channel preview used to be called Insiders. 00:04:55.600 --> 00:04:59.900 Current Channel used to be called monthly monthly Enterprise 00:04:59.900 --> 00:05:01.600 Channel. That's a brand new one. 00:05:02.800 --> 00:05:07.300 Semi annual Enterprise Channel preview used to be called targeted. 00:05:08.200 --> 00:05:11.700 Semi annual Enterprise Channel used to be called broad. 00:05:11.700 --> 00:05:15.100 I know a little bit confusing but it is what it is. 00:05:16.700 --> 00:05:19.700 Remember starting on June 9th, you'll have to download a brand new 00:05:19.700 --> 00:05:23.200 office deployment tool and use that in your configuration 00:05:23.200 --> 00:05:23.900 files. 00:05:26.100 --> 00:05:29.100 And here in the configuration file is where you specify what 00:05:29.100 --> 00:05:33.500 channel and again this is using the old naming broad was the 00:05:33.500 --> 00:05:37.700 old name of the channel and the current new one will be called 00:05:37.700 --> 00:05:42.400 semiannual and it's here in this configuration that you specify 00:05:42.400 --> 00:05:46.800 what channel you're going to choose your deployment what you 00:05:46.800 --> 00:05:51.100 might want to do for some of your organization pick out some 00:05:51.100 --> 00:05:52.700 that will be on Insider fast. 00:05:52.700 --> 00:05:53.800 That's the preview one. 00:05:53.800 --> 00:05:56.800 I wouldn't suggest doing that for production. 00:05:58.000 --> 00:06:01.800 Next I would suggest some people on monthly. 00:06:03.100 --> 00:06:07.100 again, I consider that more of a beta Channel and then finally 00:06:08.300 --> 00:06:10.200 you can test out monthly Enterprise. 00:06:12.000 --> 00:06:15.300 Along with semiannual and then the article and see you. 00:06:15.300 --> 00:06:18.100 So online I have several links for release notes for these 00:06:18.100 --> 00:06:22.000 multi-channel releases and the semi-annual to releases you want 00:06:22.000 --> 00:06:25.000 to bookmark these to know what being released in each Persian 00:06:25.000 --> 00:06:27.900 and don't forget that you can use delivery optimization 00:06:27.900 --> 00:06:29.800 in office click-to-run as well. 00:06:29.800 --> 00:06:34.100 Remember those click-to-run versions are pretty big and what 00:06:34.100 --> 00:06:37.300 delivery optimization allows you to do is share the bandwidth 00:06:37.300 --> 00:06:38.900 amongst your workstations. 00:06:38.900 --> 00:06:44.000 So rather than every single workstation pulling down gigabytes 00:06:44.000 --> 00:06:44.200 of data. 00:06:45.600 --> 00:06:46.900 One or two can bring it down. 00:06:48.500 --> 00:06:52.500 And then the rest can share in that payload as long as you have 00:06:52.500 --> 00:06:55.700 version 1808 you can use this for background updates. 00:06:57.400 --> 00:06:59.800 If you have Windows 10 Enterprise or Windows 10 education 00:06:59.800 --> 00:07:04.900 editions delivery optimization is enabled by default for Virgin 00:07:04.900 --> 00:07:07.700 1912 or later of Microsoft 365 apps. 00:07:07.700 --> 00:07:12.600 No additional configuration is needed there ready to go 1908 00:07:12.600 --> 00:07:15.700 through 1911 version of Microsoft 365 apps. 00:07:15.700 --> 00:07:18.600 You need to configure a register Kiana's devices. 00:07:19.800 --> 00:07:22.600 And last but not least for anyone using configuration 00:07:22.600 --> 00:07:27.500 manager. You may need to review your changing automatic 00:07:27.500 --> 00:07:31.100 2.8 rules used by configuration manager. 00:07:31.100 --> 00:07:34.800 If you've used any specific title in your name and in the title 00:07:34.800 --> 00:07:38.900 properties, you may need to go back and revisit it if use the 00:07:38.900 --> 00:07:42.000 naming Office 365 client update in your packages. 00:07:42.000 --> 00:07:45.900 You're going to have to rename them to Microsoft Office 365 apps 00:07:45.900 --> 00:07:49.500 update again review you were deployment and what you've done 00:07:49.500 --> 00:07:52.900 in the past and you may need to go back and revisit it Powershell 00:07:52.900 --> 00:07:54.000 script should be fine. 00:07:54.000 --> 00:07:59.000 But you may need to also review any registry key values that 00:07:59.000 --> 00:08:02.700 you go back and review your Office 365 or rather Microsoft 00:08:02.700 --> 00:08:08.300 365 app settings check what channel you want to choose re-evaluate 00:08:08.300 --> 00:08:09.900 what you might need for your organization, 00:08:09.900 --> 00:08:14.200 especially now with with everyone working from home and making 00:08:14.200 --> 00:08:17.100 all the changes we've been doing so take the time to review 00:08:17.100 --> 00:08:18.900 and see what setting you want. 00:08:19.600 --> 00:08:25.200 And always remember we're out here on the it dgtech talk YouTube 00:08:25.200 --> 00:08:29.100 channel with the latest news of the day and see you next time. 00:08:29.100 --> 00:08:30.900 This is Susan Bradley for CSO online.