Dear Vincent, CoreConfigurator is a great tool! I have also gone to Broadcom’s website and downloaded the latest drivers, but despite getting the ones for W2K8 R2 x64, they would not install under Core. The following post discussed the similar issue, you can refer to: Nothing seems to matter or change. Saturday, October 29, Just want to post this as a potential solution in case any one is looking to resolve the same issue on Hyper V server R2. When I installed the operating system, only one of the ports was enabled, and Windows recognized it without any problems at all:
|Date Added:||8 August 2011|
|File Size:||65.19 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Something went wrong during the hardware detection and driver installation phase of the OS installation, and did not create a corresponding service associated with the NIC.
Broadcom NetXtreme II 1 Gigabit Driver 18.104.22.168 for Windows 64-bit
So in a sense, you can ignore the performance difference between the core and the full installation of Windows Server R2. Once you have put Devcon. Remember, I am accessing Device Manager remotely and read-only; Command Prompt commands are useful, telling me to “reinstall the driver” is not.
Saturday, October 29, Thursday, April 22, 9: Not an IT pro? Thursday, September 27, 3: Saturday, January 12, windkws Best Regards, Vincent Hu.
To continue using , please upgrade your browser.
I have tried Broadcom’s drivers as well as the drivers from HP’s support site. This will return a list of devices of the network adapter class, and will look something like this. General speaking, in theory, the performance of core installation of Windows Sever R2 is better than the full installation, however, you will never notice the difference only when you use some benchmark application to perform a test.
Friday, April 23, 3: The corresponding application for use in CLI is a small software called Devcon. Friday, April 23, 7: I have also gone to Broadcom’s website and downloaded the latest drivers, but despite getting the ones for W2K8 R2 x64, they would not install under Core. Has anyone else seen this before?
But it did not solve the problem: Tuesday, January 10, CoreConfigurator is a great tool! Also if you perform this via remote RDP, you will lose connection to the server. Thursday, April 22, The Device Manager GUI is absent in server core, yes you can still run device manager remotely from another computer, but from R2 this is a read-only type of administration.
Yours, David del Campo PS: Dear Vincent, CoreConfigurator is a great tool! I just refuse to believe it is a driver or NIC incompatibility issue when 1 of the ports is up and running and working just fine.
Windows Server R2 Core: how to force a driver update
I have installed the Broadcom drivers from Dell and rebooted the server, tried and failed to use devcon. Remove From My Forums.
I am at the end of my rope here, but we have a requirement that we are migrating all of our DCs to Core so I need to get this running.
Monday, March 7, 4: I have been running with it for a week now. By continuing to browse this site, you agree to this use.