How to get around having to allow Flash Player and reload every time you visit a site in Google Chrome on Mac

As of Google Chrome 62 onwards “Allowing” a site to use Flash Player is a per-session setting which is really annoying if you still visit sites that rely on Flash Player.  You can allow a site to use the plug-in and tell it to keep the setting but it will get tossed out when you close the browser.


Here’s a quick guide on how to actually allow a site like Sky Sports NZ to use Flash and save that setting permanently until the 2020 removal of Flash Player itself from Chrome.

1. Download Chrome Enterprise for Mac –  Grab the DMG for Mac

2. Also Download the Chrome bundle for Windows 64‑bit ZIP – Yes you need the Windows file as it contains the Chrome Enterprise Templates.

3. Copy the Google Chrome app into your Applications directory and replace your existing normal version of Chrome

Screen Shot 2019-04-19 at 1.35.17 PM.png

4. Open up the Chrome bundle for Windows and unzip it.  Inside the Configuration folder you’ll find a “” file.


5. Open up the .plist file edit any of the Defaults as you need for your case. Once done add in the following entries to the bottom after the last <key> </key> pair and edit the strings as needed for your use case:

<string> </string>
<string> </string>

Full info here on the available settings:

My example file, I’ve set DefaultPluginsSetting to 1, other options are as below.

  • 1 = Allow all sites to automatically run the Flash plugin
  • 2 = Block the Flash plugin
  • 3 = Click to play

1 doesn’t allow all sites as it suggests, as per the notes on the Policy page linked above:

“Automatic playback is only allowed for domains explicitly listed in the PluginsAllowedForUrls policy.  If you want to enabled automatic playback for all sites consider adding http://* and https://* to this list.”

PluginsAllowedForURLs I’ve specified are two strings for the http and https SkyGo NZ URLSScreen Shot 2019-04-19 at 1.49.41 PM.png

6.  Now we need to turn this plist file into a Profile so it can be used on Mac OS.  Download Tim Sutton’s MCXtoProfile python script to convert it from as per Googles Guide.  Download the ZIP and extract it so you have

Screen Shot 2019-04-19 at 2.01.01 PM.png

7. Put your edited file into the same directory as and run in it:

./ –plist –identifier

If you get any errors double check the syntax in your plist file.

Screen Shot 2019-04-19 at 2.04.54 PM.png

8. Copy the newly created .mobileconfig to the Mac(s) you want to allow Flash on the sites for and run it.

9. Install the Profile…

Screen Shot 2019-04-19 at 2.07.29 PMScreen Shot 2019-04-19 at 2.07.41 PMScreen Shot 2019-04-19 at 2.07.51 PM

If you want to use this in an actual Enterprise environment I’d suggest editing the .mobileconfig file to have a better name and signing it with an Apple Developer ID.

10. Finally Open up Chrome and test the site(s) you just allowed.





How To Create a WDS Boot and Discover Image for Windows 10 / WinPE 10

Creating new Boot Images is something I do very rarely for our WDS Server (Server 2012 R2) and always run into issues with.  All the guides you’ll find are for Server 2008, SCCM, Custom WinPE Images and are often dated or not quite what we need for a straight up WDS environment…  So I’ve spent two days investigating this and will write it up below in code type format with comments. Commands here as well –

Start of by Installing the Windows ADK for your OS, i.e. 1703 ADK for Win10 1703.

Once installed open the Deployment and Imaging Tools Environment Command Line via the Start menu and typing Deploy… right-click, Run As Admin and type:

copype amd64 C:\WinPE_amd64\

Some guides don’t use copype, they just skip to mounting the WIM file we are using copype as it lays down the folder structure necessary for this to be a Boot Image in WDS and also a ISO / USB Flash Drive style image.  Now mount the wim file via:

dism.exe /mount-wim /wimfile:C:\WinPE_amd64\media\sources\boot.wim /index:1 /mountdir:C:\WinPE_amd64\mount

