Podcast on Service packs

I did a podcast on service packs and while it’s focusing on Windows 2003 sp2 the basic rules are the same.  Service packs are to be planned for.  One thing that I just take for granted and do and don’t even think about much when doing service packs is ensuring the normal backup worked and then taking a special quick system state backup before a service pack.  I don’t do this before security patches mind you, but will do a system state before a service pack (especially a OS service pack).

When you are applying a Server OS service pack also ensure you have access to a workstation and connect to that and test connections there as well.

A little bit of pre planning will ensure a solid service pack deployment


Check on vendor support
Review the SBS blog
Ensure you have a good backup
Do a system state backup as a just in case backup

Reboot the server before applying

Scan the event log

Ignore the standard messages

Like MAD, Exchange AD

Like DSrestore

Install latest NIC drivers

Install patch

SP 2 fix up patch http://support.microsoft.com/kb/936594

Help and support – http://support.microsoft.com/kb/937231/en-us


Test RDP

Test VPN

Test connectivity to server

Ensure you test the following that may have had issues, test VPN, connect to a workstation, test connections. 

  • Unable to VPN to the Server (“Error 800: Unable to establish connection”).

  • Unable to RDP to SBS server

  • Unable to connect to shares on SBS server from the LAN

  • Unable to join a client machine to the domain

  • Unable to connect to Exchange from Outlook

  • Unable to connect to SSL sites either on the SBS server or on the Internet (including CompanyWeb)

  • Slow network performance

  • Outgoing FTP connections fail

  • DHCP Server service crashes

  • Slow domain logins

  • Intermittent connection failures from NAT clients behind the server

  • Intermittent RPC communications failures

Call support if needed:

Comments are closed.

Post Navigation