But I'm not sure if its set up correctly.Here's an example of what I want it to do:Client at site B accesses a namespace folder thats DFS'd at all sites.Windows should look for it at the local site first (Site B).If it can'.
If worse comes to worse, I'll have to reimage all these laptops with a 64 bit Windows. This issue was supposedly corrected in the 32 bit driver I'm trying to get and it was definitely fixed in the 64 bit. The software vendor finally pinpointed the issue being that the current video drivers are using Windows older way to render the display where the software and Windows are using a new rendering method and it's causing massive memory leakage that eventually requires the laptop to be rebooted. I understand the concern over a bad update, but that's not as bad as the problem we're having. We obviously have our updates managed through WSUS and it's set to require admin credentials to bypass WSUS. This is really the first time that we've come across a driver that needs to be updated for software to be run. I like the idea of a standalone installer since all these laptops are mobile and connect to the network via cellular VPN connections.Īs far as your second point, the massive amount of drivers available is why we don't have drivers update via WSUS. I wasn't sure if drivers had KB numbers or not. All you need to do is update a video driver from Windows Update." I'd write up a simple procedure (with images) and email it to those users and say simply: "Hey, we got a fix for that annoying problem you've been experiencing.
Unless there's some reason you don't trust your Toughbook users to browse to WU and install one video driver update. A hosed video driver install can be a hundred times worse than the problem you may be currently experiencing. 'Tis much better, IMHO, to do a video driver installation FROM the system being updated so that you can see that the video actually still works AFTER the update. The fact that it's available via WU does not necessarily make it available via WSUS.įinally, given that this is a *video* driver, I'd be very nervous about doing a PUSH installation. I would suggest searching the Microsoft Catalog ONLINE first to determine if the exact driver you need is actually in the WSUS catalog. Second, enabling the Drivers classification is going to dump 30,000+ updates in your WSUS repository, and that still may not provide the video driver you're looking for. First, drivers don't have Microsoft KB numbers.