Add the necessary features to make it work with WDS, this part is confusing as the MS TechNet articles and other documentation are as clear as mud on Optional PE Components…  This is what I consider will cover all your bases.  Do you need the en-US of each, I don’t know most guides suggest so but I’m not 100% on it, I just add them…

Common issues I know of are:

  • auto-reboots during the final load states of a PXE boot, just after blue screen appears, you haven’t included “”
  • iastorB.sys error on boot.  Is not a driver problem,  again you haven’t included “” go back and re-add it.
  • errors about language packs, add “”
  • errors about no default language being set add the lang.ini file as mentioned below

Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\”
Dism /Add-Package /Image:”C:\WinPE_amd64\mount” /packagepath:”C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\”

Set the Language to en-US

Dism /image:C:\WinPE_amd64\mount /Set-AllIntl:en-US

Now we need to a manually copy a lang.ini file into the C:\WinPE_amd64\mount\sources or you’ll get this error:

Windows could not determine the language to use for setup. Error code: 0x80004005.

Using NotePad create a new file called lang.ini with the following in it:

[Available UI Languages]
en-US = 3

[Fallback Languages]
en-US = en-us

Add your base drivers, in my example we’re using the DELL WinPE CAB from here

dism.exe /image:C:\WinPE_amd64\mount /add-driver /driver:”C:\forbootimage\WINPE10.0-DRIVERS-A04-942XJ\winpe” /recurse

Add any extra special drivers at this point as well. You only need “network” and “storage” drivers unless you’re having input problems then you might need to add a special USB3 driver as well.  I assume WinPE 10 1703 has some standard USB3 drivers in it by now…

The typical you don’t have a compatible Network Driver error is:

WdsClient: An error occurred while obtaining an IP address from the DHCP server.


The Typical you don’t have the right Storage controller driver loaded is the inability to see any disks in the pick a disk to install Windows on window.  Although on some models this is a weird USB issue and restarting the install process and plugging the USB drive into a different port will make the internel drive magically appear.

Once all done Commit the changes you’ve made to this wim file.

unmount and commit the changes to the WIM file (close any open explorer windows to avoid errors…):
dism.exe /unmount-wim /MountDir:C:\WinPE_amd64\mount /commit

Copy the newly saved C:\WinPE_amd64\media\sources\boot.wim over to the WDS Server into a local temp folder and “Add Image” it to the Boot Images section. Name it and test.

To also create an ISO at this point or USB Drive you can either go back to WDS and use the “Create Capture Image” option and a bunch of other steps… but we’ve already done all the hard work so lets just tell this Custom WinPE Boot Image about our WDS Server manually:

Opening the Deployment and Imaging Tools Environment Command Line via Start menu and typing Deploy… Run As Admin

Re-mount the wim file again via:

dism.exe /mount-wim /wimfile:C:\WinPE_amd64\media\sources\boot.wim /index:1 /mountdir:C:\WinPE_amd64\mount

Manually create a winpeshl.ini file via NotePad add in:

%SYSTEMDRIVE%\sources\setup.exe, /wds /wdsdiscover /WdsServer:fqdn


move this file into C:\WinPE_amd64\mount\Windows\System32

Once all done Commit the changes you’ve made to this wim file again.

unmount and commit the changes to the WIM file (close any open explorer windows to avoid errors…):
dism.exe /unmount-wim /MountDir:C:\WinPE_amd64\mount /commit

As we used copype originally we can now just do the following to make an ISO or USB bootable drive:

Opening the Deployment and Imaging Tools Environment Command Line via Start menu and typing Deploy… Run As Admin

MakeWinPEMedia /ISO C:\WinPE_amd64 C:\WinPE-WDS-1703.iso (call it whatever you want)

MakeWinPEMedia /UFD /F C:\WinPE_amd64 G: (whatever drive letter your Flash Drive appears as)

When creating USB Installers, use the following settings:  MBF for UEFI, FAT32. i.e. in Rufus:


