Windows Server 2008 Drivers Download

0 views
Skip to first unread message

Cecelia Seiner

unread,
Aug 5, 2024, 1:01:51 AM8/5/24
to lumadtigymk
Implementthe HP UPD version 6.9 on all your HP devices and make your life easier. In terms of print servers, even HP internally moved away from print servers to direct printing deployed through group policy. I posted the white paper on it here last week.

If you are using UPD drivers, the same 64bit driver package will support any 64bit OS. If you have 32 bit systems you will need to add the 32bit driver package but everything is the same other than that.


Then you need to see your business print cases. Universal Print Drivers have their own drawbacks (else why do HP etc develop specific drivers) ? So I would closely monitor errors especially printing pdf as some errors may cause printing single sheet PDF to churn out 100s of sheets of codes.


Hp laser jet V still works in most cases. Dont put printers on your server!!! If it is hp it will still talk PostScript if you really want it. HP just works. If you are trying to install old printer drivers to push out to your clients via GPO I understand the question and the older drivers have nothing to do with the server. Server is just a place holder/spooler. The devices (workstation/printer) will talk to each other and will work out how to print.


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.


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.


Also note that if you previously installed the Intel HD Graphics 630 driver in TestSigning mode, you should uninstall it from Device Manager with the option to Delete the driver software for this device - otherwise it might use the cached unsigned catalog and fail to install.

Then add your signed driver via scan or Browse my computer/Have Disk.


I cannot vouch for whether multi-monitor works (I only have the KVM adapter plugged in as you can see from my attached screenshot), but OpenCL CPU and GPU support does work, and 1920x1200 output resolution at 59Hz does too.


you may be able to use the Windows 8.1 drivers for HD Graphics 630, as they are compatible with Windows Server 2012 R2. You can download the drivers from the Intel website or through the Device Manager in Windows Server 2012 R2.


Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.


To directly answer your question, the "Windows Server 2016 and Later Servicing Drivers" product category does contain updates that might be applicable to your servers, but they are all device drivers, so they will not affect the build number.


In this case, the particular Windows build you are interested in was released as KB4519979, on October 15. I've checked my WSUS server (which has all products and classifications enabled) and this update is not present, nor was any other Windows 2016 update released on or near that date. So it appears that it simply hasn't been released via WSUS.


Occasionally non-security updates do get left out of WSUS, for reasons that are unclear. Don't worry about it; when the November updates are released they should bring your DCs back in line with your other servers.


Servicing stack updates provide fixes to the servicing stack, the component that installs Windows updates. Additionally, it contains the "component-based servicing stack" (CBS), which is a key underlying component for several elements of Windows deployment, such as DISM, SFC, changing Windows features or roles, and repairing components. The CBS is a small component that typically does not have updates released every month.


Servicing stack updates improve the reliability of the update process to mitigate potential issues while installing the latest quality updates and feature updates. If you don't install the latest servicing stack update, there's a risk that your device can't be updated with the latest Microsoft security fixes.


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.


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.


The list under "This download is valid for the product(s) listed below" shows both I219-LM and I219-V. Since Windows Server OS are not supported with I21x-V, the presence of I219-V on this list looks like a mistake.


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.


Ironically, I have another much cheaper NUC5PPYH featuring Realtek gigabit Ethernet that has no trouble working with Windows Server 2012 R2 or Windows Server 2016. It looks like I'll just have to give up trying to get my NUC6i5SYH to run WS2012 R2 or WS2016.


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.


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.


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.


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.


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.


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.


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.


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.)


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..




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.


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?

3a8082e126
Reply all
Reply to author
Forward
0 new messages