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 and issue.
– When “DHCP” is set to “Active” and “DNS Method” is set to “Auto-Obtain (DHCP)”, an extra character is added in the domain name.
– 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
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
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
Exception: EXC_CRASH (SIGABRT)
Date/Time: 2016-10-07 03:12:21 +0000
Application Name: Microsoft Office Setup Assistant
Application Bundle ID: com.microsoft.office.setupassistant
Application Signature: MsLi
Application Version: 184.108.40.206509
Crashed Module Name: merp
Crashed Module Version: 220.127.116.11509
Crashed Module Offset: 0x00004422
Blame Module Name: PowerPlantCore
Blame Module Version: 18.104.22.168509
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.
Adobe Flash Player 11.3 for Mac has a new “Silent Update” feature, detailed here: http://blogs.adobe.com/asset/2012/06/flash-player-11-3-delivers-additional-security-capabilities-for-mac-and-firefox-users.html
“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)
PKG – https://docs.google.com/open?id=0ByZBlcehUDfOZFNyOU1wR1ZWN3c (use the File Menu > Download)
& here’s a PKG todo the opposite – AutoUpdateDisable = 1 & SilentAutoUpdateEnable = 0
PKG – https://docs.google.com/open?id=0ByZBlcehUDfORFQ1eWdpMnp4Rzg (use the File Menu > Download)
Checkout Greg’s package here for a Package that disables updates – http://managingosx.wordpress.com/2011/05/13/disabling-auto-update-notifications-for-flash-player-10-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.
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.
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 – http://support.apple.com/kb/TA23576 (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.
<key>system.preferences</key> <dict> <key>allow-root</key> <true/> <key>class</key> <string>user</string> <key>comment</key> <string>Checked by the Admin framework when making changes to certain System Preferences.</string> <key>group</key> <string>everyone</string> * Changing this from 'admin', to another local group. i.e. staff, everyone, or a custom group you created yourself. <key>shared</key> <true/> </dict>
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> </dict> <key>group</key> <string>admin</string> ** Change admin to another local group that your user is in. i.e. staff, everyone etc... <key>shared</key> <false/>
* 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>system.preferences.security</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>com.apple.DiskManagement.reserveKEK</key>
<dict> <key>en</key> <string>__APPNAME__ is trying to modify an encrypted disk.</string> </dict> <key>group</key> <string>admin</string> *Change this to another local group: staff, everyone <key>shared</key>
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>system.preferences.network</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>system.services.directory.configure</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.
</dict> <key>rule</key> <string>root-or-admin-or-authenticate-admin</string> *Change it to authenticate-session-owner-or-admin </dict>
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 – http://support.apple.com/kb/TA23576 (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.