Using this method, you can easily make USB Bootable drives over and over for that new weird Tablet or Laptop that you need to image, add some drivers in as above and then commit the changes and follow the steps above, still doesn’t work?  mount the WIM again, add more drivers, commit it again and create a new ISO / Flash Drive until you get the result you want.


Ricoh SP3510N / 3500 freeze on adding

So we update users to 10.11.x all the time and I found our existing Ricoh installer pkg’s were working fine but when you went to add a Ricoh SP3510 via the Add Printer dialog it would just freeze for a long time if you left it for 30-45 mins it might actually finish….

Ricoh released a Firmware Update for the 3510 & a New Driver.

You need to flash the firmware first then install the new driver and then add the printer.  The long delay due to the “Queue” field being blank is no longer an issue.

Release notes
Version 2.08

1) Supported
– None

2) Fixed
– When “DHCP” is set to “Active” and “DNS Method” is set to “Auto-Obtain (DHCP)”, an extra character is added in the domain name.

3) Others
– In Mac OS X 10.11, if the “Queue” field is blank when adding a printer by specifying its IP address, the operating system experiences a significant delay in response time

Office 2011 – Word / PowerPoint wont let you type in text

Haven’t wrote a post for many years, thought I try to get back into the habit of documenting fixes for strange things so I’ve got them for my own reference and hopefully saves someone else some time.

So I upgraded someone from 10.8.5 with Office 2011 to 10.11.6 with Office 2011.  All was going fine and then they called and said they couldn’t type text into Word any more.  Sounded odd, can’t type in all other apps, can even type in the search bar of Word

Screen Shot 2016-10-18 at 9.17.05 AM.png

Went over and confirmed this, checked the Input Sources Menu and it was set to English Australian, US also had the same result…. Odd….

Tried clearing Word Prefs, Caches, font caches and all sorts.  Still the same result.  Tried removing and re-installing Word 2011.

But just ended up getting this error on re-install:

Microsoft Error Reporting log version: 2.0

Error Signature:
Date/Time: 2016-10-07 03:12:21 +0000
Application Name: Microsoft Office Setup Assistant
Application Bundle ID:
Application Signature: MsLi
Application Version:
Crashed Module Name: merp
Crashed Module Version:
Crashed Module Offset: 0x00004422
Blame Module Name: PowerPlantCore
Blame Module Version:
Blame Module Offset: 0x00014a81
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Crashed thread: 0

Thread 0 crashed:

#  1  0x0000d422 in _MerpCreateSession + 0x000015CF (merp + 0x00004422)
#  2  0x9aedb79b in __sigtramp + 0x0000002B (libsystem_platform.dylib + 0x0000279b)
#  3  0xffffffff in  ( + 0x00000000)
#  4  0x99b80c38 in _abort + 0x0000009C (libsystem_c.dylib + 0x0005ec38)
#  5  0x9d4ef6f9 in ___cxa_bad_cast + 0x00000000 (libc++abi.dylib + 0x000006f9)
#  6  0x9d5115c5 in default_terminate_handler() + 0x00000110 (libc++abi.dylib + 0x000225c5)
#  7  0x9d50e5fd in std::__terminate(void (*)()) + 0x0000000E (libc++abi.dylib + 0x0001f5fd)
#  8  0x9d50e00b in __cxxabiv1::exception_cleanup_func(_Unwind_Reason_Code, _Unwind_Exception*) + 0x00000000 (libc++abi.dylib + 0x0001f00b)
#  9  0x05a7ba81 in LException::Throw(long, unsigned char const*) + 0x00000091 (PowerPlantCore + 0x00014a81)
# 10  0x05a7ba9b in LException::Throw(long) + 0x00000019 (PowerPlantCore + 0x00014a9b)
# 11  0x08dfd2a2 in UCharset::ConvertScriptToUnicode(char const*, unsigned long, short) + 0x00000054 (OutlookCore + 0x000032a2)
# 12  0x0835b4a8 in CTimeInfo::CTimeInfo() + 0x000001E4 (OutlookLegacy + 0x000024a8)

