Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

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

Posted on 2010-08-23
1
Medium Priority
?
1,312 Views
Last Modified: 2012-05-10
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?
0
Comment
Question by:jfsedlar3rd
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
jfsedlar3rd earned 0 total points
ID: 33506196
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

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question