It
has been suggested that this update does not end the problems for Java. In
fact, some experts on Java are recommending that Java not be used unless
necessary. If you require Java, here are
two suggestions:
- Turn Java on only when you
need it and turn it off when you don’t. - Use two browsers: A primary
browser with Java disabled and a secondary browser with Java enabled for
when you need it.
My
recommendation is for two browsers. That
is what I have done on my ultrabook where I need to run a Java app on occasion. I use Internet Explorer for my general
browsing and I am using Firefox when I need the Java application.
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.