WEBVTT FILE 1 00:00:04.500 --> 00:00:05.000 Hi, I'm Jason Githens, 2 00:00:05.500 --> 00:00:09.000 a Principal Program Manager Leadon the Enterprise Client team. 3 00:00:09.500 --> 00:00:11.000 And today, I'm going to betalking about accelerating your 4 00:00:11.500 --> 00:00:16.000 Windows 10 deployment at scaleusing the management products 5 00:00:16.500 --> 00:00:19.000 of System Center ConfigurationManager combined with Intune. 6 00:00:19.500 --> 00:00:22.000 So, let's jump right in. 7 00:00:22.500 --> 00:00:24.000 So the objectives andtakeaways for 8 00:00:24.500 --> 00:00:28.000 today are really about choosingthe best deployment options for 9 00:00:28.500 --> 00:00:31.000 your organization to get toWindows 10, keeping Windows 10 10 00:00:31.500 --> 00:00:35.000 up to date, and then managingthose key enterprise features 11 00:00:35.500 --> 00:00:39.000 of Windows 10, and enhancingproductivity while you do that. 12 00:00:39.500 --> 00:00:45.000 So let's move onthrough the slide deck. 13 00:00:45.500 --> 00:00:48.000 So what's driving change here? 14 00:00:48.500 --> 00:00:52.000 What's driving change inthe way that we use devices, 15 00:00:52.500 --> 00:00:53.000 the way that we manage devices, 16 00:00:53.500 --> 00:00:57.000 is really aroundthe devices being anywhere. 17 00:00:57.500 --> 00:01:00.000 Devices are on the Internet,devices are in pockets, 18 00:01:00.500 --> 00:01:03.000 devices are still oncorporate networks as well. 19 00:01:03.500 --> 00:01:06.000 Between the user andthe devices, there are apps, 20 00:01:06.500 --> 00:01:07.000 there's data. 21 00:01:07.500 --> 00:01:09.000 Then the IT departmentis accountable for 22 00:01:09.500 --> 00:01:13.000 making sure that those devicesare secure, that data is secure, 23 00:01:13.500 --> 00:01:16.000 and it's a rapidly evolvingecosystem with users 24 00:01:16.500 --> 00:01:19.000 getting new devices,new platforms. 25 00:01:19.500 --> 00:01:24.000 And Microsoft's reaction tothis is really around providing 26 00:01:24.500 --> 00:01:29.000 all the tools that IT needs atthe cadence they need them to be 27 00:01:29.500 --> 00:01:33.000 successful managing the newworld of mobile devices, 28 00:01:33.500 --> 00:01:37.000 the new world of managementof these devices, and 29 00:01:37.500 --> 00:01:40.000 protecting dataon these devices. 30 00:01:40.500 --> 00:01:44.000 With Windows 10, the significantinvestments for business around 31 00:01:44.500 --> 00:01:48.000 protection against modernsecurity threats, managed for 32 00:01:48.500 --> 00:01:52.000 continuous innovation to notonly benefit the end-user. 33 00:01:52.500 --> 00:01:56.000 But to enable the IT pro toprotect those devices and 34 00:01:56.500 --> 00:01:59.000 the data on thosedevices as the ecosystem 35 00:01:59.500 --> 00:02:04.000 of technology evolves in a waythat is on a rapid cadence. 36 00:02:04.500 --> 00:02:07.000 And Windows,as well as the management tools, 37 00:02:07.500 --> 00:02:11.000 the Microsoft management toolsaround Windows, need to evolve 38 00:02:11.500 --> 00:02:14.000 in that rapid cadence andconstantly design for 39 00:02:14.500 --> 00:02:17.000 innovation to make devicesthat users love to use and 40 00:02:17.500 --> 00:02:22.000 make devices that IT departmentsare able to manage and protect. 41 00:02:22.500 --> 00:02:24.000 Also, there's enhancedproductivity. 42 00:02:24.500 --> 00:02:28.000 It's an investment for businessthrough the business store, 43 00:02:28.500 --> 00:02:31.000 as well as the universal appsin the business store and 44 00:02:31.500 --> 00:02:32.000 then delivering thosebusiness store apps, 45 00:02:32.500 --> 00:02:36.000 as an example, throughthe Microsoft management tools. 46 00:02:36.500 --> 00:02:39.000 Finally, there's innovativedevices for your business. 47 00:02:39.500 --> 00:02:42.000 There's multiple device types,multiple form factors. 48 00:02:42.500 --> 00:02:45.000 There are devices that are meantto make the information worker 49 00:02:45.500 --> 00:02:49.000 successful, devices for the taskworker, for the assembly line. 50 00:02:49.500 --> 00:02:50.000 Multiple devices and 51 00:02:50.500 --> 00:02:53.000 multiple ways to manage thosedevices using Windows 10 and 52 00:02:53.500 --> 00:02:57.000 the Microsoft ManagementSolutions on top of Windows 10, 53 00:02:57.500 --> 00:03:00.000 specifically System CenterConfiguration Manager combined 54 00:03:00.500 --> 00:03:05.000 with Intune. 55 00:03:05.500 --> 00:03:10.000 So the Enterprise Mobility Suiteis the suite of management 56 00:03:10.500 --> 00:03:13.000 solutions that layer on topof Windows 10 to provide 57 00:03:13.500 --> 00:03:18.000 a unified identity model throughAzure Active Directory Premium, 58 00:03:18.500 --> 00:03:23.000 for managing applications anddevices through Intune, and for 59 00:03:23.500 --> 00:03:27.000 protecting data throughAzure Remote, Azure RMS. 60 00:03:27.500 --> 00:03:30.000 Another piece of the EMS,the overall EMS suite, 61 00:03:30.500 --> 00:03:33.000 is also System CenterConfiguration Manager, 62 00:03:33.500 --> 00:03:38.000 because that's the foundationalon premises PC agent management 63 00:03:38.500 --> 00:03:41.000 tool in use by predominatelythe enterprise today. 64 00:03:41.500 --> 00:03:45.000 And there's the connectivetissue between systems in our 65 00:03:45.500 --> 00:03:48.000 Configuration Manager andIntune, along with the other 66 00:03:48.500 --> 00:03:52.000 pieces of EMS, provide an allencompassing management suite 67 00:03:52.500 --> 00:03:56.000 that traverses the on-premisesrequirements of today and paints 68 00:03:56.500 --> 00:04:00.000 the path towards the cloudmanagement model of the future. 69 00:04:00.500 --> 00:04:03.000 While providing customersthe ability to pick and 70 00:04:03.500 --> 00:04:06.000 choose from a flexiblearchitecture to manage devices 71 00:04:06.500 --> 00:04:10.000 where they live and the waythat you want to manage them. 72 00:04:10.500 --> 00:04:15.000 And I'll get into thata little bit more. 73 00:04:15.500 --> 00:04:17.000 So enhancing the Windows10 experience with EMS, 74 00:04:17.500 --> 00:04:20.000 it really startswith deployment. 75 00:04:20.500 --> 00:04:22.000 Deployment with Windows10 provides a number of 76 00:04:22.500 --> 00:04:26.000 options to get business,get Windows 10 business ready. 77 00:04:26.500 --> 00:04:29.000 For the first step, like rightout of the box, you can use 78 00:04:29.500 --> 00:04:33.000 Azure Active Directory Join andauto enrollment into Intune or 79 00:04:33.500 --> 00:04:35.000 a hybrid configurationof Intune and 80 00:04:35.500 --> 00:04:38.000 Systems in our ConfigurationManager plus Intune. 81 00:04:38.500 --> 00:04:43.000 And you can achieve the out ofbox experience where a user gets 82 00:04:43.500 --> 00:04:43.000 a device, 83 00:04:43.500 --> 00:04:46.000 they open it up, they put intheir corporate credentials. 84 00:04:46.500 --> 00:04:49.000 It auto registers withAzure Active Directory and 85 00:04:49.500 --> 00:04:51.000 auto enrolls into Intune. 86 00:04:51.500 --> 00:04:52.000 Policies andapps start flowing, and 87 00:04:52.500 --> 00:04:55.000 the user can startdoing work right away. 88 00:04:55.500 --> 00:04:56.000 Additionally, there'sa new model for 89 00:04:56.500 --> 00:04:59.000 provisioning calledthe provisioning package. 90 00:04:59.500 --> 00:05:01.000 There's an authoring tool forthe provisioning package 91 00:05:01.500 --> 00:05:05.000 whereby the IT pro can authora configuration standard for 92 00:05:05.500 --> 00:05:09.000 their devices andinject that into the devices. 93 00:05:09.500 --> 00:05:13.000 So that they boot up Intune andstart life against, 94 00:05:13.500 --> 00:05:17.000 with a corporate configuration,as defined by the IT department. 95 00:05:17.500 --> 00:05:21.000 And finally, there is in placeupgrade of Windows 10 of your 96 00:05:21.500 --> 00:05:25.000 existing devices,your Windows 7, 8, 8.1 PCs, 97 00:05:25.500 --> 00:05:29.000 that you can use the ConfigManager agent to upgrade those. 98 00:05:29.500 --> 00:05:31.000 An upgrade is nowa first class citizen. 99 00:05:31.500 --> 00:05:32.000 And I'll talk about that. 100 00:05:32.500 --> 00:05:36.000 Whereby you can use a powerfulnew upgrade process to greatly 101 00:05:36.500 --> 00:05:39.000 reduce the barriers toadoption of Windows 10 for 102 00:05:39.500 --> 00:05:43.000 your install base of Windows 7,8, and 8.1 clients. 103 00:05:43.500 --> 00:05:45.000 Alongside those options,of course, 104 00:05:45.500 --> 00:05:49.000 there are traditional models ofwipe and load using the Windows 105 00:05:49.500 --> 00:05:52.000 80k and the operatingsystem deployment tool and 106 00:05:52.500 --> 00:05:55.000 Systems CenterConfiguration Manager, and 107 00:05:55.500 --> 00:05:58.000 the traditional ways ofdoing image management, 108 00:05:58.500 --> 00:06:01.000 along with the Microsoftdeployment toolkit, MDT. 109 00:06:01.500 --> 00:06:06.000 So for configuring Windows 10,there are expansive windows MDM 110 00:06:06.500 --> 00:06:10.000 settings exposed for managementin Windows 10, across SKUs, 111 00:06:10.500 --> 00:06:14.000 across mobile andX86 versions of Windows. 112 00:06:14.500 --> 00:06:17.000 There are other things likePirep VPN, Microsoft Passport 113 00:06:17.500 --> 00:06:21.000 policies to simplify and secureauthentication on the device. 114 00:06:21.500 --> 00:06:24.000 There's Windows Universalapps and 115 00:06:24.500 --> 00:06:26.000 Win32 app supportthrough the MDM channel. 116 00:06:26.500 --> 00:06:28.000 And there's also support for 117 00:06:28.500 --> 00:06:34.000 volume purchase apps throughthe Windows Store for Business. 118 00:06:34.500 --> 00:06:37.000 For management and protection,there's a great new security 119 00:06:37.500 --> 00:06:40.000 feature of Enterprise DataProtection to prevent data 120 00:06:40.500 --> 00:06:41.000 leakage on devices and 121 00:06:41.500 --> 00:06:45.000 manage applications directlyfrom the platform, including new 122 00:06:45.500 --> 00:06:49.000 applications as well as yourlegacy Win 32 applications. 123 00:06:49.500 --> 00:06:53.000 RMS integration adds anotherlayer of file security as part 124 00:06:53.500 --> 00:06:54.000 of the EMS suite. 125 00:06:54.500 --> 00:06:58.000 Additionally, there is DeviceGuard and AppLocker policies. 126 00:06:58.500 --> 00:07:01.000 Device Guard provides the toolswhereby you can fully lock down 127 00:07:01.500 --> 00:07:04.000 a system to run onlyapproved applications and 128 00:07:04.500 --> 00:07:06.000 that works fromthe boot level up. 129 00:07:06.500 --> 00:07:09.000 We also have the abilitywith existing versions of 130 00:07:09.500 --> 00:07:12.000 Config Manager toconfigure Device Guard, 131 00:07:12.500 --> 00:07:15.000 apply those policies, andinstall those applications that 132 00:07:15.500 --> 00:07:17.000 are inherent toDevice Guard policies. 133 00:07:17.500 --> 00:07:22.000 And we can search for a blogon that, which is coming out, 134 00:07:22.500 --> 00:07:26.000 which will explain how to dothat with Configuration Manager. 135 00:07:26.500 --> 00:07:29.000 There's advanced conditionalaccess policies, which gates 136 00:07:29.500 --> 00:07:33.000 access to office resources byconditions of compliance and 137 00:07:33.500 --> 00:07:36.000 management, which works acrossour ecosystem of management 138 00:07:36.500 --> 00:07:40.000 through MDM enrollment throughIntune and Configuration Manager 139 00:07:40.500 --> 00:07:44.000 agent based management throughConfiguration Manager. 140 00:07:44.500 --> 00:07:46.000 Additionally, there'smeasures for 141 00:07:46.500 --> 00:07:49.000 integration with WindowsHealth Attestation Service. 142 00:07:49.500 --> 00:07:53.000 Health Attestation Serviceprovides rigid compliance, 143 00:07:53.500 --> 00:07:57.000 validation of the clientas it talks to a health, 144 00:07:57.500 --> 00:08:01.000 a cloud service to validate thestructural health of the client. 145 00:08:01.500 --> 00:08:03.000 Which can also be a form, 146 00:08:03.500 --> 00:08:07.000 can also be a part of theconditional access model gating 147 00:08:07.500 --> 00:08:11.000 access to resources on thathealth attestation state that 148 00:08:11.500 --> 00:08:16.000 comes back from the cloudservice for health attestation. 149 00:08:16.500 --> 00:08:18.000 And finally, there isunify device management. 150 00:08:18.500 --> 00:08:23.000 Unify device management isa key differentiator of the EMS 151 00:08:23.500 --> 00:08:28.000 suite plus SDCM in thatit provides a pathway for 152 00:08:28.500 --> 00:08:32.000 your implementation ofConfiguration Manager to 153 00:08:32.500 --> 00:08:37.000 help you get to Windows 10 andthe flexibility to use both 154 00:08:37.500 --> 00:08:41.000 the agent based management ofConfiguration Manager along with 155 00:08:41.500 --> 00:08:44.000 the connector to Intune for yourmobile device management story. 156 00:08:44.500 --> 00:08:48.000 Expanded by the EnterpriseMobility Suite to cover things 157 00:08:48.500 --> 00:08:52.000 like identity through AzureActive Directory Premium and 158 00:08:52.500 --> 00:08:55.000 data protectionthrough Azure RMS. 159 00:08:55.500 --> 00:08:58.000 And new inConfiguration Manager, 160 00:08:58.500 --> 00:09:01.000 it's faster to upgradeto the new version, 161 00:09:01.500 --> 00:09:04.000 we support Windows 10 servicingfor the Windows as a service 162 00:09:04.500 --> 00:09:07.000 model which I'll talka lot about today. 163 00:09:07.500 --> 00:09:10.000 And we provide on premisesMBM for Windows 10 for 164 00:09:10.500 --> 00:09:14.000 those business critical devicesthat perhaps you don't want 165 00:09:14.500 --> 00:09:15.000 talking to the cloud, 166 00:09:15.500 --> 00:09:19.000 you can enroll those directlyinto Configuration Manager. 167 00:09:19.500 --> 00:09:22.000 And get mobile device managementcapabilities on those on 168 00:09:22.500 --> 00:09:26.000 premises devices withoutthe device talking to the cloud. 169 00:09:26.500 --> 00:09:29.000 Now that does requirean Intune subscription but it 170 00:09:29.500 --> 00:09:34.000 doesn't mean that the device hasto actually go out to the cloud. 171 00:09:34.500 --> 00:09:37.000 So a little bit about ourflexible management options. 172 00:09:37.500 --> 00:09:39.000 We have on the left handside here our Intune 173 00:09:39.500 --> 00:09:41.000 standalone model. 174 00:09:41.500 --> 00:09:42.000 And that's purely cloud. 175 00:09:42.500 --> 00:09:45.000 That's our cloud based modelthat can do mobile device 176 00:09:45.500 --> 00:09:49.000 management along with a coupleof all the other pieces of EMS 177 00:09:49.500 --> 00:09:52.000 and provide you thingslike conditional access, 178 00:09:52.500 --> 00:09:56.000 mobile application management,etc, purely from the cloud. 179 00:09:56.500 --> 00:10:00.000 No on premises hardware requiredfor that configuration. 180 00:10:00.500 --> 00:10:02.000 Then there's the ConfigMgrintegrated with Intune, 181 00:10:02.500 --> 00:10:04.000 which we often call ourhybrid configuration. 182 00:10:04.500 --> 00:10:09.000 Our hybrid configuration is agreat flexible deployment option 183 00:10:09.500 --> 00:10:13.000 that lets you take your existinginstalled base of agent-based 184 00:10:13.500 --> 00:10:17.000 Windows 7, 8, 8.1, the PCs,get them to Windows 10. 185 00:10:17.500 --> 00:10:20.000 It has the flexibility to extendthat perimeter to the cloud 186 00:10:20.500 --> 00:10:24.000 to manage those devicesthrough MDM, Windows 10, and 187 00:10:24.500 --> 00:10:27.000 other platforms throughthe Intune side of the service, 188 00:10:27.500 --> 00:10:30.000 which manages deviceswhere they typically live, 189 00:10:30.500 --> 00:10:33.000 which is often not onthe corporate network. 190 00:10:33.500 --> 00:10:36.000 It's often roaming,roaming on the public Internet. 191 00:10:36.500 --> 00:10:39.000 So the flexible configurationoption here really provides 192 00:10:39.500 --> 00:10:42.000 a way to manage devices thatbest suits your organization 193 00:10:42.500 --> 00:10:46.000 through a combination of mobiledevice management on the Intune 194 00:10:46.500 --> 00:10:48.000 side of this hybridconfiguration, 195 00:10:48.500 --> 00:10:51.000 to the agent-based managementstyle of Configuration Manager 196 00:10:51.500 --> 00:10:54.000 on the on-premises sideof this configuration. 197 00:10:54.500 --> 00:10:58.000 Additionally, ConfigurationManager agent-based management 198 00:10:58.500 --> 00:11:01.000 is a great pathway toget your existing 7, 8, 199 00:11:01.500 --> 00:11:06.000 8.1 devices to Windows 10. 200 00:11:06.500 --> 00:11:08.000 So how should youdeploy Windows 10? 201 00:11:08.500 --> 00:11:12.000 There are multiple methodswhich I've touched on, so 202 00:11:12.500 --> 00:11:14.000 I'll cover a little bitmore in depth here. 203 00:11:14.500 --> 00:11:17.000 There's the traditional model,where you take an existing 204 00:11:17.500 --> 00:11:20.000 device or new device,we often call bare metal, and 205 00:11:20.500 --> 00:11:24.000 you use imaging tools likeMicrosoft Deployment Toolkit or 206 00:11:24.500 --> 00:11:28.000 Operating System Deployment andConfiguration Manager, and 207 00:11:28.500 --> 00:11:30.000 you effectively wipe andload the device. 208 00:11:30.500 --> 00:11:34.000 You wipe the old image, loada new image, and you basically 209 00:11:34.500 --> 00:11:38.000 move data, you protect it or yousave data, and you put the data 210 00:11:38.500 --> 00:11:42.000 back on the device after thatwipe and load is complete. 211 00:11:42.500 --> 00:11:44.000 You can also inject drivers,install applications, etc. 212 00:11:44.500 --> 00:11:48.000 It's a traditional way of doinga Windows deployment supported 213 00:11:48.500 --> 00:11:52.000 by Configuration Manager todayand with the vNext version, 214 00:11:52.500 --> 00:11:56.000 as well as the MicrosoftDeployment Toolkit. 215 00:11:56.500 --> 00:11:58.000 There's an improvedprocess here, 216 00:11:58.500 --> 00:12:01.000 which I touched onearlier around upgrade. 217 00:12:01.500 --> 00:12:05.000 Upgrade is great forexpediting the time it 218 00:12:05.500 --> 00:12:09.000 takes to deploythe upgrade to Windows 10. 219 00:12:09.500 --> 00:12:13.000 It also doesn't have all ofthe overhead around driver 220 00:12:13.500 --> 00:12:17.000 validation, or gettingthe right drivers back down, or 221 00:12:17.500 --> 00:12:20.000 the application validation. 222 00:12:20.500 --> 00:12:22.000 It preserves statethrough the process, and 223 00:12:22.500 --> 00:12:23.000 it truly is an upgrade. 224 00:12:23.500 --> 00:12:26.000 And we've done a number ofinvestments working with Windows 225 00:12:26.500 --> 00:12:29.000 to make upgrade a first-classcitizen in getting to 226 00:12:29.500 --> 00:12:30.000 Windows 10. 227 00:12:30.500 --> 00:12:33.000 And that's inclusive, as I'vesaid, Windows 7, 8, 8.1 to 10, 228 00:12:33.500 --> 00:12:35.000 through the upgrade process, and 229 00:12:35.500 --> 00:12:38.000 I'll talk a little bit moreabout the value of upgrade. 230 00:12:38.500 --> 00:12:41.000 Then there's the modernways to do it. 231 00:12:41.500 --> 00:12:46.000 Modern ways are really aboutthe two paths to modern 232 00:12:46.500 --> 00:12:50.000 provisioning of Windows andthat's the IT Pro provisioning. 233 00:12:50.500 --> 00:12:53.000 And there are a couple of toolsthe IT Pro can use there, 234 00:12:53.500 --> 00:12:57.000 both based on the conceptof a provisioning package. 235 00:12:57.500 --> 00:13:00.000 A provisioning package isan instruction set that the PC 236 00:13:00.500 --> 00:13:03.000 takes or the device takes andexecutes at reboot, 237 00:13:03.500 --> 00:13:06.000 and it applies all theconfigurations embedded in that 238 00:13:06.500 --> 00:13:09.000 instruction set, which isthe provisioning package. 239 00:13:09.500 --> 00:13:14.000 Additionally, we have a lighterform of the provisioning profile 240 00:13:14.500 --> 00:13:16.000 built intoconfiguration manager, 241 00:13:16.500 --> 00:13:20.000 which can boot-strap theenrollment of the device into 242 00:13:20.500 --> 00:13:24.000 directly into on-prem MDMthrough Configuration Manager, 243 00:13:24.500 --> 00:13:27.000 or through Intune ina hybrid configuration. 244 00:13:27.500 --> 00:13:31.000 And what that is, is we callthat our life-line profile, 245 00:13:31.500 --> 00:13:33.000 which gets the deviceon the network and 246 00:13:33.500 --> 00:13:37.000 it also enrolls the device intothe appropriate management 247 00:13:37.500 --> 00:13:40.000 authority of your choosing. 248 00:13:40.500 --> 00:13:43.000 And I'll click through thatexample in a little bit. 249 00:13:43.500 --> 00:13:46.000 The other piece here to mentionis, that I talked a little bit 250 00:13:46.500 --> 00:13:48.000 about earlier,is that out-of-box experience, 251 00:13:48.500 --> 00:13:52.000 where a user can open a box, putin their corporate credentials, 252 00:13:52.500 --> 00:13:54.000 register with Azure ActiveDirectory, which auto-enrolls 253 00:13:54.500 --> 00:13:58.000 into Intune, and policies andapplications start flowing down. 254 00:13:58.500 --> 00:14:02.000 The user can go from the boxto productive in a very short 255 00:14:02.500 --> 00:14:06.000 amount of time. 256 00:14:06.500 --> 00:14:09.000 So thinking about deploying andmanaging Windows 10, 257 00:14:09.500 --> 00:14:11.000 we have all these options now. 258 00:14:11.500 --> 00:14:14.000 What's the best option for you? 259 00:14:14.500 --> 00:14:17.000 This is a simplified diagramof the ways to think about 260 00:14:17.500 --> 00:14:18.000 deploying Windows 10. 261 00:14:18.500 --> 00:14:21.000 This isn't all of the options. 262 00:14:21.500 --> 00:14:24.000 There are multiple that reallyhighlighted in the previous 263 00:14:24.500 --> 00:14:26.000 slide, but this is a wayto think about the value of 264 00:14:26.500 --> 00:14:29.000 the flexible architectureof Configuration Manager 265 00:14:29.500 --> 00:14:32.000 combined with Intune,combined with EMS. 266 00:14:32.500 --> 00:14:36.000 If you take, for example,your existing Windows 7, 267 00:14:36.500 --> 00:14:41.000 8, 8.1 devices, they have Win32apps with loads of dependencies, 268 00:14:41.500 --> 00:14:45.000 a lot of LOB applications,complex applications that 269 00:14:45.500 --> 00:14:48.000 Large Application Suites alreadyconverted to the ConfigMgr 270 00:14:48.500 --> 00:14:52.000 app model and their ConfigMgragent based managed today. 271 00:14:52.500 --> 00:14:56.000 Then an ideal path there, ora path to really consider, 272 00:14:56.500 --> 00:14:59.000 is the upgrade path toWindows 10 with ConfigMgr. 273 00:14:59.500 --> 00:15:04.000 The upgrade path preservesyour apps in configuration and 274 00:15:04.500 --> 00:15:07.000 it maintains the managementprocesses, tools, prints and 275 00:15:07.500 --> 00:15:09.000 principles that you have today. 276 00:15:09.500 --> 00:15:12.000 What I mean by that is that itminimizes the change control 277 00:15:12.500 --> 00:15:15.000 that you have to go through tochange your management style 278 00:15:15.500 --> 00:15:20.000 from agent base to MDM, or goingthrough a full wipe and load 279 00:15:20.500 --> 00:15:23.000 process, which we all know takesa lot of time to prepare for. 280 00:15:23.500 --> 00:15:26.000 So it's a fast path to getyour existing ecosystem to 281 00:15:26.500 --> 00:15:27.000 Windows 10. 282 00:15:27.500 --> 00:15:31.000 And it's also an on rampto the cloud over time. 283 00:15:31.500 --> 00:15:33.000 With our flexible architecture, 284 00:15:33.500 --> 00:15:37.000 we have both MDM capabilitieson-prem through Intune via 285 00:15:37.500 --> 00:15:40.000 the connector ina hybrid configuration. 286 00:15:40.500 --> 00:15:43.000 And agent based, you reallyhave the management style, 287 00:15:43.500 --> 00:15:46.000 you can move to the managementstyle of your choosing at 288 00:15:46.500 --> 00:15:48.000 the cadence you choose. 289 00:15:48.500 --> 00:15:51.000 For example,you may have users that use 290 00:15:51.500 --> 00:15:55.000 predominantly universalapplications from the store. 291 00:15:55.500 --> 00:15:57.000 They are rarely onthe corporate network, 292 00:15:57.500 --> 00:15:59.000 they're often traveling, and 293 00:15:59.500 --> 00:16:02.000 they'd be the ideal candidatesto move to a mobile device 294 00:16:02.500 --> 00:16:05.000 management solution whenthey get to Windows 10. 295 00:16:05.500 --> 00:16:08.000 Then you may have a department,like a treasury department, 296 00:16:08.500 --> 00:16:09.000 which never leaves the office, 297 00:16:09.500 --> 00:16:11.000 dealing with highlysensitive data, 298 00:16:11.500 --> 00:16:14.000 uses a ton of line of businessapplications that are Win32 299 00:16:14.500 --> 00:16:15.000 based with complex dependencies. 300 00:16:15.500 --> 00:16:19.000 They may be users that youdon't move right away to cloud 301 00:16:19.500 --> 00:16:21.000 management ormobile device management, 302 00:16:21.500 --> 00:16:24.000 where the agent based modelmakes the most sense. 303 00:16:24.500 --> 00:16:28.000 So the main point to makeis that with the flexible 304 00:16:28.500 --> 00:16:31.000 architecture, you canmanage the devices the way 305 00:16:31.500 --> 00:16:33.000 that your businesswants to manage them 306 00:16:33.500 --> 00:16:36.000 given the standardsthat you have. 307 00:16:36.500 --> 00:16:41.000 And you have the mobility andflexibility to move to different 308 00:16:41.500 --> 00:16:44.000 management styles over time ata cadence of your choosing. 309 00:16:44.500 --> 00:16:46.000 But with ConfigMgr foundation, 310 00:16:46.500 --> 00:16:50.000 that's a great bootstrapperto get you to Windows 10. 311 00:16:50.500 --> 00:16:54.000 And then with the flexiblearchitecture combined with 312 00:16:54.500 --> 00:16:57.000 Intune and EMS provides an entrypoint to the cloud using 313 00:16:57.500 --> 00:17:01.000 the same configuration thatyou have today optimized for 314 00:17:01.500 --> 00:17:03.000 that Intune connector. 315 00:17:03.500 --> 00:17:06.000 Then at the bottom of thisis just an example which 316 00:17:06.500 --> 00:17:07.000 I mentioned earlier, 317 00:17:07.500 --> 00:17:10.000 the new Windows device shows up,a new Windows device 318 00:17:10.500 --> 00:17:12.000 that's not pre-existingin your environment. 319 00:17:12.500 --> 00:17:14.000 And you can hand thatout to the user, 320 00:17:14.500 --> 00:17:17.000 who can use theircorporate credentials and 321 00:17:17.500 --> 00:17:19.000 chose this asa corporate-owned device. 322 00:17:19.500 --> 00:17:22.000 And, like I mentioned,enroll directly into Intune or 323 00:17:22.500 --> 00:17:23.000 a hybrid configuration. 324 00:17:23.500 --> 00:17:27.000 Or you can take a provisioningpackage, put that on the device, 325 00:17:27.500 --> 00:17:28.000 reboot it and 326 00:17:28.500 --> 00:17:33.000 get to the default standardconfiguration at first boot. 327 00:17:33.500 --> 00:17:35.000 And then you can managethose devices with MDM. 328 00:17:35.500 --> 00:17:38.000 You can take advantage ofthe great new universal apps in 329 00:17:38.500 --> 00:17:41.000 the Windows Store for Business,and there's even some basic MSI 330 00:17:41.500 --> 00:17:45.000 support with MDM there forthose well written MSIs that 331 00:17:45.500 --> 00:17:48.000 don't have a big dependency,don't have a dependency chain, 332 00:17:48.500 --> 00:17:51.000 that you want to executean MSI installation on. 333 00:17:51.500 --> 00:17:54.000 So as you can see, the modelsare starting to converge, but 334 00:17:54.500 --> 00:17:57.000 there will still be paths thatyou would choose that will 335 00:17:57.500 --> 00:17:59.000 be optimized for your business. 336 00:17:59.500 --> 00:18:01.000 And we want to give youthe flexibility to use 337 00:18:01.500 --> 00:18:03.000 the architecture that makesthe most sense for you. 338 00:18:03.500 --> 00:18:07.000 So let's talk a little bit aboutin-place upgrade with ConfigMgr. 339 00:18:07.500 --> 00:18:10.000 The main value of in-placeupgrade is that, well, 340 00:18:10.500 --> 00:18:11.000 it's three-fold. 341 00:18:11.500 --> 00:18:15.000 It reduces upfront testing,it's faster, and has more robust 342 00:18:15.500 --> 00:18:20.000 robot capabilities,as well as, it's really 343 00:18:20.500 --> 00:18:24.000 another tool in your toolbox fordeploying Windows 10. 344 00:18:24.500 --> 00:18:27.000 There, you'll still havecases where wipe unload or 345 00:18:27.500 --> 00:18:29.000 refresh is optimal, 346 00:18:29.500 --> 00:18:32.000 you'll have cases where moderndeployment methods are optimal. 347 00:18:32.500 --> 00:18:35.000 It's a tool for you to consideras an expedited path to get to 348 00:18:35.500 --> 00:18:40.000 Windows 10 and it has a lotof value in expediting 349 00:18:40.500 --> 00:18:43.000 the process and readiness tostart moving to Windows 10 on 350 00:18:43.500 --> 00:18:48.000 your existing install baseof Windows 7, 8, and 8.1. 351 00:18:48.500 --> 00:18:52.000 As an example, taking theMicrosoft IT experience using 352 00:18:52.500 --> 00:18:55.000 upgrade, you can reallytrace the arc up. 353 00:18:55.500 --> 00:18:59.000 And the main lines to payattention to here are the green 354 00:18:59.500 --> 00:19:03.000 line around user experience oruser satisfaction going up from 355 00:19:03.500 --> 00:19:07.000 7 to 10, as the Windowsdeployment models used 356 00:19:07.500 --> 00:19:11.000 by Microsoft IT transitionedfrom custom solution to MBT, 357 00:19:11.500 --> 00:19:13.000 SECM, plus the ITeasy installer. 358 00:19:13.500 --> 00:19:17.000 Then they started experimentingwith upgrade around the 8.1 time 359 00:19:17.500 --> 00:19:20.000 frame, using update,the 8.1 update. 360 00:19:20.500 --> 00:19:25.000 And then a full-on upgrade pathfrom all versions of Windows 361 00:19:25.500 --> 00:19:28.000 to Windows 10, and you can seethat user satisfaction based on 362 00:19:28.500 --> 00:19:32.000 user polls, that line trendingway up with the upgrade process. 363 00:19:32.500 --> 00:19:35.000 What's also interesting,what trends down in this model, 364 00:19:35.500 --> 00:19:40.000 is the complexity and the,effectively, help desk calls. 365 00:19:40.500 --> 00:19:43.000 So calls went down,user experience and 366 00:19:43.500 --> 00:19:44.000 user satisfaction went up. 367 00:19:44.500 --> 00:19:48.000 And so this is a real case fromreal data from Microsoft IT that 368 00:19:48.500 --> 00:19:51.000 shows the value of upgrade,and how it can be used as 369 00:19:51.500 --> 00:19:55.000 an effective tool to not usejust as a cost savings tool, 370 00:19:55.500 --> 00:19:58.000 as well as a usersatisfaction capability or 371 00:19:58.500 --> 00:20:01.000 user satisfaction increaseas users go through 372 00:20:01.500 --> 00:20:05.000 that transition process fromtheir existing operating system. 373 00:20:05.500 --> 00:20:08.000 To their new Windows 10operating system so for 374 00:20:08.500 --> 00:20:12.000 a quick demo here, so fora quick demo here, I'm going to 375 00:20:12.500 --> 00:20:17.000 cut over and show the nativetask sequence for an upgrade. 376 00:20:17.500 --> 00:20:20.000 So it's pre-created,I've created it in advance. 377 00:20:20.500 --> 00:20:22.000 And I just want to talkthrough the taxonomy a bit of 378 00:20:22.500 --> 00:20:23.000 the task sequence. 379 00:20:23.500 --> 00:20:27.000 So if you select edit here, justa quick run through, there's 380 00:20:27.500 --> 00:20:30.000 a check for readiness optionwhere you can do some check for 381 00:20:30.500 --> 00:20:34.000 readiness settings, for example,ensuring minimum memory, 382 00:20:34.500 --> 00:20:36.000 drive space, etc. 383 00:20:36.500 --> 00:20:40.000 Then there isa upgrade page that has 384 00:20:40.500 --> 00:20:42.000 a simplified set ofvalues you set for 385 00:20:42.500 --> 00:20:46.000 the upgrade process, pickingyour upgrade package, and 386 00:20:46.500 --> 00:20:49.000 down here, you also can see thatyou can check perform setup 387 00:20:49.500 --> 00:20:52.000 compatibility scan withoutactually starting the upgrade. 388 00:20:52.500 --> 00:20:55.000 That's a great way on some testmachines to see what would 389 00:20:55.500 --> 00:20:58.000 have happened had you actuallytried to install the image or 390 00:20:58.500 --> 00:21:00.000 the new version of Windows 10. 391 00:21:00.500 --> 00:21:02.000 And it gives you statusreporting back as to 392 00:21:02.500 --> 00:21:05.000 any issues it might have foundin Lime without actually 393 00:21:05.500 --> 00:21:07.000 upgrading the system. 394 00:21:07.500 --> 00:21:10.000 From the restart perspectivethere's custom messaging you can 395 00:21:10.500 --> 00:21:11.000 provide the end-user. 396 00:21:11.500 --> 00:21:15.000 And then there's Post-Processingor installing applications or 397 00:21:15.500 --> 00:21:16.000 updates once youget to Windows 10. 398 00:21:16.500 --> 00:21:19.000 So we've tried to make asimplified task sequence process 399 00:21:19.500 --> 00:21:22.000 built natively inthe Configuration Manager, 400 00:21:22.500 --> 00:21:27.000 that can help you authora Create Your Upgrade process. 401 00:21:27.500 --> 00:21:30.000 And taking advantage ofthe work we did with Windows on 402 00:21:30.500 --> 00:21:34.000 improving setup in Windows 10 towork better with configuration 403 00:21:34.500 --> 00:21:36.000 manager when itcomes to upgrade. 404 00:21:36.500 --> 00:21:39.000 So that's just a quick runthrough of what's available in 405 00:21:39.500 --> 00:21:42.000 the next version ofConfiguration Manager 406 00:21:42.500 --> 00:21:45.000 in terms of a native tasksequence to help you with that 407 00:21:45.500 --> 00:21:46.000 upgrade process. 408 00:21:46.500 --> 00:21:49.000 So on to moderndeployment options. 409 00:21:49.500 --> 00:21:52.000 We have really twoclassifications of modern 410 00:21:52.500 --> 00:21:53.000 deployment options. 411 00:21:53.500 --> 00:21:56.000 One is the IT-driven process,using new tools 412 00:21:56.500 --> 00:21:59.000 such as the Windows ImageConfiguration Designer to 413 00:21:59.500 --> 00:22:01.000 author a provisioning package. 414 00:22:01.500 --> 00:22:03.000 Or authoring a provisioningprofile directly in 415 00:22:03.500 --> 00:22:05.000 the Config Manager console forIntune or 416 00:22:05.500 --> 00:22:07.000 Config Manager enrollment. 417 00:22:07.500 --> 00:22:09.000 And then there's user driven. 418 00:22:09.500 --> 00:22:12.000 User driven's that example Igave before where the user 419 00:22:12.500 --> 00:22:16.000 walks out on his front steps,grabs a box, opens it up, 420 00:22:16.500 --> 00:22:19.000 puts in his Azure ActiveDirectory credentials, and 421 00:22:19.500 --> 00:22:22.000 authenticates directlyon the device, 422 00:22:22.500 --> 00:22:24.000 registers inAzure Active Directory and 423 00:22:24.500 --> 00:22:27.000 auto enrolls into Intune ora hybrid configuration. 424 00:22:27.500 --> 00:22:29.000 Applications andpolicies start coming down, 425 00:22:29.500 --> 00:22:31.000 and the user get'sright to work. 426 00:22:31.500 --> 00:22:35.000 So that's another great optionfor a modern deployment option, 427 00:22:35.500 --> 00:22:38.000 and I'll demo a couple of those. 428 00:22:38.500 --> 00:22:40.000 So quickly,about the provisioning package, 429 00:22:40.500 --> 00:22:42.000 this slide just gives youan example of some of 430 00:22:42.500 --> 00:22:45.000 the capabilities that comewith the Windows Image and 431 00:22:45.500 --> 00:22:48.000 Configuration Designeraround setup. 432 00:22:48.500 --> 00:22:50.000 One of the really coolones that I think, 433 00:22:50.500 --> 00:22:54.000 is addition upgrade process orthe addition upgrade model, that 434 00:22:54.500 --> 00:23:00.000 lets you author a provisioningpackage and put in your key. 435 00:23:00.500 --> 00:23:02.000 And what that allows you todo is get from a Pro SKU, 436 00:23:02.500 --> 00:23:07.000 as an example,to an Enterprise SKU directly 437 00:23:07.500 --> 00:23:11.000 on a device withouthaving to reimage it. 438 00:23:11.500 --> 00:23:15.000 The benefit of this is you canorder a vanilla image device 439 00:23:15.500 --> 00:23:18.000 from an OEM, you can usea provisioning package to invoke 440 00:23:18.500 --> 00:23:22.000 a SKU upgrade and you can thatdevice from pro to enterprise 441 00:23:22.500 --> 00:23:27.000 without having to put down a newimage which is a big time saver. 442 00:23:27.500 --> 00:23:30.000 There's also the provisioningprofile built to configuration 443 00:23:30.500 --> 00:23:33.000 manager for that auto enrollmentinto configuration manager. 444 00:23:33.500 --> 00:23:35.000 And so I'll do a cut over for 445 00:23:35.500 --> 00:23:38.000 a quick demo there, to show youwhat the authoring experience in 446 00:23:38.500 --> 00:23:39.000 Configuration Managerlooks like. 447 00:23:39.500 --> 00:23:42.000 So if you go down here toWindows Enrollment Profile, 448 00:23:42.500 --> 00:23:44.000 this is where you can createan enrollment profile, 449 00:23:44.500 --> 00:23:48.000 which will allow you to autoenroll a device with this 450 00:23:48.500 --> 00:23:52.000 provisioning profile you createhere for on premises or cloud. 451 00:23:52.500 --> 00:23:54.000 That would be foron premises MDM. 452 00:23:54.500 --> 00:23:57.000 Or to in tune ina hybrid configuration. 453 00:23:57.500 --> 00:24:00.000 And, it's fairly simple,straight forward workflow. 454 00:24:00.500 --> 00:24:06.000 You pick your site assignment. 455 00:24:06.500 --> 00:24:09.000 We'll pick our site code. 456 00:24:09.500 --> 00:24:13.000 Enrollment proxy, we'll pickan internet enrollment proxy. 457 00:24:13.500 --> 00:24:15.000 Any certificatesthat you might need. 458 00:24:15.500 --> 00:24:18.000 WI-FI profile and that's it. 459 00:24:18.500 --> 00:24:21.000 Then you create the provisionenrollment profile, 460 00:24:21.500 --> 00:24:24.000 you export it out, and you putit on a device and then reboot 461 00:24:24.500 --> 00:24:26.000 the device and it effectivelygoes through all the steps of 462 00:24:26.500 --> 00:24:30.000 getting the device on WI-FI,enrolling it into configuration 463 00:24:30.500 --> 00:24:35.000 manager MBM or into the InTuneMBM in a hybrid configuration. 464 00:24:35.500 --> 00:24:38.000 So it's a simple five clickprocess to get a provisioning 465 00:24:38.500 --> 00:24:39.000 profile. 466 00:24:39.500 --> 00:24:41.000 You can time bomb the profile. 467 00:24:41.500 --> 00:24:44.000 You can password protect it,etc. 468 00:24:44.500 --> 00:24:46.000 But it's easy to get out,put on a share, 469 00:24:46.500 --> 00:24:50.000 put on a USB drive,an SD card, an NFC tag. 470 00:24:50.500 --> 00:24:52.000 And simplify, for example, 471 00:24:52.500 --> 00:24:57.000 a branch manager can go tapa Windows tablet to an NFC tag. 472 00:24:57.500 --> 00:25:00.000 Get the profile on their andreboot it and 473 00:25:00.500 --> 00:25:01.000 the device enrolls directly for 474 00:25:01.500 --> 00:25:05.000 MDM management without a lot ofIT overhead in that process. 475 00:25:05.500 --> 00:25:08.000 So it's just another example ofone of the modern management and 476 00:25:08.500 --> 00:25:11.000 modern enrollment processesto get to Windows 10 into 477 00:25:11.500 --> 00:25:13.000 management quickly that'snew with Windows 10 and 478 00:25:13.500 --> 00:25:15.000 configuration manager, 479 00:25:15.500 --> 00:25:18.000 the next version ofconfiguration manager. 480 00:25:18.500 --> 00:25:20.000 So then exit out of that. 481 00:25:20.500 --> 00:25:23.000 The next process I'm gonnatalk through is I've mentioned 482 00:25:23.500 --> 00:25:25.000 it quite a bit so I'll not go, 483 00:25:25.500 --> 00:25:28.000 I'll not re-cover the sameground again but it's the auto 484 00:25:28.500 --> 00:25:32.000 enrollment into Intune throughAzure Active Directory Join. 485 00:25:32.500 --> 00:25:34.000 I think that's bestshown by demo but 486 00:25:34.500 --> 00:25:39.000 the high level process is, iteffectively, like I mentioned, 487 00:25:39.500 --> 00:25:41.000 you boot the device,the user boots the device. 488 00:25:41.500 --> 00:25:44.000 She puts in her credentials orchooses it. 489 00:25:44.500 --> 00:25:45.000 It's a corporate owned device, 490 00:25:45.500 --> 00:25:48.000 puts in Azure Active Directorycredentials, 491 00:25:48.500 --> 00:25:51.000 which are effectively the samecredentials she used to 492 00:25:51.500 --> 00:25:55.000 access corporate mail orto log on her PC at work. 493 00:25:55.500 --> 00:25:59.000 And then the process startswhere by the device is enrolled 494 00:25:59.500 --> 00:26:00.000 into Intune. 495 00:26:00.500 --> 00:26:02.000 Are registered withActive Directory, 496 00:26:02.500 --> 00:26:05.000 enrolled into Intune andit's under management. 497 00:26:05.500 --> 00:26:08.000 So for a quick demo ofthat let me cut over to 498 00:26:08.500 --> 00:26:10.000 my demo host again. 499 00:26:10.500 --> 00:26:12.000 So what you see here is, 500 00:26:12.500 --> 00:26:15.000 I pre-loaded the machineup to the window. 501 00:26:15.500 --> 00:26:17.000 Imagine a first boot experience. 502 00:26:17.500 --> 00:26:19.000 I've just pulledthe device out of a box. 503 00:26:19.500 --> 00:26:22.000 I booted it andat this point I get to pick, 504 00:26:22.500 --> 00:26:26.000 do I want to join Azure AD orjoin a domain? 505 00:26:26.500 --> 00:26:28.000 Now, this is onan Enterprise skew. 506 00:26:28.500 --> 00:26:31.000 If I had pulleda professional version 507 00:26:31.500 --> 00:26:34.000 out of the box, I would havethe ability to choose between 508 00:26:34.500 --> 00:26:38.000 an Azure Active Directory login or a Microsoft Account login 509 00:26:38.500 --> 00:26:40.000 based on the ownershiptype that I choose. 510 00:26:40.500 --> 00:26:43.000 So the screen is slightlydifferent based on enterprise or 511 00:26:43.500 --> 00:26:44.000 professional. 512 00:26:44.500 --> 00:26:46.000 The primary use casewould be professional, 513 00:26:46.500 --> 00:26:49.000 where you would go directly,you'd order a professional 514 00:26:49.500 --> 00:26:52.000 SKU directly from OEM,ship it to the user. 515 00:26:52.500 --> 00:26:54.000 They would then choose thatthis is corporate-owned. 516 00:26:54.500 --> 00:26:57.000 They would put in their AzureActive Directory credentials, 517 00:26:57.500 --> 00:26:58.000 and off they go. 518 00:26:58.500 --> 00:27:01.000 The other option here, whichI'm showing on screen, is for 519 00:27:01.500 --> 00:27:02.000 an enterprise skew. 520 00:27:02.500 --> 00:27:06.000 You could have a joined standardon-prem domain experience or 521 00:27:06.500 --> 00:27:11.000 you could joinAzure Active Directory. 522 00:27:11.500 --> 00:27:15.000 And so, if I choose joinAzure Active Directory here, 523 00:27:15.500 --> 00:27:17.000 it tells me whatthat is optimal for. 524 00:27:17.500 --> 00:27:21.000 I click next andthen I simply go in and 525 00:27:21.500 --> 00:27:23.000 type in my credentials. 526 00:27:23.500 --> 00:27:35.000 [SOUND] 527 00:27:35.500 --> 00:27:41.000 Put in my password. 528 00:27:41.500 --> 00:27:42.000 And click sign in. 529 00:27:42.500 --> 00:27:48.000 And that's just going to,that's all there is to it. 530 00:27:48.500 --> 00:27:51.000 I've put in my credentials andit starts setting up my device. 531 00:27:51.500 --> 00:27:53.000 Now we'll come back tothat towards the end and 532 00:27:53.500 --> 00:27:56.000 we'll show the device isat the pin set screen. 533 00:27:56.500 --> 00:27:58.000 So it shows you itgoes to the workflow. 534 00:27:58.500 --> 00:28:00.000 >> It takes the pin policy from, 535 00:28:00.500 --> 00:28:03.000 it takes the pin policy that'sbeen defined and the user has to 536 00:28:03.500 --> 00:28:06.000 put a pin in that meets thatpolicy, but for now we'll cut 537 00:28:06.500 --> 00:28:10.000 back to slides and we'll comecheck back on that in a minute. 538 00:28:10.500 --> 00:28:14.000 So, Windows as a service,Windows as a service is a new 539 00:28:14.500 --> 00:28:19.000 paradigm being used by Windowsthat really changes the game. 540 00:28:19.500 --> 00:28:22.000 Instead of a multi-year cycle,where new version 541 00:28:22.500 --> 00:28:24.000 of Windows come out, and youget new features, with Windows 542 00:28:24.500 --> 00:28:27.000 as a service, there will beiterative new feature and 543 00:28:27.500 --> 00:28:30.000 value added and rapid innovationthat will be, that will come out 544 00:28:30.500 --> 00:28:34.000 throughout the course of theyear, multiple times per year. 545 00:28:34.500 --> 00:28:35.000 For consumer devices, 546 00:28:35.500 --> 00:28:38.000 keep it hundreds of millionsof consumers up to date. 547 00:28:38.500 --> 00:28:42.000 Business users update employeedevices after features 548 00:28:42.500 --> 00:28:43.000 are validated in the market, so 549 00:28:43.500 --> 00:28:45.000 after they've hitthe consumer market. 550 00:28:45.500 --> 00:28:46.000 Then there's the business user, 551 00:28:46.500 --> 00:28:49.000 which is calledthe Current Branch for Business. 552 00:28:49.500 --> 00:28:54.000 And then those users basicallythe consumer branch or 553 00:28:54.500 --> 00:28:58.000 current branch is used tovalidate all the new changes to 554 00:28:58.500 --> 00:29:00.000 Windows before theygo to business users. 555 00:29:00.500 --> 00:29:03.000 And so they get a lot ofrun time to make sure that 556 00:29:03.500 --> 00:29:04.000 they've been tested,they've been validated, 557 00:29:04.500 --> 00:29:06.000 that there are no issues. 558 00:29:06.500 --> 00:29:09.000 And then a current branch forbusiness releases. 559 00:29:09.500 --> 00:29:13.000 Additionally, there's a specialsystems type of use case 560 00:29:13.500 --> 00:29:15.000 which is caused the longterm servicing branch. 561 00:29:15.500 --> 00:29:17.000 And with the long termservicing branch, 562 00:29:17.500 --> 00:29:21.000 that branch of Windows isnot upgraded frequently. 563 00:29:21.500 --> 00:29:24.000 That's primarily intended forthose business critical systems 564 00:29:24.500 --> 00:29:27.000 that you don't want orneed new features on. 565 00:29:27.500 --> 00:29:31.000 That you want the foundationalbuild that was released 566 00:29:31.500 --> 00:29:33.000 at a particular period of time. 567 00:29:33.500 --> 00:29:34.000 And you don't want to, or 568 00:29:34.500 --> 00:29:37.000 you can't risk absorbingchanges on those devices. 569 00:29:37.500 --> 00:29:39.000 They have a special use case, 570 00:29:39.500 --> 00:29:41.000 you wanna keep them consistentwith that use case. 571 00:29:41.500 --> 00:29:50.000 And you don't want them to beconsuming a servicing model. 572 00:29:50.500 --> 00:29:53.000 So, the rings ofWindows as a service. 573 00:29:53.500 --> 00:29:57.000 There's the engineering builds,which is internal validation, 574 00:29:57.500 --> 00:30:00.000 then there's broad Microsoftinternal validation for 575 00:30:00.500 --> 00:30:02.000 tens of thousands of users. 576 00:30:02.500 --> 00:30:05.000 There's the insider previewof several million users, 577 00:30:05.500 --> 00:30:08.000 then you get into hundreds ofmillions with current branch. 578 00:30:08.500 --> 00:30:10.000 And then Current Branch forbusiness. 579 00:30:10.500 --> 00:30:13.000 And within Current Branch forbusiness with power of 580 00:30:13.500 --> 00:30:17.000 configuration manager is thatwe let you define internal 581 00:30:17.500 --> 00:30:20.000 rings to basically schedulewhen the current branch for 582 00:30:20.500 --> 00:30:24.000 business will hit various userswithin your organization. 583 00:30:24.500 --> 00:30:26.000 So you can stage the rollout, 584 00:30:26.500 --> 00:30:30.000 and your day zero roll outmaybe your IT department. 585 00:30:30.500 --> 00:30:34.000 And then 30 days later you wantearly adopters or the equivalent 586 00:30:34.500 --> 00:30:38.000 of insiders in your organizationto get that release. 587 00:30:38.500 --> 00:30:41.000 But the main point of thisslide is to show under that 588 00:30:41.500 --> 00:30:45.000 Current Branch for businessthat configuration manager 589 00:30:45.500 --> 00:30:49.000 with its adaptation to andsupport of Windows as a service. 590 00:30:49.500 --> 00:30:52.000 Provides you the way to do thoseinternal rings at a schedule of 591 00:30:52.500 --> 00:30:56.000 your choosing using the power ofConfiguration Manager deployment 592 00:30:56.500 --> 00:31:00.000 scheduling and the integrationwith Windows as a service to 593 00:31:00.500 --> 00:31:07.000 support the Windowsas a service model. 594 00:31:07.500 --> 00:31:10.000 So just talking a bit througha deployment strategy. 595 00:31:10.500 --> 00:31:13.000 There's the Insider PreviewBranch with specific features 596 00:31:13.500 --> 00:31:17.000 and specific feature performancefeedback, test machines, 597 00:31:17.500 --> 00:31:18.000 small pilot. 598 00:31:18.500 --> 00:31:21.000 Then there's Current Branch,great for IT departments, 599 00:31:21.500 --> 00:31:22.000 early adopters. 600 00:31:22.500 --> 00:31:23.000 Current Branch for 601 00:31:23.500 --> 00:31:27.000 Business is after you've donethat internal validation against 602 00:31:27.500 --> 00:31:29.000 those technical users inyour organization, or 603 00:31:29.500 --> 00:31:31.000 those select users inyour organization. 604 00:31:31.500 --> 00:31:33.000 And there's Current Branch for 605 00:31:33.500 --> 00:31:36.000 Business which is informationworks general population and 606 00:31:36.500 --> 00:31:38.000 that's where you stageyour broader deployment. 607 00:31:38.500 --> 00:31:40.000 And you roll thatout over time and 608 00:31:40.500 --> 00:31:43.000 Config Manager gives you thepower to control that schedule 609 00:31:43.500 --> 00:31:46.000 and which users are hit at whichpoint in time with the new 610 00:31:46.500 --> 00:31:48.000 Current Branch forBusiness update. 611 00:31:48.500 --> 00:31:52.000 And, you can manage that rollout in a way that's secure for 612 00:31:52.500 --> 00:31:52.000 your environment. 613 00:31:52.500 --> 00:31:56.000 So, your taking advantage ofthe great new features in that 614 00:31:56.500 --> 00:31:58.000 new release of Windows ornew update to Windows. 615 00:31:58.500 --> 00:32:02.000 But in a cadence that meets yourorganizations requirements and 616 00:32:02.500 --> 00:32:04.000 the users that you wannatarget with that deployment. 617 00:32:04.500 --> 00:32:06.000 Again, Current Branch. 618 00:32:06.500 --> 00:32:07.000 You may target yourIT department and 619 00:32:07.500 --> 00:32:08.000 your early adopters. 620 00:32:08.500 --> 00:32:09.000 And with Current Branch for 621 00:32:09.500 --> 00:32:12.000 Business, you startan iterative rollout, or 622 00:32:12.500 --> 00:32:16.000 gradual rollout, to your broaderinformation worker population. 623 00:32:16.500 --> 00:32:18.000 And then of course you stillhave the Long Term Servicing 624 00:32:18.500 --> 00:32:21.000 Branch on the far right there,for your specialized systems and 625 00:32:21.500 --> 00:32:26.000 the systems that you don'twant to invoke any change on. 626 00:32:26.500 --> 00:32:28.000 And so all models are available. 627 00:32:28.500 --> 00:32:32.000 And configuration manager, I'llshow in a minute, has been been 628 00:32:32.500 --> 00:32:34.000 designed being next to reallysupport this model and 629 00:32:34.500 --> 00:32:39.000 make you successful withWindows as a service. 630 00:32:39.500 --> 00:32:42.000 So the new System CenterConfiguration Manager. 631 00:32:42.500 --> 00:32:45.000 Really, the first step issimplifying the upgrade 632 00:32:45.500 --> 00:32:45.000 experience. 633 00:32:45.500 --> 00:32:48.000 We wanna make it easy foryou to get 634 00:32:48.500 --> 00:32:53.000 from your existing ConfigurationManager 2012 installation. 635 00:32:53.500 --> 00:32:56.000 To the next version ofConfiguration Manager. 636 00:32:56.500 --> 00:32:58.000 So the upgrade isservice-pack like. 637 00:32:58.500 --> 00:33:00.000 It is not a complex upgrade, 638 00:33:00.500 --> 00:33:04.000 it's not a migration, it isvery much service-pack like. 639 00:33:04.500 --> 00:33:07.000 And what happens when youadopt the new model of 640 00:33:07.500 --> 00:33:08.000 Configuration Manager, 641 00:33:08.500 --> 00:33:10.000 the new version ofConfiguration Manager. 642 00:33:10.500 --> 00:33:13.000 Is that we are now ona servicing model. 643 00:33:13.500 --> 00:33:17.000 So, we are on a model matchesthe Windows as a service model. 644 00:33:17.500 --> 00:33:21.000 Whereby, we are bringingupdates down and making updates 645 00:33:21.500 --> 00:33:26.000 available to you in a iterativeway that just continues 646 00:33:26.500 --> 00:33:30.000 over time aligned with thecadence of Windows as a service. 647 00:33:30.500 --> 00:33:33.000 For example, 648 00:33:33.500 --> 00:33:36.000 the release name of the nextversion of Configuration Manager 649 00:33:36.500 --> 00:33:40.000 is System Center ConfigurationManager without a year. 650 00:33:40.500 --> 00:33:42.000 The reason that it doesn'thave a year is that 651 00:33:42.500 --> 00:33:47.000 we will iteratively update thatversion with an update that will 652 00:33:47.500 --> 00:33:51.000 come out along the same cadenceof Windows as a service. 653 00:33:51.500 --> 00:33:55.000 For example, the Q fourrelease might be called 654 00:33:55.500 --> 00:33:59.000 System Center ConfigurationManager version 1511. 655 00:33:59.500 --> 00:34:02.000 That's year followed by month. 656 00:34:02.500 --> 00:34:06.000 Then, there may be an update inFebruary, which would be 1602. 657 00:34:06.500 --> 00:34:10.000 So, we will provideupdates at a regular 658 00:34:10.500 --> 00:34:14.000 cadence to support the Windowsas a service model and 659 00:34:14.500 --> 00:34:16.000 the new features in Windows 10. 660 00:34:16.500 --> 00:34:19.000 And we'll make it very easy toconsume those updates without 661 00:34:19.500 --> 00:34:21.000 impacting your environment, or 662 00:34:21.500 --> 00:34:24.000 without risk to impactto your environment. 663 00:34:24.500 --> 00:34:26.000 That comes down to ournew servicing model 664 00:34:26.500 --> 00:34:28.000 there's a role that connectsup to a Cloud service that 665 00:34:28.500 --> 00:34:29.000 brings the updates down. 666 00:34:29.500 --> 00:34:32.000 They show up in your console andyou have 667 00:34:32.500 --> 00:34:35.000 up to 12 months to installthe latest cumulative update. 668 00:34:35.500 --> 00:34:38.000 So we do give you 12 months tostart consuming those updates as 669 00:34:38.500 --> 00:34:40.000 they come down. 670 00:34:40.500 --> 00:34:43.000 They also keeps us inline withthe monthly Intune updates. 671 00:34:43.500 --> 00:34:46.000 For our hybrid configurationcustomers this 672 00:34:46.500 --> 00:34:49.000 channel provides us a way tokeep parity with our Cloud 673 00:34:49.500 --> 00:34:50.000 service which we update monthly. 674 00:34:50.500 --> 00:34:53.000 And the on-prem components ina hybrid configuration that 675 00:34:53.500 --> 00:34:55.000 connect to that cloud service. 676 00:34:55.500 --> 00:34:59.000 So the new update model supportsboth Windows as a service and 677 00:34:59.500 --> 00:35:01.000 optimizes forWindows as a service. 678 00:35:01.500 --> 00:35:05.000 As well as keeping up withparody with the Cloud 679 00:35:05.500 --> 00:35:08.000 part of the hybrid configurationthat's done on the in-tune side, 680 00:35:08.500 --> 00:35:10.000 which is a monthly cadence. 681 00:35:10.500 --> 00:35:14.000 So this greatly simplifies andexpedites our ability to deliver 682 00:35:14.500 --> 00:35:18.000 great new features for bothMDM and Windows 10 safely over 683 00:35:18.500 --> 00:35:22.000 time at the pace the customerchooses to consume them. 684 00:35:22.500 --> 00:35:26.000 And then the last bulletpoint here is really around 685 00:35:26.500 --> 00:35:30.000 we've really take put investeda lot in In UserVoice, and 686 00:35:30.500 --> 00:35:32.000 taking the feedbackfrom UserVoice. 687 00:35:32.500 --> 00:35:34.000 And using that to drive ourengineering processes, and 688 00:35:34.500 --> 00:35:37.000 delivering the great featuresthat customers want. 689 00:35:37.500 --> 00:35:40.000 Couple of examples there of oneof the top UserVoice items was 690 00:35:40.500 --> 00:35:45.000 combining the software centerwith Application Catalog, 691 00:35:45.500 --> 00:35:46.000 which we've done now. 692 00:35:46.500 --> 00:35:48.000 We'll talk about ita little bit later. 693 00:35:48.500 --> 00:35:50.000 We have a combinedend user portal. 694 00:35:50.500 --> 00:35:55.000 And another factor thatwe use to able us to 695 00:35:55.500 --> 00:35:59.000 achieve this rapid iterationsis that we have data intelometry 696 00:35:59.500 --> 00:36:03.000 that we use that helps ustest and release fast. 697 00:36:03.500 --> 00:36:05.000 So, these are critical changes,both user voice and 698 00:36:05.500 --> 00:36:06.000 data intelometry. 699 00:36:06.500 --> 00:36:12.000 Which lets us identify issuesthat customers might be seeing. 700 00:36:12.500 --> 00:36:14.000 Features customers want, and 701 00:36:14.500 --> 00:36:17.000 the data intelometry to buildout what we need to test. 702 00:36:17.500 --> 00:36:20.000 What we need to validate beforewe release one of these updates 703 00:36:20.500 --> 00:36:23.000 to assure that it's safe foryour environment. 704 00:36:23.500 --> 00:36:28.000 It is high quality andit allows you to consume that 705 00:36:28.500 --> 00:36:32.000 update pack rapidly to keep upwith the Windows 10 cadence. 706 00:36:32.500 --> 00:36:35.000 And enjoy all the great featuresthat are coming to Windows 707 00:36:35.500 --> 00:36:38.000 as a service. 708 00:36:38.500 --> 00:36:41.000 So as I mentioned earlier,the upcoming release of 709 00:36:41.500 --> 00:36:43.000 Configuration Manageris year-less. 710 00:36:43.500 --> 00:36:47.000 It's year-less becauseit's release vehicle is 711 00:36:47.500 --> 00:36:48.000 Current Branch. 712 00:36:48.500 --> 00:36:51.000 Current Branch means that wewill keep it current til the end 713 00:36:51.500 --> 00:36:52.000 of time. 714 00:36:52.500 --> 00:36:57.000 It doesn't have a date wherebyyou need to go upgrade 715 00:36:57.500 --> 00:37:00.000 to the next version ofConfiguration Manager. 716 00:37:00.500 --> 00:37:03.000 We're iteratively releasingupdates to Config Manager 717 00:37:03.500 --> 00:37:06.000 all throughout the year,year over year, and 718 00:37:06.500 --> 00:37:09.000 it's generally availablein Q4 of this year. 719 00:37:09.500 --> 00:37:12.000 So all the new Windows 10features are supported 720 00:37:12.500 --> 00:37:15.000 in this version ofConfiguration Manager. 721 00:37:15.500 --> 00:37:16.000 Now, the reason for 722 00:37:16.500 --> 00:37:19.000 that is that with the rapiditeration of Windows, 723 00:37:19.500 --> 00:37:21.000 it would be very challenging forus to go back and 724 00:37:21.500 --> 00:37:25.000 keep adding cumulative updatesand service packs to 2012 to 725 00:37:25.500 --> 00:37:28.000 keep that version currentwith new Windows features. 726 00:37:28.500 --> 00:37:31.000 So, we're really askingcustomers to join us on this 727 00:37:31.500 --> 00:37:35.000 journey to a current branchmodel, a servicing model for 728 00:37:35.500 --> 00:37:40.000 configuration manager becauseit allows you to keep up and 729 00:37:40.500 --> 00:37:43.000 support the great newfeatures of Windows 10. 730 00:37:43.500 --> 00:37:46.000 And also allows for hybridcostumers that are also using 731 00:37:46.500 --> 00:37:50.000 Intune for MDM to keep paritybetween those to configurations. 732 00:37:50.500 --> 00:37:53.000 To assure that 733 00:37:53.500 --> 00:37:55.000 we deliver on that flexiblearchitecture promise. 734 00:37:55.500 --> 00:37:58.000 That we deliveron-prem capability 735 00:37:58.500 --> 00:38:02.000 as rapidly as we're deliveringcloud-based capability. 736 00:38:02.500 --> 00:38:05.000 It's really just the Microsoftway of the future to deliver 737 00:38:05.500 --> 00:38:08.000 that continuous innovation,not just in one product. 738 00:38:08.500 --> 00:38:10.000 Not just in Windows. 739 00:38:10.500 --> 00:38:11.000 Not just in Office. 740 00:38:11.500 --> 00:38:13.000 But the ecosystem of productsthat's required to make 741 00:38:13.500 --> 00:38:17.000 enterprises successfulin using both of those 742 00:38:17.500 --> 00:38:19.000 cornerstone productsof Microsoft. 743 00:38:19.500 --> 00:38:22.000 Like I said, you can deferupdates up to 12 months. 744 00:38:22.500 --> 00:38:26.000 And the new version of SystemCenter Configuration Manager 745 00:38:26.500 --> 00:38:28.000 will support Windows10 current branch, 746 00:38:28.500 --> 00:38:33.000 current branch for business, andthe long term servicing branch. 747 00:38:33.500 --> 00:38:36.000 And the graph at the bottom herejust shows the current branch 748 00:38:36.500 --> 00:38:37.000 version being 1511. 749 00:38:37.500 --> 00:38:41.000 Then come winter there will beanother version that's year year 750 00:38:41.500 --> 00:38:44.000 month month, and another versionbeing year year month month. 751 00:38:44.500 --> 00:38:46.000 So that's the cadencethat we'll get into. 752 00:38:46.500 --> 00:38:50.000 And when I cut over to the demo,you'll see that naming 753 00:38:50.500 --> 00:38:53.000 convention reflectedin a console node. 754 00:38:53.500 --> 00:38:56.000 That gives you easy access tothose updates, tells you what 755 00:38:56.500 --> 00:38:59.000 features are those updates andlet you install and 756 00:38:59.500 --> 00:39:03.000 apply those updates to the timeof your choosing in a safe way. 757 00:39:03.500 --> 00:39:05.000 By doing prerequisite checks and 758 00:39:05.500 --> 00:39:08.000 installing at a settingservicing Windows for 759 00:39:08.500 --> 00:39:11.000 your servers that might beimpacted and also staging any 760 00:39:11.500 --> 00:39:16.000 client updates that comeas part of an update pack. 761 00:39:16.500 --> 00:39:20.000 This graph is really just meantto show what current versions of 762 00:39:20.500 --> 00:39:22.000 configuration managerwill support. 763 00:39:22.500 --> 00:39:25.000 The main point to make here isthat we will support Windows 764 00:39:25.500 --> 00:39:28.000 10 app compat withinmarket versions 765 00:39:28.500 --> 00:39:30.000 of configuration manager. 766 00:39:30.500 --> 00:39:34.000 But for new capabilities,you will need to move to 767 00:39:34.500 --> 00:39:38.000 the system center configurationmanager version releasing in 768 00:39:38.500 --> 00:39:42.000 Q4 starting the with 1511 updateto configuration manager. 769 00:39:42.500 --> 00:39:46.000 That's where the new Windows10 features come in. 770 00:39:46.500 --> 00:39:49.000 So now I'm gonna cutover to Demo here and 771 00:39:49.500 --> 00:39:51.000 show you the new update andservicing node. 772 00:39:51.500 --> 00:39:53.000 The servicing dashboard forWindows and 773 00:39:53.500 --> 00:39:57.000 how to configure those updaterings as you navigate the new 774 00:39:57.500 --> 00:39:59.000 Windows as a Service model. 775 00:39:59.500 --> 00:40:02.000 Okay, so here we are atthe updates and servicing node. 776 00:40:02.500 --> 00:40:06.000 The new node that we've addedthat allows you to effectively 777 00:40:06.500 --> 00:40:11.000 Keep configuration manager upto date with the latest features 778 00:40:11.500 --> 00:40:14.000 of Windows,the latest features for 779 00:40:14.500 --> 00:40:18.000 MDM and they effectively wereland in this list view and 780 00:40:18.500 --> 00:40:21.000 it's very simple tointeract with them. 781 00:40:21.500 --> 00:40:23.000 So this is an example here. 782 00:40:23.500 --> 00:40:26.000 This should read 15 11, 783 00:40:26.500 --> 00:40:28.000 but there's an issuewith the string. 784 00:40:28.500 --> 00:40:32.000 Anyway, all you really need todo here is you highlight it. 785 00:40:32.500 --> 00:40:33.000 You click on Features. 786 00:40:33.500 --> 00:40:36.000 It shows you the featuresthat are available in this 787 00:40:36.500 --> 00:40:38.000 particular update. 788 00:40:38.500 --> 00:40:40.000 And then you right click, and 789 00:40:40.500 --> 00:40:43.000 you can either installall the update pack, or 790 00:40:43.500 --> 00:40:45.000 you can run a prereq check tosee what components might be 791 00:40:45.500 --> 00:40:49.000 impacted if you went ahead andinstalled the update pack. 792 00:40:49.500 --> 00:40:52.000 And with that, you caneffectively run prereque, 793 00:40:52.500 --> 00:40:55.000 see what will be impacted,make a decision to move forward. 794 00:40:55.500 --> 00:40:58.000 Or you can choose to justinstall the update pack and 795 00:40:58.500 --> 00:41:01.000 that will run throughprerequisite checks for you and 796 00:41:01.500 --> 00:41:03.000 then let you choose,for example, 797 00:41:03.500 --> 00:41:06.000 to stage the client roleout if it's required. 798 00:41:06.500 --> 00:41:08.000 It'll tell you whichcomponents are impacted, etc. 799 00:41:08.500 --> 00:41:11.000 So we tried to make it assimple to adopt as possible. 800 00:41:11.500 --> 00:41:16.000 These will roll in hereat a regular cadence. 801 00:41:16.500 --> 00:41:19.000 We're not limited to Windowsas a service cadence. 802 00:41:19.500 --> 00:41:22.000 We can effectively deliverupdates to this updates and 803 00:41:22.500 --> 00:41:25.000 service team at any point,and they can be inclusive of 804 00:41:25.500 --> 00:41:29.000 hotfixes, bug fixes, securityfixes, as well as new features. 805 00:41:29.500 --> 00:41:34.000 And we can deliver these, like Isaid, at any point in time where 806 00:41:34.500 --> 00:41:37.000 try to keep these aligned to thewindows of the service model, 807 00:41:37.500 --> 00:41:40.000 but if a new feature for MDMcomes out, we'd have the ability 808 00:41:40.500 --> 00:41:43.000 to drop that down as well andlet you choose to do that. 809 00:41:43.500 --> 00:41:46.000 And there are effectively threetypes of update packs you would 810 00:41:46.500 --> 00:41:47.000 see in here. 811 00:41:47.500 --> 00:41:50.000 There's cumulative update,which is more of about three, 812 00:41:50.500 --> 00:41:54.000 four times a year update thathas a bundle of features, fixes, 813 00:41:54.500 --> 00:41:55.000 updates in it. 814 00:41:55.500 --> 00:41:58.000 Then there is an update,which effectively 815 00:41:58.500 --> 00:42:01.000 might be an out-of-band releaseof just supporting a new 816 00:42:01.500 --> 00:42:03.000 MBM capability that's maybenot tied to Windows 10. 817 00:42:03.500 --> 00:42:07.000 And then there is hotfix andsecurity updates. 818 00:42:07.500 --> 00:42:09.000 Those could be delivered for 819 00:42:09.500 --> 00:42:11.000 urgent security fixes thatwe find or get reported, 820 00:42:11.500 --> 00:42:14.000 we could also drop those downto this channel as well. 821 00:42:14.500 --> 00:42:16.000 So really gone are the days, 822 00:42:16.500 --> 00:42:18.000 when you have to go seekout a C.U., a service pack, 823 00:42:18.500 --> 00:42:21.000 a hot fix, those will all plumbdown through this channel. 824 00:42:21.500 --> 00:42:24.000 It's very simpleto use interface. 825 00:42:24.500 --> 00:42:28.000 So if we move on tothe Windows servicing model. 826 00:42:28.500 --> 00:42:31.000 So what we're looking at here isour dashboard that we've put in 827 00:42:31.500 --> 00:42:33.000 place to really try tohelp you navigate and 828 00:42:33.500 --> 00:42:37.000 be successful with Windows,as a service. 829 00:42:37.500 --> 00:42:39.000 And the first diagram or 830 00:42:39.500 --> 00:42:42.000 first graphic here isshowing you your usage. 831 00:42:42.500 --> 00:42:44.000 This just shows the number ofclients that are on a particular 832 00:42:44.500 --> 00:42:45.000 version of Windows. 833 00:42:45.500 --> 00:42:48.000 That's a quickglance view of what 834 00:42:48.500 --> 00:42:50.000 versions are out inyour environment. 835 00:42:50.500 --> 00:42:52.000 Your rings are the users or 836 00:42:52.500 --> 00:42:55.000 the devices you've targetedwith a particular branch. 837 00:42:55.500 --> 00:42:58.000 There's release readywhich is current branch, 838 00:42:58.500 --> 00:43:01.000 business ready which is currentbranch for business and 839 00:43:01.500 --> 00:43:02.000 long term servicing branch. 840 00:43:02.500 --> 00:43:06.000 So this just outlines the numberof users that you've targeted 841 00:43:06.500 --> 00:43:08.000 in each of those branches,users or systems and 842 00:43:08.500 --> 00:43:12.000 the collection, it'sa reflection of collection view. 843 00:43:12.500 --> 00:43:14.000 So this gives you a quick viewof who's been targeted or 844 00:43:14.500 --> 00:43:17.000 a number of users been targetedwith the various branches of 845 00:43:17.500 --> 00:43:18.000 Windows. 846 00:43:18.500 --> 00:43:20.000 And then under servicing plan, 847 00:43:20.500 --> 00:43:25.000 you can then create a servicingplan here that allows you to 848 00:43:25.500 --> 00:43:30.000 build out that iterativeschedule I talked about, so 849 00:43:30.500 --> 00:43:36.000 we'll call thisContoso IT current. 850 00:43:36.500 --> 00:43:41.000 And then we'll go pick a targetcollection of Contoso Insiders. 851 00:43:41.500 --> 00:43:44.000 Pick a deployment package andthen pick a servicing ring. 852 00:43:44.500 --> 00:43:46.000 And since this isour IT department, 853 00:43:46.500 --> 00:43:48.000 we want these to beon current brands. 854 00:43:48.500 --> 00:43:49.000 So we're gonna pick those. 855 00:43:49.500 --> 00:43:51.000 And I won't run throughthe whole wizard here but 856 00:43:51.500 --> 00:43:55.000 effectively this gives you asimple way to create your Day 0 857 00:43:55.500 --> 00:43:58.000 ring for current branch bytargeting your IT Department. 858 00:43:58.500 --> 00:44:00.000 Now if I go down here, 859 00:44:00.500 --> 00:44:02.000 I don't have any deploymentsactually going on, but 860 00:44:02.500 --> 00:44:05.000 if I go down here, you'll seeyou're be able to monitor your 861 00:44:05.500 --> 00:44:11.000 serving plans to seethe number of users or devices 862 00:44:11.500 --> 00:44:14.000 in each of those servicingplans that are compliant. 863 00:44:14.500 --> 00:44:16.000 Whereas compliant means theyhave the latest version of 864 00:44:16.500 --> 00:44:19.000 Windows based on the branchthat you have chosen for them. 865 00:44:19.500 --> 00:44:23.000 So for example, I pre-createdContoso, IT early adopters and 866 00:44:23.500 --> 00:44:25.000 Contoso insiders. 867 00:44:25.500 --> 00:44:28.000 The early adopters,which I'll cut over now to 868 00:44:28.500 --> 00:44:32.000 the servicing plans list view,so we can get some more details. 869 00:44:32.500 --> 00:44:35.000 So for the IT early adopters,if I could go in here and 870 00:44:35.500 --> 00:44:40.000 check properties, And 871 00:44:40.500 --> 00:44:43.000 I cut over to deployment ring,the deployment ring tabs, 872 00:44:43.500 --> 00:44:46.000 this shows that these users aregonna get the release ready or 873 00:44:46.500 --> 00:44:48.000 current branch forWindows 10 and 874 00:44:48.500 --> 00:44:50.000 they're gonna startgetting it at day 0. 875 00:44:50.500 --> 00:44:52.000 And that's day 0 relativeto when Microsoft has 876 00:44:52.500 --> 00:44:55.000 published the new upgrade andit's been consumed by 877 00:44:55.500 --> 00:44:58.000 Configuration Manager forredistribution. 878 00:44:58.500 --> 00:45:02.000 So day 0, Microsoft releasesthe Windows 10 current branch 879 00:45:02.500 --> 00:45:04.000 update for November. 880 00:45:04.500 --> 00:45:06.000 Day 0, the IT departmentwill start seeing it. 881 00:45:06.500 --> 00:45:09.000 And of course you can setthe mandatory times and 882 00:45:09.500 --> 00:45:11.000 make it optional andthen mandatory 7 days later. 883 00:45:11.500 --> 00:45:15.000 Similar to most deploymentsin Configuration Manager. 884 00:45:15.500 --> 00:45:20.000 But this just is an easy wayto configure which users will 885 00:45:20.500 --> 00:45:24.000 get which branch at which pointin time relative to its release. 886 00:45:24.500 --> 00:45:27.000 So if I cancel out of this andI go to my insiders, 887 00:45:27.500 --> 00:45:28.000 I don't have oncurrent branch but 888 00:45:28.500 --> 00:45:31.000 I have them on currentbranch for business. 889 00:45:31.500 --> 00:45:32.000 So if I go to my insiders. 890 00:45:32.500 --> 00:45:37.000 I can see that their servicingplan is, or their deployment 891 00:45:37.500 --> 00:45:42.000 ring, is business ready, so thenthe current branch for business. 892 00:45:42.500 --> 00:45:44.000 Even though the current branchfor business is going to be 893 00:45:44.500 --> 00:45:47.000 offset from the current branchrelease, I wanna give them 894 00:45:47.500 --> 00:45:51.000 an additional 30 days from whenthat current branch for business 895 00:45:51.500 --> 00:45:54.000 is released and brought down byConfig Manager and deployed. 896 00:45:54.500 --> 00:45:57.000 So this gives me some time to goahead and validate that as well. 897 00:45:57.500 --> 00:46:00.000 I may have a release ringin between these two, 898 00:46:00.500 --> 00:46:02.000 where I validate IT departmenton current branch for 899 00:46:02.500 --> 00:46:04.000 business or part of the ITdepartment on current branch for 900 00:46:04.500 --> 00:46:06.000 business, day 0. 901 00:46:06.500 --> 00:46:09.000 And then I defer my insiders30 days offset from that, 902 00:46:09.500 --> 00:46:11.000 just to get deeper validation. 903 00:46:11.500 --> 00:46:14.000 And I can run that allthe way out to 120 days past 904 00:46:14.500 --> 00:46:21.000 the release of the new upgradeof that particular branch. 905 00:46:21.500 --> 00:46:25.000 So that's a overview of oursupport for the servicing model. 906 00:46:25.500 --> 00:46:28.000 So I'll now cutback to my slides. 907 00:46:28.500 --> 00:46:30.000 I mentioned conditionalaccess earlier, and 908 00:46:30.500 --> 00:46:35.000 the conditional access is a keyinvestment we made in EMS, 909 00:46:35.500 --> 00:46:38.000 complimenting Windows 10 toassure that whatever way you 910 00:46:38.500 --> 00:46:41.000 manage the device, whether it'swith a Config Manager agent, 911 00:46:41.500 --> 00:46:44.000 whether the device isjust domain joined, or 912 00:46:44.500 --> 00:46:48.000 if the device is enrolled intoIntune for MDM management. 913 00:46:48.500 --> 00:46:53.000 That we provide you thosecontrols to control 914 00:46:53.500 --> 00:46:57.000 user access to corporateresources like Office 365, by 915 00:46:57.500 --> 00:47:01.000 assuring the device is compliantand the device is managed. 916 00:47:01.500 --> 00:47:02.000 So those are the primarypivots of our 917 00:47:02.500 --> 00:47:04.000 conditional access control. 918 00:47:04.500 --> 00:47:06.000 And the main point I wantedto make on this slide 919 00:47:06.500 --> 00:47:10.000 is that we support allflavors of management for 920 00:47:10.500 --> 00:47:12.000 conditional access. 921 00:47:12.500 --> 00:47:14.000 Again there is Intune andConfig manager managed, 922 00:47:14.500 --> 00:47:17.000 meaning that they have tobe managed by Intune or 923 00:47:17.500 --> 00:47:19.000 managed byConfiguration Manager agent. 924 00:47:19.500 --> 00:47:24.000 And there is also compliantwith Intune In Config Manager 925 00:47:24.500 --> 00:47:26.000 managed devices. 926 00:47:26.500 --> 00:47:28.000 Compliance would mean like,software updates are current, 927 00:47:28.500 --> 00:47:32.000 latest version ofthe Defender signature, etc. 928 00:47:32.500 --> 00:47:35.000 Multiple complianceconditions you can set, 929 00:47:35.500 --> 00:47:37.000 that effectively gate access to 930 00:47:37.500 --> 00:47:40.000 corporate resourcesbased on that condition. 931 00:47:40.500 --> 00:47:43.000 For example, if I have theConfig Manager Agent installed 932 00:47:43.500 --> 00:47:48.000 and it reports that I'm notcompliant with updates, 933 00:47:48.500 --> 00:47:51.000 that value, that compliancestate, can be written up through 934 00:47:51.500 --> 00:47:55.000 config manager through Intune ina hybrid configuration over to 935 00:47:55.500 --> 00:47:59.000 Azure Active Directory to flagmy device as non-compliant. 936 00:47:59.500 --> 00:48:03.000 So when I try to accessOffice 365 resources, 937 00:48:03.500 --> 00:48:09.000 it will effectively return backto me that I'm not compliant and 938 00:48:09.500 --> 00:48:12.000 I can't get my mail unlessI get back to compliant. 939 00:48:12.500 --> 00:48:15.000 And so again, the main pointof conditional access here is 940 00:48:15.500 --> 00:48:18.000 that it ensures that you're notaccessing corporate resources 941 00:48:18.500 --> 00:48:20.000 if you don't meet the ITcompliance standards and 942 00:48:20.500 --> 00:48:23.000 that it's applicable toall of our configurations. 943 00:48:23.500 --> 00:48:26.000 Again highlighting thatflexible configuration or 944 00:48:26.500 --> 00:48:28.000 flexible architecturepower of EMS and 945 00:48:28.500 --> 00:48:34.000 configuration managerbetter together story. 946 00:48:34.500 --> 00:48:38.000 With enterprise data protection,we get the ability to 947 00:48:38.500 --> 00:48:42.000 really protect data leakageat the platform level. 948 00:48:42.500 --> 00:48:44.000 Prevent data leakageat the platform level. 949 00:48:44.500 --> 00:48:48.000 And the beauty of the enterprisedata protection model 950 00:48:48.500 --> 00:48:52.000 is that it is platform based,it is Windows based. 951 00:48:52.500 --> 00:48:55.000 So it applies to Win32 applications, 952 00:48:55.500 --> 00:48:57.000 universal applications. 953 00:48:57.500 --> 00:49:01.000 It's highly configurableto set the applications 954 00:49:01.500 --> 00:49:05.000 that you use and identify andtarget them as managed. 955 00:49:05.500 --> 00:49:09.000 So when then corporate data isopened in those applications, 956 00:49:09.500 --> 00:49:11.000 the data is encrypted, 957 00:49:11.500 --> 00:49:15.000 the data can be deletedupon wiping of that device. 958 00:49:15.500 --> 00:49:17.000 And these policies canbe managed by both 959 00:49:17.500 --> 00:49:22.000 Config Manager Agent or ina hybrid configuration through 960 00:49:22.500 --> 00:49:25.000 MDM orthrough InTune stand alone MDM, 961 00:49:25.500 --> 00:49:27.000 where you can configure whatyour managed applications are. 962 00:49:27.500 --> 00:49:31.000 You can configure the behaviorof data moving from managed 963 00:49:31.500 --> 00:49:34.000 applications to unmanaged,meaning you can block, cut, 964 00:49:34.500 --> 00:49:35.000 copy and paste. 965 00:49:35.500 --> 00:49:36.000 You can block, save as. 966 00:49:36.500 --> 00:49:40.000 You can prevent corporate datafrom going to non-corporate 967 00:49:40.500 --> 00:49:46.000 sources where their datamight be at risk for leakage. 968 00:49:46.500 --> 00:49:50.000 To wrap up on some of the keyfeatures we're adding with 969 00:49:50.500 --> 00:49:53.000 Config Manager Vnext andwith Windows 10 is enhanced user 970 00:49:53.500 --> 00:49:56.000 experiences like Imentioned before. 971 00:49:56.500 --> 00:50:01.000 There's a consistent look andfeel of the company portal, 972 00:50:01.500 --> 00:50:06.000 combining software center andthe application catalog. 973 00:50:06.500 --> 00:50:08.000 There is the support for 974 00:50:08.500 --> 00:50:12.000 Microsoft Passport to supportnext generation credentials, and 975 00:50:12.500 --> 00:50:16.000 the support for WindowsUniversal apps, both offline and 976 00:50:16.500 --> 00:50:19.000 configuration manager andonline in our hybrid and 977 00:50:19.500 --> 00:50:22.000 Intune stand aloneconfigurations, which lets 978 00:50:22.500 --> 00:50:26.000 you take full advantage ofthe Windows Tour for Business. 979 00:50:26.500 --> 00:50:29.000 To procure your applications,and deliver those using 980 00:50:29.500 --> 00:50:35.000 the combined management suite ofEMS plus configuration manager. 981 00:50:35.500 --> 00:50:39.000 So for a last demo I willcut over to enterprise data 982 00:50:39.500 --> 00:50:41.000 protection and show a quickdemo of Windows Store for 983 00:50:41.500 --> 00:50:43.000 Business and then we'll wrap up. 984 00:50:43.500 --> 00:50:45.000 So what I wanna show forenterprise data protection here. 985 00:50:45.500 --> 00:50:49.000 On the console sideI've already configured 986 00:50:49.500 --> 00:50:53.000 enterprise data protection forOffice 2013 applications. 987 00:50:53.500 --> 00:50:55.000 Fairly simple to configure. 988 00:50:55.500 --> 00:50:57.000 I choose the nameof the publisher. 989 00:50:57.500 --> 00:51:00.000 I choose the name of the productand the path to the binaries if 990 00:51:00.500 --> 00:51:05.000 I wanna do explicit applicationsin the Office 2013 suite. 991 00:51:05.500 --> 00:51:07.000 The one key piece here isthis is Office 2013 not 992 00:51:07.500 --> 00:51:10.000 even Office 2016, so it's just 993 00:51:10.500 --> 00:51:14.000 to show that it works on the Win32 application that you define. 994 00:51:14.500 --> 00:51:17.000 That you use in your environmentwithout any special updates to 995 00:51:17.500 --> 00:51:21.000 the application needed whichis a great way to start using 996 00:51:21.500 --> 00:51:24.000 enterprise data protection rightaway, there are also multiple 997 00:51:24.500 --> 00:51:27.000 options around enterprisedata protection around what 998 00:51:27.500 --> 00:51:31.000 happens when data tries to leavea managed to an unmanaged app. 999 00:51:31.500 --> 00:51:34.000 You can for example,you can have it turned off. 1000 00:51:34.500 --> 00:51:37.000 You can audit soyou can build sort of a heat 1001 00:51:37.500 --> 00:51:42.000 map of what your users' typicaldata transfer patterns are. 1002 00:51:42.500 --> 00:51:45.000 And you can allow but 1003 00:51:45.500 --> 00:51:47.000 warn to tell the users that hey,I see your copy from 1004 00:51:47.500 --> 00:51:51.000 an unmanaged to managedto an unmanaged location. 1005 00:51:51.500 --> 00:51:52.000 Are you sure you wanna do that? 1006 00:51:52.500 --> 00:51:53.000 This will be audited. 1007 00:51:53.500 --> 00:51:55.000 And you can block out right, and 1008 00:51:55.500 --> 00:51:57.000 you can tell the userthat we don't allow this. 1009 00:51:57.500 --> 00:51:59.000 And I'm gonna show an exampleof the last option to 1010 00:51:59.500 --> 00:52:01.000 block out right. 1011 00:52:01.500 --> 00:52:03.000 First thing to point out hereis you can see that there's 1012 00:52:03.500 --> 00:52:07.000 a graphical indicator that theseare managed applications by this 1013 00:52:07.500 --> 00:52:08.000 lock and building icon up here. 1014 00:52:08.500 --> 00:52:14.000 And then if I go open Windows,or open Word. 1015 00:52:14.500 --> 00:52:17.000 Which as you can see fromthat screen is blocked, or 1016 00:52:17.500 --> 00:52:20.000 is managed I should say. 1017 00:52:20.500 --> 00:52:25.000 And if I select all here, And 1018 00:52:25.500 --> 00:52:30.000 then try to go open thisTop Secret Details into Notepad. 1019 00:52:30.500 --> 00:52:35.000 And Notepad is not definedas a managed application. 1020 00:52:35.500 --> 00:52:38.000 It's gonna inform me thatI can't move encrypted 1021 00:52:38.500 --> 00:52:39.000 content here. 1022 00:52:39.500 --> 00:52:41.000 So it's telling me that thisdocument that I am working out 1023 00:52:41.500 --> 00:52:46.000 of was authored, edited, openedin a managed application and 1024 00:52:46.500 --> 00:52:47.000 can't be moved. 1025 00:52:47.500 --> 00:52:50.000 And the content fromthat application or 1026 00:52:50.500 --> 00:52:53.000 that file can't be moved toan unmanaged application, so 1027 00:52:53.500 --> 00:52:56.000 it tells me that I can'tmove encrypted content here. 1028 00:52:56.500 --> 00:53:00.000 I'm gonna say got it andthen from file explorer, 1029 00:53:00.500 --> 00:53:04.000 we also clearly indicateda protected file, encrypted file 1030 00:53:04.500 --> 00:53:07.000 that is adherent to enterprisedata protector policy. 1031 00:53:07.500 --> 00:53:09.000 Relative to unprotected file, 1032 00:53:09.500 --> 00:53:13.000 which is a personal file thatyou can open, cut, copy and 1033 00:53:13.500 --> 00:53:19.000 paste as much as you want, bythe same building block icons. 1034 00:53:19.500 --> 00:53:21.000 In explore view, you can geta sense of what your corporate 1035 00:53:21.500 --> 00:53:24.000 documents are, and what yourpersonal documents are. 1036 00:53:24.500 --> 00:53:28.000 And if I were to later wipe thisdevice, the corporate documents 1037 00:53:28.500 --> 00:53:30.000 would go away, but the personaldocuments would stay. 1038 00:53:30.500 --> 00:53:35.000 So if I'm doing a selective wipeof the device which preserves 1039 00:53:35.500 --> 00:53:36.000 my recipes, but 1040 00:53:36.500 --> 00:53:41.000 my top secret information aroundmy corporate data goes away. 1041 00:53:41.500 --> 00:53:43.000 So that's a quick overview ofenterprise data protection. 1042 00:53:43.500 --> 00:53:45.000 Again, those policies can beauthored in configuration 1043 00:53:45.500 --> 00:53:50.000 manager console foron premises with HM based, 1044 00:53:50.500 --> 00:53:53.000 hybrid for hybrid or Intune andconfig manager together, 1045 00:53:53.500 --> 00:53:55.000 and it can also be authoredin Intune standalone. 1046 00:53:55.500 --> 00:53:58.000 To all configurations aresupported to author enterprise 1047 00:53:58.500 --> 00:54:00.000 data protection policies. 1048 00:54:00.500 --> 00:54:02.000 Okay, I have one last demo Iwanna show today and that's 1049 00:54:02.500 --> 00:54:07.000 the Windows Store for Businessand how Windows Store for 1050 00:54:07.500 --> 00:54:10.000 Business with the managementproducts of configuration 1051 00:54:10.500 --> 00:54:15.000 manager and Microsoft Intune,can be a powerful way to cure 1052 00:54:15.500 --> 00:54:19.000 and deliver great new universalapps to your Windows 10 users. 1053 00:54:19.500 --> 00:54:22.000 So, let's startwith an example of. 1054 00:54:22.500 --> 00:54:24.000 I'm in the Windows Store forBusiness portal, 1055 00:54:24.500 --> 00:54:29.000 I'm going to go ahead andgrab Office out of here. 1056 00:54:29.500 --> 00:54:30.000 So click on Office and for 1057 00:54:30.500 --> 00:54:33.000 configuration manager I'mgonna choose offline mode. 1058 00:54:33.500 --> 00:54:37.000 I'm gonna choose offlinemode primarily for 1059 00:54:37.500 --> 00:54:40.000 the reason that I want todownload the payload for 1060 00:54:40.500 --> 00:54:44.000 the application as wellas the license file. 1061 00:54:44.500 --> 00:54:47.000 So, that I could redistribute itthrough configuration manager, 1062 00:54:47.500 --> 00:54:50.000 and take advantage of all mydistribution points, and my 1063 00:54:50.500 --> 00:54:53.000 infrastructure, my hierarchy, toget the application out there. 1064 00:54:53.500 --> 00:54:56.000 And I'm choosing offlinelicensing mode because I'm not, 1065 00:54:56.500 --> 00:54:59.000 my clients can't talk tothe internet to validate their 1066 00:54:59.500 --> 00:54:59.000 license. 1067 00:54:59.500 --> 00:55:03.000 So they're optional licensemodes in Windows Store for 1068 00:55:03.500 --> 00:55:04.000 Business. 1069 00:55:04.500 --> 00:55:06.000 They're online where youactually, the user would go out, 1070 00:55:06.500 --> 00:55:08.000 or the client would go out and 1071 00:55:08.500 --> 00:55:10.000 validate it's licensewith the service. 1072 00:55:10.500 --> 00:55:14.000 And there's offline mode whereyou re-download the payload. 1073 00:55:14.500 --> 00:55:17.000 The client doesn't actuallyvalidate it's license. 1074 00:55:17.500 --> 00:55:21.000 You effectively have a setnumber of licenses as you 1075 00:55:21.500 --> 00:55:22.000 can use. 1076 00:55:22.500 --> 00:55:23.000 And you're accountable for 1077 00:55:23.500 --> 00:55:27.000 maintaining your licensingdetails that way. 1078 00:55:27.500 --> 00:55:29.000 But for offline mode, I'mgonna show that because that's 1079 00:55:29.500 --> 00:55:34.000 the one we've integrated intoconfiguration manager so far. 1080 00:55:34.500 --> 00:55:37.000 So if I choose offline andthen choose get the app, 1081 00:55:37.500 --> 00:55:39.000 that's then going to getme to distribution option. 1082 00:55:39.500 --> 00:55:42.000 And it's gonna tell me that Ican use my management tool to 1083 00:55:42.500 --> 00:55:44.000 distribute the offlinelicensed apps or 1084 00:55:44.500 --> 00:55:46.000 download them frommy inventory page. 1085 00:55:46.500 --> 00:55:49.000 So I'll give that a second toprocess and post to my inventory 1086 00:55:49.500 --> 00:55:52.000 page and the Windows Store forBusiness portal. 1087 00:55:52.500 --> 00:55:53.000 So it says it's ready and 1088 00:55:53.500 --> 00:55:57.000 tells me to go to the Inventorypage to get the application. 1089 00:55:57.500 --> 00:56:00.000 So I'm just gonna click OK hereand I'll land in Inventory, 1090 00:56:00.500 --> 00:56:03.000 and I see the offlineversion of Office, and 1091 00:56:03.500 --> 00:56:05.000 I have some actionsrelated to that. 1092 00:56:05.500 --> 00:56:08.000 And this is where I candownload it for offline use. 1093 00:56:08.500 --> 00:56:12.000 So I simply choose download foroffline use. 1094 00:56:12.500 --> 00:56:14.000 So I download herewith the license file. 1095 00:56:14.500 --> 00:56:15.000 So I just choose download and 1096 00:56:15.500 --> 00:56:17.000 there's the standarddownload process. 1097 00:56:17.500 --> 00:56:19.000 I pick a folder to save into. 1098 00:56:19.500 --> 00:56:20.000 I do save as. 1099 00:56:20.500 --> 00:56:23.000 And so I save it here inmy store apps folder on my 1100 00:56:23.500 --> 00:56:24.000 file server. 1101 00:56:24.500 --> 00:56:27.000 And what I would just simply dowith configuration manager is 1102 00:56:27.500 --> 00:56:32.000 I would just simply go tothe applications node. 1103 00:56:32.500 --> 00:56:36.000 And start an application wizard,pick a deployment type of this 1104 00:56:36.500 --> 00:56:40.000 application type, referencethe source and out it goes. 1105 00:56:40.500 --> 00:56:40.000 So it's that easy. 1106 00:56:40.500 --> 00:56:42.000 I just go downloadthe application, 1107 00:56:42.500 --> 00:56:44.000 redistribute it to mytargeted collection. 1108 00:56:44.500 --> 00:56:48.000 And out the application goes,so I'm able to go to the store. 1109 00:56:48.500 --> 00:56:51.000 Get a new universal app,say in this case Office, 1110 00:56:51.500 --> 00:56:55.000 download it into my environment,stage it on a file server, and 1111 00:56:55.500 --> 00:56:58.000 then redistribute it throughnormal configuration manager 1112 00:56:58.500 --> 00:57:02.000 processes, and the configmanager agent will then 1113 00:57:02.500 --> 00:57:05.000 effectively installthe application at the scheduled 1114 00:57:05.500 --> 00:57:08.000 time of its availability or ifit's optional the end user can 1115 00:57:08.500 --> 00:57:12.000 install it using the newend user portal. 1116 00:57:12.500 --> 00:57:13.000 So that wraps up the demos for 1117 00:57:13.500 --> 00:57:17.000 today, and now we're justgonna roll into the summary to 1118 00:57:17.500 --> 00:57:20.000 highlight the main pointsI was making today. 1119 00:57:20.500 --> 00:57:22.000 First step in howshould you deploy and 1120 00:57:22.500 --> 00:57:24.000 manage Windows really depends. 1121 00:57:24.500 --> 00:57:29.000 The EMS plus configurationmanager with the configuration 1122 00:57:29.500 --> 00:57:32.000 manager servicing model that Ihighlighted to keep it current 1123 00:57:32.500 --> 00:57:34.000 and up-to-date withcloud services and 1124 00:57:34.500 --> 00:57:36.000 the constant iterationwe're doing on that. 1125 00:57:36.500 --> 00:57:38.000 Really providesa great foundation 1126 00:57:38.500 --> 00:57:43.000 of flexible architecture touse upgrade or refresh or 1127 00:57:43.500 --> 00:57:46.000 whatever method you want to use,to get to Windows, get from 1128 00:57:46.500 --> 00:57:51.000 your existing Windows 7, 8, and8.1 population to Windows 10. 1129 00:57:51.500 --> 00:57:54.000 Additionally, thereare new capabilities for 1130 00:57:54.500 --> 00:57:58.000 new Windows devices such asAzure Active Directory join and 1131 00:57:58.500 --> 00:57:59.000 Intune auto enrollment, or 1132 00:57:59.500 --> 00:58:03.000 the provisioning package to bootstrap the device into a desired 1133 00:58:03.500 --> 00:58:07.000 configuration state at firstrun on new Windows device. 1134 00:58:07.500 --> 00:58:10.000 Including the option to do skewupgrade from Pro to Enterprise. 1135 00:58:10.500 --> 00:58:13.000 So, you can get that OEM baseimage device and get that up to 1136 00:58:13.500 --> 00:58:19.000 your enterprise skew usingyour volume license key. 1137 00:58:19.500 --> 00:58:20.000 With the configurationmanager and 1138 00:58:20.500 --> 00:58:24.000 Intune better together, boththose options are supported. 1139 00:58:24.500 --> 00:58:28.000 We provide you with the abilityto stay on track with your 1140 00:58:28.500 --> 00:58:31.000 current agent based deploymentthat's used to manage your 1141 00:58:31.500 --> 00:58:34.000 existing population of Windows,use that to get to Windows 10, 1142 00:58:34.500 --> 00:58:38.000 take advantage of the MBM sideof the hybrid configuration to 1143 00:58:38.500 --> 00:58:43.000 start managing Windowsthrough MBM manageability. 1144 00:58:43.500 --> 00:58:46.000 Manage devices where they livewith the levels of manageability 1145 00:58:46.500 --> 00:58:49.000 you need for particularusers in your organization. 1146 00:58:49.500 --> 00:58:52.000 And we allow you to dothat at your own cadence. 1147 00:58:52.500 --> 00:58:56.000 So the better together storyhere is really industry leading 1148 00:58:56.500 --> 00:59:00.000 in a sense that we provideboth sides of management. 1149 00:59:00.500 --> 00:59:03.000 What you typically use today,which a configuration manager 1150 00:59:03.500 --> 00:59:06.000 and then mobile devicemanagement through Intune. 1151 00:59:06.500 --> 00:59:09.000 And then those twoare tightly coupled together 1152 00:59:09.500 --> 00:59:13.000 to give you the best of bothworlds, to manage your way and 1153 00:59:13.500 --> 00:59:15.000 to move to modern management or 1154 00:59:15.500 --> 00:59:18.000 mobile device management at atime of your choosing for users 1155 00:59:18.500 --> 00:59:21.000 of your choosing at a cadencethat you choose to go with. 1156 00:59:21.500 --> 00:59:25.000 So the main point Iwanted to make is that 1157 00:59:25.500 --> 00:59:27.000 main point I wantedto make to recap 1158 00:59:27.500 --> 00:59:31.000 is our flexible architecturelets you manage your way. 1159 00:59:31.500 --> 00:59:34.000 Our servicing model forConfiguration Manager 1160 00:59:34.500 --> 00:59:37.000 is great for keepingConfiguration Manager current 1161 00:59:37.500 --> 00:59:41.000 without massive updates ofservice packs, new versions. 1162 00:59:41.500 --> 00:59:44.000 And it lets us keep in lock stepwith the changing ecosystem of 1163 00:59:44.500 --> 00:59:46.000 mobile devices. 1164 00:59:46.500 --> 00:59:49.000 And in particular the rapidinnovation going on with Windows 1165 00:59:49.500 --> 00:59:52.000 10 through the Windowsas a service model. 1166 00:59:52.500 --> 00:59:55.000 That, combined with our rapiditeration on the Intune service 1167 00:59:55.500 --> 00:59:59.000 side at a monthly cadence,give you high speed velocity 1168 00:59:59.500 --> 01:00:01.000 in a flexible architectureto deploy and 1169 01:00:01.500 --> 01:00:05.000 manage Windows your way. 1170 01:00:05.500 --> 01:00:08.000 To recap, we talked aboutchoosing the best deployment 1171 01:00:08.500 --> 01:00:11.000 method for your organization. 1172 01:00:11.500 --> 01:00:14.000 We talked about keeping Windows10 up to date with the servicing 1173 01:00:14.500 --> 01:00:17.000 model and the new servicingchanges we made to configuration 1174 01:00:17.500 --> 01:00:20.000 manager as well as to the rapiditeration we're doing on 1175 01:00:20.500 --> 01:00:22.000 the Intune side ofthe service and 1176 01:00:22.500 --> 01:00:28.000 we talked about managing some ofthe new Windows 10 capabilities. 1177 01:00:28.500 --> 01:00:34.000 To explore, try theEnterprise Mobility suite now. 1178 01:00:34.500 --> 01:00:37.000 Look it up on,you can get more information at 1179 01:00:37.500 --> 01:00:41.000 the link here withmicrosoft.com/ems. 1180 01:00:41.500 --> 01:00:43.000 Start using Windows 10. 1181 01:00:43.500 --> 01:00:45.000 Lots of documentationon TechNet. 1182 01:00:45.500 --> 01:00:47.000 Lots of documentation on MSDN. 1183 01:00:47.500 --> 01:00:49.000 Let us know your feedback. 1184 01:00:49.500 --> 01:00:52.000 Go to those forums, read theblogs, there's a lot of great 1185 01:00:52.500 --> 01:00:56.000 blogs out there by folks inour organization talking about 1186 01:00:56.500 --> 01:00:58.000 the servicing model,the better together story. 1187 01:00:58.500 --> 01:01:00.000 There's a lot ofinformation on there. 1188 01:01:00.500 --> 01:01:02.000 Lots of forums topost your feedback 1189 01:01:02.500 --> 01:01:03.000 around the servicing model. 1190 01:01:03.500 --> 01:01:05.000 Questions, concerns. 1191 01:01:05.500 --> 01:01:08.000 Go out there find the documents,find the collateral, 1192 01:01:08.500 --> 01:01:11.000 give us your feedback andthanks so much for your time. 1193 01:01:11.500 --> 02:00:00.000 Have a great day.