Migration paths from Linux to Windows

Microsoft Windows
Can anyone assist me with migration paths from Linux to Windows?

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Subhendu Sen
    What environment is there? How many PCs/laptops are there and also what OS is there like mixed/ only Linux OS? Have you sketched any plan for this job? You can check here for your good concept, http://searchenterpriselinux.techtarget.com/tip/Migrating-applications-from-Linux-Unix-to-Windows-or-vice-versa

    But for good replies, please provide more details.

    139,010 pointsBadges:
  • carlosdl
    What do you want to migrate? Servers or workstations?

    What kinds of applications are currently running on the Windows machines?
    What's the end goal of the migration?

    Please provide more details.
    84,745 pointsBadges:
  • ToddN2000
    More info on the current hardware set up is needed as well as what you are looking to accomplish. There are a lot of variables that are unclear at this point.
    132,840 pointsBadges:
  • TheRealRaven
    There are (at least) two types of migration paths: personal and business. Since ITKE says that it's for "IT professionals", I'll give a description of a basic plan for a small business office environment. (Larger sites almost certainly have sufficient resources to work out their own plans.)

    Personal is trivial if you have some basic spare equipment or don't mind investing maybe $100US. But a business office...

    This would need to be a staged conversion with at least three phases.

    First phase, set up a couple demo systems that users can sit down at for simple personal viewing and experience. Use at least two different distros -- right now I'd go with Linux Mint 18, Cinnamon desktop, in addition to Fedora 25, Gnome desktop. (Both are personal opinions, but based on experience.) I'd possibly also have a couple variations of each desktop with task-bars at top/bottom, docking differently, etc., so each distro could be booted two or more different ways.

    All required apps would be configured for user review. This phase would not only be for simple user introduction, but also for proofs-of-concept for apps, networking, hardware drivers, etc., for support person(s) to ensure that everything worked and was understood within this environment. Nothing goes forward until all actual problems are solved and documented.

    Then, if that goes well enough, a couple users could volunteer for a live roll-out test phase. These users should commit to total conversion. No dual-boot nor VM fail-safes that allow them to do things the old way just because they like it better. It's necessary to see if they can simply become accustomed to changes that they'll learn. This needs to run a good couple of weeks. Support person(s) need to be ready to be helpful for the time period.

    Then, if that goes well enough (the site determines pass/fail criteria), other users are converted, a few at a time over the final few weeks. Each week, maybe 3-5 users are converted. As a new group begins, earlier ones help teach whatever details or tips have been collected.

    That's all simplified and should be fleshed out and customized; but as long as each phase concludes successfully, it should be reasonably smooth. Simply doing much of the first phase should tell everything needed for demonstrating feasibility. Older, used hardware can be enough for quick test, though expected production hardware needs to be used for formal progress.

    Fedora 25 (Gnome) might be acceptable for this group. However, I prefer the most recent Mint (Cinnamon) distros for helping users adapt outside of Windows. It's usually a little behind many other distros in incorporating the "latest/greatest", but that's often a plus, especially for new users. It's common for latest/greatest to have issues when used in general populations, no matter how many Linux geeks have kicked it around for months. (You can manually update if you wish.) Mint updates/upgrades are deliberately kept to more stable levels specifically to keep disruptions to a minimum. (Issues can still arise; they're just rare and easily resolved if good procedures are followed.)

    Somewhere along the path, the need for VMs is likely to arise. Ideally, a support person should be setting up and running one or more VMs to be competent with running Windows in them and accessing specific required apps that cannot be replaced (yet) in Linux. This investigation should be going on as soon as any decision is made to look seriously into migration.

    As a secondary path, multiple open-source programs/suites may be distributed to various volunteers. Some might use FireFox or Chromium/Chrome for a browser, others might use Thunderbird instead of Outlook, and others might use Libre Office in place of Word/Excel/PowerPoint/Access (or in addition to, since all can co-exist on Windows). Others are possible.

    As sites get larger, questions get bigger. Active Directory or not? In-house Exchange? SQL Server? SCCM...? But then we start getting into an actual project, and that potentially points to contracts and responsibilities.
    35,130 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: