RE: 2003 in place upgrade - NIC driver

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello,

Good to hear from you.

According to the message, I understand that the NIC driver is not
recognized after you in place upgrade win2k server to win2k3 server. Is
this correct?

It seems that you now have two concerns:
1. Understand why /checkupgradeonly doesn't help.
You have tried /checkupgradeonly option on server prior to upgrade,
however, this option doesn't help.
2. How to preload the 2003-compatible NIC driver.

As for the first concern, please check the article below.

Hardware compatibility
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Serve
rHelp/3e4d2b67-c2ff-45a1-ac5b-d4266858c935.mspx

/checkupgradeonly will check to see if the hardware or software is
compatible with the win2k3. This is just like we go to Windows catalog to
check if the hardware is compatible with win2k3. However, Windows catalog
will not inform us to upgrade the driver. It is the same thing

/checkupgradeonly will check if the hardware is compatible, however, it
will not tell us that we need to change the driver. So we need to check
drivers and system BIOS or firmware after upgrade.

As for the second concern, it seems to be a "how to" issue. Since our
newsgroup mainly focuses on break/fix issues, we would like to offer some
general information on it.

Please refer to the following article. I believe it is useful for your work.

HOW TO: Create an Unattended Installation of Third-Party Mass Storage
Drivers in Windows Server 2003
http://support.microsoft.com/?id=816299


In addition, if you have related break/fix issues, you are welcome to post
back in this newsgroup. We are happy to help you with them.

Hope this helps and thanks for your understanding!

Best regards,

Frances He

Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.



Relevant Pages

  • cvs-src summary for 11/04/04 to 18/04/04
    ... Brian Feldman added support to dump and restore for a -P argument ... lightweight SNMP server used by the ATM implementation. ... Robert Watson merged the umct driver, ... Upgrading GDB ...
    (freebsd-current)
  • Re: ExtremeZ-IP and Tiger
    ... Our support team will help you if you open a support case with Group ... ExtremeZ-IP File Server: ... and Classic on a dozen G4s and we want to upgrade to Tiger, ...
    (comp.sys.mac.system)
  • Re: Upgrade Win2K DC to Win2K3 DC...?
    ... I've not used PC anywhere to upgrade a server. ... If the upgrade does not load the driver ... Win2K3 DCs for years. ...
    (microsoft.public.windows.server.general)
  • Re: Installing Windows Server 2003 on Dell Dimension 2400
    ... The only card I could find that supported Windows Server 2003 was the D-Link ... if you accessed the Driver Download service ... The Intel cards mentioned below do support 2003 per the Intel website, ...
    (alt.sys.pc-clone.dell)
  • Re: Will BES 3.6 Enterprise Edition works on SBS 2003
    ... I don't think we have a support agreement ... said we have to pay for the upgrade. ... The BES is install on a W2K Ad ... configure this server to talk to SBS? ...
    (microsoft.public.windows.server.sbs)