stop on BITS download errors

reject 0 byte dsa-collector.exe before launching

README.md

@@ -1,13 +1,21 @@
 # Management Scripts
 
 Most scripts here require the Tools.ps1 script. You can dot source that script like this:
-    . $([Scriptblock]::Create((New-Object Net.WebClient).DownloadString('https://dev.emberkom.com/emberkom/management-scripts/raw/branch/master/Tools.ps1')))
+
+```powershell
+[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
+. $([Scriptblock]::Create((New-Object Net.WebClient).DownloadString('https://dev.emberkom.com/emberkom/management-scripts/raw/branch/master/Tools.ps1')))
+```
+
+On older Windows PowerShell/.NET configurations, select TLS 1.2 **before** the first HTTPS download. The TLS setting inside `Tools.ps1` cannot help download `Tools.ps1` itself. See [Microsoft's PowerShell TLS guidance](https://learn.microsoft.com/en-us/security/engineering/solving-tls1-problem#update-windows-powershell-scripts-or-related-registry-settings).
 
 You can then run any of the scripts using the Run-Script function:
     Run-Script -LivePSScript Script-Name
 
 If you're using an RMM tool, the scripts in the /rmm directory are all that's needed to hook the main script in this directory.
 
+For DSA collection, paste [rmm/Get-DSAManifest.ps1](rmm/Get-DSAManifest.ps1) into the RMM caller, preserving its configured platform variables. This caller selects TLS 1.2 before downloading, stops on bootstrap failure, and dot-sources the downloaded tools in the caller's scope. Updating the repository alone will not change an existing RMM caller.
+
 ## Uploading files
 
 After dot-sourcing `Tools.ps1`, scripts can upload a completed file to the Emberkom FileDrop:
@@ -31,4 +39,5 @@ Offline tests (no uploads or notifications):
 ```powershell
 powershell.exe -NoProfile -File .\tests\Upload-File.Tests.ps1
 powershell.exe -NoProfile -File .\tests\Get-DSAManifest.Tests.ps1
+powershell.exe -NoProfile -File .\tests\Download-File.Tests.ps1
 ```