ADSM-L

Re: win32 3.1.0.6 DEinstall issues [long]

1999-01-11 16:53:11
Subject: Re: win32 3.1.0.6 DEinstall issues [long]
From: Francois-Xavier Peretmere aka MD5 <fx AT 4JS DOT COM>
Date: Mon, 11 Jan 1999 21:53:11 +0000
> From: ALLEN BARTH <abarth AT KEMPER DOT COM>
> Date: Mon, 11 Jan 1999 13:57:52 -0600

> Since my last posting....
>
> I did a de-install of the ADSM client, and rebooted the machine....
>
> However, the following two services still appear:
> ADSM Client Acceptor
> ADSM Remote Client Agent
>
> Are there bugs in the de-install?  How do I get rid of these?

 i'm currently fighting with the win nt adsm client, and i can not
say i'm very successfull.

 first, to answer your question, when the services are not
uninstalled, you could use a programm like "service manager"
which can install / uninstall service and do lots of other
interesting things. i don't have the url right now, but i
can't check it, just send me a private email to remind me.
you can either use the service utilities (one gui and one
command line) which are in nt ressource kit - they can
either remove a service.

 second, i have three different nt wks sp3 with adsm client
3.1.0.6: one works, one works sometimes and on the last one,
the adsmsvc.exe crash when scheduled backup time comes.

 i did complet uninstall (uninstall + services deleted + deleted
all files + deleted everything adsm relevant in registry), rebooted,
reinstalled, reboot, dsmcutil install schedule, dsmcutil install
schedule configuration, reboot, configured dsm.opt: no way.
backups with gui works fine, but the services crashs.

 another problem i didn't encountered on the others computers,
'dsmcutil updatepw ...' or 'dsmcutil update /password...' fail:
  found registry key...
  an error occured...

  i tryed to trace the registry access by adsmcutil.exe but found
 nothing usefull.

 on the first computer, it used to crash, but complete uninstall
and full reinstall apparently made it work.

 i noticed during my many [un]installation that checking web
client install did not create the wsstuff directory. and on
some computers, the web client binaries are copied (mkpasswd.exe
& related), but sometimes not - perhaps when a previous adsm
client was already installed.

 last thing, i checked various manuels, but did not
found a clear explanation about the four services, what
exactly they are supposed to do. looking trough archives,
i found a mail stating that the acceptator must be the only
one with autostart, but our adsm consultant said she
configure always all services autostarted. and my test
led me to everything autostart except the "remote client".

 as usual, any explanations / advices / gifts are welcome.

  amicalement,
                        fx

---
---
---
Peretmere Francois-Xavier - paris, france, europe, earth... - fx AT 4js DOT com
Peretmere Francois-Xavier - paris, france, europe, earth... - fx AT 4js DOT com
 "never used to be so tired, never used to be so anxious    - #5165176
  never said 'used to be' so much"                       negation / live
<Prev in Thread] Current Thread [Next in Thread>
  • Re: win32 3.1.0.6 DEinstall issues [long], Francois-Xavier Peretmere aka MD5 <=