So Long Story short the ConvertScriptToUnicode part was the clue.  It turns out the user had changed the Primary OS Language in the Language & Region pane from English (New Zealand) – Primary to English (Maori) – Primary.  They were simply trying to type some Macrons in Word…  Set it back and rebooted, Office 2011 now re-installed fine and Word let us type text again…  Showed the user how todo macron’s via the input sources menu instead.

Screen Shot 2016-10-11 at 5.32.26 PM.png

Authorization File Change Log (of sorts) & Archive

I’ve been playing with VMWare Fusion Snapshots and OS builds and have compiled a repository of original etc/authorization files incase you mess yours up.  Authorization File Archive.

And the correct permissions are: permissions

A few have asked if these posts are still valid for 10.8.x & I’d like to confirm Yes they are.  I decided to go back and look at each & compare them to find the changes throughout the OS builds in the etc/authorization files.

10.7.2 to 10.7.3  Just some new strings added in to support multiple new languages.


10.7.3 to 10.7.4 – A couple of new Keys were added, brief description below:

<key></key> (Probably allows you to set who can see passwords in Safari)

<string>This right is used by Safari to show passwords </string>

<key></key>  (Probably allows you to set who can repair libraries)

<string>__APPNAME__ is trying to repair your photo library.</string>

<key></key> (Not too sure)

<string>Modify Settings</string>


10.7.4 to 10.7.5 – No Changes


10.7.5 to 10.8 – Lots of Changes, Notes below.

<key></key> (To investigate) 


<string>Used by diskmanagementd to allow access to its privileged functions</string> (To investigate) 

<key></key>  appears to be exactly the same as <key>system.preferences.softwareupdate</key>  but new rule of   <string>root-or-entitled-admin-or-app-specific-admin</string>  (app-specific-admin seems to be new as well)

<key></key> (This replaced a Podcast Producer key, to investigate)

<key></key> (To investigate) 

<key></key> (To investigate) 

<key>system.preferences.nvram</key> (To investigate) 

<key></key> (Is now a USER rule)


New Keys (abbreviated)

<key></key> (Appears the same, To investigate) 

<string>For making change to network configuration via System Configuration.</string>

<key>system.volume.</key> (Not sure about this lot of volume related keys) 







<key>app-specific-admin</key> (New Rule type, To investigate) 








10.8 to 10.8.1 – No Changes


10.8.1 to 10.8.2 - Some Changes.






<string>Login mechanism based rule.  Not for general use, yet.</string>





<string>builtin:login-begin</string> (NEW, not sure of use)


<string>builtin:login-success</string> (NEW, not sure of use)


———  Updated : 22 July 2013  ———-


10.8.2 to 10.8.4 - A few new entries


<key></key>  (Described as: __APPNAME__ needs to repair your Library to run applications)



A couple of New Wifi Strings that look very useful

<string>For restricting WiFi control</string>
<string>Used by the WirelessDiagnosticsSupport framework to restrict XPC services provided by the wdhelper daemon</string>

Adobe Flash 11.3 Enable or Disable Silent Update Package

Flash Logo

Adobe Flash Player 11.3 for Mac has a new “Silent Update” feature, detailed here:

“The background updater being delivered for Mac OS X uses the same design as the Flash Player updater on Windows. If the user chooses to accept background updates, then the Mac Launch Daemon will launch the background updater every hour to check for updates until it receives a response from the Adobe server. If the server responds that no update is available, the system will begin checking again 24 hours later. If a background update is available, the background updater can download and install the update without interrupting the end-user’s session with a prompt.”

Supposedly it will allow Flash to update itself with no user interaction but I can’t confirm this until another Flash Update comes out.  Anyway I’ve put together a really basic Package the turns the feature On for anyone who wants to give it a try.

It  simply puts a new mms.cfg files into /Library/Application Support/Macromedia/ with the following 2 lines of text:


This package can be deployed via the normal methods. (ARD, Munki, Casper)

Pic of Package IconPKG –  (use the File Menu > Download)


