Migrating from Windows 2003 to Windows 2012

[Cantor, Scott]

On 10/21/15, 12:52 PM, "users on behalf of Simpson, Jerry (simpsjy)" <users-bounces at shibboleth.net on behalf of SIMPSJY at ucmail.uc.edu> wrote:



>Bear with me as I'm pretty new to Shib.  We don't want to upgrade the 2003 server, we want to decommission it.  That being said, will Shibboleth work if I upgrade the 2012 server to the latest version and leave the 2003 server as is?  Also, can x32 be run on the 2003 server and x64 on the 2012 server?  The plan is to upgrade to the lastest version once we finish migrating.

They're separate servers. The software on each server is entirely independent of the other, so I'm not sure what kind of interaction you're thinking about exactly.

The modern SP (that you aren't running on the old server) comes only in packages that have to be installed based on the OS. If it's a 64-bit OS, you can only install the 64-bit installer, which now contains both sets of files. You can use either arch on that OS depending on IIS app pool requirements, with some work.

All I'm telling you is that it would be ridiculous to install a dead, unsupported, insecure SP version on a new server, so that's just not even a consideration.

I don't know anything about your application, or how you're intending to do the migration, so there's not much else I can say. Running both at once in production for a single population of clients and somehow trying to cluster them is theoretically possible but patently nuts. So I don't think that's what you're planning. Assuming not, then there's really no possible interaction between the two servers in regard to Shibboleth or anything else, it's a cut over after testing is done. Testing is quite trivial given /etc/hosts manipulation on a client. The IdP(s) should be oblivious to the difference.

-- Scott