From Newsgroup: comp.lang.mumps

<div>Version 17.10.5 is the latest general availability (GA) version of the 17.x driver. If you have a previous version of Microsoft ODBC Driver 17 for SQL Server installed, installing 17.10.5 upgrades it to 17.10.5.</div><div></div><div></div><div>If you can't find driver project templates in Visual Studio, the WDK Visual Studio extension didn't install properly. To resolve this, run the WDK.vsix file from this location: C:\Program Files (x86)\Windows Kits\10\Vsix\VS2022\10.0.22621.2428\WDK.vsix.</div><div></div><div></div><div></div><div></div><div></div><div>windows server 2008 lan driver download</div><div></div><div>Download: https://t.co/9iA2uPeKiU </div><div></div><div></div><div>As an alternative to downloading Visual Studio, the SDK, and the WDK, you can download the EWDK, which is a standalone, self-contained command-line environment for building drivers. It includes Visual Studio Build Tools, the SDK, and the WDK.</div><div></div><div></div><div>Now I have the correct driver (I219-V, dated October 2018 for Win10x64 containing the right VEN-DEV combination) that will work fine if I force the install using the GUI. But Windows considers it an incompatible driver and as such it won't install if I just supply the driver.</div><div></div><div></div><div>I also tried simply adding two lines into the inf file (since it already contains all the necessary instructions, they just disabled them), but the it becomes unsigned, so now I need to find a way to install unsigned drivers.</div><div></div><div></div><div>First you should use the free devmanview tool from NirSoft to check that you have the correct PnP vendor string. I know that you already have the string, but just to make sure that there is no mistake. Then you need to ensure that you have NDIS68 drivers, previous versions will not work. Then you need to patch the corresponding inf to move the lines with your vendor string from the Windows 10 section to the Windows Server section, it seems that this part is also ok in your case.</div><div></div><div></div><div>You can check with devmanview if the driver shows up with your NICs. Then you can set testsigning to off again and re-enable secure boot (if applicable). I also installed the PROSet Adapter Configuration Utility from Intel to check the adapter settings and verify the hardware and cabling. If you have multiple NICs beware that the numbering on the device is not the same as in the drivers. The number 1 adapter was the physical port 2 in my case. If you plug your cable to another port Windows will complain that there is no active network adapter.</div><div></div><div></div><div>In the Device Manager, update the drivers for the Ethernet Connection and 'Browse my computer for driver software'. Choose 'Let me pick from a list of available drivers', then selecting the PRO1000/Winx64/NDIS68 folder and selecting any of the .inf files in there. One of the following devices should show up, use one of these:</div><div></div><div></div><div>I personally have Win Server 2016 Essentials in my house used for file sharing, Vmware, Web page hosting, game server hosting and I also need the use of GFX card to handle video processing, rendering, and compiling. which is why I personally need "minimal" Driver install , (settings app would also be nice) (I also do some gaming on it directly when my main gaming rig is in use.)</div><div></div><div></div><div>Im stuck on 17.7.2 because its the last version that didn't block the install and it works and all but its also outdate by a lot. If I knowen AMD blocked the driver install I would have bought a NV 1050ti over the MSI RX 560 Nitro (4gig) solely because of drivers.. (my server requires a GPU due to the fact there zero integrated video, due to being Xeon cpu). So it was either 1 or the other at 75watt or lower is what I was stuck with in chooses..</div><div></div><div></div><div></div><div></div><div></div><div></div><div></div><div></div><div>once again I know its not support.. which is fine... but don't block users from install driver anyways... if it mucks up the users machine that's entirely on them.. and I personally can deal with that.</div><div></div><div></div><div>Ive just learned this the hard way. Built a vega server system from scratch on the assumption that drivers would installs on windows server 2016, i mean why not right? ive lost so much money I am thinking about legal action. Im sorry but the software team should be ashamed to do this to people, just terrible. Why AMD? just why?</div><div></div><div></div><div>This has been a thorn since forever. There is a way to use driver 19.2 with an edit to the installer config files. Beyond that no-go. That does not mean that amd does not mean to support server 2016. If you want a recent graphics board that has real driver support, get a radeon pro board. It won't have the high power multiple fans. Probably not the high end graphics features that you might want if you are a gamer. And it will cost you more than a gamer board. The thing about that is that server 2016 is the most stable gaming os I have found. Not sure about 2019.</div><div></div><div></div><div>I hope this works, I'm gonna put my rx580 in my multiseat gaming server... Got the server 2016 for that sweet multiseat gaming powered by multipoint services and Hyper-V like this chap over on the Linus Tech tips forum</div><div></div><div></div><div>I have an Intel NUC6i5SYH with I219-V gigabit Ethernet and discovered that the Intel Ethernet driver installs and runs with Windows 10, but not with Windows Server 2012 R2 or Windows Server 2016 OS. In looking for Intel Ethernet drivers on the downloadcenter.intel.com website, I found driver package 21.0 that lists support for both I219-LM and I219-V, but actual driver installation testing indicates that for Windows Server 2012 R2 and Windows Server 2016 OS, the e1d65x64.sys driver only installs against I219-LM but not I219-V.</div><div></div><div></div><div>Will Intel please clarify the support position of your Ethernet drivers for I219-V and Windows Server 2012 R2 and Windows Server 2016. If the drivers have no support for this HW/OS combination then a correction is in order for the downloadcenter.intel.com website, as the information on it currently is misleading.</div><div></div><div></div><div>I've been trying to get my NUC6i5SYH to run Windows Server 2012 R2 or Windows Server 2016 as part of an experimental audio setup. Since Intel LAN driver will not install for I219-V with WS2012 R2 and WS2016, I have lost the ability to get the NUC6i5SYH to boot one of these two server OS in a diskless configuration (using Microsoft iSCSI virtual disk). This is very unfortunate. Had this NUC featured I219-LM LOM there would have been no trouble with WS2012 R2 or WS2016, but this is not the case.</div><div></div><div></div><div>Can Intel confirm I219-V is supported with Windows Server 2012? Looking at Intel's supported driver matrix PDF it shows even Windows Server 2012 as not being supported with I219-V. I can consider running Windows Server 2012 with my NUC6i5SYH if the I219-V driver can install properly.</div><div></div><div></div><div>I need to dispute your most recent statement above. I just completed an installation of Windows Server 2012 into my NUC6i5SYH with I219-V Ethernet, and the latest 21.1 LAN driver does NOT install against I219-V.</div><div></div><div></div><div>This is basically proof that I219-V Ethernet is not supported with Windows Server 2012, in the same way Windows Server 2012 R2 and Windows Server 2016 are not supported for I219-V by the same driver package. Also, in studying the contents of the e1d63x64.inf, e1d64x64.inf and e1d65x64.inf files within the 21.1 driver package, it has become clear that I217-V/I218-V/I219-V are categorically excluded for Windows Server OS editions (2012, 2012 R2 and 2016), but I217-LM/I218-LM/I219-LM remain supported.</div><div></div><div></div><div>I would advice Intel to be more careful in stating which Windows OS edition is supported for which Intel LAN solution. There is obviously at least one case where the driver support matrix is incorrect, with the error not detected or corrected by Intel due to lack of verification of whether the driver can actually install or not.</div><div></div><div></div><div>I've had the same issues as you. Tried getting an ASUS B150i Pro motherboard with I219-V to work with Windows Server 2012R2 and 2016 as well. I started out with the Hyper-V Server editions, and tried to load drivers from Intel and Asus via the pnputil -i -a command, but this didn't work.</div><div></div><div></div><div>Guys! All these "LAN driver not supported on server" issues are easily solved by "hacking" the corresponding code-base driver ie Windows 7 driver for 2008, Windows 8 driver for 2012, Windows 10 driver for 2016, respectively.</div><div></div><div></div><div>The procedure is for a 4-gen NUC and Hyper-V server, and running the BCD edit commands. But with Windows server, all you have to do is do all the same steps, then have Device Manager browse to the hacked driver and you're good to go.</div><div></div><div></div><div>Thanks for answering. I have tried the drivers supplied by Asus (pnputil -i -a from the NDIS65 folder) and also from the latest 21.1 Intel drivers. I've tried running the supplied SETUPBD.exe application also.</div><div></div><div></div><div>I'm currently only using the Hyper-V role on the host machine and haven't installed any graphics drivers (other than the default ones the Windows Server install used). Was curious if there were any benefits or draw-backs to installing them?</div><div></div><div></div><div>There is a benefit to installing graphics drivers if you're using the graphics card at all, such as because you're running a GUI on the server. The benefit would be improved graphics performance, better stability and usually more options that allow the OS to make full use of the graphics card's capabilities (most obvious among those is usually the availability of higher display resolutions).</div><div></div><div></div><div>The downsides to installing the driver is that it could cause instability on the server if it's not solid, and like other drivers, will have to be updated/patched as necessary. Other than that it won't hurt.</div><div></div><div></div><div>I'm trying to find graphics drivers for my i7-7700 CPU running Windows Server 2012 R2 without any luck. I have Intel HD Graphics 630, but all the drivers for that are only supported for Windows 10. Where can I find graphics drivers? Right now I'm running on generic Windows graphics drivers and it's not able to detect my dual screens.</div><div></div><div></div><div>I followed the signing instructions from -to-sign-an-unsigned-driver-for-windows-7-x64/ but instead of downloading the Windows SDK and DDK (which now wants you to install Visual Studio), I just downloaded and ran the Enterprise WDK (EWDK) for Windows 10, version 2004 which is an ISO you can mount and since you're not building a driver you can just run LaunchBuildEnv.cmd from the ISO to get access to the command line tools you need to create the signed catalog.</div><div></div><div> df19127ead</div>
--- Synchronet 3.21d-Linux NewsLink 1.2