Could you describe in greater detail how these systems, "wouldn't come up" ?
The only thing I have noticed with SP3 and other service packs, is that there tends to be pre as well as post-login processes that occur *without* any visual queues or information/dialogue boxes to let you know whats happening. In those cases, I have seen it take anywhere from 3-30 minutes to complete depending on the power of the system as well as the fragmentation of the HD. The key to this is checking for hard drive activity. Not waiting, and rebooting the system to try to "fix" the issue can very likely cause the system to become non-bootable. I have had a long and hard (queue the cracks) road up hill both ways trying to educate my users about this - as they tend to be self-medicating with rebooting prior to informing me of an issue. Their kindness to try to not bother me is both a blessing and a curse. On Fri, May 9, 2008 at 8:14 AM, David W. McSpadden <[EMAIL PROTECTED]> wrote: > Had a couple family members call last night about SP3 killing their > machines. > They use Windows Updates nightly and when they rebooted their machine it > wouldn't come up. > After many SafeMode boots I called TechSupport and they told me there is an > issue with the WindowsUpdate > version of SP3 and to have it blocked from being downloaded on any other > machine until it is resolved. > They seemed to know all about it because they stepped me through the correct > SafeMode fix for it. > > Didn't know what anybody else knew. > > Good night. > > > > > > > > > > IT works, > but keeping IT working is the hard part. > > Automation is great, > until it breaks. > -- ME2 ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
