Upgrade Cisco 9300 Catalyst switches in Install Mode

I think you can modify a firmware template to achieve this. Haven't tried this on a C9300 but here are my thoughts.

I copied a firmware upgrade template and modified it to work for the cgr-2010 switch module (GRWIC-D-ES-2S-8PC)

The upgrade section which normally copies the bin file over can be repurposed like so:
archive download-sw ${TransferProtocol}://${StorageAddress}/${SubFolder}/${NewImageName}${CRLF}
Not this could be the request platform software package install command.

Now the file is transferred and unpacked at once. In this case the file was a tar including the bin and other important files like fpga upgrade.

The verify uploaded firmware image integrity can be adapted to look at the specific file like so:
verify /md5 flash:/grwicdes-lanbasek9-mz.152-4.EA9a/grwicdes-lanbasek9-mz.152-4.EA9a.bin 29cb2b5bb8685ead5f6c78c808317c0d${SuccessRegEx:Verified}
Note that the md5 hash of the extracted bin file was provided here since otherwise solarwinds would by default compare it to the hash of the compressed file instead which was already expanded. This can be easily determined after upgrading a single device. Yes it would be better if the firmware upgrade template was designed for the c9300 or this module and thus could understand how to do this without adaptation and I hope they do make more templates to improve the experience.

The delete recursive is a bit tricky. I posted here thwack.solarwinds.com/.../ncm-firmware-delete-directory-not-just-bin-file-existingimagepath about this issue. I only offered what I went with currently given no better option yet. Let solarwinds auto detect the largest file which takes up the most space and delete that. It leaves behind other files and folder structure that needs to be cleaned up but so long as you are always upgrading all your devices from one version to another it will be a simple matter to put together a a single job for all of device machine type x, running the target version and include all the cleanup related command once ready. It wont be time sensitive as Solarwinds will theoretically clear enough space for the new software already so it can wait till after all your devices are upgraded.

Hope this helps you, I know we have found this to not be perfect but still quite efficient.

I think you can modify a firmware template to achieve this. Haven't tried this on a C9300 but here are my thoughts.

I copied a firmware upgrade template and modified it to work for the cgr-2010 switch module (GRWIC-D-ES-2S-8PC)

The upgrade section which normally copies the bin file over can be repurposed like so:
archive download-sw ${TransferProtocol}://${StorageAddress}/${SubFolder}/${NewImageName}${CRLF}
Not this could be the request platform software package install command.

Now the file is transferred and unpacked at once. In this case the file was a tar including the bin and other important files like fpga upgrade.

The verify uploaded firmware image integrity can be adapted to look at the specific file like so:
verify /md5 flash:/grwicdes-lanbasek9-mz.152-4.EA9a/grwicdes-lanbasek9-mz.152-4.EA9a.bin 29cb2b5bb8685ead5f6c78c808317c0d${SuccessRegEx:Verified}
Note that the md5 hash of the extracted bin file was provided here since otherwise solarwinds would by default compare it to the hash of the compressed file instead which was already expanded. This can be easily determined after upgrading a single device. Yes it would be better if the firmware upgrade template was designed for the c9300 or this module and thus could understand how to do this without adaptation and I hope they do make more templates to improve the experience.

The delete recursive is a bit tricky. I posted here thwack.solarwinds.com/.../ncm-firmware-delete-directory-not-just-bin-file-existingimagepath about this issue. I only offered what I went with currently given no better option yet. Let solarwinds auto detect the largest file which takes up the most space and delete that. It leaves behind other files and folder structure that needs to be cleaned up but so long as you are always upgrading all your devices from one version to another it will be a simple matter to put together a a single job for all of device machine type x, running the target version and include all the cleanup related command once ready. It wont be time sensitive as Solarwinds will theoretically clear enough space for the new software already so it can wait till after all your devices are upgraded.

Hope this helps you, I know we have found this to not be perfect but still quite efficient.