Here's a slightly different question.

On an NT 4.0 machine,
We just installed the V3 win32 client at PTF 1 on TOP of the V2 client
at 2.1.0.6.

We stopped the scheduler service before installing, but did NOT remove
it.

The V3 client installed cleanly, and the OLD scheduler service was still
there.
We started the service, and it cranked up and ran the V3 backup as you
would expect.

The question:  Is this OK?  Is there any reason to remove and re-install
the service?


===============================================================
Wanda Prather
Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think."
              - Scott Adams/Dilbert
===============================================================




> ----------
> From:         Cindy Cannam[SMTP:CCannam AT genam DOT com]
> Sent:         Friday, February 13, 1998 10:51 AM
> To:   ADSM-L AT vm.marist DOT edu
> Subject:      Re: NT scheduler install in V3R1
>
> I, too, agree with you on the latest NT scheduler service! I
> downloaded the
> latest single-byte executables for v3r1.1 (to make certain I received
> the
> newest fix, etc.), but had a terrible time trying to get the DSMCUTIL
> to
> bring up the scheduler. I fortunately had NOT deleted my v3r.1 files
> (just
> renamed them and placed them in a different directory), but even when
> I
> tried to fall back to the old scheduler (which probably won't work
> with the
> newest version anyway), I was unable to get the machine to start a
> schedule
> automatically. And, on top of all that, the activity log in the new
> version
> kept giving me an error code I couldn't locate in any of the
> documentation:
> ANS8500I (an invalid parameter called ORIGINATOR was causing a problem
> for
> the log in some fashion, but gave me no hints about its location or
> how to
> repair it). It was a frustrating afternoon! I'll be interested to see
> what
> answers we receive!
>
> C.L.Cannam
> Storage Management
> GENAM/St. Louis, MO/USA
>
>
>
>
> David Killingsworth <david_w_killingsworth AT AMOCO DOT COM> on 02/12/98
> 06:38:38
> PM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:    (bcc: Cindy Cannam)
> Subject:  NT scheduler install in V3R1
>
>
>
>
>      I have about 25 installs of V2.1.06 client in place and have had
> them
>      in place for over a year.  Originally they were OS/2, but I
> slowly
>      migrated them to NT.  I thought it was great to be able to run
> ADSM
>      Scheduler as a service.  The service was pretty easy to install.
>      I just upgraded one of my machines from V2.1.06 to V3.1.1.  I
>      completely uninstalled the old version of the backup/archive
> client.
>      After I did the new install, I couldn't figure out how to install
> the
>      scheduler service.  Why was the neat little menu option taken
> away.
>      Secondly, why did they take away the easy to use executible.
>      I had to fumble around trying to get the right parameters before
> I
>      could install the service even with the scarce help using the
> dsmcutil
>      executible.  When I finally did get it installed I did not
> understand
>      that the service name I was giving would be what it would
> actually be
>      called.  I thought it was asking for the service executible.
>      Consequently, my first attempt at installing the service ended up
>      being dsmcsvc in my services panel.  Removing it was just as
>      difficult.
>      WHY?????  That is my question.  Why make it harder than in a
> previous
>      release.
>