# Read the environment, config settings and get status target $Status = New-PackageStatus -Message 'Update Extension' -Status 'transitioning' -Name 'AmdGpuDriverWindows' -Operation 'Update' If ( -not $env:Path.Contains( "$PSScriptRoot ") ) $PSScriptRoot = Split-Path $MyInvocation.InvocationName Place the script in the scripts folder of the extension before running it. In order to run the script, the driverupdate.ps1 file needs to be located in the scripts folder of the extension.īelow you can find an outline of the script. What I’ve done, I took the update.ps1 as the base and added the install parts from the enable.ps1 script. To keep current with your AMD GPU driver version control the following paragraph will describe how you can achieve this by taking the above scripts into account, and provide a best of both worlds joint solution to ease up the versioning of your AMD GPU drivers. There is a check mechanism included to see if a driver is already installed. When taking a closer look at the “enable” script, this is the script that is run during the deployment of the AMD GPU extension, the “enable” script takes care of the installation. Looks like the driver update part will be something for the next version of the extension :). In the scripts folder (C:\Packages\Plugins\\1.0.0.0\scripts) you can find all of the scripts used by the extension.Ĭurious thing is that there is an “update” script, however, it seems that some parts are still missing. When looking at the scripts used by the AMD GPU extension, when applying for the extension, it will automatically download and install the latest version of the drivers.
Looking at the different hosts, we noticed that some hosts had other deployment times or received a VM update somewhere along the road.
0 kommentar(er)
