LOGON_USER not working after KB942615

Our corporate intranet is having problems storing the users username using
asp Request.ServerVariables("LOGON_USER").

Request.ServerVariables("LOGON_USER") is assigned to a session variable in
the global.asa file but if I try to recall the session variable it returns
empty yet when I use Request.ServerVariables("LOGON_USER") directly on the
same page it returns the correct username. It works for everyone without
KB942615 even for the same users before the update so it can't be a code
issue. It was working correctly before and when I uninstall the update it
works correctly again.

Is there any way to block this update? Possible a registry entry I can push
to the computers?

Dave wrote:

> Our corporate intranet is having problems storing the users username using
> asp Request.ServerVariables("LOGON_USER").
>
> Request.ServerVariables("LOGON_USER") is assigned to a session variable in
> the global.asa file but if I try to recall the session variable it returns
> empty yet when I use Request.ServerVariables("LOGON_USER") directly on the
> same page it returns the correct username. It works for everyone without
> KB942615 even for the same users before the update so it can't be a code
> issue. It was working correctly before and when I uninstall the update it
> works correctly again.
>
> Is there any way to block this update? Possible a registry entry I can push
> to the computers?

Since this is a Critical Security update it would behoove you to contact
MS for no charge support in order to get it installed :

>
>> Support:
>> • Customers in the U.S. and Canada can receive technical support from Microsoft Product
>> Support Services at 1-866-PCSAFETY. There is no charge for support calls that are
>> associated with security updates.



MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

Windows version(s)? IE version(s)?
=============================
Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

Support for Windows Update:
http://support.microsoft.com/gp/wusupport

Customers in the U.S. and Canada can receive technical support from
Microsoft Product Support Services at 1-866-PCSAFETY. There is no-charge for
support calls that are associated with security updates. When you call,
clearly state that your problem is related to a Security Update and cite the
update's KB number (e.g., KB931678).

In other countries, see
http://support.microsoft.com/default...r=securityhome > "No-Charge
Support...for virus and other security-related" issues in right-hand menu
for localized contact information.

For more information about how to contact Microsoft for support issues,
visit the International Support Web site:
https://support.microsoft.com/common/international.aspx
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L.ORG http://66.39.69.143/


Dave wrote:
> Our corporate intranet is having problems storing the users username using
> asp Request.ServerVariables("LOGON_USER").
>
> Request.ServerVariables("LOGON_USER") is assigned to a session variable in
> the global.asa file but if I try to recall the session variable it returns
> empty yet when I use Request.ServerVariables("LOGON_USER") directly on the
> same page it returns the correct username. It works for everyone without
> KB942615 even for the same users before the update so it can't be a code
> issue. It was working correctly before and when I uninstall the update it
> works correctly again.
>
> Is there any way to block this update? Possible a registry entry I can
> push
> to the computers?