Pointer size macOS Sequoia

[skhan619]

Hi all - really annoying that the option for pointer size is greyed out and our developers need the option to adjust available.  Has anyone seen this and found a workaround via Jamf through a script or profile? All my efforts have failed, many thanks :)

 

[talkingmoose]

Appears a Jamf Pro administrator may have deployed a computer configuration profile that includes the Accessibility payload. Under the Seeing tab you'll find a setting for Cursor Size.

The only way to allow your developers to adjust this is to exclude their computers from this configuration profile.

[skhan619]

Yeah I have seen this option but it only sets the curser size.  Is there a method to allow the developers to adjust this themselves?  Thanks.

[AJPinto]

Your Jamf Administrator needs to update the Configuration Profile that is managing this setting. Either the developers need to be excluded, and moved to a profile that does not manage this setting (if not removed entirely) or the check box needs to be unchecked in the configuration profile. Myself, I would just uncheck box this as it’s a very strange thing to manage.

It’s being managed with a Configuration Profile; no terminal command will let you change the setting.

[PMullins1]

In order of impact and difficulty, from least to greatest:

1. Exempt the developers from this configuration profile.
   or
2. Delete the Accessibility payload from your configuration profile entirely.
   or
3. Duplicate the CP, delete the Accessibility payload, and scope that to Developers only (exempting them from the original of course).
   or
4. Download and edit the configuration profile, as agungsujiwo suggested, so that Cursor Size is not set. Re-upload and scope to developers.

Options 1-3 are within Jamf, option 4 requires a third-party utility (which I think you might really like, once you start playing with it).

[skhan619]

Hi @PMullins1 appreciate your response too, like I mentioned to @agungsujiwo there is no accessibility payload enabled.  I have even gone as far as to descope some test devices from existing configuration profiles but the setting still remains! 

[skhan619]

@nick533 exactly there is no need for this option to be checked.  The issue is that I can locate the setting in the configuration profile under any payload.  Do you know the where it is - really appreciate all the responses thanks all. 

[agungsujiwo]

Hi @skhan619 ,
You can try creating an accessibility profile using iMazing Profile Editor.
Select the settings you want to apply, but do not include the Cursor Size setting.
Once done, you can apply it to The Developer Team.

[skhan619]

Hi @agungsujiwo I explored this previously and could not find the payload to edit?  I checked under 'restrictions' but nothing. Any idea where thanks?

[agungsujiwo]

Hi @skhan619 ,

First, the Pointer Size setting is grayed out and cannot be edited because the Configuration Profile > Accessibility setting is enabled. Even if no specific options are selected, the Pointer Size remains grayed out.

To resolve this, remove the Accessibility setting from your configuration profile.

If you need to add a custom accessibility setting, use the iMazing Profile Editor app. Create a new profile without enabling or selecting the Cursor Size option. Once you have created and uploaded the profile to Jamf Pro, the Pointer Size setting will no longer be grayed out.

Note: Customize the profile according to your organization's needs, ensuring it aligns with the department or scope you want to configure.

[skhan619]

Hi @agungsujiwo really appreciate your response, unfortunately we have no accessibility configured on any configuration profile.  So this isn't what's causing it.  We have no requirement to have any accessibility settings and the payload is absent.  

[agungsujiwo]

Hi @skhan619 ,

This is very strange.

I tested it on a Mac, and the Pointer Size setting is grayed out when the Configuration Profile > Accessibility is applied. However, it becomes editable again once the Accessibility configuration profile is removed.

It seems like you may need assistance from Jamf Support. I suggest creating a support ticket for further investigation.