Talk:Security Account Manager

Disable LM hashes

The article states that Windows can be configured to disable LM hashes, but there is no mention of how this would be done. Therefore, a link to Microsoft's Knowledge Base where this is explained in detail [1] could prove useful. —Preceding unsigned comment added by 78.34.139.156 (talk) 21:56, 27 June 2009 (UTC)

This is not completely true. on Windows XP, you could remove the file, login to the Administrator account, which allowed you to modify any accounts password. —Preceding unsigned comment added by 123.243.27.198 (talk) 11:02, 29 January 2008 (UTC)

Registry Location

I came here because I was looking for the registry location of the SAM. Unfortunately it's not mentioned. --193.134.254.25 (talk) 15:04, 22 November 2012 (UTC)

The registry location for SAM is HKEY_LOCAL_MACHINE\SAM — Preceding unsigned comment added by Shrimadhav (talk • contribs) 10:28, 7 August 2014 (UTC)

Related Attacks section

Multiple tools do exist for the purpose of cracking these hashes, perhaps most notably BackTrack, specifically the Jack the Ripper (I think that's the name) utility. Flashgamer001 (talk) 23:49, 19 December 2012 (UTC)

John the Ripper is used to get the password from a hash stored in a file. BackTrack uses another utility called chntpw(pogostick.net/~pnh/ntpasswd/) to make Windows password blank. — Preceding unsigned comment added by Shrimadhav (talk • contribs) 10:31, 7 August 2014 (UTC)

Security Account Manager

The article should be renamed Security Account Manager. Although it manages multiple accounts, the name of the tool / technology is singular. See Security Account Manager. -- Dave Braunschweig (talk) 16:38, 29 May 2013 (UTC)

I agree. It is the official MS TechNet name.

It should be renamed to "Security Account Manager" and a redirect page should be added. dudeprgm^talk_ϝɑɼĸ 19:27, 10 May 2015 (UTC)

No. It is not nearly as simple as you represent. You have probably made a slapdash determination and taken useless if not wrong action – drive-by research and drive-by editing. A Google search on microsoft.com for "Security Account Manager" gets 6,250 hits; "Security Accounts Manager" gets (more) 7,860 hits; both together get "about 400" hits. Having not imposed consistency, Microsoft apparently doesn't know or doesn't care which variation is correct. Are the variations 100% interchangeable, or does one term mean one thing (the database) and the other term mean something else (the software)?

The cited source now redirects to a 28,365 page PDF of "retired content" pages for Windows Server 2003, with no link to which page you intended, and its 28,365 pages, scraped from the Microsoft site, contain both terms. An indication of why there are two terms, or which one is preferred, does not leap out. The original page, available (for now) in archive, says "The Security Account Manager (SAM) is a database...". It also says "Security Accounts Manager (SAM) debug logs...". So the "reference" is not even consistent. There is no "official" name. The move was unjustified, and therefore was either pointless or wrong.

Windows Task Manager (Windows 7) shows a service, name: SamSs, Description: Security Accounts Manager. The one unambiguous indication I can find (the name of running software) says the opposite of what you determined and did. -104.148.244.119 (talk) 17:16, 23 February 2017 (UTC)

"Only recently"

"Only recently, Microsoft released a utility called LockSmith, which is part of MSDart. MSDart is not freely available to end-users, however."

How recently? Can this be dated please? 195.188.200.14 (talk) 09:43, 2 September 2013 (UTC)