Unable to deploy Intel Graphics Drivers Via SCCM (ECM) due to system folder restriction

[Stephen_in_TN]

Hello,

I am attempting to silently deploy the latest Intel graphics drivers to endpoints via Endpoint Configuration Manager (formerly SCCM). Because our users are not administrators, we must use an endpoint management system to deploy software. ECM uses the built-in system account to install software. Due to some odd restriction on your graphic (and possibly other) installers, we are unable to deploy the latest graphics driver.

When the system attempts to install the driver, we receive a pop-up message stating, "The application is in an unauthorized location. Please move to a non-system folder".

As I stated before, we use ECM, which installs applications, drivers, etc, via the system account. The temp folder for the system account in this case, is c:\Windows\Temp.

I have never run into a restriction such as this with software from ANY other vendor and I deal with hundreds!  Why on earth does Intel do this? 

Is there another version of the driver that is meant to be used in managed environments?

[ACarmona_Intel]

Hello Stephen_in_TN,

Thank you for posting in our community.

Please try the following troubleshooting steps provided in the link below and let us know the results.

• Unable to Install the Graphics Driver from Within Any Windows System Folders
  • https://www.intel.com/content/www/us/en/support/articles/000088280/graphics.html

Thank you, and have a great day ahead.

Best regards,

Carmona A.

Intel Customer Support Technician

[Stephen_in_TN]

Hello,

I want to state outright that having this "no system folders" policy for driver installers is incredibly dumb. So far, no one can tell me who is responsible for this genius move or its reasoning. I can tell you that Intel is THE ONLY vendor with this sort of restriction built into its installers.

That rant aside, I would like to ask you how we are supposed to implement solution number 2 in the referenced article when there is ZERO documentation on how to EXTRACT the drivers from the installer?

If for any reason, it’s not possible to move the temporary folder, a possible alternative is to use PnPUtil /add-driver command in a script to install the driver.

• For integrated graphics: The target INF to be used is iigd_dch.inf.
• For discrete graphics: The target INF to be used is iigd_dch_d.inf.

In order for this to work, we need to be able to extract the inf files and associated driver contents from the installer. This is the only command line reference available:

https://www.intel.com/content/www/us/en/support/articles/000006773/graphics.html

[ACarmona_Intel]

Hello Stephen_in_TN,

We are checking in with you on the graphics driver issue we are having in case you have any additional queries or require further explanation. Please know that we would be happy to assist you if you have any.

Thank you, and have a great day!

Best regards,

Carmona A.

Intel Customer Support Technician

[ACarmona_Intel]

Hello Stephen_in_TN,,

We are checking in with you on the graphics driver issue that we have, as we have not heard any response from you.

Thank you, and have a great day!

Best regards,

Carmona A.

Intel Customer Support Technician

[ACarmona_Intel]

Hello Stephen_in_TN,

We have not heard back from you, so we will close this enquiry now. If you need further assistance, please submit a new question, as this thread will no longer be monitored.

Thank you, and have a great day ahead.

Best regards,

Carmona A.

Intel Customer Support Technician

[Nico6]

@ACarmona_Intel  @Stephen_in_TN Has there been any resolution to this issue ?? I am also experiencing the same issue when deploying the current  intel® Graphics Driver 32.0.101.5768  via MECM 2303. 

I do not have this issue with any other vendors. 

[J_Budd]

I was able to get this working with MECM. It was a little tricky but it paid off in the end. I downloaded the Intel UHD 770 driver package from Intel and used 7zip to extract the contents of the exe. Next, I created a folder on my MECM server named "Intel UHD 770", Inside that folder I created a batch file named "Install.bat" and another folder named "Driver Contents". I copied the extracted files from the Intel driver into the "Driver Contents" folder. I then created a package in MECM named "Intel UHD 770 Graphics driver" and pointed it at the root "Intel UHD 770" folder. In my MECM package, I created a program to run the "Install.bat" batch file silently whether or not a user was logged in. The batch file was configured to use the xcopy command to copy the driver files in the "Driver Contents" folder to "C:\TempDir" and then run the installer with the --silent and --fresh command line switches. I then targeted a collection of PC's with my deployment and ran the package. This worked to install the driver, however, the Software Center reported that it failed to install the software. After doing a little digging, it turns out that after the batch file ran, MECM was looking for an exit code to tell it that the installation was completed properly. To remedy this I added "exit /b 0" as the last step in the batch file. I updated the contents of the package on my distribution points and then re-ran the deployment. After re-running the deployment the driver was installed properly and the MECM Software Center reported a successful install. You can see the contents of my batch file below for reference.

@Echo OFF

xcopy /e "%~dp0\Driver Contents" "C:\Tempdir\"

C:\Tempdir\Installer.exe --silent --fresh

exit /b 0

Root Intel UHD FolderDriver ContentsPackageProgram