Windows 10 - Insights for the Enterprise (January)
January 16, 2019
Rex McMillan | Principal Product Manager | Ivanti
Adam Smith | Senior Product Marketing Manager | Ivanti
New bi-monthly webinar series offering updates from Windows experts from Ivanti, professional service providers, and your peers from companies like yours. This webinar will feature short, helpful sections including:
- Insider Preview - What features and changes are brewing at Microsoft and what it means for you when they become a part of your enterprise Windows 10 channel
- Outside Insights - Key understandings from customers, channel partners, or industry experts
- Migration Magic - Latest tips for improving the move to Windows 10
- Best Practices - A tip or two to help you improve your processes for managing Windows as a service
- Just Ask Rex - throw your questions at one of our leading experts on Windows 10! Let's see how he handles them
Adam: Welcome everyone to this Windows 10 Insights for the Enterprise webinar series. I think this is about the third or fourth one we've done, but the first one this year, in 2019. We're excited to be here. We will... Trying to make sure slides are working here. All right, so let's just kind of go over the agenda. The first thing is we'll do the intros and the goals of this webinar series. We'll also talk about 2019, and we're kind of in the final stretch to get to Windows 10 across the board. Next, we'll talk about some pivot points Microsoft is doing with their Windows 10. We'll also have what we call a conversation cafe, which is we take subjects that may be advantageous to some of you, and talk about it. They may be controversial at times, too. And sometimes I have to keep these two guest panelists away from each other, because we argue a little bit. Which is fun. Next, we'll talk about digital transformation, which is talking about kind of the things that are happening in the industry, and maybe the future of things. Finally, we'll talk about some Windows 10 features and how they apply to your Enterprise, and things to be aware about those. And finally, we'll have a question and answer. And applying to that question and answer, we have the question and answer panel in there, so you can enter your questions, we'll be monitoring those, we'll probably answer them towards the end. But if they come in context, maybe we'll answer them then. So let's get started.
So the first thing is, let's introduce ourselves. I'm Adam Smith, I'm the Senior Product Marketing Manager of UEM. I'm there in the middle. On my left...ah, we're arranged just like it is on the screen. On my left is Rex McMillan, and he's a manager, Senior Product Manager, probably Principal Man-...I don't know what your title is.
Rex: I can make one up.
Adam: Let's make one for today, okay.
Rex: Let's just not call me what you normally call me.
Adam: Okay. I won't call you what I normally call you. But anyway, he's in product management over at UEM as well as Ivanti Cloud and some things we're doing there. And on my right, I have Ryan Worlton, he's a Senior Product Manager as well over at the UEM products, especially focusing on the core things that we do with our endpoint management solutions. Very good. So, if we go to our next, we'll talk about the goals. The goals of this are first, create a conversation. You'll find that we have more of a conversation here, then really go through a lot of things and we can try to...I don't know. It's educational in the conversation, let's just put it that way. We want to talk about migrating and managing Windows 10, that's kind of the focus of this. And then finally...not finally, but multiple perspectives. In this case, I've got three people here, but many times we'll bring in guest speakers as well. This time we're not, we're starting off clean. So, and then the fourth, we'll get the most out of Windows 10. That's kind of our goal, is to make sure that you in the Enterprise get the most out of Windows 10 and can manage it and migrate to it. So, very good. Let's move along.
Windows 10 in 2019 I think is kind of the final stretch. If we talk about Windows 7 end of life, it is January 16th, if I'm not mistaken, and so that means 363 days from now it'll be the end of life of 7.
Rex: So it's actually not the end of life. End the life was last year.
Adam: Oh, okay. So, end of...
Rex: End of support.
Adam: Oh, okay. So I should change my slide.
Ryan: Well, a lot of us...I think you made the slide right, because a lot of us in the industry have really looked at it and said, yeah, I've got 2020.
Rex: As long as I have a support I'm okay.
Man: That's true, that's true.
Ryan: show some other slides here that kind of speak to those numbers...
Adam: Because after that, data will go on life support, probably. Because then you can actually still pick up support, but it's a little more costly.
Rex: Now, we've had some conversations with some Microsoft people, and like XP, they did end of support, and then a few months later there was a critical bug, and they released an update to it.
Adam: So they never really stopped supporting it. I mean, I think Microsoft, you know, is conscious of the fact that people are still on Windows 7, and if there's a critical enough bug, they're going to fix it.
Rex: Their verbal line out is, though, January 14th there will be no more updates.
Adam: They probably learned from the past, and want to make it a little bit more hard to fix. But I don't know.
Ryan: We'll see. You know, it's going be hard. I'm not saying it's going to be easy, but I think they're going to take a same tack that they have with XP. And there's going to be one or two things that are security related that may come out, and they say, okay, we've got to do some thing.
Rex: I think they'll be very far and few between.
Ryan: Agree. Agree.
Adam: So, here's an interesting thing. In your refresh cycle, many people have three years, some people have five years. So are you at least two thirds migrated?
Rex: And if you're on a three-year cycle and you're not two thirds migrated, you're not going to be done migration if you're doing a refresh cycle before migration.
Adam: Yeah. So if you're not doing that, then you have to consider other options to migrate, right?
Rex: That's right.
Adam: Okay. So, the question would be, how are your updates doing? So you may have migrated those two thirds, are you in that pattern of updates and feel comfortable with the schedule of updates, and how you're updating all of those machines? Because we've seen some customers who've lagged behind on some and then have to catch up. And it's a problem, you know, that's a problem for them.
Rex: And then the refresh cycle's kind of a moving target. Microsoft came out with an aggressive 18-month window, and it kind of had to change your tune a little bit. It's morphed, it's now if you're on Enterprise edition, you get up to 30 months.
Ryan: So it's been a moving target, right?
Rex: Twenty four...
Ryan: Yeah, but so 24 months, two years. I mean, I think a lot...I've talked to some companies that've said, we're just going to still go with the hardware refresh.
Adam: For the updates? For the Windows 10 Oh, wow.
Rex: ...I replaced the machines at 36 months. So basically, by time you get your new machine, it will have been out of support for three or four months, critical updates, and that's it. That's it.
Adam: Okay, so how about if people are planning on staying Windows 7 on some areas? Like, maybe there are certain applications that haven't been updated, what's the options there? Like, virtualize that, and then you do something with it, or...?
Ryan: I don't think it's anything new. I think there's still some, especially in the manufacturing plant, you still have some machines that are running specialized applications on XP. They isolated them, they virtualize them, they do things around them to make sure that they're still running. As long as it's not broken, they let them continue to run.
Rex: So the interesting part is, is like Windows 7, we know it's end of the extended support, which we'd love to argue that there will be no more patches from Microsoft. But if you go buy the Microsoft Managed Desktop, right, you've got that new virtualization where they provide the Managed Desktop, the VDI world. If you buy the Microsoft VDI, they're allowing you to stay on Windows 7 in their VDI environment with no additional charge for updates.
Ryan: Well, we're going to talk about that, man.
Rex: So they've got additional ways, we know that you're still going to be able to get hot fixes, just due to some of the features and functions that they're offering in a couple of their unique products. So, staying on Windows 7, it will be expensive but you can do it. But it may cheaper than some alternatives.
Ryan: Yeah, you might have a business operation where you say it's too critical, and I can't touch it.
Adam: Okay, very good. Well, what's interesting about that two thirds is you look at the market data and it says, really, the industry in a whole is just...as a whole is just over halfway there. So they're not two thirds of the way there, they're halfway there.
Rex: Now, the challenge with all statistics is where they collect the number, and who made the number, and what purpose did they make the number for. So, how many consumer boxes are included in this that will never get upgraded, they'll get thrown away this Christmas season, or bought a new one? How many of those are there? Well, they're pretty big play in the numbers. But 50% feels pretty realistic for the Enterprise as well.
Ryan: Yeah, I bet it's a wash. I bet it's a wash out there.
Rex: So, that's kind of scary, though. If you're telling me I have to be two thirds through, statistics show I'm 50%, there's a bunch of us with a lot of work to do.
Adam: Yeah. So there's going to be some that's going to be migrated in other ways, besides just a hardware refresh, obviously.
Rex: Absolutely. You know, I think the other part that's interesting on this chart is that Mac OS 10.14 is 4.73.
Ryan: Getting market shares?
Rex: That's the latest build. That's the latest Mac edition.
Adam: That's Mojave. That's Mojave.
Ryan: So the adoption rates for Mac OS continue to be pretty, pretty quick.
Rex: Yeah, I think they kind of set the standard out there of like, hey, here's how fast people will really migrate their devices if the experience is good.
Ryan: I think that's why Microsoft is doing what they are doing, in that way.
Rex: So let's take a look.
Adam: Oh. Here, this chart is pretty interesting, because it looks like they're catching up, as far as...
Rex: I would say it in July, when we look at the adoption rate of 1803, that was awesome. I mean, Microsoft's got to be thrilled. That spiked up less than 60 days, you're trending up into 80% of are on 1803. That's probably exceeding max rate of adoption.
Adam: That's right. And it probably is, until you get to 1809. Let's talk about the elephant in the room right now. see in the corner there
Ryan: So, I think Microsoft changed something. I don't think we know what it is yet, but they changed something in their process and their procedures in 1809 that was bad.
Rex: That definitely...
Adam: That leads us to our conversation cafe. We said it would be kind of controversial, maybe, but let's talk about 1809, where we're at with that.
Ryan: And I think if we asked the audience on the call today how many are frustrated with 1809, I think we'd have a lot of hands go up. If they were so brave to
Rex: So but Microsoft, I mean, you're pointing out all the challenges, but let's be honest. They had data, they leveraged the data, and they've done what's right. They stopped. They blocked it.
Rex: So they blocked that thing, they've gone public with it. It's just part of the new world of, hey, we've all known for all the years that software had bugs, we always swept under the rug, and we tried to contain it and not keep it in the media. And now Microsoft's like you know what? With the rate of change, we're all going to know. Okay, so it's just part of the game.
Ryan: You know, if we to go back to your original, the other slide there, where we see the adoption rates and the adoption curves, we've got this nice adoption curve, nice adoption curve, nice...we gte to 1809. If that's the true adoption curve, then we're actually slowing down the pace of... Right? It's kind of going the other way.
Rex: 1809 definitely brought some problems. Nine weeks. I have to concede to you, something changed.
Ryan: Something changed.
Rex: Something's broken. And I know when I get to the next slide, you're gonna whip up on me again.
Adam: So wait a second. What's the initial problem?
Rex: So, the initial problem here was that when Microsoft came out with 1809, users would lose data during the upgrade. And that's probably the biggest no-no of everything you do in an upgrade, you can't lose users data.
Ryan: Yeah. And sure it was only 1%, but if that 1% happened to be your CEO or a C-level executive, unacceptable. Right, you just can't.
Rex: As I lose data, it's unacceptable.
Adam: Yeah. Any percentage. Yeah.
Rex: And you know, one, you know... About a week ago, it's 10:30 at night, luckily I haven't gone to bed yet, I'm walking around my house, my cell phone starts going crazy. Neighbor lady, hard drive's gone down, she thinks she's lost the last three weeks of pictures of her kids. It doesn't matter if it's your CEO or your family pictures, loss of data is an emotional, huge, expensive, impactful, event.
Adam: And for an IT guy, it's a political black eye, right?
Ryan: ...pictures of a wedding.
Adam: Oh, yeah. I mean...
Rex: Oh, don't worry. You can reenact that.
Adam: It depends on the data, right?
Rex: So, data can't happen. So, that was their initial problem. Now, we know, because we've got nine weeks of data, in their upgrades in their...early adopters, or insiders, they had seen that problem. It had been reported. But it was a small enough percentage they thought they had found it. Now, we've both chased bugs over our lives in the software world that we know that there's bugs that you think you've fixed, then they reoccur and they reoccur, and...
Ryan: And you miss them
Rex: ...and you just...there's the same problem, or the same result can be caused by multiple sets of bugs. I lost data, I can't find my home drive, I can't get to my files.
Rex: That could be 12 bugs, not 1, even though it demonstrates to the enduser as one bug.
Adam: So how many times? How many times did they go through this process? Because you would think they would come out with a patch and we'd be done.
Ryan: It was more than a few times.
Rex: Well, I guess, really, if we go look at their support page, we're actually still in a blocked state.
Ryan: Still in a blocked state.
Adam: Oh. So when he said nine weeks, it's nine weeks and counting.
Rex: Well, now...
Adam: For the general enterprise.
Rex: 1809 is fully available for advanced users who manually request the update.
Ryan: So if you're a glutton for punishment, and you really want to apply the update...
Adam: Did you get it yet?
Ryan: Well, I'm on the Insider Preview, so I'm on, what, 1903, I think? I have to remember where I'm at, so... I don't know.
Rex: Right. So, when we go to the support page, they've been really good, very transparent. You can go and you can track out through every week, they put in a date of the status of what's going on. So, 1809's out. It's only being pushed out to users who request it. They're working on it. Just two days ago, the "what's new" got posted. So yes, they've had issues, but they've tried to be transparent and keep anybody from suffering any pain that they didn't have to. Now, the problem with being data driven and having an issue like this is it becomes really hard for me to, or anyone, to defend the...like, hey, we have data, we have telemetry, we push it out when it's good. Obviously, we missed some anomaly here, and we pushed it out anyway.
Adam: You know, it makes me wonder. I'm thinking out loud here, but is Microsoft being more open now than they were in the previous builds, and that's why we're seeing this difference in 1809? Is it just more visibility?
Ryan: Is it just a critical bug that just now...
Adam: I know we had the big, critical bug, with the data being lost, but it seems like after that they've really been very careful with some of these things that they may have let just kind of go in the past. And it's a hot fix for post release.
Rex: And that's very possible. So it's a very good key learning for those of us in the software industry, watching how they handle these bugs, the openness, the discussions of it. That's very helpful. The next part of it is, like, hey, if you're going to be telemetry based, you better really make sure your telemetry's dialed in.
Ryan: It's true.
Adam: So, how does this affect us? I mean, for instance, right here, things that make you go hmm. They haven't allowed me, as a Windows user, to be able to pause long enough, right? I mean, how long can you pause?
Rex: So, right now you don't pause? The new feature that's coming out with is pause.
Adam: Ohh. It's a new feature.
Rex: So this is a brand new feature...
Ryan: Top option.
Rex: Top option, pause for seven days. So this is kind of cool, because you can pause for seven days...
Adam: Vs. nine weeks?
Rex: ...which isn't really that great, because you just went on, like, a 10-day vacation. So I don't know really what you do on a 10-day vacation, but...
Adam: You should take one.
Ryan: That's not here, Rex, it's not here. Anywhere but here.
Rex: I come straight to the office everyday, 10 days straight, and you guys tell me it's not a vacation. I don't get it. But so, pause for seven days, while it feels really powerful to begin with, you could have been on vacation and had an update during the middle of that.
Rex: So the challenge that we're seeing here is as users, consumers, and IT departments, how do we maintain control and only take the updates when it's the appropriate time? Are we really willing to turn over to Microsoft our patching world?
Ryan: Well, I think as Microsoft acknowledged then, there still has to be control around when these updates happen. You know, that pause feature has not really occurred until they've gone to this we're just going to shove it down your throat kind of mentality. And then you've seen them kind of soften that, and here's a pause. So I kind of see it as a good sign, even though it's maybe not enough. For an Enterprise perspective, we still need to make sure that... Because we can control it from an Enterprise perspective, you've got more layers of things, different tools that can handle deploying that OS at the right time and making sure that we're not...
Rex: So, I think the key taking for me is, as an Enterprise, we don't run Windows update. Keep that thing turned off...
Ryan: Yeah, absolutely.
Rex: Get it turned off, get a patch management process, get the right red pilot groups, and make sure you're testing.
Rex: You know, I did this really good job a while back, and I talked you into joining my pilot group. Which now is, like, entertaining and horrible all at once. So for the last few years, I've been on Insider Preview, fast string, I run there...
Ryan: "Come on in, Ryan. The water's great. Insider Preview! It's great, it's solid."
Rex: It's nice, the water's blue, the sand is white. I didn't it was glass and chopping your feet to death the whole time you walk through this.
Ryan: Yeah, it's not that good.
Rex: So, your particular experience has been not very good.
Ryan: because I've gone from different inside Preview builds to other Preview builds that had conflicts with some of our own internal applications that I've had to work through. Which is good, because being a product manager, I find some of those issues and we get it to our DEV teams before others see them as the build releases. So there's goodness there, but there's also been a ton of pain lately.
Rex: So, you came to me and you railed me, explained to be the evilness of my sales pitch. And I've had to make a confession. The last 60 days have been my roughest and hardest time I've ever had on Insider Preview. So you bring up that 1809's a challenge, Inside Preview's been treating you...maybe not the most friendly methodology.
Adam: So, how does this affect my trust in Microsoft Managed Desktop, though? I mean, if we've had all of these issues, and it's going to be just updated on my desktop, and then there's problems, how is it going to...
Rex: It doesn't change my trust in Microsoft Managed Desktop at all, because Microsoft Managed Desktop, when you talk to them and you drill into a Managed Desktop...Microsoft Managed Desktop says we'll provide you the hardware, you give us the refresh rate, we provide you the OS, and we provide the support for that. Now, they're only using specific pieces of hardware, they're only using specific pieces of hardware, they're very, very specific on which things they're doing and how and where they're maintaining things. So, they have full control of those updates, when and where and how they're doing that. So Microsoft Managed Desktop, I don't think you have a problem, because they're not going to update your Enterprise until it's the right time.
Adam: Yeah. So, what would be the advice, then? I mean, we've kind of put it up there, but...
Rex: The advice is...
Adam: Either do Microsoft Managed Desktop, or create a process that's similar.
Rex: Make sure your process kind of mirrors what Microsoft's doing. What they're doing, they're doing kind of what Ryan and I haven't done. Ryan runs Dell, I run an HP, we're on diverse hardware. They standardize the hardware, they're only running on hardware that they've got drivers they trust, they update it, they put full controls around the updates, and they make sure that the experience is correct.
Ryan: Yeah, we've had a couple questions come in from that mentioned that, you know, that he's had issues with driver updates. You know, if I want a driver update, sometimes that's bundled into the Windows OS update process. And so if I want that new driver, I gotta go check for updates. And as soon as I do that, I'm kind of hosed. And so I think that that does extend...this whole updating process does need to extend into the driver side of this equation, and making sure that our process... You just, you can't really trust that Microsoft process, and those drivers can be delivered outside of the Windows update process. And Window's update's made it convenient, but I think we do need to look for other, as an Enterprise, look for other tools to control that update process.
Rex: Right. And, you know, the... As pointed out, if you leave automatic updates on, once you do a check for updates, you're done.
Adam: You're getting it. Yeah.
Rex: You're getting it. So, if you leave on automatic updates, you will be forced. So get those turned off, use a patch management solution, and get controls around this. That's kind of the methodology that we see...
Adam: So you can manage it like Microsoft.
Rex: Manage it like Microsoft, that's...
Adam: Okay, very good. So, let's go to our pivot point. And hanging off the edge, this is one of those pivotal points.
Rex: Go ahead.
Adam: So let's talk about Edge. So, is Microsoft losing its edge? Or are they sharpening it with Chromium? And tell me exactly what you mean by that.
Rex: So, Microsoft came out and made an announcement that they were going to quit writing their own browser engine, and they're going to use Chromium. So now in the naming convention of Google, you have Chrome, Chromium, and Chromium.
Adam: Wait a second. What was that?
Rex: You have Chrome, Chromium, and Chromium.
Ryan: All the same.
Adam: Was there an echo?
Rex: They're not the same. So you Chrome, Chrome is the browser that we're all familiar with that probably, you know...I'm not even going to guess the percentage today, but the most popular browser out there today is Chrome. It's based on an engine called Chromium. Now, Chromium is this component, but there's also this engine called Chromium. So the bare bones web engine is called Chromium, but you have an SDK called Chromium as well. So, it's kind of like Android, you call it Android, and you call it Android. There's 17 flavors of Android.
Adam: Okay, but it's still Android.
Rex: Its engine underneath is all the same.
Ryan: It's still Android.
Adam: Yep. Google is swallowing the internet. It's happening.
Rex: So, there's some good parts here, and some scary parts. The great part is Microsoft's browser's not going to be on the same rendering engine as Chrome.
Ryan: And this is a good thing because especially from a software development house, we tested one platform. It didn't work on Chromium, or Chromium based browsers...
Rex: But that doesn't mean they're the same. Chrome and Edge won't be the same, because the codecs, the plugins, the extensions are all custom for every browser that runs Chromium. So it's not Chrome, it's Chromium. So how a video plays in Chrome and how it will play in Edge will still be different. So your web page, when you embed video in, doesn't just mean it's going to work the same on one as the other because how I put codecs, which codecs I put in, that's just one example of the extensions Microsoft will have to do to Chrome.
Ryan: I agree. There's still going to be some [inaudible 00:27:29] from Microsoft to make this thing work. But I also think it's interesting that Microsoft has essentially thrown in the towel, or the whatever you want to call it, the napkin [crosstalk 00:27:40] That's kind of an all right, all right, you get one. And the interesting thing is, we were talking about this yesterday, it's a little bit like the VHS and Betamax wars, right? Betamax was better... Maybe Chromium isn't the best web standard for a browser that's out there, but it's going to win as an underlying browser technology. And I think it's a good thing. I know that there's going to be other extensions on top of it, but those extensions invariably will be very similar in nature, and I'm not sure that it's going to be that...it's a lot closer than it was before. You know, before I had Ed, which is a completely different browser, and Mozilla that was completely different, and Chrome was completely different. And now I've got...I can only focus on two that are very similar. And not exact, but they're similar.
Adam: Yeah. So, we're talking about reducing risk. What are the risks, then? I mean, that sounds like a good thing, if all the application vendors are going to be able to do their apps on one browser, or...
Rex: Right. I think this will bring some good things to the Chromium world because Microsoft's going to go put some of the extensions into Chromium that no one else has to support some of those unique extensions, and things that they really know that the browser has to do so they can continue to legacy out Edge and IE. The other risk is rendering engine Blink, if it's the de facto engine, can they veto the standards world? Up 'til now, we've kind of had the standards-driven, we've had, you know, we've got Firefox, and we've got Microsoft, and we've got Google, and nobody could run a veto. And now we have one group that owns it? Mmm.
Adam: You said swallowing the internet.
Ryan: It's going to happen. I think this is a step towards that end. I think people and developers are going to gravitate towards that and say, yep, Chromium's the thing, Blinks the thing. If you don't have those two worlds...
Adam: It becomes the standard.
Ryan: It becomes the standard.
Rex: The only other real risk that we have as an industry is as everything focuses and becomes part of that platform, if we have a bug in the rendering engine and you want to go change and fix that bug, you could impact thousands and thousands of things. As too many things get deep down in there, a bug can really impact a lot of apps.
Ryan: That knife that's there, it should have an edge on the other side. Because you're exactly right, it's going to simplify a whole bunch of stuff, you're going to see a lot more stability, but it's also going to affect a bunch of...
Adam: I should have found a double-sided...
Ryan: I know. Right?
Adam: I'm sorry.
Ryan: Trust the marketing guy to do our slides, right?
Adam: Digital transformation. So, how can Windows 10 help? In this case, we put that, but we want to kind of go out in the future a little bit since it's the beginning of 2019, and project a little bit and talk about some of the things that, for instance, our millennials. So, what devices are millennials using? You know, the impact millennials have if they get into management, or when they get into management, I should say, what will the future of devices be? So I want to have a little discussion about that. Windows 10, all right, is Windows 10 good enough for millennials?
Rex: You know, we always talk about millennials, and there's all these conversations, and then the study comes out and shows that millennials use email more than the previous generation. So they're still people...
Ryan: Yeah, they're still people, they still have to assimilate. And we've seen the numbers, only 4% of people are on Macs, and we kind of had to run the numbers of who those people are, they're not the new guys on the block, typically. They're typically the CEOs, the C-level executives...let's call them the technically challenged, shall we? I don't know.
Rex: It's a very expensive way to go.
Ryan: And it's a very expensive way to go.
Rex: So, if you're on Mac you...not to pick on our marketing guy with his Mac...
Ryan: when I said technically challenged, that was
Adam: Yeah. There's a glare.
Rex: No, Mac has a great point, but it's definitely not been the most affordable route. Windows is still the predominant, our millennials have used it, learned it. So the debate really comes down out of, you know, what's the role of some of the tablets and phones in the future? Do they replace my laptop? Does my laptop and my wearable replace my phone? Does my tablet go away?
Adam: So, yeah. So, how do things change? I mean, if you're talking about those devices, what do you have? Do you have a phone and a watch? Or do you have a watch and a laptop? Do you have a watch, air pods? A phone? What does that look like? What does that mix look like?
Ryan: And see, this is...yeah. And I look at this and I say people still have to be able to type, they still have to be able to do certain things. And if we look in the future, what progresses further? I would love to just carry my watch around instead of my phone, but the one killer app for phone that still I see everybody use, every day is the camera. And so I can't say that you're not going to have a phone with you, because people are so used to taking pictures. I mean, we're in meetings and you're drawing on the whiteboard and you say, great, I want to capture that. Ninety percent of the time, somebody takes out their phone, snaps a picture so they can go back to their desk and capture that information. Now, there might be one thing, we're on this screen, that might change that, but...
Adam: You said something about needing to type. It's true. Rex, you had point about this that [crosstalk 00:33:27] 93%...
Rex: Windows 10 is the first OS to really, from a desktop viewpoint, really start to push those barriers and boundaries. So in my Windows 10, I have the predictive type. So when I start typing words on my emails, I almost felt like I was back in networking, I type two letters, I hit tab, it grabs the word and I go on. I was like, man, I'm back in the Cisco IOS, because you can start to use tab as much as I do the other words. So predictive typing, anything to help us speed up. So, one of the statistics that's really interesting out there is 28% of time that you're on your computer, you're doing email. Now, so a quarter of my time, Adam and I had to argue, a quarter or a third, a quarter of our time...
Adam: Yeah. Do a quarter, I guess...
Rex: ...is spent in email. So, the average person types 40 words per minute, the average person speaks and reads at 300 words per minute. So if you can go from typing to talking to talking and dictating your emails, there's a 8X gain possible.
Ryan: Sure. But most, and I'm going to argue with you here a little bit, because I think that while that's great and fantastic, and pie in the sky kind of stuff, and I agree text to speech is awesome, it works great. But the problem is the workspace. We are in a ton of open office, open-air workspaces, bullpens, whatever you want to call them, that if everybody on the floor is text to typing, they're going to drive people crazy? And I know okay, you're going to tell me
Rex: You wear your headphones anyway.
Ryan: You wear your headphones anyway, and blah, blah, blah. But, you know...
Adam: But you're almost...what's the point of an open thing if everyone
Ryan: Right. That totally defeats the purpose. And so I just think in order for this to really, fully take off in the business world, I think you're going to have to see a change and a shift to the workspace as well. The physical workspace.
Rex: That may be possible. So today, they say that speech to type is about 93% accurate, 92, 93% accurate. And it's pretty dang good
Adam: Mm-hmm. I've used it.
Rex: They claim, the behavioral people that have been studying it, they claim when it crosses about 96% it will be as accurate as what we type
Ryan: And it'll be error free.
Rex: And at that point in time, you just adopt it because you're editing is less than what you're editing is anyway. Once it's as accurate as what you're typing is, it'll be just like the light switch. You just turn it on, and off you go...
Ryan: I know, I know.
Adam: So, keyboards are going to go away.
Rex: No. Keyboard's will still be there. You'll still use them. You'll still have jobs that you have to have your keyboard for.
Ryan: Well, we were talking about this in relation to engineers, software engineers.
Rex: Yeah, you know the little, you know, today and Windows 10, the editing commands are like go to word, and you say the word and it'll go to it. And if you say, like, "Go to Ivanti," and where the document has Ivanti in it 12 times, it'll highlight each one and put the number on, and then you just say, "Four," and the cursor will jump to the fourth Ivanti in your document. So the editing powers of it are super good. Go to the start of the paragraph, go to end of sentence, go to start of sentence, highlight sentence, those all are editing functions. Now, it's a learning curve. Just like we all had to learn to type, we're going to have to learn to edit, and there's going to be a lot of behavioral changes.
Adam: Yeah, but the speed of innovation from our developers is going to be phenomenal. I mean, I think we have a guy here by name of Paul Hillier that I think his typing speed was in the hundreds, just over 100. It was stupid fast, but you're talking 300, you're doing 3X our fastest developer, and you're giving them tools to automatically create complex syntax and things of that nature that could be bundled into voice commands. I think you could see, as this voice to text really grows in the development community, faster innovation and faster products to market, and disruption.
Rex: And one of our chat people just pointed out Dictate Dragon was 93% accurate 20 years ago, 25 years ago. And it's true, but the challenge with Dictate Dragon was I had to do the learning, I had to train it, I had to do all these trainings. And now, I turned on Windows 10, I went in and turned on speech to type, turned my Bluetooth headset on, and it's gotten better over the few weeks that I've used it. But I can actually compose a lot of my emails with speech, and it's pretty dang fast. My emails are now 20 words instead of 12 words when I send you an email, Ryan, so it's really going to delay your amount of time.
Ryan: It's awesome for Rex, because I've worked with Rex for probably 20 years. When he first started, the guy used, like, I think three fingers. Maybe four.
Rex: Two of them that
Ryan: But he was pretty fast, I'm just saying. But voice to text is going to be a game changer for Rex.
Adam: It already is.
Rex: But there's a lot of capability and change here. So the...
Adam: So, we may go back to those smaller offices, you know? Rows and rows of smaller offices.
Ryan: I totally see that coming.
Adam: That way you can still open up into a bullpen, you can still have the collaboration type thing...
Ryan: Yep. I think you're looking at forced change there.
Adam: But we may be going back that way, especially for the productivity.
Ryan: There's other things in that, but yeah. Yeah.
Adam: Okay. So, Windows 10 features. We're down to a few features here that we want to talk about. And the first one is related to speech, I believe, isn't it? No...yes, it is.
Rex: So, you know, one of the things that's happened in the security world is it's sometimes difficult to know which one of your things is being used. On my phone, I always tend to look down and say, is my GPS being used? So microphone now has a nice, new little feature. If your microphone's turned on and being used by an application, it's white, it's right on the bar, you can see it, it' highly visible. And right here, you and I were having a Skype call, so it actually even tells me who were you Skyping with so that we know, hey, it's there. So, as one of those training things, we have to tell our users don't be scared, little microphones going to appear. And if you see the microphone and it's white...
Adam: It's not listening.
Rex: ...it's being used. If it's black, it's not being used.
Adam: Oh, no...that's right. That's right.
Rex: So it's increased visibility, it's a good security feature, it's a good usability feature, and by putting it in here, you can also click on it and disable your microphone, change your microphone on a lot of features, come around. So microphone, more and more things are using microphones. We're using our computers to do more Skype calls, Zoom, there's tons of ways that people are making these calls. So it's nice to see this stuff coming up front.
Adam: Very good. Let's see...
Rex: So, the... Keep going.
Adam: Yeah. So what's next on our list of... Here we go. So we're going to talk about Windows Sandbox. So what does that mean?
Rex: Sandbox. Okay, so you know, in the past...there's a screenshot of my machine. You see down in the bottom toolbar, my box, I am either running VMware or I'm running Hyper-V, and I'm always trying to get a virtual machine so I can go put something in and test it. I always need that little test spot to go test an app, go test something, and it's a Sandbox, essentially. Microsoft has come out with a new feature, you can go in and enable this feature as part your OS, and it's called Sandbox. So you can see here I have an OS running inside my OS, it's called the Sandbox...
Ryan: So, wait, wait. So if I want to see if that email is really okay, I can pull it in the Sandbox?
Rex: You can go open it up in Sandbox.
Adam: Open it up and see if it's going to infect everything.
Rex: And every time you relaunch the Sandbox, it's fresh and clean.
Adam: Totally wipes everything.
Rex: Totally wipes everything. You don't have to install an OS, you don't have to bring a VDMK down, you don't have to bring a WHM, it uses your OS and creates the Sandbox...
Ryan: Pretty cool. Pretty nice security tool, too.
Adam: That is clever. So where would you use it? I can see how power users might use it, but...
Rex: It's a power user tool. This is a tool for IT guys. This is a tool so you can quickly spin up a Sandbox, test stuff, look at things. It's a security tool. You've got something bad, get it in the Sandbox. They're getting more and more controls around Sandbox, so Sandbox is a very powerful little tool without the expense of Hyper-V, without having to have the disk space of WHMs. It just spins up and it's an exact replica of the version of OS you're running. Upgrade your OS, your Sandbox is updated. Less management overhead and headache.
Adam: Okay, very good. So the next one, Explorer-friendly dates. Why Explorer? I thought Internet Explorer was something different.
Ryan: This is from the technically challenged man with the Mac. Uh-huh.
Rex: So, you know, it's been really refreshing to see them come back and put some of the friendly things in the OS. You know, in previous versions... Okay, so I'm date challenged, I have to, like, sort by date. Then I'm like, oh, so today really is the...what day is today? The 16th.
Adam: You are challenged.
Rex: So, by having the date modified, just now, two minutes ago, is a much friendlier methodology. So it's fun to see that they're coming back through, enhancing some of those tools that the users use all the time to be a little more user-friendly, and a little more...
Ryan: Of course, they kind of have to go find this. It's a pretty hidden feature to turn on. But it's there, it's not, like, right there.
Ryan: It's unfriendly...that's right, it's unfriendly... If you're a nice IT administrator, you can go set this for your users.
Rex: But the challenge is you want to make sure that you rolled these things in correctly. I appreciate how Microsoft has made this. We turn it on, we get testing, they get that ever important telemetry data. When the time is right, they'll turn it on for everybody.
Ryan: I can see that. I can see them making that
Rex: You don't want them to come out and say I got a new way to put dates. I don't care that your workflow and your process and everything is built on those. Here's a better way, and now you have to adapt. This gives us time, this gives us learning, our users can adopt things over time. So, it is a nice thing.
Adam: Focus Assist.
Ryan: I like this, this is great. Except for I hate the name, because, like, Focus Assist, what the heck is that?
Rex: It's little arms that hold my head, and it makes me look at the screen.
Ryan: Yeah. But I had to say to myself "do not disturb" before I really got it. I mean, you can turn this thing on, and it's going to only give you the updates in the Windows notification bar on the right side, of things you really care about. So if you're doing a presentation, you go in here and you turn on priority only, or you can turn it into totally disabled so I don't see anything, and life is great. Obviously, they're calling it Focus because now I can focus, but they really should call it Do Not Disturb, but...
Rex: I run, like, priority, only when I'm in internal meetings. Like, I don't care. Like, if something comes in that's top priority, you're not going to be offended that you see the little email ping thing come in and say, hey Rex, you need to look at this. So I run that pretty much all the time, and when I get done, like, in a meeting, presenting Focus Assist comes up and says, hey, while you were presenting, here's the things I suppressed, here's where it that. I love the feedback after I get done.
Adam: Yeah. It's a pretty cool little feature. I like it. Very good. And Screen Record. So, you were showing me this and, like, I have in the notes that it gaming...
Ryan: Written for gamers.
Adam: It's a game capture.
Ryan: Written for gamers, but you know, I think we're going to see this applicable in the workplace. I mean, for tutorials and a how-to kind of scenario where I just want to take a quick screenshot. People have been doing WebEx's and using other tools, finally, it's something that is native in the OS, so I can go out and say great, here's a little tutorial on how to go through and do something. It's Windows key G, which is pretty dang cool.
Rex: It's super cool.
Ryan: Not sure the G really means screen capture to me, but okay.
Rex: It means games.
Adam: What does it save it in?
Ryan: It's game, I know.
Adam: What does it save it in? What format?
Rex: So, it's very standard. It is interesting, there's a lot of controls with it. It does a great job, the resolution of the video and the audio are both great. But it is interesting for me to go in and enable gaming on my box. So...
Adam: What other problems does that bring? Just to get a screen capture.
Rex: No, I haven't found any downfalls. It just felt a little weird. Like, so I'm in here enabling gaming. But it's a great feature, it's nice to be able to tell you people, okay, just go to Windows key G, open up gaming... Or you can go down to the little search, type gaming, it'll bring it up, and off you go.
Adam: Very good. We have had a plethora...love that word, plethora...of questions during this session. So, if you want to open up and look at your questions, since you've been... Oh, okay. So, let's see. Let's pull up a few.
Rex: Okay, so... How about I'll start the first. "What is Microsoft Managed Desktop?" We referred to that, Microsoft Managed Desktop is a new service that Microsoft provides. You contract with them as an IT department, and they take over your hardware and your OS. So, you tell them how many users, which type of devices they're on, what level of performance they need, and they maintain the hardware, they maintain the software...
Ryan: Patching is awesome.
Rex: ...and patching. So, it's OS hardware and patches, and that burden's offloaded. Now, if your end users have a problem with it, they also get to call a support line for Microsoft Managed Desktop. So it's really fun to watch Microsoft step in and try to do those things with their OS that you guys's IT departments have been trying to accomplish as well. So, that's Microsoft Managed Desktop.
Adam: Hey, by the way, Ryan Cook says, "I've been in IT for 30 years, what's a vacation?" So, you're not the only one.
Ryan: You guys need to try it sometime and tell me about it.
Adam: So, let's see. "Just for clarification, are we saying updates can be paused for a maximum of one week? Will this result in increased effort needed from IT to manage?"
Rex: So, if you leave the control up to the end user, and leave automatic updates enabled, now your end users have a seven-day pause they can put. Once they push and check for updates, like, it's going to come, it's going to happen. Like 1809 right now, if any of you users have automatic updates and they go check for updates, they're going to get it. So, really from an Enterprise viewpoint, the best answer is disable automatic updates, get control back, and push them when you want. You really probably don't want to be running an automatic update world. Now, you may have some users that are running theirs, and at that point in time you'd want to teach them about snoozing and some of those features. But this is really a, you know, not an IT feature as much as it is an admission from Microsoft of you better get control of when you're going to apply updates.
Adam: Yeah, it's really...you know, from their perspective, it's really for them to...for the users who are not in IT, right? Here's another question, "Is the Sandbox a member of the domain and have network capabilities, or is it isolated?"
Rex: It can be isolated, it can have network access, it is not a member of the domain when it comes up.
Ryan: No, it's a flat machine in a workgroup.
Rex: Yes. Very, very isolated. Now, the interesting part about its isolation is while it's isolated, there's some things that bleed into it, which makes me really, like, puzzled. So, if you're on a laptop, and you enable Sandbox, and you're in economy mode trying to save your battery, your Sandbox is as well. So it inherits battery settings, but it's totally isolated as a virtual machine. So, very powerful that way,
Adam: Let's see. Just a continuation of that, "Is it a copy of just the OS, or your PC as it is loaded currently? Can you test programs in the Sandbox?" Yeah, that one.
Rex: You can test programs.
Ryan: You can test programs, yep.
Rex: But it is a copy of the OS, it is not your whole machine.
Ryan: And it's not the same machine as your machine. Same hardware, but it's a different...there's different registry keys, there's different...it's just like a new virtual machine on that box.
Rex: It's a new virtual machine, on your hardware. It's just like a new VMware. It's the exact same OS as your machine.
Ryan: Yeah, it's a new Hyper-V
Adam: Okay. "Will they retain..." this is related to Edge, I believe, "Will they retain Internet Explorer as a legacy browser?" Any ideas?
Ryan: I'll bet they do. I bet they have to keep IE out there for a little while longer.
Rex: They know they have to get rid of IE.
Ryan: I think they... Yeah, well...
Rex: It's all legacies, they know they have to. They're trying to make the moves to do it. Part of me wonders if this move isn't something that makes it so they can enable extensions and get rid of IE quicker. That would be the key motivator, if I was them, of why I'd make this move. So, no announcements have been made that I've found, but yeah.
Ryan: Yeah, it'll definitely be interesting to watch.
Adam: Here's one, "Driver issues?" with a question mark. "Please give an example. Thanks." I'm thinking he was talking about...
Rex: So, we talked about drivers a few times. Ryan's had, when he's updated on Insider Preview, you had a USB driver that was incompatible...
Ryan: I had a USB driver that was incompatible, I've had video driver issues that I've had to go out and get...and wait for Dell to actually produce a later video driver for me so that I could actually get it to work. And it's not that it didn't work, it reverted me to a generic driver. But there were some features that, like Windows key P that wasn't quite working right, so I couldn't present or connect to an external monitor, which was very painful until I got it fixed.
Rex: You could see your screen, but none of the rest of us. It was kind of refreshing.
Ryan: Well, thanks. Yeah, so...and there's been other issues. I mean, think if you go out to...if you Google the change history for Windows 10, and just browse down the change history for the last couple releases of 1809, you'll see a few driver related issues that are in there for other hardware platforms. So you've just got to be cautious. I think in the past we've just kind of blindly accepted that if I'm 10 or on Windows 7 and I go to the latest version, they're going to be supported driver wise. But with these, you know, updates from Windows 10 side, it's not been the case.
Adam: Yeah, to confirm that, Shelley makes the comment, "Oh, yeah. I accidentally got 1809 somehow, and it busted my Dell dock. And now the driver's to the point where I had to reinstall my OS. : ("
Ryan: Yeah, so it can be very disruptive.
Rex: So, Intel VLANS have been broken since 1803.
Ryan: Yep. VLANS, another driver issue there, with Intel. So, it's something that we've got to be very cautious of. And again, I'm very glad that Microsoft came out with the change to give you a 30-month window. So, once you get a stable build of Windows 10 running, you can stay on it for 30 months, and put the next build you're going to jump to through its paces before you do so. And again, it brings in the standardization, right? Because if you've got a, you know, proliferation of different devices in your environment, you're not going to be able to test through all of them.
Rex: Correct. I think the comment from Carlos Herras, the, "Hey, what do we recommend, installing the latest version of Windows 10 for the Enterprise, or Windows 10 long-term sustaining branch?" So, my response on this is long-term sustaining branch is super stable, but Microsoft has a lot of restrictions about where it can be ran, and when it can be ran. I've heard people actually have Microsoft reps tell them that Office 365 will not be supported on long-term sustaining branch, and...
Ryan: Yeah. I think...for my advice to anybody out there will be that this will be only for your devices running a very specific set of applications and
Rex: APMs, manufacturing...
Ryan: Yeah, something that's going to run... A piece of software is its main goal in life. It's not somebody's workstation, it's not, you know, used by Yeah.
Rex: If they need Office, long-term sustaining branch is not the right place to be.
Ryan: It's not right. But if it's running like a, you know, something in a manufacturing plant, LTSB is where you want to be.
Rex: That's right. I do appreciate the comment from Mark, that says, "Hey, we have blind employees. And they use JAWS to read the screen to them, and they're just as fast as the employees that can see."
Adam: Oh, I bet.
Rex: So, the reading and the audio interactions...
Adam: With speech-to-text, yeah.
Rex: Yeah, and this is the inverse, where it reads the menus to you, it reads the whole screen, and you react to those readings. So, definitely a lot of room for innovation here.
Rex: It's fun to see this becoming part of the base OS.
Adam: Yeah. Very good. I think we're almost at the top of the hour. So, let's see, if you go to the next we're always encouraged by comments that come in. And looking at future webinar topics, we've thrown a few up there. We'll look at some others, so please send us your comments. We'd love to hear from you. And hopefully this has been advantageous to you and helped you in some way to manage your Windows 10 in the Enterprise. And with that, we'll say goodbye.