When Our Next One Hits Are You Prepared?
The 7.2 earthquake two weeks ago in Turkey got me thinking again about disaster preparedness and IT. It reminded me of the 5.9 earthquake that occurred on the U.S. east coast, a region that is not supposed to get earthquakes. I just did a couple of walk-throughs at two different client facilities. One had server racking very well secured at the top and bottom that looked like it would withstand a pretty severe shaking while the other site did not have any fasteners at either the top or the bottom of the server racks. I could have pushed the racks over myself by leaning on them.
Smoke testing is a term used to describe the testing process for servers after patches are applied. 
Estimating an average time for patching servers and PCs can be a bit tricky. It can vary from one month to the next, depending upon the number and complexity of the patches released by your software vendors. You must consider all versions of operating systems and have a complete inventory of all your application software to do this job correctly. Our experience has shown that manual patching of systems takes on average of about 1.5 hours each.
This is a basic cost calculator for you to compute your typical monthly cost for patching your servers, PCs, laptops, tablets and associated application software. It also forms the basis for you to begin calculating your Return on Investment for software patching, or for comparison with alternatives to the manual process of patching operating systems and application software—such as Patch Management as a Service, also known as Vulnerability Management as a Service.