Disable Find My Mac

[al_c]

I set a Restrictions configuration profile to disable Find My Mac. I ensured that I'm part of the scope and that the config profile actually installed on my machine. My machine is checking in with no problem. However, I'm still able to turn on/off Find My Mac after the Restrictions profile is installed

Anyone having this issue or recommend a better way of disabling? What scares me the most is a user being able to remote wipe their Mac without IT's consent.

[Swordfish]

Hello @whiteb , 

I posted the original post when I noticed the key I had in place stopped working when we deployed macOS Ventura to our enterprise. However, I updated it after chatting with some users here who ran into the same issue. I can confirm that after updating the 13.4, the key I had put in place is still working, as you had stated. Please see below. I will def followup if this changes in anyway. 

In addition, thank you for the iMazing Profile Editor tool. Really good to be aware of that. 

Thanks, again!

----

PLIST file containing key value pairs for settings in the specified domain

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>DisableFMMiCloudSetting</key>
<true/>
</dict>
</plist>

------

[whiteb]

Awesome, great to hear! In my testing, turning Find My on seemed to require admin rights as well (which none of our users have).

[JBartkowiak]

So I am working on checking and updating/cleaning up some polices and came to check in on this. I saw that it was now working for "Sonoma". But when I am testing with it today for "Sequoia" 15.4.1 It looks to not be working again maybe on this latest version? With "Allow iCloud Find My Mac" unchecked I am still able to enable and disable the feature.... Any one else tried this on the latest os? The being able to use the built in options instead of needing to set it with a Plist? 

Thanks so much! 🤙🏻

[whiteb]

I just signed into a test computer running 15.4.1 with a personal Apple ID. The behavior I'm still seeing is that clicking 'Turn On' for Find My Mac doesn't do anything, so it does seem to be still working for us in the latest Sequoia.

But I'm still using a profile I made with iMazing Profile Editor and not Jamf's built-in one. Maybe theirs is bugged?

If you use Jamf's built-in one, create the profile, save it, look at it in a text editor, what key are they using?

DisableFMMiCloudSetting is still working in 15.4.1.

We disable this as part of a larger baseline config profile, but a standalone one that does just this would look like:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>PayloadContent</key>
	<array>
		<dict>
			<key>DisableFMMiCloudSetting</key>
			<true/>
			<key>PayloadDisplayName</key>
			<string>iCloud Find My</string>
			<key>PayloadIdentifier</key>
			<string>com.apple.icloud.managed.E6510E38-D6AB-4B6F-A230-439CD08EFC16</string>
			<key>PayloadType</key>
			<string>com.apple.icloud.managed</string>
			<key>PayloadUUID</key>
			<string>E6510E38-D6AB-4B6F-A230-439CD08EFC16</string>
			<key>PayloadVersion</key>
			<integer>1</integer>
		</dict>
	</array>
	<key>PayloadDisplayName</key>
	<string>Disable Find My</string>
	<key>PayloadIdentifier</key>
	<string>2B0DAAC6-F620-4E62-BEB9-5E673DED4876</string>
	<key>PayloadOrganization</key>
	<string>Your Org Here</string>
	<key>PayloadType</key>
	<string>Configuration</string>
	<key>PayloadUUID</key>
	<string>2B0DAAC6-F620-4E62-BEB9-5E673DED4876</string>
	<key>PayloadVersion</key>
	<integer>1</integer>
</dict>
</plist>

 I generally like to sign profiles before uploading so Jamf can't mess with them, but it's not always required.