Bogdan, 

I can't give you any feedback for "how does it run on windows" but considering IIS is native and ActiveState is designed to be Perl on Windows, I'd go with it's not going to be bad.

That said, I had my own struggles with installing 3.3.6-win-installer on a Win 7 64 bit box (Hint: ActiveState Perl 32-bit is required for IIS integration, it seems). And I had an issue with actually getting into the system when I logged in.

I even tried that by hand with apache and OTRS source. All roads for a *fresh* install on windows lead to the same place for me. 

I didn't bother to try 3.3.5 as I was just on a factfinding mission for the forums. (My focus has been on Linux installations). 

I wish I could provide you better/more feedback, but on the other hand, after all this, I'd personally be looking at upgrading by backup database, filesystem/rename, extracting otrs source into a fresh otrs directory, copy over config.pm, any filesystem attachments, and upgrade the database (follow along according to the Upgrading file). 

As usual, don't blindly follow the lead of some random post on the Internet. Your data is your responsibility. My response is based upon my experience and is biased based upon what I've encountered, and others may have different experiences. Please backup, backup, backup, test restoring the backup, test things in a sandbox environment before applying to production. The best disaster recovery scenario is the one you've already prepared for on your dev/testing box. 

At which point, you'll have answered your own questions about the experience that matters most: yours.


On Wed, May 7, 2014 at 10:53 AM, Bogdan Iosif <bogdan.iosif@gmail.com> wrote:
Hi everyone,

Looking at OTRS 3.3 admin manual, Ch 2, Using the Windows Installer I see the following:

Important: The Windows installer for OTRS contains all needed components for OTRS, i.e. the Apache web server, the MySQL database server, Perl (with all needed modules) and cron for Windows. However you can also use it to set up OTRS on the Microsoft IIS Web Server instead of on Apache.


Since I've been running OTRS 3.2.3 decently in production for ~14 months, on Windows, on Apache & Strawberry, with ~150 customers & ~50 agents, I would like to keep this combo of OS, web server and Perl runtime.

Unfortunately, the latest otrs-3.3.6-win-installer-3.0.5.exe deploys directly on IIS & ActivePerl and never asks me about anything except the db backend.

  • Is it possible to deploy Apache & Strawberry with the Win installer, as claimed in the admin manual?
  • Anyone has positive / negative experiences to share about running on IIS & ActiveState? I loath changing the whole underlying platform and running the risk of having to rollback everything if performance is an issue in the new configuration.

Thanks,

Bogdan



---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs