I've learned the hard way to incorporate logging into all my packages and the result of this one is. I've made several packages in this way, but not for drivers. I made an intunewin package with some Powershell scripts using pnputil.exe to install the Intel ProSet drivers for IT Admins. Set logfile=c:\logs\t410s_Driver_Update.logĮcho Starting ATI Driver Update Phase 1> %logfile%Įcho Determining Machine Code>%logfile%įor /f "tokens=3 skip=2" %%f in ('reg query "HKLM\software\vanguard\initial build" /v machinecode') do set machinecode=%%fĮcho Machine Code is >%logfile%Įcho This Model is not a t410s> %logfile%Įcho Failed: INTEL Video Driver did not install > c:\elevate\statusmif\smsjob.statusĮcho Starting the INTEL Video Applet Installation >%logfile%Įcho Finished INTEL Video Driver Installation >%logfile%Įcho Success: INTEL Video Driver is installed > c:\elevate\statusmif\smsjob.We've had the frustration of using Intel Wireless cards on Meraki gear near an airport which has resulted in a wide range of issues, particularly surrounding the weather radars and DFS channels.īasically, we need to make sure everyone has the latest Intel driver to ensure that this and a vulnerability are squashed. I have also tried many other more simplistic ways of accomplishing this and still no go.
It will not go to the :INSTALL_Driver section of the script unless I skip the If.Else statement. The bigger problem is that the script fails at the If.Else statement. I am not real familiar with using errorlevels so I took that from another script but am not certain I am using it correctly. I am packaging the Intekl HD Graphics Driver for Windows XP (32bit) for Lenova Thinkpad T410S laptops. I have been packaging software for years and am actually doing my first hardware driver. I am new here! Just looking for some help.
0 kommentar(er)
