Sure. You could have a path to request Systems to bounce schedulers/server,
i.e. service request tickets or whatever, or they can give Operations
appropriate permissions for day-to-day operations.
UNIX: Systems could give Operations read/write access to the TSM client
directory and put together a script/app that runs as root and can be used to
kill the scheduler and restart it.
NT: Systems could give Operations read/write access to the TSM client
directory and Start/Stop Services policy privileges.
Server: read/write permission to the server directory, script that runs as
root to kill server. I think you can start the server under any ID you like
and it'll still work. If not, they can provide a script to start the server
under root.
I can't think of anything else off the top of my head, but if there is
something else, it should be pretty easy to address.
Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail
-----Original Message-----
From: Maria Ragan [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 19, 2001 1:58 PM
To: [EMAIL PROTECTED]
Subject: Root/Amin Privilege
My management has directed the move of the TSM Administrator function to our
Operations department. We have a unix TSM server with a mixture of unix and
NT clients. Software installation/planning would still be done on the
Systems side of the house, but everything else would be handled in
Operations. Do you know if this hand-off is possible without providing
root/admin provileges on each client and the server to Ops?
Thanks,
Maria
