We've had few problems with the V3 scheduler once we got the hang of
installing it correctly. Make certain you shut down the current scheduler
service prior to the V3 upgrade, and place it in manual mode. Then do your
upgrade. When the new code is in place, use the DSMCUTIL utility to
de-install your current service -- after a few botched installs and some
trial and error, this appears to be the best method for cleaning up any old
V2 stuff (especially on some of the larger and more picky IBM
client/servers). Reboot. This is the final scrubbing. Install the new
service using the DSMCUTIL utility. Start the new service. Check your usual
logs. Make certain your individual drive permissions match to ensure proper
backup (bumped into this one recently, and am in the process of correcting
the problems that consequently arose). You're on the way.

I tried to hang onto the V2 format scheduler installer for a while, but it
became more of a pain than a help as more upgrades were made available (I
think the presence of the required DLL was the culprit but couldn't prove
it definitively).

Hope this helps.

C.L.Cannam
Storage Management/ADSM
GENAM/St. Louis, MO/USA
ccannam AT genam DOT com





Julie Phinney <jphinney AT HUMANA DOT COM> on 11/09/98 05:03:35 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/GENAM)
Subject:  Win NT client upgrade




When upgrading a V2 Win NT client to V3, what's the recommended thing to do
with the Scheduler service?
For instance
 - Leave it installed as is, leave the  V2 gui facility in place for future
updates
Delete the entire old ADSM folder with the old gui, remove the existing
service with DSMCUTIL, then re-add it
How are you all doing it?
Any of you that have had successful upgrades of V2 to V3, I'd like to know
the basic plan.  We've had so many troubles with the new scheduler service.
Thanks for any advice,
Julie
JPHINNEY AT HUMANA DOT COM