Skip to main content
Question

"Killer" Policy - has anyone experienced this?

  • August 22, 2011
  • 2 replies
  • 41 views
C
Forum|alt.badge.img+10

Hello,
I have a big question mark after a very simple policy messed up a few clients here.

Scenario: JSS 8.1 running from OSX Server 10.6.8, clients are 10.6.8

The policy just contains a simple pkg created with Composer to install Cyberduck at login.

![external image link](attachments/5a2fe1b109d24c42b2cc13aea4609f4a)

After the policy successfully run (according to JSS logs), I found several clients with rather scary symptoms:

network volumes without their icon (carrying a generic icon) "broken" iDVD, iPhoto apps (they are still within Application but their icon in the dock is a question mark) Fonts messed up, text in Finder messages is Courier, like system font were missing. General slowness

I ended up re-imaging those clients but would be very interested in understanding what happened.
I am sure it's that policy's fault, as everything came back to normal as soon as I stopped it.

Have you ever seen something like this?
Many thanks for your attention
Ciao
Carlo

    2 replies

    J
    Forum|alt.badge.img+5
    • Janowski
    • Contributor
    • August 22, 2011

    yikes - thats a lot of trouble for what appears to be an innocent policy :)

    I see your snapshot below. Was that literally the only thing in the package? And the package was the only thing you ran with the policy?

    Could it be possible that after your cyberduck policy, the machine recon'd which then triggered some other policy?

    ben janowski
    Senior Macintosh Support Technician
    Kohl's Mac Support Team
    262.703.1396 | benjamin.janowski at kohls.com

    ![external image link](attachments/f1d4052fc2bc4f1e9e9365f7d7a1f120)

    C
    Forum|alt.badge.img+10
    • carlo_anselmi
    • Author
    • Valued Contributor
    • August 22, 2011

    Hello Ben,
    Yes to first two question and no to the last one. Also, forgot to say the policy is not part of any imaging workflow.
    Tomorrow I'll try to run the pkg manually to see what happens… did not have the time yet, being too busy fixing the little mess! :-)

    --
    ![external image link](attachments/3e7463daa42f429e886e55357f498505)

    Da: "Benjamin.Janowski at Kohls.com<mailto:Benjamin.Janowski at Kohls.com>" <Benjamin.Janowski at Kohls.com<mailto:Benjamin.Janowski at Kohls.com>>
    Data: Mon, 22 Aug 2011 12:04:31 -0500
    A: "casper at list.jamfsoftware.com<mailto:casper at list.jamfsoftware.com>" <casper at list.jamfsoftware.com<mailto:casper at list.jamfsoftware.com>>
    Oggetto: Re: [Casper] "Killer" Policy - has anyone experienced this?

    yikes - thats a lot of trouble for what appears to be an innocent policy :)

    I see your snapshot below. Was that literally the only thing in the package? And the package was the only thingyou ran with the policy?

    Could it be possible that after your cyberduck policy, the machine recon'd which then triggered some other policy?
    ben janowski
    Senior Macintosh Support Technician

    Terms & ConditionsCookie settingsAccessibility statement