Right drivers, wrong OS ^Īre you still deploying Windows 7? Are you using MDT 2013? If so, don’t forget that MDT 2013 uses Windows PE 5.0, which uses the same drivers as Windows 8.1. Many times, the hardware manufacturer will have newer drivers than your OEM has. ![]() When it doesn’t, I’ll usually go to the network card manufacturer’s web site or do a search on the hardware ID to track down a current driver. That tends to resolve it 90% of the time. When in doubt, I always start with the OEM’s web site to see that I have the latest driver they’re supporting. The new network chipset driver is sometimes backward compatible with older revisions, and sometimes it isn’t. Worse yet, some OEMs like to use the new chipset, especially in their non-Enterprise business/small business brands. Intel, Broadcom, and all the other network card manufacturers are really bad about making minor revisions to their hardware that require an updated version of the driver. ![]() The following networking device did not have a driver installed. If your MDT server doesn’t have the right drivers for a NIC, you may see, “The following networking device did not have a driver installed,” followed by a hardware ID. ![]() This one may sound totally obvious, but I’ve wanted to beat my head against the desk a few times when dealing with getting the right drivers for a system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |