cochise33 has asked for the wisdom of the Perl Monks concerning the following question:

I'm running Perl on a Windows 2003 Server. The time has come to finally move to a more current version of Windows and I was wondering if you guys have any suggestions or warnings. Am I going to have any problems with Windows Server 12 or 16?

Though I've used Perl for 20 years, I've only installed/reinstalled it or any packages like GD or some .pdf scripts a couple of times, so from that angle I'm a beginner.

We also use MDaemon for the email part of what we do.

Thanks for any help,

Steve

Replies are listed 'Best First'.
Re: Migrating from Windows Server 2003
by dasgar (Priest) on Jul 19, 2018 at 13:56 UTC

    As far as using Perl in newer versions of Windows, you shouldn't have any issues.

    My personal preference for Perl on Windows is Strawberry Perl. And if you think you might want multiple versions of Perl installed, I'd recommend checking out berrybrew. However, if you're requiring support (i.e. more than relying on community support for an open source product) and are willing to pay for that support, ActiveState's ActivePerl along with their paid support might be better suited to your needs.

[reply]
Re: Migrating from Windows Server 2003
by Discipulus (Canon) on Jul 19, 2018 at 16:49 UTC
    Hello cochise33 and welcome to the monastery!

    (Un)fortunately I run perl on windows on a daily base, 2012 and 2016 too. I see no problem at all to switch (at least if no CGIs are involved in the migration.. ;). Me too I strongly suggest you to try Strawberry Perl. Look at their releases. I'd try directly the latest 64Bit portable edition (running the comfortable portableshell.bat tha comes with the portable release) to see if you can install GD and run your previously developped programs. With strawberry perl you can do the same as in Linux, just: cpan GD will suffice.

    Then you can choose if install a "system perl" for the users that also modify the ENV

    I also see that GD matrix is very green for windows users even with recent versions of Perl, so dont worry!

    L*

    There are no rules, there are no thumbs..
    Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
[reply]
[d/l]
[select]
Re: Migrating from Windows Server 2003
by soonix (Chancellor) on Jul 20, 2018 at 10:54 UTC
    xiaoyafeng's suggestion reminds me: I had difficulties with interfacing Word/Excel/Access (e.g. via DBI). Some of the drivers would work differently in their 32bit vs. 64bit version...

    Therefore I'd recommend to

    1. record your current configuration (perl -v) and
    2. directly start with berrybrew or Strawberry portable editions to be able to switch versions.

[reply]
[d/l]
Re: Migrating from Windows Server 2003
by marto (Cardinal) on Jul 20, 2018 at 15:00 UTC

    "We also use MDaemon for the email part of what we do."

    I've no experience of this, but how to you currently use it from perl?

    My advice would be to ignore this. Unless you have a very good reason to use ActiveState Perl download the latest Strawberry Perl, up to date releases, ships with lots of helpful modules, libraries as well as a compiler and build tools. Install your the modules you need, from your old perl get all install modules:

    perl -MCPAN -eautobundle

    [download]

    Generates a file in the format Snapshot_YYYY_MM_DD_00.pm. Examine and edit to your satisfaction in a text editor. Transfer to the new server and install them all:

    perl -MCPAN -e "install Bundle::Snapshot_YYYY_MM_DD_00

    [download]

    Address any failures (a new thread here if required). Install and configure your application, run your test suite, load testing, UAT testing....

[reply]
[d/l]
[select]
Re: Migrating from Windows Server 2003
by xiaoyafeng (Deacon) on Jul 19, 2018 at 14:52 UTC
    Migrating perl on windows is painful, since it lacks a reliable way to complete this job. I can give you some advice:
    1. 1. Because windows 2003 is a 32bit system, I strongly recommend you test 32bit perl on new windows first. Then you can try 64bit perl
    2. 2. Don't use the latest perl, consider 5.20 or 5.22
    3. 3. Use portable strawberry perl , and by setting path to switch between various version for testing
    4. 4. Just copy the old perl to new windows to see if it will still work
    5. 5. Use par to know the dependencies of your script and install them on new perl respectively


    I am trying to improve my English skills, if you see a mistake please feel free to reply or /msg me a correction

[reply]
      Because windows 2003 is a 32bit system

      I am far from an expert on this topic, but my understanding (admittedly, just from Wikipedia) is that there is a 64-bit edition as well. If you have experience with Windows Server 2003, can you say if a 64-bit Perl wouldn't work on a 64-bit edition?

      Don't use the latest perl, consider 5.20 or 5.22

      Why?

[reply]

        I am far from an expert on this topic, but my understanding (admittedly, just from Wikipedia) is that there is a 64-bit edition as well.

        well, originally, windows 2003 has only 32bit edition, and lately Microsoft add a windows 2003 64bit extended edition.

        Why?

        because of GD, IIRC, the older GD (like 2.5x) only run correctly on windows 5.20, 5.22. he can install the same version GD on windows 2003 to new windows to avoid API changing.


        I am trying to improve my English skills, if you see a mistake please feel free to reply or /msg me a correction

[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.

Back to Seekers of Perl Wisdom