Re: Help with Win2K Client Password in Registry

Thanks Jack-

When I run dsmcutil showpw, it shows the correct password in the registry
for this machine.
Then when I reboot and run dsmcutil showpw again, it says it can't find the
registry key.

It appears that registry changes are not being saved.
I installed a new version of the client in a new directory, but after a
reboot, the registry entries still indicate the old version of the client is
installed and point to the old path name.

So we deleted some of those registry entries manually.
After a reboot, they come back!

So this appears to be a WIN2K thing, not a TSM thing.

Any of you Windows Wizards out there have some suggestions as to what causes
this?


> -----Original Message-----
> From: Jack Palmadesso [SMTP:Jack.Palmadesso AT SWPC.SIEMENS DOT COM]
> Sent: Thursday, December 14, 2000 7:29 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Help with Win2K Client Password in Registry
>
> "Prather, Wanda" wrote:
> >
> > Well, I'm stumped.
> > I've got a Win2K system running the Win32 client; was at 3.1.0.6, now at
> > 3.7.2.01.
> > It's been running fine for months, with PASSWORDACCESS GENERATE in
> dsm.opt.
> > THe scheduler service was backing up fine daily.
> >
> > Then we tried to change the password.
> >
> > Now when you start TSM (dsmc or dsmc sched or GUI), it prompts for the
> TSM
> > password.
> > When you give the password, it works fine.  You can shut down TSM (dsmc
> or
> > dsmc sched or GUI), and it doesn't prompt for the password if you start
> the
> > TSM client again.
> >
> > Until you reboot.
> > Then it doesn't know the password anymore.
> >
> > In dsmerror log I see this:
> > 12/04/2000 06:42:46 ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2
> >
> > Which just tells me it can't find the password in the registry, yes?
> >
> > I first upgraded the client from 3.1.0.6 to 3.7.2.01, and that didn't
> help.
> > So I uninstalled the 3.7.2.01 client and did a complete reinstall.  That
> > didn't help.
> >
> > I have no clue how to fix this one.
> > What makes a client not save its password across a boot?
>
> Try using the dsmcutil  program in the client directory.
>
> I believe the correct syntax is:
>
> dsmcutil showpw /node:nodename    This should show you what password is
> in the registry.
>
> dsmcutil updatepw /node:nodename /password:password   This should reset
> your password.
>
> Jack