It still works, except you can ignore the part about going into the WOW6432Node branch, it all lives in HKLM\Software\Microsoft\SMS\Components\SMS_DISCOVERY_DATA_MANAGER now. I have a few VMs I keep excluded using either the ExcludeServers or ExcludeMACAddress values.
Thank you, Jeffery C. Juett SCCM Administrator, Information Technology UnityPoint Health From: [email protected] [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Monday, November 17, 2014 8:57 AM To: [email protected] Subject: [mssms] Prevent Client Installation Does this method still work for CM12? Or is there a more preferred method? I was about to just create a CCM and ccmsetup file in C:\Windows but if there is a better solution, I'd prefer that. http://technet.microsoft.com/en-us/library/bb693996.aspx Thanks, James Beardsley | Firm Technology Group Dixon Hughes Goodman LLP [Description: Description: Description: cid:[email protected]] ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation. This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. sections 2510-2521, and contain information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
