Request.LogonUserIdentity.Name pulling old uid after it was updated in Active Directory

I have an asp.net application that pulls the user currently logged onto the machine via :  Request.LogonUserIdentity.Name

This has always worked flawlessly in the past, however my Active Directory admin changed a user id within AD . When My app pulls the  Request.LogonUserIdentity.Name it is still pulling the old name. We have already tried recreating the local profile for the user and windows shows them logged in as the new ID but this code method is still pulling the old id. Can anyone offer some insight?
jfsedlar3rdAsked:
Who is Participating?
 
jfsedlar3rdConnect With a Mentor Author Commented:
Resolved:

To work around this issue, disable the local SID cache on the domain member computer. To do this, follow these steps:

   1. Open Registry Editor.

      To do this in Windows XP or in Windows Server 2003, click Start, click Run, type regedit, and then click OK.

      To do this in Windows Vista, Click Start, type regedit in the Start Search box, and then press ENTER.
   2. Locate and then right-click the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
   3. Point to New, and then click DWORD Value.
   4. Type LsaLookupCacheMaxSize, and then press ENTER.
   5. Right-click LsaLookupCacheMaxSize, and then click Modify.
   6. In the Value data box, type 0, and then click OK.
   7. Exit Registry Editor.

Note The LsaLookupCacheMaxSize registry entry sets the maximum number of cached mappings that can be saved in the local SID cache. The default maximum number is 128. When the LsaLookupCacheMaxSize registry entry is set to 0, the local SID cache is disabled.
0
All Courses

From novice to tech pro — start learning today.