Patching on WIndows server 2008

I have in my environment windows 2008 R2.These server's are not patched since last one year.

Question is :

1) How to identify pending applicable /Known /Critical patches?
2) how to install manually these patches?
3) What is the Risk for these patching?
4)What is mitigating and how much time its  take to successes to complete

Kindly help me to update above answer please.

Thanks for your update
neeladminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

awawadaCommented:
1) How to identify pending applicable /Known /Critical patches?
Install Microsoft Baseline Security Analyzer 2.3 on a client and run a scan to the Server.
http://www.microsoft.com/en-us/download/details.aspx?id=7558

2) how to install manually these patches?
Download them from http://www.microsoft.com/en-us/download/,  http://catalog.update.microsoft.com/v7/site/Home.aspx or just run Windows update and select what you want.

3) What is the Risk for these patching?
Create a full backup before.

4)What is mitigating and how much time its  take to successes to complete
It depends on your environment (Hardware, Network speed etc.)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
madunix (Fadi SODAH)Commented:
Generally, take the following points into consideration
- Prior to deploying updates to production servers, make certain that a full system backup is conducted. In the  of a system crash, due to the update, the server and data can be recovered without a significant loss of data.
- Do the update first on a staging server
- Do the updates by hand and watch the output and behavior
- When implementing updates, I prefer to plan ahead, test on a non-critical server or a staging server, create a change plan B
- Depends on your appliation such as web, db ..etc I don't auto-update.  There are too many variables involved that may negatively affect the server's functions.
- After an update I prefer to restart the services or in some cases to reboot
- Be sure to read the release notes, there may be special instructions related some packages
0
David Johnson, CD, MVPOwnerCommented:
Organizations typically use WSUS to manage updates with multiple approval groups. i.e. deploy first to lab servers and if successful then approve for production servers.  And you can approve updates in order of severity i.e. critical updates, security updates, patches, service packs, drivers.

The more backups you have the better you will be.

The longer you wait the more updates that are required which will require time to install and your exposure to attack increase.
0
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.