Moving MODx site from Windows Server 2003 to Windows Servers 2012

Hi there,

I have a site that is currently hosted on a server running Windows Server 2003. The site is running on IIS 6.0, the site is developed in MODx Evolution 1.0.5, PHP version 5.3.6, Server API - CGI/FastCGI, MySQl version 5.2.0.

I am looking to move the site onto a new server that has the Windows Server 2012 operating system.

Anybody with a site on Windows Server 2012? Is there anything that I need to look out for?

Thanks

Hi paraicc1972,

I haven't dealt with Windows Server 2012 per se, but here are some potential pitfalls:
1) IIS 8.0: IIS changes with each new Windows Server that comes out. Having worked on Windows Server 2003 for the longest time, I found the move to IIS 7.0 (Windows Server 2008) a bit of a pain because there are now more options to deal with and a bunch of gotchas
2) MySQL 5.2.0 compatibility with Windows Server 2012: Not sure if it has been deemed compatible.
3) Security: Security settings keep getting tighter, so in earlier versions of Windows Server, there was a lot that was allowed by default but the move has in recent years been to keep a lot of things closed. For people that deal with WS 2012 on a regular basis, they would know about these things, but for those that deal with it only as a given client requires, it can be frustrating.

Hope this helps.

Regards,
Tom

Hi Tom,

Thanks for getting back to me on this. Much appreciated. I will probably try and do a test installation on an evaluation copy and see how it goes. Fingers crossed!

Regards,
Paraic

Quote from: stalemate at Apr 30, 2013, 09:38 PM

Hi paraicc1972,

I haven't dealt with Windows Server 2012 per se, but here are some potential pitfalls:
1) IIS 8.0: IIS changes with each new Windows Server that comes out. Having worked on Windows Server 2003 for the longest time, I found the move to IIS 7.0 (Windows Server 2008) a bit of a pain because there are now more options to deal with and a bunch of gotchas
2) MySQL 5.2.0 compatibility with Windows Server 2012: Not sure if it has been deemed compatible.
3) Security: Security settings keep getting tighter, so in earlier versions of Windows Server, there was a lot that was allowed by default but the move has in recent years been to keep a lot of things closed. For people that deal with WS 2012 on a regular basis, they would know about these things, but for those that deal with it only as a given client requires, it can be frustrating.

Hope this helps.

Regards,
Tom