FleetDeck logo
Overview
Pricing
FAQ
Sign in

Frequently Asked Questions

If you've encountered a bug, shoot us an email to support@fleetdeck.io with the following attached:
  • If concerning the Commander, zip and attach the contents of %temp%\FleetDeck (typically C:\Users\your_user\AppData\Local\Temp\FleetDeck)
  • If concerning an Agent, zip and attach the contents of %systemroot%\temp\FleetDeck (typically C:\Windows\Temp\FleetDeck)
  • If any of the above folders contain .dmp files in a reports subfolder, please include these in your email.

The Commander is used to deploy, organize and remote-desktop into Agents.

Agents run on the remote machines that you manage. Agents report system information and enable remote desktop access.
You can get a link to download the Agent software by creating a Deployment.

A Deployment is an installer configuration that can be created via the Commander. A Deployment can be downloaded as an msi for installation or shared via a link.
When the installer is run on a computer you want to manage, an Agent is created.

You can invite team members in Teams via the application menu.
When you invite team members, an email is sent to them for signup if they don't have a FleetDeck account already. All team members have equal access to Agents within your team.

You can set it up in Settings via the application menu.
You may use any TOTP Authenticator app such as Google Authenticator, Microsoft Authenticator or FreeOTP Authenticator.

The following allow outbound rules should be added to your firewall:
  • 443 (TCP)
If your firewall performs DNS filtering, allow the following FQDNs:
  • *.fleetdeck.io
  • cognito-idp.us-west-2.amazonaws.com (only required for running Commander behind a firewall)
If your firewall performs Full SSL Inspection, Full SSL Inspection or HTTPS Inspection, exempt the following FQDN from interception:
*.fleetdeck.io
The following allow outbound rules may optionally be added to improve performance:
  • 53 (UDP)
  • 443 (UDP)
  • 1337 (UDP)
  • 5060 (UDP)

We support the following x86/x64 operating systems as well as their variants:
  • Windows 8
  • Windows 8.1
  • Windows 10
  • Windows 11
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022
All server variants require GUI features to be enabled.

We support the following x64 operating systems as well as their variants:
  • Windows 10
  • Windows 11
  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022

Agents running on the following x86/x64 operating systems as well as their variants:
  • Windows 10 (1809 and above)
  • Windows 11
  • Windows Server 2019
  • Windows Server 2022

This is likely due to third-party anti-malware software that automatically quarantines or removes executables that are new and have not built reputation within their database.
If you suspect that this is not the case, please report it as a bug.

We support the following:
  • Reboot
  • Reboot to safe mode
  • Shutdown
These actions can be found by right clicking on an Agent row in the Fleet tab.
When rebooting into safe mode, the agent will attempt to reestablish a connection to the internet. If unable to do so, the Agent will automatically reboot back into normal mode within 5 minutes.

You can export all agent data by clicking the icon in the bottom right corner of the Fleet tab.
All agent data is exported recursively from the path specified in the dialog.

When Agents are deleted in the Fleet tab, they stop counting towards the number of computers in your subscription plan and can no longer be accessed.
In the future we intend to have deleted Agents automatically uninstall on the endpoints.

You can install a Deployment without GUI by executing the following:
fleetdeck-agent.exe -silent
If the same Deployment is already installed, the installation will be skipped.
If a different Deployment is already installed, it will be replaced with the new one.

You can create an MSI + MST from a Deployment installer by running the following:
fleetdeck-agent.exe -msi
This will create two files:
  • fleetdeck-agent.msi
  • fleetdeck-agent.mst
The MSI requires the MST to be used as a modification transform during install time. These files are separate in order to maintain the digital signature of the msi.
To deploy using Active Directory, perform the following steps:
  1. Create an enforced GPO for the domain
  2. Create a new Software installation package and select the msi
  3. Choose Advanced as the deployment method
  4. In the Modifications tab of the package, click Add and select the mst
You can also deploy the MSI + MST manually by running the following:
msiexec /i "fleetdeck-agent.msi" TRANSFORMS="fleetdeck-agent.mst" /qn

Anti-virus vendors occasionally upload Agent installers to virtual machines in their cloud environment for runtime analysis. When the installer is run in their environment, it will register and report as being online briefly but will generally go offline within a few minutes.
These Agents usually have randomized system information but a deterministic hostname such as ABBY-PC, as is the case with Windows Defender. If you see one of these machines, you can delete them from the Fleet tab by right-clicking on the Agent row.

You can now install the Commander using Chocolatey by running the following command:
choco install commander
The Commander is auto-updating, so there is no need to upgrade the package once installed.

We are based in Marina Del Rey, California.

Report abuse to abuse@fleetdeck.io

We currently do not have a mechanism in place to perform this.

Feel free to reach out to us at contact@fleetdeck.io
US flagcontact@fleetdeck.io
© FleetDeck Inc. 2019-2026 privacy & terms