Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Patch management process for critical severs

  • Please log in to reply




  • Member
  • PipPip
  • 52 posts
Hi guyz,

Hope you are doing well. I need to discuss about the process for patch management especially for the critical servers. I have read that typically such process should be like analyze the patch’s fix i.e. what bug is fixed in the patch is it related to security or system? Then taking approval and verification and testing the patch in a testing environment, , making a back off plan in case of any issue arise with new patch installed etc.

But small business company where there is no testing environment is present what should be the best practice for deploying these patches? How can we safely deploy these patches as there is no actual testing environment present and what should be done in case of a major security fix? Should that be deployed immediately or take some time even deploying such critical patches.
  • 0


Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP