[LMStone]

Originally Posted by Rich Graves

If you want to override LoginBanner.png and AppBanner.png for *all* users on the system, replace them in /opt/zimbra/jetty/webapps/zimbra/skins/_base/ and disable the more experimental skins: lemongrass, waves, hotrod.

Hi Rich,

Thanks for the reply.

We do indeed want a majority of users to get our custom logo (same as our signature here) regardless of the skin they are using.

But, for a group of users in one COS, we want them to have an entirely different set of logos.

Under 4.5, we got them to see their custom logo on the login screen by appending "?skin=tarnation" to the login URL, and then distributing that URL as a shortcut on their Desktops.

Under 5.0, that trick doesn't work anymore, so the users see the wrong logo until they log in.

The short-lived splash screen displays the correct logo for users in that COS, and once the ZCS UI fully paints the correct logo in the upper left is also displayed properly. But once they log out, the post-logout screen then again displays the "wrong" logo.

It's as if under ZCS 5 each of those four logo-displaying screens reloads the png files from the server afresh, whereas under 4.5, the png files I think were cached by the browser and rarely reloaded from the server--making for a more consistent logo experience under 4.5 than under 5.0.

I'll add myself and this use case to the bug report, but if you have any ideas in the interim, that would be appreciated (feel free to vote for the bug too!).

Perhaps there is a different way to accomplish what we want to do here?

Thanks!
Mark