Plan of attack: Windows Small Business Server 2011 install.

[rotelocke]

Hi all

I am planing to install OTRS 3.2.9 on a 64bit Windows Small Business Server 2011.
I would like to have OTRS using Apache and MySQL rather than going the MsSQL and IIS way*. So my first thought was to use the Windows installer, as I have neither Apace nor MySQL running on the server yet.

What made me think is that the Server is of course running IIS7 at this time (which needs to stay and needs to continue working). Does using the windows installer (3.0.2) conflict in any way with the IIS7 webserver running now? Would it be better to go through the process of a manual installation? As I am no professional I would be able to do that but it would take me quite a while longer, as I would need to read a lot of documentation.

Would be thankfull for any insights on this matter, also if anyone knows of a good installation how-to for my configuration (could not for my life find one on the net), a link would be great.

cheers


*mainly because I was told of performance deficits regarding the ODBC connection compared to MySQL.

[crythias]

Does using the windows installer (3.0.2) conflict in any way with the IIS7 webserver running now?

Yes. There will be a race condition for port 80.

[rotelocke]

Hi and thanks for the speedy reply.
I thought something like that might happen. I did a little research and found out that you can run IIS and Apache parallel easily when changing the port Apache is listening on (see here: http://stackoverflow.com/a/15212225). What would you think happens if I used the installer and changed the Apache port after installation? Or doesn't that make sense because Apache needs to be running already for the installation and I am left with the (for me) arduous manual installation anyway?

[crythias]

What would you think happens if I used the installer and changed the Apache port after installation?

There's (roughly) two parts regarding "installation". 1) exe install, 2) web interface configuration/setup

First, I'd strongly suggest you NOT install anything on a domain controller. Spin up a VM running Linux or an old desktop or ... something ... but don't put it on your DC.
(OK, you're not listening ... :) )
Second, the part 2 installation probably will run without a hitch if you remember what port you're using:
http://localhost:newport/otrs/installer.pl

Or, disable IIS to install and change ports afterwards.. either way.

Don't forget that now all the references to FQDN for notifications, replies, etc... must include the port number of Apache's instance of OTRS.