![]() ![]() Here are some of my favorite comments you submitted along with this survey. There seems to be a great unhappiness that patching requires rebooting the server which usually means it must be done after normal working hours. This is where the comments came in and an overwhelming clarity of how much patching stretches manpower. "Other" ranked as the next reason, followed by IT departments which have regulatory requirements that require time-consuming tests of each patch. ![]() And very close behind was the fact that people frequently find that Microsoft's patches cause issues with software and resolving those issues often took more than 24 hours. Yet not far behind was the lack of manpower to roll out critical patches testing less-imortant patches ranked lower in priorities. Custom software came in as the main reason it would take more than 24 hours to test and deploy patches.
0 Comments
Leave a Reply. |