Small Business Susan

Before you install

If the readme for SP2 was written like it should be it would be like this:


Before you install


Before you install SP2:

Backup the server

Review the following documentation.

Article 914962 in the Microsoft Knowledge Base, for a list of the updates included in this service pack (http://go.microsoft.com/fwlink/?LinkId=74380 if(typeof(IsPrinterFriendly) != “undefined”) { var l = “http://go.microsoft.com/fwlink/?LinkId=74380″; var nl; var c = l.charAt(0); var o = document.getElementById(“EV”); switch (c){ case “/”: nl=(” [http://" + document.domain + l + "]“); break case “#”: nl=(“”); break default: nl=” [" + l + "]” } if(o != null) o.innerHTML = nl; } ).

“Release Notes for Windows Server 2003 Service Pack 2″ (http://go.microsoft.com/fwlink/?LinkId=74381 if(typeof(IsPrinterFriendly) != “undefined”) { var l = “http://go.microsoft.com/fwlink/?LinkId=74381″; var nl; var c = l.charAt(0); var o = document.getElementById(“E4″); switch (c){ case “/”: nl=(” [http://" + document.domain + l + "]“); break case “#”: nl=(“”); break default: nl=” [" + l + "]” } if(o != null) o.innerHTML = nl; } ), for a list of the known issues with this version of SP2.

“Installing and Deploying Updates for Microsoft Windows Server 2003″ (http://go.microsoft.com/fwlink/?LinkID=64779 if(typeof(IsPrinterFriendly) != “undefined”) { var l = “http://go.microsoft.com/fwlink/?LinkID=64779″; var nl; var c = l.charAt(0); var o = document.getElementById(“EFB”); switch (c){ case “/”: nl=(” [http://" + document.domain + l + "]“); break case “#”: nl=(“”); break default: nl=” [" + l + "]” } if(o != null) o.innerHTML = nl; } ), for information about combining this service pack with other updates.

“Windows Server 2003 Service Pack 2 Installation and Deployment Guide” (http://go.microsoft.com/fwlink/?LinkID=64780 if(typeof(IsPrinterFriendly) != “undefined”) { var l = “http://go.microsoft.com/fwlink/?LinkID=64780″; var nl; var c = l.charAt(0); var o = document.getElementById(“ENB”); switch (c){ case “/”: nl=(” [http://" + document.domain + l + "]“); break case “#”: nl=(“”); break default: nl=” [" + l + "]” } if(o != null) o.innerHTML = nl; } ), for more deployment options.

Check the disc space requirements. See article 926029 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=74454 if(typeof(IsPrinterFriendly) != “undefined”) { var l = “http://go.microsoft.com/fwlink/?LinkId=74454″; var nl; var c = l.charAt(0); var o = document.getElementById(“EWB”); switch (c){ case “/”: nl=(” [http://" + document.domain + l + "]“); break case “#”: nl=(“”); break default: nl=” [" + l + "]” } if(o != null) o.innerHTML = nl; } ).

Back up your servers. Your backup should include all data and configuration information that is necessary for that server to function. It is important to perform a backup of configuration information for servers, especially those that provide network infrastructure, such as Dynamic Host Configuration Protocol (DHCP). When you perform the backup, be sure to include the boot and system partitions and the system state. Another way to back up configuration information is to create a backup set for Automated System Recovery.

Disconnect UPS devices. If you have an uninterruptible power supply (UPS) connected to your destination computer, disconnect the connecting serial cable before running Setup. Setup automatically attempts to detect devices connected to serial ports, and UPS equipment can cause problems with the detection process.

Disable your antivirus software. If you are not connected to a network or the Internet and you want to minimize the installation time, you can disable your antivirus software. The time that it takes for the antivirus software to scan each file can add significant time to the installation: as much as an hour or more on slower computers. Be sure to enable the antivirus software after you install SP2.

Uninstall prerelease versions of SP2. Unless you have a supplementary support agreement with Microsoft, you must uninstall any prerelease versions of SP2 before you proceed. Upgrading to this version from any prerelease version is not supported.

Close all open programs.

If you are running a SBS 2003 box — ensure you read the following blog posts

http://blogs.technet.com/sbs/archive/2007/06/01/unable-to-rdp-rww-into-the-sbs-server-after-applying-sp2.aspx
http://blogs.technet.com/sbs/archive/2007/04/24/common-networking-issues-after-applying-windows-server-2003-sp2-on-sbs.aspx
http://blogs.technet.com/sbs/archive/2007/03/20/help-and-support-service-missing-after-installing-windows-2003-service-pack-2.aspx
http://blogs.technet.com/sbs/archive/2007/03/19/vpn-securenat-nat-and-outlook-clients-not-working-after-installing-windows-service-pack-2-in-sbs-2003-premium.aspx
http://blogs.technet.com/sbs/archive/2007/03/19/error-when-trying-to-approve-windows-2003-sp2-within-update-services.aspx
http://blogs.technet.com/sbs/archive/2007/03/14/can-i-install-windows-server-2003-sp2-on-sbs-2003.aspx

——–

That’s a lot of blog posts on the impact of SP2 in our servers isn’t it?  And I’m sure a lot of you are holding back waiting so we’ve not gotten the full impact. 

This must be an R2 Friday or something to get me in a mood but when you scroll through all those blog posts about the issues with SP2…remind me again why we want this service pack?  Chris’ blog post about how we’re the runt group is right sometimes.  If all of those things happened to big server land SP2 installs, you’d think that the release notes would at least point to “Known issues”.  Sorry but all those things ARE known issues down here and just because it happens on our boxes and not big server land’s it gets a little annoying to be the Cockroaches sometimes and not be acknowledged for all of our “ouchies”.

While I can understand that ISA’s service packs should not be done remotely, when you can’t even dependably install SP2 on a system without losing RDP access which is what we depend so much on around here, that’s rough.  That means anytime you patch with SP2 be prepared to drive to that client.