ADSM-L

Re: Client install id

2005-09-09 16:46:29
Subject: Re: Client install id
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 9 Sep 2005 16:46:03 -0400
If you look in the TSM client manual, it lists what rights you need to
do the install.
(Pretty much, you need the ability to update the registry, create &
start/stop services.)
In most shops, All the accounts you mention will have the rights to do
that.

The ID you INSTALL WITH, however, is not the id the TSM client RUNS
under.

When you CONFIGURE the Scheduler, Journal, and Web services with the
Setup Wizard, you are installing standard Windows services.  By default
they run under the SYSTEM account, whose password never expires.  You
have the opportunity to change the account during the setup, and you can
always access the service PROPERTIES later and change the account.  But
usually "system" is appropriate.  

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)


  

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Larry Peifer
Sent: Friday, September 09, 2005 4:35 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Client install id


We're installing 90 TSM 5.3 clients on a mix of W2K and W2K3 servers.
These are all new - 1st time installs.  Several are domain controllers
and
several are clustered for failover.    Looks to me like we have several
choices for ID's to use for installs: Local Administrator ID, Domain
Administrator ID, and members of the Administrator group.  We run
Journal,
Schedule, and Web services.  All passwords for all IDs mentioned above
get
changed every 90 days per Corporate IT Security mandate.  What pros /
cons
are there for using a particular ID to install with?

<Prev in Thread] Current Thread [Next in Thread>
  • Re: Client install id, Prather, Wanda <=