Windows 10 - One Year Later

August 16, 2016

In the one year since the launch, Windows 10 is off to the fastest start in Windows history, with over 350 million active devices. Are organizations reaping the productivity benefits, how far along are they in their migration efforts, what best practices have distilled around how to handle apps and carry out updates with Windows 10?


Andreas: Hello and welcome everybody to this webinar. My name is Andreas Fuchs. I'm a Product Manager for Unified Endpoint Management at HEAT Software. And with me today is my colleague, Mario Schwalm, he is the Sales Engineer. We are both located in Germany, so good evening from Germany. This webinar is being recorded and please feel free to enter questions and we will follow up either at the end or after this webinar.
Okay, let's get started. It has officially been more than a year since Microsoft introduced Windows 10 in summer last year. And after 365 days, more than 350 million devices are running Windows 10. And this actually means that almost one million Windows 10 installation or upgrades per day. Let's have to look at the agenda. The agenda for today's webinar is first of all, we talk about how Windows 10 has been adopted in the market and if organizations have already migrated to the latest operating system. Then we talk about Windows 10 provisioning and best practices. And then we will spend some time on security, deployment, and configuration, and finally, how the consumerization of IT has impacted the businesses. It seems that there are not all lines on mute.
Okay. It's all about philosophy. More than one year ago, for Microsoft it was very important to position the new operating system in the market. And Microsoft had actually learned from their mistakes they did with Windows 8, which was not well received by the market. And Microsoft promised, an operating system providing all kinds of devices on a unified platform. And which they've always on top of the latest updates and patch levels in which is easier to maintain. It was supposed to be more, it's like a paradigm shift, for Microsoft it is Windows as a service.
Since its introduction, Windows 10 has become the most rapidly adopted PC operating system. Outpacing Windows 7 adoption rates by 140% according to Microsoft. And analyst research indicates that in the enterprise market, Windows 10 now accounts for a full third of all Windows deployments which is equivalent to the number of current Windows 7 deployments. And according to our surveys we did on our webinar in September last year, more than 20% of attendees said, that they would begin rolling out the Windows 10 within a year of its launch. And then additional 40% said that they would deploy it within two years. That bet played out almost exactly as predicted. So by end of June 2016, almost 40% of organizations across the globe had adopted Windows 10. And over 300 million devices are now running Windows 10. And more than 135 billion hours have been spent by users on Windows 10 actively using the system. That is quite a lot, an enterprise Windows 10 tablet adoption rates where proportionally even more dramatic. As roughly, half of all the Windows tablets used to perform business tasks and now running Windows 10. And the rapid adoption rate in the PC market was broadly driven by Microsoft aggressive upgrade program that allowed Windows 7, 8, and 8.1 users to transition to the new platform for free through July 29th of this year. It is currently unknown if Microsoft will extends any additional upgrade incentives after that date, but many companies utilized volume licenses and the enterprise editions of Windows, which they can upgrade later at no additional cost.
So talking about the PC market on this slide, Microsoft designed the new operating system to provide a more seamless use experienced across PCs, laptops, tablets, and smartphones. And in terms of the actual spread, organizations in the implementation phase are largely running the operating system on laptops, followed by desktops. However, at nearly 40% are running Windows 10 on their tablets, and only 10% are running it on their Windows smartphone. In the previous slide where we saw roughly half of all Windows tablets used to perform business tasks are now running Windows 10 is, because the majority of these deployments are newly purchased devices rather than upgrades. And account for a 40% increase in overall Windows tablets adoption since the operating system was introduced. While Apple iPad continue to dominate the enterprise tablet market, Windows 10 is helping Microsoft closing the gap. In fact, an EMA research the data, revealed that 10% of iPad market share has been given away to Windows devices in the last year, correlating directly with Windows 10 availability and adoption rate.
Certainly, one factor in the increased attractiveness of Windows tablets is the lower purchase costs of Windows surface tablet, and Windows based tablets offered by third party vendors. But the primary motivation for business adoption of the devices is the unified code base of Windows 10. Applications commonly employed on PCs can be simply stalled on Windows 10 tablet without requiring any porting or recompiling processes. In addition to this, they can be managed and secured by solutions which are already in place.
And we saw this picture many times last year. So when Microsoft launched the latest version of Windows a year ago it claimed that one billion devices would run the new operating system by mid-2018. And as I said, over 350 million devices are now running Windows 10, so it's still a long way until they will reach that goal. There are so many articles out there talking about Windows 10 after one year and whether it has been a success for Microsoft or not. Microsoft recently admitted that they will likely miss its target for one billion devices to be running their operating system by end of summer 2018. And the reason for that could be, that growth has been slower than expected because fewer people are buying new PCs, and many who have older versions of Windows don't care enough to update to Windows 10. About half of all PC's are still running Windows 7. The issue isn't really missing that self-imposed deadline. What's more of a problem is that Windows 10 on mobile devices such as phone failed to get the momentum.
So now I would like to open the line for our first polling question. We would like to do the first poll and kindly ask to whether you have started a Windows 10 project already or not. And the question is either yes or no.
While you are voting, I mean according to analysts, now that the free period has ended businesses will begin to deploy their operating system in earnest, and many organizations are already piloting Windows 10 devices. Maybe you see no reason why you shouldn't continue using Windows 7 until Microsoft stops patching it against security flaws. We're still waiting for the results to show up. Okay, so the result is that 57% have already started Windows 10 project and 42, not.
Let's talk about Windows 10 provisioning. For business work environments the availability of Windows 10 has opened the door for the broad adoption of Unified Endpoint Management practices and actually this Unified Endpoint Management practices have redefined how applications, and data, and services are distributed across enterprise user devices. And rather than maintaining independent solutions for managing mobile and PC endpoints, the unified code base of Windows 10 allows organizations to employ a single set of consolidated processes and tools to support all the Windows based user devices. This greatly simplifies and reduces the administrative practices and makes the Windows platform even more attractive to the enterprise market. So what are the market rivals for that? First and foremost, we have the users. Well users actually expect to be able to work in any location and have access to all their work resources. A user usually has at least a desktop, or a laptop, and a mobile device, and then we have the devices and we have seen a proliferation of devices, and that has changed the stand-up based approach to corporate IT in managing and securing all kinds of devices. And we have the variety of applications. Deploying and managing applications across a platform is difficult, and all kinds of applications have to be taken into account, whether they are desktop applications, universal, all of the modern UI applications offered them in an app store, or even in a corporate store. They are all some roots applications available. And then we have to take data and security into account. The users need to be productive while the administrators are maintaining the complaints, and also the data must be secured. It's also the separation of corporate data and private data, we have all seen the concept such as the "bring your own computer" or "bring your own device", and corporate data and the private data. And finally, it also requires an infrastructure that is able to securely manage the corporate connected devices over the local area network, or the cloud based devices, or endpoints everywhere. Any it has to take bandwidth into account, considering all of these requirements, scalability requirements has support offline installation, VPNs, Wi-Fi, and so on.
Before we move on, let's ask some questions that might be important when considering a Windows 10 migration or update endeavor. So first of all, what are the benefits for a company's thinking of rolling out Windows 10? And besides the fact that this is a clear recommendation for Microsoft, it is a platform which supports all devices such as traditional devices but also mobile tablets, convertibles, and so on. And according to IT professionals, the reasons can also be the end of life support for Windows 7 by 2020, and also the enhanced security Windows 10 provides, and there are a lot more reasons and benefits. Just to mention a few, and what is the right time to migrate? Well, there is probably no right answer to this question. It really depends on the organization and the plans they have. It can be compatibility reasons on newly provisioned hardware if purchased with, and Windows 10 preloaded already. Then of course Windows 10 has some appealing features. To only mention a few and I'm sure you all know them. The optimized start button, enhanced security, or the ability to operate as Windows update or and in place upgrade. And we are going to talk about that as well. Support for multiple desktops, the new browser, Edge, and Cortana, and maybe some more. So everybody has their own favorite feature they would like to see in Windows 10. But there are also some Windows 10 concerns, adopting the new operating system. So according to IT professionals, the reasons for waiting before upgrading to the new operating system can be, well first of all the user training end-users have to become acquainted with the new look and feel, and the new behavior of the operating system. Maybe there are still a lacked of support from third-party vendors for the new operating system, and in terms of the top challenges organizations experience when implementing Windows 10, compatibility issues with hardware and software and the time required for the upgrade process, they top the list. However, only about 30% of organizations experienced that in the early releases of Windows 10. So, as far as the time is concerned necessary for the whole upgrade process, this is actually something we will cover in this webinar as well, and we'll show how we can help in migrating to Windows 10. Maintaining Windows 10, as well as assisting vulnerabilities, and provide appropriate patches to the system with a centrally controlled mechanism.
What tips can we provide for updates? First of all, organizations need to decide what strategies they will pursue regarding Windows 10. Will they do an in place upgrade? And wide and load updates on attrition based upgrade? Where with newly machines coming in they are all already have the Windows 10 on it, so they come automatically under management. The upgrade phases, they need to be planned. Analysts typically recommended 12 to 18 months. It is necessary to check the compatibility readiness of hardware and software. Check the license contract if they fit. Then what about the privacy settings? You should think about the security concepts prior to migration. By default, Windows 10 save and for instance browser and search history in the cloud but it does also a lot more. And it talks a lot to the Internet by default. And we will see a lot more best practices in the next couple of slides.
What are some of the security issues to be aware of in regards to Windows 10? So with this operating system the way Microsoft provides updates has changed. Microsoft releases updates, both security and non-security, also outside of the legacy Patch Tuesday. And of course, patch management remains the very important topic, and I will talk about this as well.
Last question, what else do they ask that need to know before they do the deployment? One answer is with the Windows 10, the approach of traditional software distribution has slightly changed. Think about Office 365 and its click to run technology. And also, the Windows business store which allows organizations to offer applications and let end users manage themselves. It might sound conflicting having control over endpoints via an endpoint management solution and at that same time giving end users the freedom to shop whatever they think they need.
Many companies spend a lot of time on migrating projects despite the fact that Windows 10 upgrades itself automatically. A holistic migration or holistic migration endeavors can become very complex. According to Microsoft, the migration from Windows 7, or 8, 8.1 to 10 is easier than before, when we look back in the former XP times. But when we look back and think of the migration from the XP, 7, 8, from the XP to Windows 7, 8, 8.1, we see that there was no direct migration way. Usually preparation were comprises backing up old data, installing the new operating system followed by drivers, applications, users settings, and other configuration changes. Compatibility was a big issue as well, all that was very time consuming. Now, with Windows 10 we see different migration scenarios, not only coming from a previous operating system, but also a feature pick-up rates. So we have or actually three scenarios. First is the wipe and load, which is more or less the reinstall. Then we have an in place upgrade, and then we have that provisioning of Windows 10. And all these mapped to the, whether you come from XP, or from Windows 7, 8, or you doing a feature pick upgrade, or have already operated to the anniversary update.
Going to details would be beyond the scope of this webinar but usually the characteristics of these migration scenarios, whether the upgrades or reinstallations via wipe and load. They are first of all, backup the data and the settings, then install the new operating system, afterwards install the drivers, applications, and so on, and then restore the safe data and the configuration. The way organizations can do, it really depends on whether they have an architectural shift from 32-bit to 64-bit because in this case, it is not possible. That would require a new install rather than an in place upgrade. Another reason is to see a fresh new installation from scratch as a clean new start, or there is the hardware change that would be another motivation. The in placed upgrade actually does more for you, more than the wipe and load approach. The in placed upgrades, Windows collects data, the configurations, and drivers, and the applications. It installs the new operating system and restores previously collected data, it also has the built in incompatibility check and recovery functionality. At first glance, in place upgrade sounds good since it reduces the deployment cost and runs automatically. However, the drawback is that, this upgrade doesn't work from 32 to 64-bit versions, and on new hardware it is just not possible because there is no operating system installed to start from. And it requires much more disk space due to apps and recovery functionality.
And storage is the Windows provisioning the Windows provisioning makes it easy for IT administrators to configure end-user devices without imaging, using the Windows provisioning, and IT administrator can easily specify desired configuration and settings required to enroll the device into management. With a simple provisioning package, it is possible to set a device name, configure Wi-Fi network access, set the local administrators password, and enroll a device into your active directory. However, according to Microsoft, this approach is best suited for only small or too small medium sized businesses. In the past, the recommendation of many IT professionals at Windows 7 times was a clean install is over an in place upgrade.
Let's have a look into the Windows 10 anniversary updates. Windows 10 second big update labeled the anniversary update is finally available. This is a huge update that touches every corner of the operating system. It includes many, many more changes than the November updated. And the funny effect is this anniversary update reports itself as version 1607, despite the fact that it technically launched in August instead of July. If you installed the anniversary update on your Windows 10 computer, you will automatically perform an in place upgrade. So the in place upgrade has become a good and useful alternative to wipe and load. However, the preferable way would be to have a solution which supports both, or any other migration scenarios of your choice.
So and that brings me to the next question. We would like to kick off the second survey and give you the opportunity to make your vote. The question this time is, when do you plan to upgrade to Windows 10? Is it this year? In the next two years? By 2020 or I don't know. And you are able to vote now. And again, last year we saw that two thirds of the organizations thought that they would update within two years. And actually when we did that webinar in September of last year, another interesting point was that in EMEA, a majority prefers the wipe and load update whereas in North America it was two thirds preferring in place migration. And probably the ones voted for yes in the first poll, actually responded with this year. Okay, so the result is 40% go within a plan to upgrade Windows 10 this year, 40% this year, and 60% in the next two years. So nobody voted for by 2020 or I don't know. That is actually a good result. Thank you very much.
Okay, talking about best practices approach. Operating system deployment and configuration are two of the most time consuming software management tasks, and automation, and compliance space management. That saves valuable time and eliminates software of error. We can actually split up the migration and upgrade plan into six phases. First of all is the compliance readiness. This is the first phase where we get an over few of existing endpoints and see whether they are Windows 10 ready or not. The goal is to get a clear statement if my environment is Windows 10 ready. What additional costs do I have considering both licenses and hardware cost? Additionally, you would see which software is installed, where and which might not be compatible with the new operating system.
The goal for the personality migration, which is the second phase, that's the user state migration. And is a fully automated backup and migration of all user specific settings within the system so that administrators are able to recover them later, quickly and to get users back to production in less time. And that is an essential part of the Windows 10 migration plan, because that is probably the phase which take very long to restore all the user settings they made over years when they spent time on the previous operating system. It's advisable to back up and migrate personal data in order to recover them later on.
The third phase obviously is the operating system deployment itself and the configuration. And that's obviously it's automating this process as much as possible. And in this phase IT administrators define what's required to roll out the operating system itself. It is not only packaging the operating system, but also the corresponding drivers for both internal and external hardware devices such as printers, scanners, and so on. And then we have the software deployment, application configuration packaging, and deployment of these applications, and with an automated solution, organizations are able to reduce their time spent on package creation and time spent on software deployment. Patch management, this is all about securing the endpoints. A solution should guarantee a high level of automation for all phases of patch management from identifying vulnerabilities, selecting the relevant patches to rule based implementation. And that's for both Microsoft patches and patches provided by third-party vendors. And then of course we have the day-to-day IT operational tasks. After the upgrade, IT administrators need to monitor and report on the roll out progress to ensure that all the endpoints have been upgraded successfully. And also in compliance date from a configuration, as well as security perspective. And in case of failure, organizations can react immediately and take the appropriate measures.
So our Endpoint Management Solution supports the deployment of the latest Windows 10 anniversary updates, not only but also and automates the update in our entire environment. This upgrade basically follows the same deployment rules like the initial Windows 10 set up when it was released in July last year. It utilizes the in place operate method to install it onto your computer, and it usually follows these for deployment steps. There is a preparation phase, where we check several requirements such as hardware requirements or an activated putlocker. Only computer passing the requirement checks would continue on the second phase. And the phase to performs the upgrade to the latest Windows 10 before in the post processing phase, additional task like this cleanup are executed. And the rollback phase is only in case something went wrong. Just imagine if something went wrong during the upgrade, then this is an automated way of getting back to the last restore point.
Heat Endpoint Management automates the fourth step. What you see here is a screenshot of the console of our endpoint management solution. And in this console, administrators create packages and assign them to endpoints, users, or groups. It allows managing all kinds of endpoints from a single console from virtually anywhere. It shows that overall compliance across your environment and displaced it in real time to the administrators in the traffic light compliance overview.
During the preparation phase, which was the first phase we saw on the previous slide. The solution gathers system prerequisites such as CPU, memory, and available disk space. And if the requirement does not meet the prerequisite, a warning is shown. The in place upgrade basically work the same way that initial Windows 10 update, and it does that by calling a setup .exe with a custom command line. There are actually a lot of custom command lines available for the setup. And the upgrade process usually does not take longer than 10 minutes on modern hardware. And administrators can manage this within that single console for the whole organization, for all endpoints, user groups, or even location, and even in a highly distributed environment. It supports several Windows 10 editions, creating package content and defining deployment targets is very flexible and easy to use even test groups, or piloting purposes can be managed within the product if environment. And given the fact that Microsoft plans to release major updates every four months, organizations will face a continuous update process here. And they have to find a way for automated testing and deploying the new updates.
Further in the endpoint management space, there is an ongoing security challenge where we have seen an incredibly growth in malware up to 40 million malware introduced every month within the last year. Malware is definitely more sophisticated and more targeted meanwhile. Essentially you have custom malware that's been created on an individual organization that would not be recognized by traditional antivirus tools. And then also it's no longer just the Microsoft world, the bad guys are really targeting beyond the Microsoft operating system and beyond the Microsoft applications that are on a typical Windows desktop or laptop. And third-party applications may make up only a third of the most prevalent applications installed on a typical Windows machine. But they actually represent 75% of the open and active vulnerabilities on a typical Windows desktop. So the majority of the vulnerabilities out there and active on the third-party applications, you need to be able to patch both the Microsoft and the third-party applications from Windows.
And then finally, it's about protecting against both the known and the unknown risks. What does that mean? When we know that over 90% of cyber-attacks exploit known security flaws for which a remediation is available. By that the remediation means there is patch available, so 90% of your risks on the desktop is eliminated by proactively managing your vulnerabilities, by proactively having a patch management process in place.
Why is endpoint security management important? So this is all about having that proactive defense-in-depth strategy. Some of the key question you want to ask yourself is, are your Windows 10 devices used outside the network? Have you ever lost a USB stick with private information on it? Are all of your programs, whether they are operating systems or third-party applications are they patched according to policy? And how long did it take for you to be productive again after your last virus outbreak or security breach? Those are all excellent questions that an administrator should be asking of their own environment. It's all about securing against Malware, data loss, and other security breaches. In any secure environment no single tool is going to provide a complete security protection. And even with all these tools in place there is still a possibility that there could be a security breach. The entire goal of a complete security solution is to provide a practical defense-in-depth and to have multiple layers of defense within your environment. Starting with configuration management, move on to patch and remediation, these are the most basic security protection tools that are available. But another point is having some basic firewall protection for configuration policies that can be sent out to the Windows 10 firewall on endpoints. And part of the goal of the defense-in-depth strategy is to slow down the attacker, so either A they give up, or B you have other tools in place, they notify you that there is an attacker that is trying to exploit your environment so that you can take action on it.
So you may probably argue, hey wait a minute there is Windows 10 with that nice feature of device guard available. With device guard, Microsoft is essentially trying to roll back the years and change to a model whereby only signed code is allowed to run on a Windows system. This is a good idea and will definitely help with making systems more secure. However, there are a few challenges to this. About 5% of Malware is already digitally signed today. And I have no doubt that this percentage will increase over time to counteract to device guard. And there is lots and lots of unsigned legacy made software out there which would get blocked by device guard. In updating this software is impractical. Microsoft understands this and has developed a process to sign these unsigned depth. Given the shared volume of unsigned applications, this place is a significant burden on administrators and on in-house software developers to ensure that their test software versions are correctly signed. As a result, it will be disabled in many cases because of these exceptions and that would create security hole. As a result of the above points, even Microsoft admits that device guard will be used alongside both antivirus and application control solution for the foreseeable future. Effectively device guard is complimentary to application control. So unlike Windows 10 with its device guard, our application control provides greater flexibility for real world software via our trust engine and it reduces administration overhead. And it provides more granular control to restrict which applications can be executed and by whom?
Keeping your endpoints updated with the latest patches is crucial to keeping your network secure. This practice is the first and last line of defense against exploits whether they are existing on you. And Microsoft has adjusted their security update mechanism with Windows 10 to one where they released cumulative updates for Windows 10 as soon as they are fully tested and not necessarily on the second Tuesday of the month. That being said, updates for all other supported Microsoft platforms and applications are still distributed on patch Tuesday. And even in the world where they are not, it's still best practice to establish a regular update timeframe in your organization. So Patch Tuesday is a convenient time to establish that upgrade cycle. Organizations need to ensure, they have the right patch management solution that supports Windows 10 as well as provide for third-party applications patching. And with the heat patching module, tightly built into the endpoint management solution, the organizations are using a centralized management capability and can now quickly determine which machines are patched and have achieved a manageable level of automation in the application of necessary patches. So they are not subject to any major virus attacks. And critical patches, or updates, or service packs can be quickly applied to all endpoints across the distributed network. All required steps can be automated, that is from scanning vulnerabilities, to downloading content, creating a ready-to-deploy packages, test all pilot patches, and finally to deploy them.
Deployment and configuration of Windows 10. Once you have found and you preferred deployment method, and you find your patch management prodigy, you might also need to take care about the configuration of your operating system. Think about all the new group policy of privacy settings. And it is not only deploying MSI files or executables. With Windows 10 also a new package type such as aptX packages, based on the universal Windows platform, need to be handled same for a trend applications such as virtual thin-up packages or Office 365 based on the click to run technology. All different kinds of applications have to be managed by one solution, and if that's not enough also creating packages for drivers, operating systems, patches and configuration settings is essential. It's all about ease of use packaging, and heat endpoint management has the most flexible and easy-to-use mouse driven application packaging engine. It is offered by a unique software and configuration packaging workbench, designed by administrators for administrators. And it's really eliminates the need for customers to rely on third-party packaging tools. We make it our goal to hide the complexity by offering easy-to-use wizard and preconfigured tools as part of our packaging engine. The goal really is to reduce the time spent on package creation and to reduce time spent on software deployment. Same for configuration settings, as I said before Windows 10 out of the box talks a lot towards the internet. There are group policies available to restrict this. Pre-defined and ready to use configuration packages help customers in the migration projects and to protect personal data and privacy. As you can see on the screen shot, there are also other configurations settings available such as power settings, firewall settings, and so on.
User experience. User expectations have changed in recent years. And IT operations used to provision a PC to an end user complete with pre-determined applications and services for a long time. End users simply have to accept what they were given, but the mobile device experience has changed all that. On-demand and self-service capabilities are common in consumer focused, mobile applications, and users are now demanding the same responsiveness in the delivery of enterprise software and services. Users must be able to access applications and perform tasks in the same manner regardless of the device they happen to be using. Establishing a consistent user experience requires the introduction of standardized user self-service processes. This portal can take the form of an enterprise app store, for instance, which provides business approved software. To ensure consistency across endpoint device platforms, user profiles should leverage group. And user information and then enterprise listing services such as active directory, and policies can be applied to these pre-defined groups or user roles that are standardized for each supported endpoint platform. A standardized workspace should also be provided that present a consistent desktop look and feel across supported endpoints.
Users are much more comfortable managing and provisioned the endpoint. In fact, they prefer self-servicing features. Access to services and applications must be quick and easy to perform. They must be reliable and highly available, and meanwhile all IT management processes should be user-focused. The software shop you see here offers applications to end-users so they can manage themselves. And in addition to this is it offers also other configuration packages such as printers and drivers. So for instance, if an end-user works in different locations and appropriate printer is available ready for installation within seconds, it's the easy button. Users also want transparency to see any progress of changes in real time and they want to configure maintenance Windows on their endpoint as well.
Operating system self-service. If that is unable from a central point it is possible to trickle the upgrade to the new operating system or the reinstallation of the whole computer during boot time. This gives the end-users the freedom to decide when to migrate rather than having that dictated by IT. After a great period, and for instance, two weeks or so, the upgrade can then be automated during a PC or UEC boot. The operating system self-service provides an easy to use user interface for end-users to provisionary, provision their endpoints and it is also customizable.
To achieve a better user experience, organization start with the base requirements for enabling user self-services and for all supported platforms, access to business applications that should be granted via some kind of a user portal. Policies apply to the portal identify who is authorized to access the resources and who is not. And to self-service capabilities, the self-service capabilities are increasingly becoming a leading area of differentiation. Together with an endpoint management solution as the automation platform, their requests get fulfilled automatically. Heat Service Management integrates software management capabilities of throughout the software life-cycle and then able end-users to select software in the service catalog. Leveraging the service management workflow, a software package goes for approval steps before production. In this example, we see here end-users can easily request and schedule a Windows 10 in place upgrade. And optionally the request needs approval before the upgrade process kicks off automatically on the endpoint. Once done, they can request and gets fulfilled. And also, Service Desk analyst can trigger either an upgrade or repair applications by simply reinstall them.
Okay, let's do the last poll. It's about the Windows business store which Microsoft first to introduce with Windows 8 and tried to accomplish the last perfection with Windows 10, and it requires the store apps so users are able to shop software from the corporate app store. So the question is how many of you plan on utilizing the Windows business store? And the answers would be A, we will use the store only, which requires the app store an endpoints for future deployment, and let the end-user decide. Or you go still with a centrally controlled deployment and configuration, or probably it's a mixture of both, option A and option B, or you just don't know. So the question really is, and that seems to be a paradigm shift as well, do organizations want to explicitly let end-users decide what to install and when? So we have 50%, oh no that changed now. Yeah, the poll is still ongoing. So it is really zero for answer A, which means only at app store. We have 42% still a centrally controlled deployment and configuration, we have 28% answering C, a mixture of both option A and B. And 28% don't know.
So HEAT Software has the comprehensive Unified Endpoint Management Solution, Consolidating Client Management, Enterprise Mobility Management, and Endpoint Protection Platform to control and secure all traditional and mobile endpoints in a unified manner. It is designed to automate the operational IT tasks from installing operating systems and applications to monitoring and maintaining the devices over the time. And the solution contains all tools necessary to manage and control physical, virtual, and mobile devices across their life cycle from a unified and intuitive console.
There is also the HEAT community, so please feel free to follow us on the HEAT community. It provides a lot of information, feel free to post your questions or search for answers from other members. It also has a portal for our globalized partners.
So as Microsoft blows out the candle on Windows 10 first birthday cake, it can rest assure that the platform's future looks bright, at least in the enterprise market space, Windows 10 can be expected to continue its aggressive migration trend. And thank you very much for your time. And I think now don't we have some time. We are going to review the questions.
Mario: Maybe Andreas let me just get to the first question and...
Andreas: Sure Mario.
Mario: One person has just asked whether, he has some Lenovo laptops for which the upgrade to Windows 10 failed, and the question is now how we can continue running Windows 7 on the laptops, and is there a possibility to update out these Windows 10 updates, and then afterward to receive patches for Windows 7? And maybe I can also directly answer those questions. For the first question, I'm sorry that you Windows 10 upgrade failed on your Lenovo laptops, but that's why we have also mentioned before this, the restore phase when the migrating you're accepting machines back. So there is of course the possibility to go back to the former operating system, and that is not easy when we want to do this afterwards. So probably if you don't have planned this already in your process, then probably you have to reinstall Windows 7 on your machine once again. But normally, it should be a restore point available that you can go back to your last working state let say. And the second answer with our patch management solution, it's probably no problem to individually define which content should be deployed to your machine. So you can easily pick out single updates from Microsoft or even from some third-party Windows and exclude them explicitly from the patch deployment to all your machines. So this possible, but of course that will need only one aside from operation on the other side is probably, maybe all patch management solution that you cannot do this today with your WSOS solution.
Andreas: Thank you Mario. Another question might be, it's about their Windows business store, how do you see the business store in the context of application management and then endpoint management? So we actually see the business store two fold. So first of all, as an alternative application packaging source, and also, and this is in regards to the poll we did, a concept to grant users more rights to let them manage themselves. And I think that you experience this influenced by the consumerization of IT. Actually there are some minor drawbacks. We see with the business store currently and they are it manages users not groups, maybe that, that will change. Still requires some customize, customizing from one an application is installed by the end-user. Maybe there are still some customizing required, and also it requires and either, and as you are active directory account or a Windows life account respectively, which is not the case when you still have that centrally controlled deployment mechanism, but leverage the app store as an alternative application packaging source.
Well there is one feedback from the audience. That he or she was not able to figure out how to vote on the question. Thank you for the feedback. Please visit us also on our website, And yes, please don't forget to submit with your feedback. That would be much appreciated. I don't see any further questions coming up. So again, thank you very much for attending this webinar. Thank you for your time. And see you soon again.