FYI: For the most part, things in my SEPM console on a WinXP Pro box were working just fine from the time I upgraded to MR2 but today I had login prompts for any links (e.g. 'Preferences' and 'More Details' in the main Home window) that fired off http://{servername}/Reporting/Resources/filter_notfound.php....  I normally see this URL flash first and then it displays the desired page but this morning they were all blank!  I couldn't even display the 'Help' link where the bottom area of the IE window seemed to be looking for my proxy server settings.  Rebooting the SEP server didn't resolve this problem although note that this issue doesn't occur if I run the SEPM console directly on the server.

 

Anyway, I had recalled that yesterday I happened to see Crypt32 errors (EventID 8) in my XP's Application event log where it appeared my PC was having difficulty getting to Windows Update for whatever reason.  I couldn't find a specific article in Microsoft's KB that exactly matched the text in my Windows App log but decided to try one of the resolutions in 317541 to import my IE proxy settings into this WinHTTP Default Proxy Configuration Tool.  Specifically, I went to a command prompt and typed in "proxycfg -u" and now the correct web pages are showing up after clicking links that require SEP reporting!  Granted, I'm sometimes still getting login prompts asking for Username, Password and Domain after clicking on a reporting component but at least the right webpage comes up for me now.

 

However, once I get a reporting login prompt and enter my admin credentials (leaving Domain blank), the Home, Monitor and Reports pages in the console change a bit (might have to click Refresh) where I now see a bunch of tabs at the top (i.e. Home, Summary, Logs, Command Status, Notifications, Quick Reports, and Scheduled Reports) with "User:admin" and "Log Out" at the right.  It's like an IE window within the Java window where you now have 2 links to log off/out.  Anyhow, not sure how long my executing "proxycfg -u" to eliminate my Crypt32 errors on my XP box will last but at least it helped in displaying the correct SEPM reporting pages for me; albeit I'm still getting login prompts from time to time.  Hopefully Symantec can make some sense out of the SEPM behavior I've described and provide a resolution.

 

Clint