When creating the component in Datto RMM, you should be able to upload the MSI file. Then you can call it via the script by just giving it the file name (the component uploads the file to the working directory).
For the token, you can create a variable called %token% via the UI, which will cause Datto RMM to prompt the token every time the component is scheduled.
I have run the script with mostly success. A few computers had the script fail because WinRE was corrupt, or missing, or whatever. You would think that if WinRE wasn't present, the update would be skipped and not repeatedly notify you that it failed, but that's Microsoft for you.
Your Framework 16? That's great! Mine had an issue where the GPU just disappeared until the BIOS updated. It's been a few days now, and it seems to be rock solid. Most of my issues were GPU related.
The Framework 13, yes. I bought my wife one. I bought another for a cousin. My company has been deploying them for other users. They have been nothing but spectacular.
The Framework 16, it's still early, but it's been riddled with bugs. The latest driver pack from late April seems to have fixed most of the issues I've been having, so we'll see, but based on my experience so far, I can't recommend anyone buy it until the get a few more driver and BIOS patches out.
Strangely enough, I may be able to help...
When creating the component in Datto RMM, you should be able to upload the MSI file. Then you can call it via the script by just giving it the file name (the component uploads the file to the working directory).
For the token, you can create a variable called %token% via the UI, which will cause Datto RMM to prompt the token every time the component is scheduled.
So your batch "script" would be:
msiexec /qn AsioAgentInstaller.msi TOKEN=%token%