Deploy Driver Update Failing
Hi,
We are trying to push out updated Wireless Drivers to our Acer tablets. I am following the directions from this article and using the script posted in it:
https://wikis.uit.tufts.edu/confluence/display/exchange2010/Updating+drivers+on+already+deployed+OS
To start the Power Shell Script, I use the same cmd file that we use for our "Join Domain" script from out K2000 that works great every time:
powershell.exe -nologo -executionpolicy bypass -noprofile -file ".\WiFiDrv.ps1"
I have created the script and it runs perfectly when initiated by hand, KACE pushed the files properly, but will not execute the script to start the process. After KACE pushes the files, I can remote to a machine and run the script manually, so it is getting all of the files there, but just will not run that cmd file. According to the Distribution page, KACE is calling each attempt a success and the package has been "installed". None are showing as failures.
Any thoughts? This is our first time trying to push drivers to an already deployed OS, so I'm sure I'm doing something wrong here.
As a side thought, logging in as admin vs not doesn't make a difference. In both cases, I can run it by hand from an elevated CMD and in neither case does KACE work.
We are trying to push out updated Wireless Drivers to our Acer tablets. I am following the directions from this article and using the script posted in it:
https://wikis.uit.tufts.edu/confluence/display/exchange2010/Updating+drivers+on+already+deployed+OS
To start the Power Shell Script, I use the same cmd file that we use for our "Join Domain" script from out K2000 that works great every time:
powershell.exe -nologo -executionpolicy bypass -noprofile -file ".\WiFiDrv.ps1"
I have created the script and it runs perfectly when initiated by hand, KACE pushed the files properly, but will not execute the script to start the process. After KACE pushes the files, I can remote to a machine and run the script manually, so it is getting all of the files there, but just will not run that cmd file. According to the Distribution page, KACE is calling each attempt a success and the package has been "installed". None are showing as failures.
Any thoughts? This is our first time trying to push drivers to an already deployed OS, so I'm sure I'm doing something wrong here.
As a side thought, logging in as admin vs not doesn't make a difference. In both cases, I can run it by hand from an elevated CMD and in neither case does KACE work.
2 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
https://support.quest.com/kace-systems-management-appliance/kb/138389
Instead of using helloworld.ps1, use your own PS1
Make sure you do everything else, and see on the script's output log if "Script Have been executed successfully" is being printed on the log.
If it's there, that means the KACE agent at least tried to execute it.. but it failed.
Maybe with different credentials? - Channeler 7 years ago
But if you upgrade to K2000 version 5.0, you can use the new powershell post installation task to make this process much easier. - cserrins 6 years ago