Hi Ken,
I have a customer who is implementing a small Sun Ray environment (10
units) for their help desk users. They’d like to be able to customize
a set of icons, toolbars, etc. for specific users, or specific groups
of users in the JDS environment. What is the simplest way to achieve
this? We’ve already been down the path of trying Sun Desktop Manager,
but have had little success in really understanding how to tie its
LDAP-based architecture to actual Solaris users on the Sun Ray server.
When using an LDAP server to provide the Desktop Manager with an
organisational structure, the link between the LDAP contents and the
Solaris user is made through the Solaris user id which has to match the
uid attribute of the user entry in the LDAP repository.
The goal is to be able to rapidly provision new help desk users with a
common desktop environment based on their group or user identity.
Again, the Sun Desktop Manager software seems to be ideal for this,
but we have had no luck in deploying it. We’ve gone through what
little documentation there is on it, and haven’t been able to get it
working. If there are any other walkthroughs/whitepapers that may be
of assistance in setting this up, I’d love to see them. Also, if there
is a simpler alternative to this than using Sun Desktop Manager, that
would also be nice to know.
The Sun Desktop Manager manuals can be found at:
http://docs.sun.com/app/docs/coll/1230.5
and there are two documents on BigAdmin which may also help you
understand better how it all ties together at:
http://www.sun.com/bigadmin/features/articles/sdtm_tutorial.html
and
http://www.sun.com/bigadmin/features/articles/desktop_mgmt.html
Please note that you don't have to use an LDAP server if you don't
already have one and/or don't want to install one, you can use a file
based repository with the Desktop Manager, provided the file location is
somehow visible from all your Sun Ray servers, this might be easier for
evaluating whether you want to continue in that direction.
An alternative to using the Desktop Manager is obviously to add some
session startup script (for instance in the Xsession.d directory) which
would, based on the user and group identifier, copy a few files to the
user's ~/Desktop directory (to create launchers), or make some calls to
gconftool-2 with premade import files to force certain values to be set
for the user (for settings depending on GConf).
Don't hesitate to ask if you need more information or if I've been
unclear, regards,
Cyrille
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