& here’s a PKG todo the opposite – AutoUpdateDisable = 1 & SilentAutoUpdateEnable = 0

Pic of Package Icon PKG – (use the File Menu > Download)


Checkout Greg’s package here for a Package that disables updates –


Using Network Accounts with the Authorization file – 10.7.3

I’ve had a couple of comments about using Network based accounts / groups instead of local groups.  I’ve done some tests on 10.7.3 and here’s a couple of ways to go about it. (Thanks goes to Shane for some of the info)

My testing and examples below assume a similar setup to mine which is.  Staff are allocated one machine each.  Windows Server 2008 Active Directory setup, Domain Users and Mac’s bound to AD via the native apple plug-in.  A local admin account on every mac for installing software, ARD use, backup for when directory services falls over.  Try and adjust my examples below to fit your needs.

A. Create a new local group and add users to it. (Small scale scenarios)

1. Login as an admin account, goto System Preferences > User & Groups, unlock the pane and click the + button.

2. Scroll down and choose the Group option at the bottom and give it a name.  i.e. testgroup.

3. Simply tick the users you want in that group and close the pane.  In the picture below I’ve added an account called Mickey Mouse.  The machine was bound to Active Directory via the built in Apple plugin then I logged in as the network user (mimouse) and forced a local home, creating a “Managed, Mobile” account.  I’ve also ticked my local admin account called The Boss.

4. You now have a group with your network non-admin account and your local admin account. As pictured below.

Now you can do as per my previous post simply replacing lpadmin with testgroup / whatever you called your new group for whichever Preference Panes you want to unlock.

B. Create a new local group and add existing groups to it, nested groups. (Larger scale scenario)

The example above works for a machine that has one or two known users but not multiple unknown users logging in. We’re going to add existing groups where the members are calculated, to a new local group so it covers all potential users.  Where going to effectively add Domain Users and local admins to this new group.

1. Create a new local group for the purpose.  As per above via Users & Groups or via the command line. (have a look at dscl . -create)

2. Active Directory users get added to the netaccounts local group when you login on your Mac.  Both Mobile and Network accounts. (See my note at the bottom about directly using Domain Groups)  To verify, login as a non-admin AD based user and check the account is in that group via Terminal:  dsmemberutil checkmembership -U mimouse -G netaccounts  (subbing mimouse for your network accounts shortname) you can also use dseditgroup -o checkmember netaccounts (it will check if the current terminal sessions user is in the group or not)

you’ll get a one line reply like this:  “yes mimouse is a member of netaccounts”

3. Add the netaccounts group to your new group, in my example  it’s called testgroup.  In Terminal paste the following: sudo dseditgroup -o edit -a netaccounts -t group testgroup

4. Verify your AD user is now also now part of test group. dsmemberutil checkmembership -U mimouse -G testgroup

 Note: Any other non-admin domain users that login to this machine will also get put into the netaccounts group and therefore be part of your new ‘testgroup’ automatically.

5. Add the local administrator group to this group as well.   You want to be able to edit all the System Preferences as well.  In Terminal paste the following: sudo dseditgroup -o edit -a admin -t group testgroup

6. Verify it’s worked as per step 4, subbing in a local admin’s username.  In my example ‘theboss’.

7. You now have a local group called testgroup, which contains nested groups Administrators and Network Accounts.  Open System Preferences > Users & Groups and you should see a result as pictured below.  Noting that you can’t achieve this result from the GUI.

Accounts Pane

Now you can do as per my previous post simply replacing lpadmin with testgroup / whatever you called your new group for whichever Preference Panes you want to unlock.

NOTE: You can also directly add Domain Groups into this new local group: i.e. below I’ve added Domain Admins and Domain Users from Active Directory to my group.

sudo dseditgroup -o edit -a “Domain Users” -t group testgroup
sudo dseditgroup -o edit -a “Domain Admins” -t group testgroup

