Error installing Exchange Server 2003 on Windows Server 2003 SP 1

Has anyone has a similar experience?

Attempt to install Exchange Server 2003 Enterprise on Windows 2003 Server
Enterprise with Service Pack 1.  The setup references an incompatibility
with "this version of Windows" but gives the option to continue.  Upon
reaching the component install screen, "Typical" is not automatically
selected, and when it is manually selected, there is about a 30 second delay
and then the error message, "Setup encountered an error while checking
prerequisites for the component Microsoft Exchange 0xc007003A (58). The
specified server cannot perform the requested operation." pops up.  One
cannot continue beyond this point.  There are numerous messages on various
message boards but no resolutions.  TechNet has no articles on this error.

I called Microsoft Product Support and their solution was to uninstall 2003
Server SP1, install Exchange, install Exchange SP1 then install 2003 Server
SP1.  This sounds far too shaky a solution for me and on my front-end
servers I installed 2003 Server slipstreamed with SP1, so, since I'm the
position to do it, I'm just reinstalling the servers from scratch without
SP1 until I have Exchange installed.

I believe this problem is due to some incompatibility with the Exchange
installer and 2003 Server SP1.  Exchange does not support slipstreaming
service packs into the original install so even if the SP1 version would
install, it can't be done.  Microsoft must come up with some sort of fix for
this because I'm certain that I'm not the only person who will install 2003
Server slipstreamed with SP1.

----------------
Mark J. Lucas, Sr. System Administrator, ITS
California Institute of Technology

--
NTBugtraq Editor's Note:

Most viruses these days use spoofed email addresses. As such, using an Anti-Virus product which automatically notifies the perceived sender of a message it believes is infected may well cause more harm than good. Someone who did not actually send you a virus may receive the notification and scramble their support staff to find an infection which never existed in the first place. Suggest such notifications be disabled by whomever is responsible for your AV, or at least that the idea is considered.
--