Skip to main content
Question

Config Profile question - comp profiles not showing up

  • May 29, 2014
  • 7 replies
  • 70 views
C
Forum|alt.badge.img+17

I'm testing various config files in 9.31 (trying to migrate away from MCX).

All user and computer profiles work fine if I image a computer and then add the computer to a profile scope. The computer profiles show up immediately, and the user ones on next login.

If I leave a test computer in a config profile scope and reimage it, the computer profiles don't show back up when computer boots up, even if I reboot a few times. The computer is enrolled (I see MDM profile in system prefs - profiles). If I go to JSS under the computer - scoped profiles, I see my test profiles there scoped for that computer.

If I go back to config profiles in the JSS, click edit, save, distribute to all, then the profile shows up on the client machine.

What am I missing to get scoped profiles to show up post image?

    7 replies

    C
    Forum|alt.badge.img+17
    • CasperSally
    • Author
    • Honored Contributor
    • May 29, 2014

    I forgot to mention that user profiles come back down post reimage fine. Seems to just be the computer level preferences.

    R
    Forum|alt.badge.img+14
    • rlandgraf
    • Contributor
    • May 29, 2014

    What version of OS are you running on the Macs? We had a huge problem getting our profiles to show up on 10.9.2 but as soon as we went to 10.9.3 they all started working.

    K
    Forum|alt.badge.img+13
    • Kumarasinghe
    • Contributor
    • May 30, 2014

    I think it might be something to do with Smart Groups and re-enrolling machines.
    Are those Configuration Profiles scoped to Smart Groups?

    We are seeing this issue as well and really like to see a solution to this.

    J
    Forum|alt.badge.img+10
    • jhuhmann
    • Contributor
    • May 30, 2014

    I'm seeing this also, but intermittently on perhaps 1/20th of our machines. We only have problems one particular profile, wireless, scoped to a smart group. 9.31 and 10.9.3

    C
    Forum|alt.badge.img+17
    • CasperSally
    • Author
    • Honored Contributor
    • May 30, 2014

    I am seeing it on 10.9.3 in our test environment on any existing computer level profile I try to push to any computer (I haven't even gotten to putting test computers in smart groups). User level profiles come down fine every time. I agree it might be tied to some enrollment issue or something that JSS thinks the computer already has the profile.

    We use the computer level profile (login window text) as a quick visual indicator for technicians to know post image that a machine has its security settings. I can't see how we could migrate to config profiles without this working consistently (I'd even take 19/20 machines at this point, for us it's 0/20).

    On the same profiles, every time, if I go in to JSS and do edit and save they come right down.

    I have 3 weeks left to upgrade our production environment to 9.x (and adopt config profiles since custom MCX doesn't exist), or try to stick out 8.73 for the next school year. I really don't want to push off this upgrade another year...

    C
    Forum|alt.badge.img+17
    • CasperSally
    • Author
    • Honored Contributor
    • June 4, 2014

    quick update for us after some 9.32 testing - The issue doesn't happen if I delete the computer from JSS and reimage (comp level profiles scoped to smart groups come down ok). Beginning to think it's autorun related or some other computer level item stored in JSS that isn't updated in time before the computer profiles are pushed out on new enrollment?

    Saw this somewhat related prior thread that mentions "" Enrollment does appear to be a defect. For some unknown reason, we are not removing the old SCEP ID when the machine is re-imaged. So when we reboot, enroll again, the JSS is verifying the client to the old signature.""
    https://jamfnation.jamfsoftware.com/discussion.html?id=9506

    L
    Forum|alt.badge.img+4
    • lynnp
    • Contributor
    • September 30, 2014

    Is there an updated solution to this problem? Re-enrolling after imaging negates the functionality of autorun imaging. In a lab environment, having to re-add machines to the JSS after each imaging is a complete headache.

    Terms & ConditionsCookie settingsAccessibility statement