Has anyone tried to install the SiteMinder R12.0 SP2 Web Agent on Windows 2008 R2 with IIS 7.5 (64 bit) ?
I know it is scheduled to be officially "certified" in August but I tried it anyway.
It installed without any errors. But then I ran into some ACL security issues. I was able to resolve them however now I'm getting an HTTP 500 error with every request whether the resource is protected or not. The web agent trace is giving the following error:
ProcessResource][Plugins did not collect required resource data.]
after successfully resolving the client IP address.
Should I fall back to Windows 2008 SP2 (64 bit) which is officially supported?
If you are planning on using this in a production environment, I would definitely fall back to a supported environment. Even if you can get it to work on IIS 7.5, if you run into a problem you will have to reproduce it on a supported environment prior to being able to get support for the configuration (at least in my experience).
My guess is that IIS 7.5 changes the way the agent needs to plug into the architecture, although I have no basis for that statement. It's purely a guess.
I can't say for sure since I don't know exactly what your requirements are, configuration required, etc., but I personally think IIS 7 is that way to go until an agent is released which officially supports IIS 7.5.
Thanks for the quick response. I've asked for our infrastructure team to set up a Win2k8 SP2 server. I'm new to 2008 and wasn't aware of the differences between the versions.
I've been able to get it working with no further issues.
The problem was with the installer. It didn't set up the ISAPI filter or the wild card script handler properly. After I set these manually at the server level everything started working normally.
It looks like IIS 7.5 on 2008 R2 (64 bit) is now officially supported with the recent release of R12.0 SP2 CR1. One caveat is to follow the manual configuration steps (similar to what I figured out on my own above):
From CA Support:
" Requires use of manual configuration steps. Please refer to Support article TEC526135"