(a) absolutely not - UNLESS you don't care about the results;  this is why a
certification or development (or LAB?) environment is necessary (and not
just for TSM - all apps.)
(b) absolutely yes - any deviation from this practice is like flying trapeze
without a net

1) yes, if you know what you're doing on the desired platform - some are
easier than others;
2) yes, for features we intend to exploit;  we're not as diligent about this
one, so it's real good practice to "stay in touch" with folks on the list,
and your vendor contacts, re. new features.

Our change management procedure requires that we be accountable and prepared
for test, install and back-out procedures to minimize negative impact on
production machines.  Doesn't yours?!?



 -----Original Message-----
From:   Richard L. Rhodes [mailto:rhodesr AT firstenergycorp DOT com]
Sent:   Friday, February 09, 2001 7:57 AM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        tsm upgrades and testing

Here is a real general question . . . . .

How do you handle tsm upgrade testing?

When a new release comes out do you:

a)  dump it on you server, upgrade and see if it works?
b)  create a test instance and try it out first?

Related questions:

1)  I know you can have multiple tsm instances running concurrently
on a server.  Can you have multiple tsm instances that are running
different tsm versions on the same server?

2)  Do you keep a test instance around so you can play with new
features without effecting your production system?


Thanks

Rick