Just a quick reminder about resolving the super-annoying keychain issue on a user’s profile since it has come up a couple of times recently. This is the one where attempting to launch almost any application on OS X (all versions) generates a whole slew of popups asking them to unlock the Local Items keychain. It’s possible to just cancel through all of the windows and you’ll eventually get to whatever app you were trying to open, but it gets really old, really quickly.

You can find Apple’s official page documenting the fix here.

Alternatively, Mr. Dowd has converted it into a Word doc and put it up on sharepoint here.

Yes, I know the fix pages reference OS X Mavericks specifically, but the problem and fix really is the same across multiple versions of OS X.

TL:DR version

The InCopy fix you’ve all been waiting for is here, and as I write this has been deployed to forty of about seventy three machines currently identified as having InCopy CC on them.

The “Jaymz likes to send way too much information in his emails” version

The fix for InCopy errors and crashes on the Macs is finally found and deployed. When I say the errors and crashing, I am referring to the set of circumstances documented in the following ticket:

[ Zoom Ticket#: 0330854 ] Adobe CC reinstallation

The long and short of it is, the policy is scoped to a smart group that identifies any machine that has the Adobe InCopy CC 2014.app installed. When identified, a script will be deployed that fixes permissions on the InCopy plugins folder and then clears the InCopy cache folder (it’s basically identical to the fix that I am pushing for the InDesign plugin errors that we ran into last December).

If you wish to see if an affected machine has had the script run against it:

• Log into the JSS
• Click on Computers
• Click on Policies on the sidebar
• Find the policy entitled “CN – Fix InCopy CC 2014 Plug-in Errors”
  • It should be near the top in the category “CN-Application Fixes”
• Click on the name of the policy
• Click on the Logs button
• In the screen that comes up, find the machine and you will see its status
  • If status is “Failed”, we need to flush the logs for that machine
  • “Pending” means the machine has not run the policy yet
  • “Completed” means that the policy has run successfully and the fix has been deployed

Now, this is the really important part:

Casper will not immediately identify a machine after InCopy or the entire CC suite is installed. Recon (inventory collection procedure) needs to be run against the machine in question before the InCopy will appear as an installed app. Recon runs on a once every twenty four hours, or the next time the machine checks in after that twenty four hours is up, so your customer may run into the error messages if they try to launch InCopy immediately after installation. If this is the case, you can manually run recon on the machine, and then check to make sure that the machine is in the appropriate smart group.

To run recon launch terminal as an Admin level user and type “sudo jamf recon” minus the quotes. This will force the machine to check in and run Recon.

To check to make sure that the machine is actually in the necessary smart group:

• Log into the JSS
• Click on Computers
• Click on Smart Groups on the sidebar
• Find the smart group named “CN – Applications – InCopy CC 2014 installed”
• Click on the View Button
• In the screen that comes up you will see all of the machines that fall into that smart group
  • As long as the machine is in this group, the policy that fixes InCopy is scoped to it

As of Monday, Community Network has quietly lifted the restriction on CN machines being able to install Mac OS X Yosemite. As machines run their daily inventory check the restriction will be lifted on the machine.

We have not made an announcement to the customer base yet as this is not a consensus decision. The topic of publicly announcing the lift on the Yosemite restriction will be brought up at the next ops meeting, at which time anybody can raise an objection to formally announcing to the customer base that it is okay to install Yosemite.

Once we announce that the restriction has been lifted we will also make the Yosemite installation available in Casper Self Service.

The OS X Yosemite Tech Tip page has been updated with the latest information on why CN is blocking installation of Yosemite. Please refer customers to the information on this page if asked about Yosemite installations.

http://is.oregonstate.edu/client-services/cn/tech-tips-using-cn/os-x-yosemite#