Typically the same value is configured on all Windows computers. The objective is to prevent any and all usages of NTLM1 due to the severity of the security risk. If a client transmits an NTLM1 hash over the network, it may be intercepted and easily cracked compared to NTLM2, depending on the length/complexity of the password. This is a common tactic used by attackers in man-in-the-middle attacks during the recon phase of an incursion. So you don't want NTLM1 anywhere in your environment.
The setting behaves differently depending if the computer is performing a client or server function. Any Windows computer (workstation, member server, or domain controller) can perform both.
Highly recommended to have a backout planned as a contingency. Assessing NTLM1 usage and impact is notoriously difficult, especially if you have a large, heterogeneous environment with a lot of crusty old legacy systems.
The Most Misunderstood Windows Security Setting of All Time
https://technet.microsoft.com/en-us/library/2006.08.securitywatch.aspx