QB-Flow ConnectWise RMM Setup

ConnectWise RMM Setup

To get started with automating QuickBooks updates in ConnectWise RMM, create a PowerShell action and run it against the Windows devices you want to update. QB-Flow can be deployed silently through ConnectWise RMM by downloading the QB-Flow executable, passing your Customer ID, and writing a local deployment log to the endpoint.

Get Customer ID

Get your Customer ID that was emailed to you when you subscribed to QB-Flow. Your Customer ID will look similar to: cus_XXXXXXXXXXXXXXXX

Replace Your_Customer_ID in the script below with your assigned Customer ID.

Create the ConnectWise RMM PowerShell Action

In ConnectWise RMM:

1. Open Automation and create a new PowerShell script / action.
2. Name it something like QB-Flow Deployment.
3. Paste the script below.
4. Save the action.
5. Run it against a small test group before deploying broadly.

PowerShell Deployment Script

# QB-Flow Deployment for ConnectWise RMM
# Run as a ConnectWise RMM PowerShell action

# Enter your Customer ID, which can be found in your Welcome Email after subscribing to QB-Flow
$CustomerId = "Your_Customer_ID"

# Log file location
$LogFile = Join-Path "C:\Windows\Temp" ("qbflow_{0:yyyyMMdd_HHmmss}.log" -f (Get-Date))

# URL to download the QB-Flow executable
$QBUpdateURL = "https://flowdevsblob.blob.core.windows.net/qbflow/QB-flow.exe"

# Destination path for the QB-Flow executable
$QBDestination = "C:\Windows\Temp\qb-flow.exe"

# Download the file
Invoke-RestMethod -Uri $QBUpdateURL -OutFile $QBDestination

# Execute QB-Flow with the Customer ID; merge stdout + stderr into the log
& $QBDestination "/customerid" $CustomerId *>&1 | Out-File -FilePath $LogFile -Encoding utf8

Write-Host "Output captured to $LogFile"

Deployment Notes

We recommend running the action against 1 to 3 test endpoints first before deploying to all devices.

The deployment log is written to: C:\Windows\Temp\qbflow_[timestamp].log
Example: C:\Windows\Temp\qbflow_20260505_143000.log

If the deployment fails, review the log file on the endpoint and confirm that:

• The endpoint has internet access
• PowerShell is allowed to run through ConnectWise RMM
• The endpoint can download from the FlowDevs Azure Blob URL
• Endpoint security or application control is not blocking execution from C:\Windows\Temp
• The correct Customer ID was entered in the script

Verifying a Successful Run

QB-Flow doesn't pop a "success" dialog when it finishes. Instead, there are two reliable signals you can check on the endpoint:

1. The log file exists. QB-Flow writes a log to C:\Windows\Temp\qbflow_<yyyyMMdd_HHmmss>.log on every run. If a recent log is there, it ran.
2. The QuickBooks installer folder is empty (or no longer contains the latest .msi / .cab files). This is intentional. The QuickBooks updater uses the presence of those files as its trigger to apply an update. QB-Flow removes them after applying the release so Intuit can't re-trigger the same update outside your scheduled window.

Do not open the QuickBooks Update window to verify a run

The QuickBooks Update window inside QuickBooks Desktop is not a passive status screen. Simply opening it can re-enable Intuit's automatic update service in the background, even if you never click "Update Now." That's the exact behavior QB-Flow is built to prevent.

If you want to confirm QB-Flow ran, check the log file. That is the source of truth, not the in-app Update window.

Quick verification checklist

• Recent log present at C:\Windows\Temp\qbflow_*.log ✔
• QuickBooks installer folder empty or pruned of latest installers ✔
• Nobody opened the QuickBooks Update window during or after the run ✔

If the log is missing entirely, the script never executed. The usual culprits are AV blocking the signed executable, or a firewall blocking the download URL: https://flowdevsblob.blob.core.windows.net/qbflow/QB-flow.exe.

Optional Reboot

A reboot is not always required for QB-Flow deployment, but you may schedule one through ConnectWise RMM after the action runs if that matches your normal patching or maintenance process. For larger rollouts, we recommend scheduling deployment and reboot tasks during a maintenance window.