PICAXE deployment via SCCM?

[pete]

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 should work, but it falls over with a 653 error when pushing to test clients. That implies a problem with the installer package, but the same file triggered manually works fine.

 

Wrapping it in a script has the same problem.

 

Using the same command at the CLI works without issue.

 

Has anyone managed to push PICAXE Editor 6 out using SCCM?

[nelliott]

I'm using the new MSI and it seems to be working fine, did you manage to deploy the USB drivers using SCCM?