Top 6 Things to Consider when Migrating to Windows 10

September 16, 2015

Windows 10 is here! Are you ready to deploy it in your organization? Whether you are actively planning a corporate Windows 10 deployment in 2015/2016 or not, the influx of the OS onto the corporate network with new devices means you need to be able to manage it. A smart Endpoint Management solution can help you both plan and deploy the new OS, as well as provide the capability to manage endpoints on the network that already have the new OS preinstalled.


Welcome everybody to this webinar, my name is Andreas Fuchs, I am a Product Manager for Client Management at HEAT Software, and I'm located in Germany. So good evening to everybody. This webinar is being recorded, and please feel free to enter questions, and we will follow up after this webinar.
Okay, so Windows 10 has been released, and with Windows 10 Microsoft shipped an operating system which supports all kinds of devices. Whether you are planning a Windows 10 deployment this year or not, the influx of the operating system onto the corporate network means you need to be able to manage it. And a client management solution helps you to plan and manage the migration of the new operating systems. HEAT Software provides a solution for planning and managing a Windows 10 migration project in your corporate network.
So this is the agenda for today. First of all we are going to talk about Windows 10 a little bit, some numbers, some facts behind Windows 10. After that, I have some questions that might be important when considering a Windows 10 migration, and then show how HEAT Client Management supports phases of a migration project. So, more than just Windows 8.1 with a "Start menu," for Microsoft it is very important to position the new operating system in the market. Microsoft has learned from their mistakes they did with Windows 8, and it is all about providing all kinds of devices with a unified platform. It is an operating system which stays always on top of the latest updates, and patch levels, and it's easier to maintain. It provides a variety of new features also. And for Microsoft it is more, it is like a paradigm shift, it is Windows as a service.
So let's have a look at some numbers today. There are more than 90% of all desktops, laptops, and convertibles in the market which have a Windows operating system installed. When we break down that a little bit, almost 60% are on Windows 7, 12% are still on Windows XP, 11% on Windows 8, and slightly over 5% on Windows 10 already. These numbers may vary for enterprises. And Microsoft's objective is to have them all migrated to Windows 10 in the next year. The big advantage for them of course is less support and maintenance costs. And since the release on the 29th of July, Microsoft had a dream start, it was better than Windows 7 and Windows 8 in the former times, and within one month they gained 5% market share with Windows 10.
So Windows 10, what are the facts over one month after the release? There are more than 75 million devices running on Windows 10. It runs on 90,000 different PC entrapment models which is quite a lot, in more than 190 countries all over the globe. And even some devices manufactured in 2007 have upgraded to Windows 10. And Cortana has told over half a million jokes.
Microsoft experts claim Windows 10 will be installed on 1 billion devices within two to three years' time, meaning by late summer 2018. And if Microsoft achieves this goal then Windows 10 would become the dominating system in the world.
Now let's ask some question that might be important when considering a Windows 10 migration. So first of all, what are the benefits for a company thinking of rolling out Windows 10? Well, besides the fact that this is a clear recommendation from Microsoft of course, because it is future proof, it contains the newest features, somethings which went wrong with Windows 8 are made much better now. It is a platform which supports and will run on all devices such legacy devices, mobiles, tablets, convertibles, etc. But also according to IT professionals, the reason can also be the end of life support for Windows 7, 2020. Or some say, it's always good to stay current on latest operating systems to benefit from new features and technology updates. Or, Windows 10 comes with many new features to ease visibility and improved productivity across devices, not only the "Start menu." And another reason can be, if a software has the requirements or a compatibility issue, Windows 10 provides enhanced security, and maybe users just make demands because they would like to go on to the new operating system.
In terms of timing, what is the right time to migrate to a new operating system? Some say as needed. What does that mean? For instance, end of life of the existing operating system, or some compatibility issues, or some more issues, or when business apps are supported by the new operating system, or the right time can be whenever a new hardware is purchased with the new preloaded operating system, then you can get that new operating system automatically, and then you have to manage it. But there are also a lot more.
What are the most appealing features in the upcoming operating system? So when we take a look at this, first of all, definitely the return of the "Start" button. Then the free upgrade from Windows 7 and 8 to Windows 10. Even after that one year period, for enterprise versions depending on the software assurance program, companies can qualify to update them without any cost. Then it has enhanced security. And ability to upgrade as Windows Update. Now it supports multiple desktops, more updates flexibility, faster update cycles, it has a new web browser. The universal apps running on both legacy devices, PCs and mobiles. That is only to mention a few. I think every person has their individual favorites in terms of new features.
There are not only advantages but also reasons to wait before upgrading to the new operating system. And again, according to IT professionals, these are first of all compatibility issues, hardware and software. The question is, how well does Windows 10 play with existing hardware and software? There might be bugs in early releases. And more important than features is stability. So businesses typically value operating systems stability and application compatibility as the main reason to consider an operating system. The latest features and functionality aren't much lower on the list of drivers. Then user training, and you also have to pay come acquainted with the new behaviors and the new user experience. Then maybe there's lack of support from third party vendors. And there is time required for the actual upgrade process, and this is what we are going to talk about today.
What tips do you have for this specific upgrade? Well, first of all organizations need to decide what strategy they will pursue regarding Windows 10. Will they do and in place upgrade? Will they do wipe and load updates, or something else? The upgrade phases need to be planned, analysts typically recommend 12 to 18 months. Critically is to check convertibility readiness of hardware, software compatibility check. Check the license contracts whether they are okay for the Windows Update. At the time of the operating system upgrade, it's also advisable to check applications, do they need to be replaced? Will you go to the Windows runtime apps? If they have been replaced with the new, modern UI. You might also check the privacy concept, concepts prior to migration. So to my knowledge, by default Windows 10 for instance saves the browser history. Also in the cloud, same for such. So organization need to look into an endpoint management solution that helps them to automate configuration management. So adjustment of privacy policies can be handled in an easy and efficient manner. Use of state migrations, it's advisable to pack up and migrate personal data in order to recover them later on.
Operating system deployment, automate this process as much as possible from packaging the operating system relevant drivers, to deploying Windows 10 on any end point automatically aligned to your corporate policies. And after the upgrade, monitor and report the roller progress to ensure that all end points have been upgraded successfully. In case of failures you can react immediately and take the appropriate measures. Secure endpoints. Identify vulnerabilities automatically, close vulnerabilities automatically utilizing patch management. Secure endpoints additionally with endpoint security capabilities.
So on the next slide, the question is, what are some of the security issues to be aware of? Talking about security, what else do we have to take into consideration? With Windows 10, the way Microsoft provides updates has changed. Windows Updates are now a service. For Windows 10 Microsoft has stated that they will release updates, both security and non-security, also outside of the legacy Patch Tuesday. So far Microsoft has released security updates for Windows 10 in both the Patch Tuesday, since the release date. And they have also released the security update outside of Patch Tuesday for Windows 10. But it's still important to fully understand the update changes. Patch management remains a very important topic and organizations need to ensure they have the right patch management solution that supports Windows 10, as well as provides third party applications patching.
What else do CIOs need to know before they do the deployment? Well, with Windows 10, the approach to traditional software distribution changed slightly, so some things are different. For instance, think of Office 365 with the new click-to-run technology, but also the Windows Store. Interesting for enterprises is the Windows Business Store which is the kind of subset of the Windows Store, and companies are still looking for ways to keep the control over software deployment, so...
CIOs need to decide what level of user empowerment they want to allow. End users are definitely more tech savvy now, and expect that software for their work is made available in a fast manner, similar to how they are used to in the consumer world and their phones. And the CIOs need to ensure they provide user productivity to provide users with the applications they need, but in a secure manner that complies to organization standards, etc. They also need to come up with guidelines and regulations of how to properly rollout software in a standardized manner, versus letting users download. For instance, Office 365 Runtime or the Windows Store.
Do you want a Windows Azure Active Directory account for each user, and let the user decide when and what to install? If yes, then go for it. What about the lockdown workstation approach and the fact that not every user is a local administrator, or actually should not be. Do you want to lower your restrictions here? Then in the Windows Business Store, CIOs should look into what they want to allow in their organizations. Which application do they want to provide via the Business Store? And in case they do not want to use the Business Store, what means of application provisioning do they want to provide to support their end users. As a matter of fact, and despite of any concerns, more than two thirds want to upgrade to Windows 10 in the first two years after launch.
Let's have a quick look at the available Windows 10 editions. There is probably a new one which is the long term servicing brand. I don't like to go now into the details and elaborate on the current brands, and current brands for business and so on, and all these advantages or disadvantages about it, that might be a separate webinar. What I want to do is, I like to start a short survey, and you can vote for the answer right now. So the question is, what is your Windows 10 adoption timeline for your business? Is it as soon as possible? Is it until end of this year? Is it in 2016, later than 2016? Or do you have no plans or just don't know which is fair enough?
Let's wait a little bit. Thank you very much. So when we look at the results, 6% - as soon as possible, 12% - until end of this year, 35% - within the next, or in 2016. Later than 2016, okay. And a fourth, they do not have any plans yet. Interesting, thank you very much.
So let's talk about the migration to Windows 10. When we look back and think of the migration from Windows XP to Windows 7 or even 8, 8.1 respectively, then we see that there was no direct migration way. Several things and preparations were necessary before we were able to operate. First of all, back up all the data then set up the new operating system, install the drivers, make sure that they work, then applications, and then restore all saved data. Compatibility was a big issue, and that was very annoying and time consuming. And at that time we at HEAT Software already showed how easy it was to do the migration utilizing our HEAT Client Management solution. However, according to Microsoft, the migration from Windows 7 to Windows 10 is easier than it was from XP to Windows 7. And Microsoft also offers more migration scenarios.
In Windows 10 we see the following migration scenarios, to only mention a few. There are some more. First of all is the wipe and load scenario. Secondly is the in place migration. I don't like to go in every detail just to highlight some characteristics of this migration scenarios. So we can go the traditional way with the wipe and load approach, which means back up data and settings, install the new operating system. Afterwards, install drivers, applications, and so on, and restore the saved data and configurations. This approach can be very time consuming, but you cannot avoid it under certain circumstances. When do you have to make use of it? It's when you have an architectural shift from 32-bit to a 64-bit operating system. That is one reason why this way is important. Another reason is, see it as a clean, new installation from scratch can be seen as a new start, or if you have a hardware change, or saving disk space.
In place upgrade. Basically it works the same way, however it has a little bit more for you, it collects data, configuration, does some compatibility checks, and you can go back every time with the built-in recovery functionality. At first glance, in place upgrade sounds good, however the drawback is as mentioned, upgrade works not from 32-bit to 64-bit. Or even on new devices it is not possible because there is an operating system to start from. It might have heavy disk space usage due to apps and recovery functionality. It still saves the Windows.old.
The recommendation of many IT professionals is still clean install over in place upgrade. However, the preferable way would be to have a solution which supports both or any other migration scenarios of your choice. A unified process which supports both a new installation of Windows 10 on a new device or any migration scenario to the new operating system is exactly that, it's possible with HEAT Client Management.
So now I'd like to another survey, and you can vote for the answer. Let me stop this. Okay, the question is, what is your preferred upgrade scenario? Is it wiPe and load, which is basically a reinstall? Is it in place upgrade? And also a mixture? Or do you have no plans yet? Which is also fair enough.
Okay, that is interesting. 33% - wipe and load. Same number almost. In place migration, a mixture of all 13%. No plans yet - 20%. Thank you very much.
We at HEAT Software help customers and prospects on their Windows 10 migration plans today. New installation or migration, hardware replacement, or on existing endpoints, or on the new endpoints, they all need to be planned carefully. Operating system deployment and configuration are two of the most time consuming software management tasks in software management. Automation and compliance based management save valuable time and eliminates sources of error. HEAT Client Management is a solution for planning and managing a Windows 10 initiative. And what we see here is that the migration plan can be split up in six phases. Introducing Windows 10 is more than just deploying an operating system. First of all, compliance readiness, make sure your environment is compatible with Windows 10, meaning it meets the hardware requirements, also the software requirements, calculate budget for Windows 10.
Second is personality migration or use of state migration. Backup and migration of personal data in order to recover them later. Third, operating system deployment which comprises packaging for operating systems, the drivers, the pre-execution environments which are necessary. And finally, the deployment of the Windows 10 operating system on any endpoint.
Phase four is the software deployment, application and configuration packaging and deployment. Number five, patch management secures your endpoint, identifies vulnerabilities automatically, closes vulnerabilities automatically, secure your endpoints additionally with endpoint security capabilities. And last, change management. That is your daily business, not only during the rollout but also afterwards, monitoring and reporting of the roll out progress, make sure that all endpoints have been upgraded successfully increase of failures, Make sure you can react immediately.
HEAT Client Management supports all of these phases for a successful Windows 10 migration. Let's have a closer look and let's go through each of them. So compliance readiness is the phase where we get an overview whether the existing devices are Windows 10 ready or not. What additional cost do I have to consider in terms of licenses, but also on the hardware side? The goal is to get a clear statement if my environment is Windows 10 ready. We split up this phase again with our inventory solution HEAT Discovery, it is possible to identify every hard and software assets. Discovery gives you the support you need for the migration project from the initial planning and budgeting, through the process of migrating and make sure that after the migration, all the endpoints will have migrated successfully.
In general it is possible to reduce the time spent to track down hardware by up to 95%. And reports show which devices are fit for Windows 10 at all. Additionally, you see which software is installed where, which might not be compatible with the new operating system. This helps also making decisions on an upcoming Windows 10 migration, same for licenses. Can I still use existing licenses or do I have to purchase additional ones? In terms of OEM licenses or Windows 7 licenses from an enterprise agreement, can they be upgraded with additional cost,etc.? HEAT Discovery supports this process, so does HEAT License Manager, and provides a dynamic and transparent view of the infrastructure.
Let's have a look into the product here provided by screenshots. What we see here is the upgrade costing wizard, the template for Windows 10 allows us to enter Windows 10 hardware requirements like processor speed, memory, etc. It is possible to change this information any time, these are just guidelines. In the next step, you can decide what should happen when for instance the processor speed is below the given value, then you probably change the hardware. In case of memory, if possible you just put in more. You can also at a cost manpower, additional costs for hardware components. And the next steps closes the wizard and you end up with a result which shows you the cost. Export the results or create a report for that.
Personality Migration. Especially for the wider load scenario, all relevant settings need to be backed up, user settings, application configurations and so on, also file can be copied. Also you can provide end users the possibility to decide what they like to back up. After a successful migration all data is restored on the new system. And the end user sees the same settings and configurations on the new system. Same can be done on every day operation, backup and restore the data on a reoccurring basis. The tool provides selecting the current or all user profiles, not only the one from the current lock down user, settings, and applications, links, favorites, etc, but also specific files. And the phases during the migration are, back up the settings, migrate to the new operating system, restore the settings, and having that restored in a very, very short amount of time reduces also the time the down time. And you can do same things in maintenance later on. The goal is a fully automated backup and migration of user states for all user specific settings within the system. And that is an essential part of the Windows 10 migration plan. The advantage is a smooth migration personal files and settings even in large environments, and decreased support costs. Users are back to production in less time.
So when we have a look into the product screenshot again, the settings can be selected in a very comfortable way. You can determine exactly what you want to take into account, for instance Internet Explorer settings, Adobe reader settings, even PDF files. It also shows for instance from which version of Office to which other it is possible to migrate without any loss of settings. So here we see from Office 2003 to the latest one. So also to Office 365. But you can also backup inactive Outlook PST files.
The solution also automatically records all user data and settings. For example, desktop layout, personalized adjustments, document templates, network connections, as well as files and folders structures. And the registry selector also takes registry keys and values into account for proprietary applications. And it does not only support Microsoft applications but also third party applications. HEAT Client Management delivers prefabricated packages to automate the user state migration process in a very flexible way as you may already know from HEAT Client Management.
Operating system deployment and configuration are two of the most time consuming software management tasks. In this phase, you define what is required to roll out the operating system itself. It is not only packaging the operating system but also their corresponding drivers for both internal and external hardware devices, such as printers, scanners, etc. With HEAT Client Management you can package the operating system, the drivers and configuration in just a few clicks. It also ships ready to use operating system deployment packages. HEAT Client Management is not only made for our mid-sized customers, but also for highly distributed environments of 100K plus devices. Even huge amount of mass data can be deployed the integrated bandwidth control, and so takes advantage of reduced bandwidth control, and so takes advantage of reduced bandwidth traffic.
Drivers and hardware related software are dynamically assigned to the specific hardware components during the deployment, and possibly BIOS update is necessary prior to installation of the operating system, or Temp files have to be deleted afterwards. Usually the admin assigns the packages from the central point and the packages get installed automatically on the endpoints. However, another way is to provide it by yourself. Then end users can initiate the migration on the endpoints. Same for re-install of the whole endpoints.
But also and integration into the HEAT Service Catalog provides multi-level approval steps when provisioning a new operating system. Whether you are doing an initial installation or migration, with HEAT you can get to Windows 10 faster and benefit from a more reliable and robust system. How does the product look like? You can package the operating system, drivers, and configurations in just a few clicks. In this case it is the packaging wizard for a new operating system.
When assigning the package to endpoints or a group of endpoints, you're very flexible here. The administrators can define installation parameters which should apply during installation. The administrators can also import drivers from an existing Windows 10 endpoint which runs Windows 10 already, but you can also import driver libraries and end up with driver packages ready for deployment within just a few clicks.
Software deployment. The phase is about application and configuration packaging in order to have them deployed after new Windows 10 operating system is up and running. For this we use our proven technology, which is the Software Factory and Packaging workbench. The Software Factory allows you to create various package types using the available wizards in no time at all, from application packaging to printer packaging configuration, right up to complex drivers. You only need a few mouse clicks to create a package that is ready for distribution. Configuration templates allow the simple creation of configuration packages to administrator the various settings of the client. So with HEAT Client Management, customers were able to reduce the time spent on package creation by up to 85%.
Let's have a closer look. The technology as already mentioned, the Software Factory allows you to create various package types. Everything is wizard driven. Software packages are updated automatically for desktops, servers, laptops, tablets, or virtual environments. The process of packaging, testing, deploying, and configuring happens always the same way following standardized process, this guarantees a high quality standard.
Packaging as mentioned before, all kinds of packages are supported, even the modern UI app which came with Windows 8. That is one of the big advantage of HEAT Client Management. It supports both user and machine related parts within one package, it is not an E4R, because of the modern UI app, they are registered per user in the endpoint, but you can still deploy to endpoints that happens in one step, but it provides many more package types. It provides also a powerful and easy to use threat automation, utilizing more than 170 commands. There are no development skills required, everything is dialog driven.
For deployment, the installation happens in a given installation order, there is a release and revision management. Before a package goes into production it runs through several release steps. Every change results in a new revision. The deployment takes not only local area network sites into account, but also remote sites, branch offices, and even offline systems. Also the distribution and installation over the Internet is possible.
The single console interface allows different stakeholders and departments to collaborate and share system management tasks. Self-services where the software shop allowed and chooses to install the software interactively and daily operational tasks can also be automated. Thus it reduces the time spent on software deployment by up to 90%, so it is all about automation. When we look at the product screenshots, the Software Factory provides for capabilities in order to automate things, these are applications, configurations reoccurring, operational tasks, operating system as we already saw and many more.
Everything is pretty much wizard-driven for every kind of package, but the packaging is done in a few minutes, some configurations even in second. The software life cycle allows us to do specific settings, define the platform, in this case Windows 10, assign the package to endpoints. The admin responsible for the packaging can do a pilot information and test it before it goes into production. As I mentioned, HEAT Client Management has its own strip command, but it is nothing to learn, no developer skills are required, everything is dialogue driven. These command extends the usual packaging process and is very powerful, you can add additional commands to your package or just create packages which then run as chops everyday on every endpoint.
This example here shows how to modify the user management on the local endpoints. And as mentioned, HEAT PSM provides more than 170 strip commands, thus it is possible to automate tasks 100%. And with these commands, admins can also access the Windows 10 "Start Menu," your task bar, there is no scripting required. Of course it is also possible to call other scripts outside of these scripts.
Configuration items making it even easier to change settings, like we see here the power settings. In the next slide, this is how the agent shows up on the Windows 10 endpoint. And the end user also has the possibility to install software interactively using the Software Shop. So if you like to provide that, you can do it. If you want to automate things then you do not provide anything here in the Software Shop. So it is up to the company's policy.
There is also an integration into the service catalog where you can request for software all requests for optional software, or you can also ask for support and trigger the reinstallation of the software. And that then goes through multi-level approval processes.
Patch management. It is always a challenge to keep an operating system up to date, and it never stops. Update patches in time reduces the risk of exposure to hacking and malware, HEAT Client Management make sure that all of your programs are patched according to policy. It identifies vulnerabilities from Microsoft as well as third party vendors in your environment. The time to install patches can be reduced by up to 80%. HEAT Client Management enables a high level of automation for all phases of patch management. That is from identifying vulnerabilities, selecting the relevant patches, to rule-based implementation.
Well, what are the steps? First of all, scan for vulnerabilities, then the solution identifies vulnerabilities for Microsoft as well as third party vendors in your environment, and automatically downloads and packages required patches for remediation. Patches can be combined in categories in terms of vendor, product versions and languages. And a maintenance window defines the time when endpoints are scanned or being patched. So that it's very flexible and can vary from endpoint to endpoint, or from endpoint group to endpoint group. Deploying patches guarantee that all endpoints are up to date at all times, and the graphical user interface immediately indicates whether the defined status was achieved or not. You can see the progress at all time and get in compliance of a few.
So what we see here is the patch management library, you're getting information about, like the patches and the affected endpoints. These are vulnerabilities, already known on Windows 10. And in the next screen shot you are able to see the patch roller status at all times.
Ongoing maintenance in the new Windows 10 environment, we do not only see the effort of the initial deployment but also the amount of time spent on ongoing administration in a Windows 10 environment. Monitoring and reporting off rollout progress makes sure that all endpoints have been upgraded successfully, in case of failures react immediately. What about software licenses? Recognize and prevent over licensing as well as under licensing, and for professional planning and budgeting of license purchases.
First, plan. It starts with an analysis of your infrastructure. With the Discovery you have have a transparent overview of all IP addressable hardware, including servers, desktop, laptops, network printer, switches, and software on the network as part of a complete IT inventory that is always kept up to date. HEAT License Manager provides central administration of software licenses, detecting over or under licensed products finally saves money. In the end, this information impacts your migration plans. So, identifies in the...and first analyze, identify vulnerabilities in the network on a regular basis, and relevant patches.
The Managed Package Test install or remove software, provision and manage desktops, servers, and virtual devices, monitor your software rollouts, and enable authorized IT staff to access and control all systems on the network with our remote control solution HEAT Remote.
HEAT Client Management reduces the effort associated with deploying and managing Windows 10 on endpoints in every stage of the software life cycle, from deploying to troubleshooting to retirement.
The dashboard shows you the current rollout status as well as the patch rollout status. It also shows the status of every single software component and the installation status of the endpoint. We see that the packages have been delivered, downloaded, but not yet installed. You also the given installation order and you get a compliance overview of all time. So that is a realistic scenario for installation, the Windows 10 operating system on an endpoint or the group of endpoints. And HEAT License Manager provides central administration of software licenses, it recognizes and prevents over licensing and under licensing.
So, summarized again hear are the steps to take when planning and doing a Windows 10 migration. It is compliance readiness, personality migration, operating system deployment, software deployment, patch management, and after that, an ongoing change management. The HEAT Client Management solution is signed to automate IT operational tasks, from installing applications and operating systems, to monitoring and maintaining devices over time. And the HEAT solution contains all the client management tools necessary to manage and control, and also to secure physical, virtual, and mobile devices from a unified and intuitive console.
For us automation makes the big difference, we want to help you be more efficient, so are focusing on 100% automation, meaning enhanced security and compliance, reduced IT costs, automate routine and complex tasks, improved efficiency and productivity, provide new or repair existing systems with a click of a button. This means improved user productivity and customer satisfaction, and also service quality, support users anytime, anywhere, also with DMZ scenarios via internet in low bandwidth size, and of course, inside the corporate network, and maintain control and security across all of your endpoints.
This is an overview of our HEAT Unified Endpoint Management Solution. This demonstrates the key capabilities we offer in our comprehensive solution. So we have HEAT Client Management, we have HEAT Enterprise Mobility Management, and we have HEAT Endpoint Security. It efficiently controls and secures all physical, mobile, and virtual endpoints across the life cycle, manages traditional desktops, laptops, and servers. Virtual environments like hosted virtual desktops, virtual desktop infrastructure, terminals servers, terminal server versions, smartphones, and tablets, and smarter vices like point of sale, and kiosks, for instance ticketing systems. And it managed the relationship between users, the application they use, the endpoints the applications are running on, and the data that is being shared.
So thank you very much for your time. I hope I was able to show you how our solution works and help you with your Windows 10 migration plans. Thank you for your questions, we will follow up on them and provide the answers later. Please visit us on our website, and please don't forget to submit your feedback. Thank you very much.