Posted on 01-18-2018 01:14 PM
Hey Team!
In the latest Jamf, opening Self Service changes its stock icon to whatever Branding graphic you define. What I'm looking to do is change the stock icon to match our branding image. I've done the following but currently stuck!
-Created an icns image of the branding image
-Command-I the Self Service.app and replace the Jamf image as well as replace the AppIcon.icns file in Show package contents>Contents>Resources
-Took the new Self Service.app, packaged it up, deployed it, and on end user's computer nothing changed. Show package contents shows the new icns file so it does go through but I feel like its a cache issue at this point?
-Clearing /Library/caches/icon caches didn't do the trick nor rebooting.
Thoughts?
Thanks!
Solved! Go to Solution.
Posted on 01-19-2018 06:19 AM
This is a known issue with self service. If you change the permissions on self service using a policy, it should remedy itself:
chmod 775 /Applications/Self Service.app
Posted on 01-18-2018 03:09 PM
@imZack Have you uploaded the .png to the Jamf Pro server? Settings > Computer Management > Self Service > Branding.
Posted on 01-18-2018 04:01 PM
Yeah, it sounds like you're trying to make it more difficult than needed.
Do as @avasani stated above.
When users download the QA package, it will install the Self Service app with the correct graphics.
Subsequent changes on the website will be reflected in Self Service automatically...
The old days where we needed the Goddess @Emily to show us how are now gone - RIP.
Posted on 01-18-2018 09:28 PM
Not to hijack this thread but I think OP may be trying to explain an issue we too are having where our icon branding only shows when the application is opened. Once it’s closed the dock icon reverts back to the stock Self Service icon until opened again it gets its custom branding back. Is this normal behavior?
Posted on 01-19-2018 05:37 AM
@bergmire That is not normal behavior. I think I understand your problem. With Self Service either opened or closed the icon remains. I have posted screenshots of what I see. Can you do the same?
Posted on 01-19-2018 06:10 AM
@bergmire Yes thank you! That is the issue we are having. Our branding shows up when the app is opened but reverts to stock when it is closed. For some reason as everything was brand new I had thought it was maybe normal behavior.
Re-enrolling machines doesn't seem to fix it either, very odd.
@avasani I/we cannot do that as you pictured.
Thanks!
~Zack
Posted on 01-19-2018 06:19 AM
This is a known issue with self service. If you change the permissions on self service using a policy, it should remedy itself:
chmod 775 /Applications/Self Service.app
Posted on 01-19-2018 08:22 AM
@jmahlman this solution has solved the issue for now, thank you!
Posted on 01-19-2018 08:40 AM
No problemo. Just mark it as the answer ;)
Posted on 01-19-2018 09:03 AM
@jmahlman You the man! Fixed it here too :)
Posted on 01-19-2018 10:01 AM
Interesting. What version are you running? We're on 10.1.1 and don't see this issue?
Posted on 01-23-2018 12:18 PM
@scottb 10.0.0-t1508873342 so hopefully it's fixed in the latest version.
Posted on 01-23-2018 08:25 PM
Hmm...just updated to 10.13.3 and this issue seems to have returned. Sadly @jmahlman solution doesn't seem to correct it.
Posted on 01-24-2018 05:18 PM
@jmahlman Also worked for me... Guess this means that I'll need to push the updated permissions to all clients?
Posted on 01-25-2018 07:05 AM
@bergmire My guess is that jamf is (hopefully) going to fix this with 10.2 (I haven't started testing 10.2 yet)
Posted on 03-01-2018 03:49 PM
Just installed 10.2.1 and had the same issue. Permissions fix did not do the trick. I noticed that the owner and group of the Self Service.app on two different systems running 10.12 were assigned to different local admins (this is odd because only one of these admins should have enrolled the system). After setting the owner to root and the group to wheel with 755 permissions the problem seems to be corrected. My 10.13 test system works fine without the change.
edit: Changed owner and group back and the issue is still resolved. ???
Posted on 03-07-2018 10:12 AM
Can confirm the same behavior @aprild After getting a little time to further test this it seems proper ownership needs to be set on the Application. Permissions at least in my case did not change the icon behavior.
chown root:wheel /Applications/Self Service.app
did the trick.
edit: this only worked on our test machine, nothing in our production environment. I'm just going to wait for 10.2 and hope for a fix there at this point...
Posted on 03-23-2018 11:14 AM
We have this issue on several production machines since upgrading to 10.2.2. Seems when updating the Self Service the permissions went wonky. It does not affect newly added systems.
Posted on 03-27-2018 08:00 AM
Posted today with 10.3.0:
[PI-004881] Fixed an issue that caused the Self Service Branding Icon to incorrectly revert to the default icon when the application was closed.
Posted on 03-30-2018 09:22 AM
We upgraded to 10.3 and Self Service stays branded in the Application folder but the Dock icon reverts back to the generic log when the app is closed. Anyone else seeing this?
Posted on 03-30-2018 09:37 AM
Oddly enough, I only see what @emily sees after the first launch of the Application. After all subsequent launches it's fine.
Posted on 04-24-2018 11:52 AM
Is this still an issue, or did they fix it with their 10.3.1 maintenance release?
Posted on 04-26-2018 10:47 AM
I'm not seeing it on 10.3.1, but I didn't always see it.
One JSS has the fix in a policy, so that one is still working OK too.
I have heard of SS crashes in 10.3.1 but I have not seen those yet either.
Posted on 10-25-2018 09:04 AM
Just to chime in, we are on 10.7.1 and I'm still having the issue mentioned above. Changes when its open, but when its closed it shows the JAMF icon in the dock.
Posted on 10-26-2018 09:59 AM
@danshaw - curious - I saw that on one Mac and it was seemingly due to the MDM Profile not being "Approved". At least once we had the client do it, that went away.
Otherwise, been pretty stable on 10.7.1/10.8.
Posted on 11-13-2018 04:15 PM
Well, not totally shocked, but onboarding some UAT clients today resulted in the generic icon business.
10.8 and macOS 10.13.x.
Might have to re-enable that old policy again...