EBS 2008 RWW Single Sign On to OWA error

Hi,

Certificate is installed and working

Charles

Go into IIS and restart it. Test.
Then stop and start the default website hosting OWA.
Test.
Failing that check to see that OWA is bound to ASP.NEt 2.0 on the default website in IIS

Chok,

I did as you suggested, ASP.NET config was also correct, still no change:(

Charles

Hi Charles,

I noticed another posting here that may be related both to OWA and RWW problems you are encountering.  I was looking at RPC issues and discovered this ...

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Essential_Business_Server/Q_24152922.html

The person who posted the problem indicated he had issues with RWW redirect and SSO both which appear to be problems you are experiencing.   The solution was to disable RPC kernel-mode authentication on the Messaging server.

Hi There,

You seem to be everywhere! the EBS forums here would be a dismal failure without you and Keith!


I applied the fix that was suggested in your link, it didn't help. I wonder if this all comes back to the same root problem with Firewall configuration between servers. As you found - the firewall was disabled on the Security server when you reinstalled it, which makes sense. We are carrying out the reinstall of EBS this weekend, i will be interested to see if and when this problem happens again - i am SURE it worked as intended originally, then along with many things, suddenly stopped working.

I can only assume tasks i or the other techs considered unrelated, weren't so unrelated - EBS is a pretty tight ship afterall...

Advise soon:)

Charles

I agree about EBS being a beast when it breaks, it seems to break everything.  I call it a tightly coupled configuration because each piece is so dependent on the others doing their job.  I've always maintained that it's best to use the wizards for everything unless the experts from MS tell you different.  It's a challenge for me because after you've worked on systems as long as I have, you tend to go by instinct and read the books after the fact.  Experience has taught that being a "cowboy" isn't necessarily the smartest way to go.

I'm sure the re-install will fix it all for you and it'll teach you more about the systems as well.  Think of it as a good learning experience and document everything.  You'll soon realize it will become a good part of your DRP documentation.  I took screen shots of every single screen pretty much and documented all the issues and workarounds.  Now I have instructions detailed enough that a junior IT person could easily do the task.

When I first installed EBS, I didn't get time to play with it as much as I wanted because I was on a contract and had limited time.  The challenge for me was to succeed at the install and convert the sites entire IT infrastructure from a bunch of old Linux servers to a state of the art Windows setup.  As it is, I still have one old LInux server running a couple of web sites and an old Novell server with an old Advanced Revelations application and database to deal with, but they'll be gone shortly.

Meanwhile, I have to figure out why the EBS Administration console isn't getting updates from WSUS and the desktops.... It either hasn't contacted them in days and days or it thinks they need updates.  I thought I fixed that problem once already (sigh)  

Dan,

You are right, this has been a huge learning curve - we ran it in test environment for a good month, with half a dozen workstations attempting to simulate any problems that might arise. As you'd have it - it was flawless, the day we swapped over, the EBS machine started blue screening, so we backpedaled, addressed the problem (corporate AV was failing and running up infinite instances of its service).

From what little i saw of the WSUS console in SCE/EBS Admin, it is extremely uninformative compared to the standard WSUS MMC Snapin. While my WSUS was working, i still used the MMC snapin directly from my workstation to troubleshoot other problems. Maybe this approach will help you too.

I also frequently had many workstations reporting in with warnings, but i put that down to disobedient staff who manage to have their workstation offline when the updates are scheduled to install:)