John Howard - Senior Program Manager in the Hyper-V team at Microsoft

Senior Program Manager, Hyper-V team, Windows Core Operating System Division.

Blogs

Windows Server 2003 SP1 RC2 (Build 3790, v1433) released

  • Comments 5
  • Likes
The second release candidate (aka RC2) for Windows Server 2003 SP1 has now been released to the web.

x32 download link: http://www.microsoft.com/downloads/details.aspx?familyid=02734CEA-7A4B-4D95-B220-8E1708C3ED46&displaylang=en

IA64/Itanium download link: http://www.microsoft.com/downloads/details.aspx?familyid=9514DA0A-44C9-4FCB-83CA-473741D2613D&displaylang=en

The home page for the Technical Preview Program is here where you can find links for a technical overview, features and functionality changes, networking features and release notes.

Comments
  • Are there any documents which detail the changes between RC1 and RC2?

    Kev

  • Sorry Kevin - no, I haven't seen any publicly available documents yet on the RC differences - just information on whats new between RTM and SP1.

  • The home page for the technical preview redirects me to the Windows Beta site, where it tells me there is an installation survey, under the Announcements section. Er, no, there isn't. There's sod all. So I can't tell you that I installed SP1 for all of 10 minutes before I found that the ICS functionality had gone and no documentation told me WTF to do with Windows bl**dy Firewall to get the rest of my little network to continue to access the Internet. I immediately deinstalled SP1, and so far have not found any idiot's guide as to how to move from ICS to Windows Firewall. Do you honestly expect folks in small companies to be able to deal with this?

  • Geoff - obviously a bad experience installing the RC for you :-) I have followed through the feedback site this morning, and it appears to be working if it wasn't yesterday. There are two routes to report these issues back to the product group - either the MBC (Microsoft Beta Client) software, or by email. If you can drop me an email also through the "contact" option at the top of my blog with some more info, I'd be interested to try and replicate your problem on a virtual machine to see if I can identify any workarounds.