| 2016-06-15 21:33:16 +0300 | commented answer | wmi fails to run in powershell LocalScripts I have moved the localScripts plugin execution to the non sysprep executed cloudbase-init run with some success. Looking like some plugins need to run in each pass. |
| 2016-06-13 21:49:20 +0300 | commented question | wmi fails to run in powershell LocalScripts From further investigation is seems the point in the sysprep process that cloudbase-init runs user scripts is to early. WMI is not available. I have attempted to use the exit codes to have the script re-run later but didn't help. Now I'm looking at using setupcomplete.cmd instead. |
| 2016-06-13 13:31:59 +0300 | received badge | ● Famous Question (source) |
| 2016-06-11 19:46:41 +0300 | received badge | ● Notable Question (source) |
| 2016-06-11 19:46:41 +0300 | received badge | ● Popular Question (source) |
| 2016-06-10 20:05:44 +0300 | asked a question | wmi fails to run in powershell LocalScripts I have written a powershell script that runs with the LocalScripts plugin. It's using the #ps1sysnativ lin and most of the code runs as expected. However anything that calls wmi like (gwmi win32operatingsystem).OperatingSystemSKU fails with a generic error. Has anybody ran into this? powershell transcript of the code failing. https://gist.github.com/trodemaster/a... Thanks, Blake |
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.