11 replies
by wesley.chin Accepted solution
by bart777 Accepted solution
The only thing you can do is look at what the updates fix and then make your pitch based on stability and security.
With most management types if you paint a dire picture of what could happen if you DON'T patch, you can usually get it put in place. Time to put on the salesman hat.
by oh smeg Accepted solution
If it does then it's not necessary and if forced onto the Upper Management may result in your termination.
If it doesn't break anything then it probably will not hurt.
Before you come off with the [b]Doom & Gloom[/b] the Service Pack should be fully tested to see if there are any issues with your current setup.
It has been known to stop Scanners working.
Col
by wesley.chin Accepted solution
by oh smeg Accepted solution
You need to remember that this is a Business Application not a domestic install.
Col
by ashishs Accepted solution
http://www.maximumpc.com/article/office_sp3_giveth_security_but_taketh_away_plenty
http://www.eweek.com/article2/0,1759,2184443,00.asp
Hope it helps in making your decision.
by Former member Accepted solution
by wesley.chin Accepted solution
by ic-it Accepted solution
Was that entirely due to the SP or was McAfee < 8.5 and E-Pol < 3.6 used?
Before we upgraded to the 8.5 with the latest E-Pol we had this issue and traced it to McAfee. Could no longer scan to Word or PDF.
The main issue was that the scan program relies on other executables to actually transfer the data and McAfee would block it, then the program would return an error.
by oh smeg Accepted solution
A couple of questions have been asked here about Scanners no longer working after SP3 for Office 2003 has been installed.
I'm assuming that the Scanner Problem was brought about by SP3 as in 1 case the person was adamant that nothing else had been added company wide except SP3.
I believe that they solved their problem with a new scanner in that case. I'm not sure though as I'm not actually there but the person in question marked that as a Helpful response.
I test every M$ update before deployment and *I personally have not had an issue with SP3. But I do have limited exposure to it in the Business Environment.
Col
by ic-it Accepted solution
This discussion is closed to new replies.
Trending Software posts
Sort by Trending