Automatically suppressing the iCloud and Diagnostics pop-up windows with Casper
When I updated to 10.10.1 yesterday, as part of the restart process I noticed that I was seeing the Diagnostics pop-up window appear on login.
I had previously suppressed this window as part of setting up this machine, but it looks like the LastSeenBuddyBuildVersion value in /Users/username/Library/Preferences/com.apple.SetupAssistant.plist had the build number for 10.10.0 stored and it needed to be updated with the build number of 10.10.1 in order to suppress the Diagnostics pop-up window again.
Fortunately, this can be addressed by setting up an automated run of my iCloud / Diagnostics suppression script with Casper. This should automatically update the LastSeenBuddyBuildVersion value in /Users/username/Library/Preferences/com.apple.SetupAssistant.plist with the build number for the current version of 10.10.x. For more details, see below the jump.
To help automate this process, I first added the iCloud / Diagnostics suppression script to my Casper server.
After adding the script, I set up a Casper policy that automatically runs this script at startup.
To help ensure that this script also runs when the Mac cannot contact my Casper server, I’ve set Execution Frequency to Ongoing, as that allows me to select the Make Available Offline option.
The policy is scoped to a smart group that contains only 10.10.x Macs.
Leave a Reply
Recent Comments
 | Mark P on 20 years of Der Flounder |
 | Bruce Carter on 20 years of Der Flounder |
 | JimH on Downloading installer packages… |
 | Sander on Downloading installer packages… |
 | Andreas Schenk on Downloading installer packages… |
Der Flounder 
FYI there are two com.apple.SetupAssistant.plists with different content.
one in /Library/Prefs.. and one in ~/Library/Prefs..
changing the LastSeenBuddyBuildVersion and LastSeenCloudProductVersion values seems not to cause the dialog to pop up.
The video you’ve linked is “private” so we can’t see it. 😦
Whoops. Fixed, please try it again.
it’s not working.
I try to force the diagnostic setup for testing purposes. I tried to set or remove all build and version values in com.apple.SetupAssistant.plist and reboot the system, it will still not ask for diagnostic setup.
I noticed that you have added /usr/bin/ before your defaults write commands. This was not there in the 10.9 script. Is it required for 10.10? What is the difference/benefit? Thanks.
I used this script to stop these diagnostic screens via Offset’s every-boot functionality. Working great so far!
i have this but doesnt prevent the sign in with apple id screen, is it suppose to be muting this?
I have been using this in our casper deployment but it now doesn’t work with 10.11, is there another version of this I haven’t found?
My understanding is that in 10.11 Sips prevents us from modifying anything in /System. Therefore we can’t modify, i used rtrouton’s config profile to suppress this. But it requires the system to be rebooted for it to work.