I used the search to try to find an answer to my question, but only found this post from 2003
in which someone brings up the same issues I have, but there doesn't appear to be any response, so I figured I'd ask again.
We're a small bank, about $350 million in assets, one branch, about 35 employees total. I currently deploy patches using PatchLink, which I really like, but I do not really have any method to "test" patches before deploying them.
My current process is to deploy a patch to one PC in every department (operations, loan operations, tellers, etc), since they may have different software packages installed, then if everything looks ok, I deploy the patch enterprise wide.
This is great for patching desktop PCs, but my problem is patching servers. We don't have the luxury of a "test lab", so patching critical system servers is a harrowing experience to say the least.
How do other small banks handle patches? Do you have some way to test patches first, or do you just deploy the patches, then hope for the best, relying on backups in a worst case scenario (blue screen)?