Latitude E7450 not installing drivers from driver feed anymore
03/16/2016 1717 views
I was working on a Windows 10 scripted installation which suddenly stopped joining the domain, even though I hadn't made any changes to my unattend.xml file. This had been working fine for more than a week.
When I checked the log files in the C:\Windows\Panther folder, it displayed
[DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is 
[DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 10 seconds...
this message repeated every ten seconds over the course of ~15 minutes.
When searching for these errors, it quickly became apparent that the domain wasn't even being reached. It could be that the NIC wasn't even initialized and thus not being able to reach it.
But since K2000 installs drivers from the driver feed this shouldn't be a problem. (Keep in mind, it used to work) However, by pure luck I happened to check the driver version on the NIC on one of the E7450s that failed to join the domain and noticed that the driver version didn't match the driver that was supposed to be installed.
I went to check in K2000's driver feed and "Latitude E7450_7450" was gone! I ran the driver_feed_discovery_tool on the same E7450 and instead of "e7450_7450", Model expected by Driver Feed reported "e7450". So I installed "Latitude E7450" in the driver feed, and voila! K2000 went back to installing drivers on the E7450, and my automatic domain join started working again.
Since the removal of "Latitude E7450_7450" in the driver feed happened during my testing of my new Windows 10 deployment, I had a really hard time figuring out the problem. One second it worked, the next it didn't. However, installing "Latitude E7450" in its place solved the problem instantaneously. I'm posting this in case someone out there is experiencing the same problem, clueless what to do.
In summary: Check your driver feed, since the entry for Latitude E7450_7450 apparently has been removed. You will have to install Latitude 7450 into the driver feed instead.
Thanks for your time,
There are no answers at this time