BUT this membership is calculated or searched for at the time of credential checking.  A simple check of Shutting down, booting up with no network cable plugged in, logging in as my mobile AD account yields no mimouse is NOT a member of testgroup.  If I connect the Ethernet cable and wait 60 seconds it returns yes they are.  This gets cached for some time period.  I wouldn’t recommending doing it this way, as a network connection is basically required at all times.

Making use of the /etc/authorization file in Lion / 10.7.x

This post will look at putting the authorization file to use in a partially managed Mac environment.  Yes some of this can be done via OD & MCX but as we’re a small environment we don’t use it nor really need it.  All testing was done with 10.7.2 and I’ve been using it with all our Mac’s up to 10.8.2 at the moment.

Q:  What’s the problem we want to solve?
: I want my users to be somewhere in between what Apple defines as a “Standard User” and a “Admin User”.  Stealing from Windows terminology,  I want them to be a “Power User”.

I want the System Preference panes marked below with red X’s to no longer require an Admin password to unlock them.  Your environment will be different to mine, so pick, choose & extend these ideas to what fits your environment.

Desired Sys Prefs

Energy Saver:  I want users to be able to set their own Sleep schedules.  I don’t want support requests from users about changing their sleep from 10 to 15minutes. Cons:   The potential downside of this is that I really don’t want them to be able to turn off  “Wake for Ethernet network access” (ARD use) but I’m hoping most won’t mess with this setting.

Print & Scan: I want laptop users to be able to add a home inkjet / laser printer. Cons:  I don’t really want them deleting or adding other printers at work so I’m not actually going to unlock this preference pane in this example.  But you may want to in your environment.  I will do it by adding the user to the lpadmin group instead.  Adding a user to the lpadmin group allows them to install or remove printers it doesn’t however unlock the Print & Scan System Preference pane but it does allow them to use the less obvious + and – buttons in that pane to make changes.  They can also use the File > Print > Printer > Add New Printer… option to add a home printer.

Network: I want laptop users to be able to adjust network settings as they travel.  Often at conferences, home or other sites, custom network settings or proxy settings are required.  Opening this up lets them adjust them as needed. Cons: Users can break their network settings which may yield a support request.

Date & Time: I want laptop users to be able to change the time zone if the ‘automatic’ feature fails.  Also if the PRAM battery fails I want users to be able to set the correct date and time. Cons:  Users can be on the wrong time zone / time which will effect things like AD based login’s.

Time Machine: I want laptop users to be able to setup a USB drive or Time Capsule at home as they’re backup device.

Not mentioned above: Software Update:  I plan to enable Software Update once I get my own Software Update Server running using Reposado.  This way I can enable standard users to update their own Mac’s via the built-in Apple system but control what updates are available via reposado.  You can also do this via Munki or this app at instead.

In my environment I’ve decided for now that I only want to open the above extra Preference Panes up for laptop users.  Desktop users I can help over the phone easily, change things remotely via ARD or go visit them.  Laptop users who are overseas or not on-site are the main concern as I can’t help them easily nor allowed to give them admin credentials.

In my environment for 10.7.x we are currently using the Apple Active Directory plug-in and Mobile User Accounts with local homes.  We add laptop users to the lpadmin group so they can install printers at home.  I do this via Apple Remote Desktop (ARD) using the Send Unix Command option:  dseditgroup -o edit -a USERNAME -t user _lpadmin if doing it locally via the command line as an admin use sudo dseditgroup -o edit -a USERNAME -t user _lpadmin  To verify the user has been added use dscl . -read /Groups/lpadmin at the command line.  Looking at the “Group Membership” field.

I am going to leverage this as it distinguishes between desktop and laptop users in our environment to achieve the outcome above. You could also create a new group and use that or use another built-in group.  Be aware that creating your own group means that you’d also need to add admin accounts to that group or the admin group itself.  By default all local admin accounts are members of the lpadmin group.  You could also use the staff or everyone group to open it wider.

So from the info in my earlier post we’re going to change the following keys in the /etc/authorization file from group admin to lpadmin using TextWrangler:


changing the bottom part of each entry above from



Note: TextWrangler will change the files owner and group, you can easily set it back via chown & chmod or just run Disk Utility – Repair Permissions which will set it back to root and wheel.

To make this even easier and ARD compatible I’ve adjusted a script from here which can be sent out via ARD to a Machine to change it immediately.  If a future apple update changes the file back to it’s original state it’s easily changed back.

#Copy the authorization file to a temporary location & make it a plist
/bin/cp -pr /etc/authorization /private/tmp/authorization.plist
# Unlock System Preferences for lpadmin group members.
/usr/libexec/PlistBuddy -c ‘Set :rights:system.preferences:group lpadmin’ /private/tmp/authorization.plist
# Unlock the Network Settings preference pane
/usr/libexec/PlistBuddy -c ‘Set lpadmin’ /private/tmp/authorization.plist
# Unlock the Time Machine preference pane
/usr/libexec/PlistBuddy -c ‘Set :rights:system.preferences.timemachine:group lpadmin’ /private/tmp/authorization.plist
# Unlock the Energy saver preference pane
/usr/libexec/PlistBuddy -c ‘Set :rights:system.preferences.energysaver:group lpadmin’ /private/tmp/authorization.plist
# Unlock the Date and Time preference pane
/usr/libexec/PlistBuddy -c ‘Set :rights:system.preferences.datetime:group lpadmin’ /private/tmp/authorization.plist
# Move file back to original location
/bin/mv /private/tmp/authorization.plist /etc/authorization

You can just copy and paste the text above into the “Send Unix Command” text area in ARD and send it as a local admin or root.  Alternatively copy the text into TextWrangler, do a save as i.e. then go to the command line and make it executable via chmod +x then run it with sudo ./ or sudo sh

This is what you’ll see when trying to unlock a pane as a standard user that you haven’t added to the lpadmin group.
Print Admin Prompt

And this is what you’ll see once you’ve added a standard user to the lpadmin group (or when logged in as an admin)

There’s other ways to achieve the same result.  You can change the key’s above from class “user” to “rule” keys and make your own rule at the bottom of the authorization file or use a built-in one but it’s much more complex & not well documented by Apple.

Mac OS X 10.7 / Lion – First look at /etc/authorization usage

The /etc/authorization file in Mac OS X / 10.x can be used to control access to the various panes of the System Preferences amongst other things. It’s used by some of us Mac Sys Admin’s to give Standard Users access to System Prefs panes that only admins could otherwise unlock.  It can also be used in the reverse to lock down panes you don’t want users messing with. An example by Apple was Allowing non-admin users to change the time zone setting – (Note this still works under Lion, tested on 10.7.4). Often the panes can’t be controlled to the exact level you may want via MCX (Local or Managed) or defaults write / plists.  Nor do you want to give users admin rights in a large business / university.

With 10.6 and now 10.7 the following Preference Panes are locked by default.  Meaning you need an admin username and password to unlock them: Security & Privacy, Energy Saver, Print & Scan, Network, Sharing, Users & Groups, Parental Controls, Date & Time, Software Update, Time Machine and Startup Disk.  As a ‘Standard User’ you can’t unlock these panes.


In 10.6 we could do the following to the /etc/authorization file, to give a standard user semi-admin access to the Preference Panes.

 <string>Checked by the Admin framework when making changes to certain System Preferences.</string>
   <string>everyone</string>  * Changing this from 'admin', to another local group. i.e. staff, everyone, or a custom group you created yourself.

This unlocks the majority of the preference panes above, the downside being you probably don’t want them all unlocked. (i.e Startup Disk) For some this was acceptable and used.  Some of us however just wanted a few unlocked, i.e. Date & Time for laptop users who travel a lot. Time Machine, so staff could connect to a Time Capsule or USB Hard Drive at home.  Energy Saver so they could adjust the settings to their liking. etc…

With 10.7 / Lion the /etc/authorization has undergone some changes and has much more granular control available in it. Making locking or unlocking individual Preference Panes possible!  (Yes TimeMachine)

