It's a long story, but the registry appears to be hosed to the point the
client can't store the password, among other things.

This in Win2k Professional.

The customer here uses NetDeploy to distribute applications, and decided
that wanted the TSM application installed somewhere other than the default
location....

Uninstalling and reinstalling consistently hairballs on W2K.

I have had this happen before and was able to clean all references to
ADSM/Tivoli from the registry an eventually got a new client installed.

It isn't working this time.

I'm apparently missing some key in the registry that needs to be removed.

-----Original Message-----
From: Rob Schroeder [mailto:robs AT FAMOUSFOOTWEAR DOT COM]
Sent: Tuesday, August 13, 2002 12:34 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: windows client


Is this from doing a restore or a save?

Rob



                      "Jolliff, Dale"
                      <xjolliff AT TI DOT COM>        To:
ADSM-L AT VM.MARIST DOT EDU
                      Sent by: "ADSM:          cc:
                      Dist Stor                Subject:  windows client
                      Manager"
                      <[email protected]
                      .EDU>


                      08/13/2002 12:21
                      PM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






Anybody know how to cure this?


08/13/2002 12:15:36 psDeletePasswordFile(): RegOpenPathEx(): Win32 RC=2 .
08/13/2002 12:15:39 WritePswdToRegistry(): RegCreatePathEx(): Win32 RC=87 .
08/13/2002 12:15:40 fioGetAttrib(): getFileSecurityInfo(\\adsm2000\c$\)
failed
08/13/2002 12:15:42 ANS1449E A required NT privilege is not held