Although it will be some time before Windows 10 becomes generally available, it\u2019s never too early to start thinking about the process for upgrading from the current Windows platform. The smart money is currently on a September or October 2015 public release, so savvy system admins can start looking ahead to some inevitable upgrade tools and techniques, along with a few extra tips to help ease the process along.\n\n\n\nThe Windows Upgrade Assistant\n\n\nAlong with new Windows releases, Microsoft usually makes pre-install evaluation tools available to help users anticipate and prepare for the upgrade process. For the past couple of releases, this has involved a downloadable tool called Upgrade Assistant (here\u2019s a link to the FAQ page for the Windows 8 and 8.1 versions of that tool, by way of example).\n\n\n\n\n\n \n\nAlso on CIO.com:\n\n\nWindows 10 cheat sheet\nHow to perform a clean install of Windows 10\nHow to handle Windows 10 updates\nIllustrated guide to Windows 10 networking\n\n\n\n\n\n\nIn addition to providing a tool that typically works for recent versions of Windows -- for Windows 10 [ Find it on Amazon \u2013 *What\u2019s this?* ], that will probably mean Windows 7 SP1, Windows 8 and Windows 8.1 Update 1 -- this page also provides useful information about which platforms the tool will support as valid upgrade sources, including required Service Packs that must be installed for the tools to work correctly.\n\n\nRunning the tool usually produces a compatibility report that either indicates that the upgrade can proceed or describes what kind of remediation is necessary to result in a successful upgrade. The items that can appear in such reports generally focus on hardware and software.\n\n\n\nFor hardware, there may be some devices in use on the source system that will no longer be supported in the target OS, and a warning will be issued to that effect. In some cases, devices may need to be uninstalled prior to upgrade, so that new drivers can be installed for those devices during the upgrade process. In other cases, it may be necessary to hunt down those new drivers after the upgrade is complete. The compatibility report from Upgrade Assistant usually provides information about all such cases.\n\n\nThat said, the occasional unknown device will pop up after an upgrade that will require its identification so that the proper driver can be located and installed, if such a drive is available. Several good tools to help resolve the appearance of unknown devices in Device Manager are available, including Unknown Device Identifier and the SourceForge project UnknownDevices.\n\n\n\u00a0[Related: What You\u2019ll Love and Hate About Windows 10 ] \n\n\nFor software, certain programs may in some cases be identified as no longer supported under the new target OS. In other cases, it may be necessary to update to a newer version of a program currently in use. In still other cases, it may be necessary to uninstall a program prior to an upgrade, then reinstall the program following the upgrade.\n\n\nAdmins will want to carefully consider building new reference images for widely used systems instead, especially if they already plan to use automated deployment tools to drive their upgrade process along. To that end, eligible parties may want to compare the capabilities that a Software Assurance license from Microsoft will convey via its Microsoft Desktop Optimization Pack (particularly if used in tandem with System Center), or the Microsoft Deployment Toolkit versus any number of excellent third-party products from vendors such as SmartDeploy and PDQ Deploy.\n\n\nThe Big Problem With Software Upgrade\/Migration\n\n\nApplications can serve as an elephant in the room when it comes to Windows upgrades. This is because there will be occasions where mission-critical or line-of-business applications can\u2019t make the move from current standard Windows platforms to some newer target OS version. In these situations, a remedy must be researched and worked out before migration can proceed, or else some or all users will find themselves suddenly unable to do their jobs.\n\n\n\t\t\t\t\n\t\n\n\t\t\t\n\t\t\t\t\n\nIt\u2019s possible to set up VMs running older OS versions and make them available to users who need them to access otherwise incompatible software, but this simply kicks the can down the road in terms of resolving compatibility issues. Another solution is to replace older applications that can\u2019t be upgraded with newer ones that provide the needed functionality in an alternate form.\n\n\nFor Windows 10, applications are something of a good news\/bad news scenario. The underlying APIs for desktop applications do not change much from Windows 8.1 to Windows 10, so what you test for compatibility now with Windows 8.1 has an excellent chance of remaining unaffected by the introduction of Windows 10. The good news: If the application works with 8.1, it will also likely work with 10. The bad news: If it doesn\u2019t work with 8.1, it won\u2019t work with 10, either.\n\n\nThat\u2019s why it\u2019s time to start testing -- and getting remediation underway -- if must-have applications don\u2019t work with Windows 8.1 now. This also means you can start with the Windows 8.1 Upgrade Assistant to get a quick read on applications by running it against a typical reference or standard image for desktops, notebooks and\/or tablets right away.\n\n\nPreparing for the Upgrade: Managing Device Drivers\n\n\nAnother bit of good news for Windows 10 is that device drivers are more like those for Windows 8 or 8.1 than they are different. If you can build a reference or standard image for your PCs running that OS, you can create an excellent working set of drivers for the upcoming upgrade by backing up those drivers into a reference or standard driver library.\n\n\nMost deployment tools support explicit construction of such a library, or you can use a driver backup tool of some kind to make a snapshot of the drivers associated with any given image instead. SourceForge DriverBackup! is a great free tool admins can use to quickly and easily kick this process off for themselves.\n\n\nMeasure Twice, Cut(over) Once\n\n\nIn general, planning for an upgrade involves a great deal of initial testing and analysis, followed by a concerted planning effort to create the necessary install images and processes and then to work through a carefully staged deployment. If you use what we already know about Windows 10, and the tools already available for Windows 8.1, you can get a considerable leg up on the process well in advance of general availability.\n\n\nBy following our advice, and using some of the tools and techniques we recommend, you can keep this process under control. Be prepared to spend some time and to expend considerable elbow grease along the way.