Posted on 08-12-2010 12:53 AM
When I login to Self Service...which the login does work.....I see that there are no Self Service items....I'm logging in from a computer that is managed by JSS and as a member of the Teacher group that is defined.
[Image:Screen shot 2010-08-12 at 2.50.20 PM.png]
[Image:Screen shot 2010-08-12 at 2.50.27 PM.png]
[Image:Screen shot 2010-08-12 at 2.50.37 PM.png]
[Image:Screen shot 2010-08-12 at 2.51.06 PM.png]
![external image link](attachments/2b81f1dbc16a4a65a842d6ba93fdff11)
![external image link](attachments/9cea94420bcb4da9b6fa61898b79819f)
![external image link](attachments/285030eece3a4adc9785e9bbe70963cd)
![external image link](attachments/20a7d0469f494e03959666b6509819e5)
Posted on 08-12-2010 02:02 PM
Does that user group contain other groups within it? You can't use nested groups I believe, the group you specify must contain the actual user accounts within it. This is an LDAP thing I think, and it's sometimes frustrating.
You also did not show your Network Limitations, but I assume there are none there.
One the client box do a 'sudo jamf manage' in the terminal before launching Self Service.
Also check binary versions just to be safe 'jamf version'
Not sure beyond that. The setup looks correct.
Craig E
Posted on 08-12-2010 02:06 PM
I agree with Craig on pointing a finger at LDAP…
Could you try removing the user group limitation and just add that user’s individual computer to the policy for a test?
I haven’t had much luck with LDAP in general, let alone in conjunction with Casper.
Bob
Posted on 08-13-2010 04:43 AM
Try removing the list of authorized users (make it available to everyone) and see if that fixes it. I had a self service package that was only for high school teachers and admins, but when a high school teacher logged in it wasn’t available. If it shows up then, you know where your problem is. Of course, fixing it will be another matter :-)