Order Now!
Windows 7 for XP ProfessionalsUpdating Support Skills from XP to Windows 7by Bink.nu's Raymond Comvalius
There are 51 guest(s) online.
There are 0 member(s) online.
• Windows Server 2003 with SP2 • Windows Server 2003 R2 with SP2 • Windows Server 2003 x64 Editions with SP2 • Windows Server 2003 R2 x64 Editions with SP2 • Windows Server 2003 for Itanium-based Systems with SP2 • Windows XP Professional x64 Edition with SP2 On Windows Update now, or see below (links are not all working yet, Bink.nu is too quick)SP2 (32-bit x86)SP2 for x64 EditionsSP2 for Itanium-based SystemsWindows Server 2003 Service Pack 2 32-bit Support ToolsSystem Preparation tool for Windows Server 2003 Service Pack 2 DeploymentSystem Preparation tool for Windows Server 2003 Service Pack 2 Deployment (x64)Windows Server 2003 Service Pack 2 MUI Pack (32-bit x86) UpdateWindows Server 2003 Service Pack 2 MUI Pack Update for x64 EditionsSP2 ISO-9660 CD Image (32-bit x86)SP2 ISO-9660 CD Image Itanium-based SystemsSP2 ISO-9660 CD Image x64 EditionsKB Analyzer Tool for Windows Server 2003 Service Pack 2 DeploymentKB Analyzer Tool for Windows Server 2003 Service Pack 2 Deployment (Itanium)KB Analyzer Tool for Windows Server 2003 Service Pack 2 Deployment (x64) + XP64Hotfix Scan Tool for Windows Server 2003 Service Pack 2 DeploymentHotfix Scan Tool for Windows Server 2003 Service Pack 2 Deployment (Itanium)Hotfix scanning tool for Windows Server 2003 SP2 Deployment (x64)System Preparation tool for Windows Server 2003 Service Pack 2 DeploymentSystem Preparation tool for Windows Server 2003 Service Pack 2 Deployment (x64)SMS Template Files for Windows Server 2003 Service Pack 2 DeploymentGeneral SP2 info KB914961 (still old page)http://www.microsoft.com/technet/windowsserver/sp2.mspx (still old page)Toolkit to Temporarily Block Delivery of Windows Server 2003 R2 Service Pack 2When I installed it I got this after the reboot:Application popup of Service Control Manager : Windows could not be started as configured. A previous working configuration was used instead.
After logging on everything worked fine, eventlog was clean too.
If you installed Internet Explorer 7 after installing Windows Server 2003 SP1, you must uninstall Internet Explorer 7 before you install Windows Server 2003 SP2.
Erm? well thats a big waste of time. So they are saying I now have to go round all of my servers and uninstall IE7 which was at the time a critical update, just so I can install SP2?
Poorly planned there by MS.
Tried to open the SMS Files. They are corrupt.
Get the following error on several PC's: WinZip Self-Extractor header corrupt. Possible cause: bad disk or file transfer error"
Any idea of the consequences if you don't do this ?
I applied it to 2 servers using windows update and it works without giving any warning about this issue !
Maybe it applys if you install IE7 directly after SP1? But if you have other updates installed after SP1 and then IE7 maybe it doesn't effect you?
I guess if you have a few boxes runing Win2k3 and can install SP2 on one of them with IE7 to test before you update the rest that's the best thing to do. You can then see if it has any problems and then decide what to do with the others.
The instructions say that if you install SP2 (say from Windows Update) and you did not uninstall IE7 first then you must uninstall SP2 and IE7 then start again.
I can imagine that rolling back a service pack would probably ruin your server. I would be insterested to know if there are any consequences of leaving it running as-is.
A few people already said that nothing seems to have gone wrong with installing SP2 with IE7 already installed, so unless problems pop up, I guess that's old info and doesn't apply anymore.
They have updated their documentation now to Version 2. The new version says the following on IE7
You do not need to uninstall Internet Explorer 7 prior to installing Windows Server 2003 SP2.Which is a relief...
I have the same issue. I tried uninstalling IE7 then applied the SP2 again same issue. I get the Error:
Application popup of Service Control Manager : Windows could not be started as configured. A previous working configuration was used instead.
The SP@ is installed but a quick check of regedit:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters
shows the "30" which is Original release version of Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 (SP1)
Right now I can't add domain controllers because my schema is different.
Is there any fix for this or work around?