Patching windows server 2k....

[Ns1]

As a service to one of my prior employers, I do a little work on their server. I think it's heavily out of date and needs to be patched. That said, I don't want to risk having it blow up.

1. how realistic is that scenario and
2. how would I mitigate such risk?

The backup procedure that's currently in place is poor, at best. I can't seem to transfer large files onto the external hard drive and I don't think the tape drive that they currently have will suffice.

 

[Nothinman]

Find a way to get a good backup before doing anything else.

 

[Ns1]

Originally posted by: Nothinman
Find a way to get a good backup before doing anything else.

That's also what I figured lol.

 

[Nothinman]

There's no real way around it. With Win2K3 you _might_ be able to get away with System Restore if something breaks but I wouldn't really trust that either.

 

[MedicBob]

Are they missing any certain features or attempting to do something that requires an update? If no, why update?

If it is secure, I would be even more hesitant to touch it then you are unless they want something else from it.

 

[Ns1]

Originally posted by: MedicBob
Are they missing any certain features or attempting to do something that requires an update? If no, why update?

If it is secure, I would be even more hesitant to touch it then you are unless they want something else from it.

It's not broken, but it's definitely NOT secure

They've had a major downturn in business and haven't had any investment in IT in years

 

[Nothinman]

Are they missing any certain features or attempting to do something that requires an update? If no, why update?

Um, security fixes maybe?

 

[wfn]

Use acronis trueimage home edition to back up to external hdd and then patch with this:

http://www.msfn.org/board/Unof...Pack-5-FAQ-t69579.html