Registry Keys Case Sensitive

[Deb H]

Are registry keys case sensitive? I need to edit these keys NoLMHash and
LmCompatibilityLevel. Most documentation I have read lists these items as
NoLMHash and LmCompatibilityLevel.

I look at my registry and they are all lower case, nolmhash and
lmcompatibilitylevel.
Are they case sensitive?

Thanks

[Dave Patrick]

Doubtful but it really depends on what consumes them.
--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

Post by Deb H
Are registry keys case sensitive? I need to edit these keys NoLMHash and
LmCompatibilityLevel. Most documentation I have read lists these items as
NoLMHash and LmCompatibilityLevel.
I look at my registry and they are all lower case, nolmhash and
lmcompatibilitylevel.
Are they case sensitive?
Thanks

[Deb H]

When you say consumes them - not sure what you mean. These are listed in the
HKLM\SYSTEM\CurrentControlSet\Control\Lsa key.

Post by Dave Patrick
Doubtful but it really depends on what consumes them.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

Post by Deb H
Are registry keys case sensitive? I need to edit these keys NoLMHash and
LmCompatibilityLevel. Most documentation I have read lists these items as
NoLMHash and LmCompatibilityLevel.
I look at my registry and they are all lower case, nolmhash and
lmcompatibilitylevel.
Are they case sensitive?
Thanks

[Dave Patrick]

I meant it may depend on what process is reading them. Looks like you can
also use the policy editor to set them.
--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

Post by Deb H
When you say consumes them - not sure what you mean. These are listed in the
HKLM\SYSTEM\CurrentControlSet\Control\Lsa key.

[Deb H]

I am guessing the Domain Security policy or Domain Controller Security policy.

Post by Dave Patrick
I meant it may depend on what process is reading them. Looks like you can
also use the policy editor to set them.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

Post by Deb H
When you say consumes them - not sure what you mean. These are listed in the
HKLM\SYSTEM\CurrentControlSet\Control\Lsa key.

[Dave Patrick]

Control Panel\Administrative Tools\Local Security Policy|Local
Policies\Security Options\Network Security:Lan Manager Authentication Level


Network security:Lan Manager authentication level

LAN Manager (LM) authentication is the protocol that is used to authenticate
Windows clients for network operations, including domain joins, accessing
network resources, and user or computer authentication. The LM
authentication level determines which challenge/response authentication
protocol is negotiated between the client and the server computers.
Specifically, the LM authentication level determines which authentication
protocols that the client will try to negotiate or that the server will
accept. The value that is set for LmCompatibilityLevel determines which
challenge/response authentication protocol is used for network logons. This
value affects the level of authentication protocol that clients use, the
level of session security negotiated, and the level of authentication
accepted by servers, according to the following table:

Possible settings include the following.Value Setting Description
0 Send LM & NTLM responses Clients use LM and NTLM authentication and never
use NTLMv2 session security; domain controllers accept LM, NTLM, and NTLMv2
authentication.
1 Send LM & NTLM - use NTLMv2 session security if negotiated Clients use LM
and NTLM authentication, and use NTLMv2 session security if the server
supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.
2 Send NTLM response only Clients use NTLM authentication only and use
NTLMv2 session security if the server supports it; domain controllers accept
LM, NTLM, and NTLMv2 authentication.
3 Send NTLMv2 response only Clients use NTLMv2 authentication only and use
NTLMv2 session security if the server supports it; domain controllers accept
LM, NTLM, and NTLMv2 authentication.
4 Send NTLMv2 response only/refuse LM Clients use NTLMv2 authentication only
and use NTLMv2 session security if the server supports it. Domain
controllers refuse LM and accept only NTLM and NTLMv2 authentication).
5 Send NTLMv2 response only/refuse LM & NTLM Clients use NTLMv2
authentication only and use NTLMv2 session security if the server supports
it; domain controllers refuse LM and NTLM (they accept only NTLMv2
authentication).





Control Panel\Administrative Tools\Local Security Policy|Local
Policies\Security Options\Network security: Do not store LAN Manager hash
value on next password change


Network security: Do not store LAN Manager hash value on next password
change

Enable/Disable
--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

Post by Deb H
I am guessing the Domain Security policy or Domain Controller Security policy.