When did you last patchyour server?

Server Patching Process

When was your server last patched? We see it all the time on or IT Support Desk. Servers with the “Updates are waiting to be installed” logo near the system tray. There can often be as many as 60 updates queued, all waiting to increase the security of your server. So why not apply them? The answer – rebooting is often needed.
There is a rational reason for the reluctance, too. Firstly, you have to reboot the server when all users are logged off, meaning out of hours, or during a scheduled (and usually inconvenient) downtime.
Then there’s the unthinkable – what if it doesn’t come back on properly? We have all heard the rumours such as “I have applied update ‘x’ and since then my computer has not been working properly”. The IT Manager knows that it’s the right thing to do, but proactively actioning such is the IT equivalent of sticking your head above the parapet; users don’t care about patches, but they DO care if they can’t access their data.
Think a moment, though, and you will realise that the opposite is true, too; what about the possibility of a security breach that results in data loss? The finger of accusation would point firmly at the IT Manager’s tardy installation of patches, and label the breach preventable. Would this be a sackable offence? Perhaps.
So in conclusion, take regular backups, restore points to roll back patches, and GET THEM APPLIED! Microsoft are not in the habit of working for nothing, so we must all assume that there are good reasons for the patches being made available in the first place. Check your server regularly, and patch as soon as you (and your users) are able!
Alternatively, if you want to leave it to an IT Support firm, why not give us a call and we can make arrangements to bring your server up to date, safe and secure!