I've found that reboots in order to proceed with the install have been necessary on
around 1/3 to 1/2 of the NT boxes I've done. It's definitely related to the Installer,
possibly whether it's been used before or not.
Just curious, why the push to upgrade, other than support (and that d**n DST b
I think the best bet is to plan for reboot on ALL these systems.
One of my methods on these systems BTW is to totally delete old version(s) and then
install new versions, saving dsm.opt of course. I find that in many cases there may
be two *SM versions on system and some other misc stuff, so t
not
required.
-Original Message-
From: Thomas Denier [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 31, 2001 8:26 AM
To: [EMAIL PROTECTED]
Subject: Reboot during NT client upgrade
My site is about to upgrade its Windows NT client systems to 4.1.2.12.
We are starting with the ones that
My site is about to upgrade its Windows NT client systems to 4.1.2.12.
We are starting with the ones that currently have 3.1.0.6 client code,
and will subsequently upgrade the ones with various service levels of
the 3.7 code. We currently have to plan every upgrade to allow for the
possibility of
