Thank you very much for the ideas on how to tackle this. Group admins would
work best in our environment.
On 1/15/04 1:54 PM, "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU> wrote:
> The userid is not part of the client definition. (If you don't believe me,
> try: q node xxxxxxx, f=d).
> When you specify a userid during registration, in addition to registering
> the node, it creates an admin id.
>
> So for node 123456, which already exists:
>
> register admin 123456 password
> grant authority 123456 authority=owner node=123456
>
> But you probably don't want to really do that.
>
> Who is doing the web based backup?
> If it is a PERSON who is going to be driving the backup for , say, server8
> and server9 and server10,
>
> it's easier to register that PERSON as admin, and grant access authority to
> server8, server9, and server10.
> Then that person uses 1 id to do web backups & restores.
>
> Hope that helps...
>
> -----Original Message-----
> From: Renee Davis [mailto:rdavis AT UH DOT EDU]
> Sent: Thursday, January 15, 2004 2:17 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: No Userids for Web Client
>
>
> In registering over 600 nodes for TSM, we registered them with
> "userid=none". Years later, we now wish to implement the web based backup
> strategy, but that requires that each node have a userid. Is there anyway
> to update the existing nodes with userids? The "update node" command does
> not have that option.
>
> Renee Davis
> University of Houston
|