On 11/18,
When we right-click on the webpage and look at the properties, it was treating the report as an internet site, instead of an intranet site. Enhanced security config protection was on, but the server was not in the ESC zone map in the registry. So our admin took it out of the Enhanced Security (escDomains) and now it opens up as Intranet without any prompting.
On 11/19/14, after 3.5 hrs we finally were able to get this to work.
SolarWinds Tech recorded these notes:
> Put the website in the Trusted sites
> Try running the Alert service under Local Admin account or the account under which you are logged in to the Orion website (does not work sometimes)
> Also move the certificates to the Trusted Root certificates zone.
> Disable UAC
> Reboot the box
> Deleted the old accounts that it was passing thru when logging into the website
> Ran the Configuration Wizard
> Finally we created a brand new Local Orion account (account = test; password = test)
> Feed that account details into the URL as below (just example)
lielanorion01/Orion/SummaryView.aspx?viewid=116&accountID=test&password=test&InlineRendering=TRUE
> Tested the Alert action again and it worked perfectly fine.
> We also ran the Scheduled reports with this test account & they also ran perfectly fine.
...
Since I couldn’t quite leave things in the state where we left off, I wanted to update you on what I did after our call. (The account names in this email are not the actual names.)
1. In Orion, added a new Orion-only account called xxx-reporter. I was able to strip it down to only have ‘Allow Report Management Rights’ & to have none for all the menu bars. (This made the report heading much smaller.)
2. I changed all the scheduled reports and the alert’s web page URL to use this new account and password. I found I had to remove the special character (#) which was on the end of the password for the webpage to work. [Before I fixed it, I once again received the logon page (but this time it showed me the xxx-reporter account in the error message and said it couldn’t log in.]
3. I re-added the domain server\xxx-report (local admin acct) in Orion, since this is the account the unmanaged/scheduled jobs are using. [This is the account I originally was trying to use to run the web page, which we couldn’t get to work. It has special characters in its password too, including a #.)
a. As before, now IE works on the server when logged in under this account. But, when you log out & try to re-login with an Orion-only account, it validates the userid/password, but opens the website using the network account you’re logged in to the server with … NOT the Orion-only account. So, as you stated, Orion’s logon page has an issue when using IE browser. (And you suggested using Chrome or Foxfire to get around this.)
4. In Orion, I disabled the Orion-only accounts we tested with (test & xxx-report).
Again, thanks for all of your help and perseverance. The 3.5 hrs was time well spent.