Historically, attempting to push PICAXE out using their MSI using SCCM falls over during packaging with path depth errors due to Rev Ed's love of deep paths.
But calling the executable with picaxeeditor6.exe /S /v/qn (that missing space isn't a typo) and then using the MSI method for detection...
↧