Before you start make a copy of the authorization file.  If you make a wrong edit your machine will get stuck and the spinning cog on boot.  You can restore from your backup by booting into Single User mode (Command + S on boot) & trashing the messed file and renaming your backup. You can also edit the file from this mode, use ‘sudo mount -auw’ then, cd etc, ‘sudo pico authorization’ at the command line.  Find the bit you messed up fix it and save and reboot.

So open up the /etc/authorization file (Finder, Go to Folder, /etc), I’d recommend using TextWrangler to edit it.  In general you are going to be searching for a <key> key-name </key> and then editing the very end section of the key / dict entry. From this, to this:

	<string>__APPNAME__ 正在嘗試解鎖“安全性與隱私”偏好設定。</string>
<string>admin</string>  ** Change admin to another local group that your user is in.
i.e. staff, everyone etc...

* Standard Users when created are automatically put into the “staff” group. “Admin” users are in the “staff” and “admin” groups

Save the file.   Update: You don’t actually need to reboot your Mac.  Sys Prefs re-reads from the file at the time of credential checking.


To unlock the Systems Preferences in General so all changes below will actually work you first need to edit this top level key.  <key>system.preferences</key>   adjust it as above changing it to a local group, i.e. staff or everyone.  Save & Close.


I certainly don’t recommend unlocking all the Prefs panes, as it may give users more access than you want or have unintended side effects.  But I will document them all incase needed.

To Unlock the Security & Privacy Pane – search for the following key  <key></key> & adjust it as above,  save & reboot.  This alone will unlock the pane, but you still won’t be able to get into it. Try logging in as a Standard user & unlocking it, it will work the first time but you’ll be prompted again at which point it won’t accept your password.  This is because it’s actually trying to unlock the FileVault tab, if you cancel out of the 2nd credential prompt and go back in you’ll get this slightly different prompt 2nd time round.

First time round it was ‘is trying to unlock Sharing preferences’, 2nd time its ‘modify an encrypted disk’.  So go back to the etc/authorization file and search for this <key></key> 

		<string>__APPNAME__ is trying to modify an encrypted disk.</string>
	<string>admin</string> *Change this to another local group: staff, everyone

save and reboot.  Login as your standard user, you can now get into the Security & Privacy pane.

Energy Saver – Unlockable by editing – <key>system.preferences.energysaver</key> (as above)
Print & Scan – Unlockable by editing – <key>system.preferences.printing</key> note this unlocks the pane but you need to be in the lpadmin group to add a printer.
Network – Unlockable by editing – <key></key>
Sharing – Unlockable by editing – <key>system.preferences.sharing</key> this alone won’t unlock sharing as the “File Sharing” component is still blocking your access You need to adjust <key>system.sharepoints.</key> as well.

Users & Groups – Unlockable by editing -> <key>system.preferences.accounts</key> again this alone won’t unlock the Pane, you will be prompted for credentials twice, it will fail on attempt two. you need to adjust <key></key> as well.  This key is slightly different and uses a rule key, rather than a group key. edit it as follows to allow the current ‘session user’ access.

        *Change it to authenticate-session-owner-or-admin

Parental Controls – Unlockable by editing <key>system.preferences.parental-controls</key>
Date & Time – Unlockable by editing <key>system.preferences.datetime</key> &  you can manually add in <key>system.preferences.dateandtime.changetimezone</key>  as per this old article – (Tested it under 10.7.4)
Software Update – Unlockable by editing <key>system.preferences.softwareupdate</key>
Time Machine – Unlockable by editing <key>system.preferences.timemachine</key>
Startup Disk – Unlockable by editing <key>system.preferences.startupdisk</key> 

and then there’s some new Keys of interest in Lion


That’s my wrap up of the authorization file in Lion.  Happy to try and answer any queries.

Mac OS X Related Notes of a Mac Sys Admin

Hi All

Often I investigate things, try to solve a problem and never remember the finer details.  From now on I’m going to post them here for myself and everyone else.  Hopefully some of the info will be useful to others.