---
title: Creating a Local Administrator with Remote Capabilities
description: Creating a local administrator with remote capabilities
---

[Skip to content](https://support.block64.com/creating-a-local-administrator-with-remote-capabilities#main-content)

<https://support.block64.com/kb-tickets/new?hsLang=en> [Customer Portal](https://customerportal.block64.com/tickets-view?hsLang=en)

[![Logo - dark](https://support.block64.com/hs-fs/hubfs/Logo%20-%20dark.png?width=350&height=86&name=Logo%20-%20dark.png)](https://support.block64.com/?hsLang=en)

- [Home](https://support.block64.com/)
- [Insights Portal](https://insights.block64.com/login)
- Platform
  
  Show submenu for Platform

    - [Block 64](https://www.block64.com/)
    - [Why Block 64?](https://www.block64.com/#:~:text=What%20makes%2CBlock%2064%20different)
- Solutions
  
  Show submenu for Solutions

    - [Unified Visibility](https://www.block64.com/solutions/unified-visibility)
    - [Cost Optimization](https://www.block64.com/solutions/cost-optimization)
    - [Proactive Security](https://www.block64.com/solutions/proactive-security)
    - [Compliance](https://www.block64.com/solutions/continuous-compliance)
- Learn
  
  Show submenu for Learn

    - [Quick Start Guides](https://support.block64.com/getting-started)
    - [Integrations](https://support.block64.com/documentation#integrations)
    - [Blog](https://www.block64.com/blog)
- Support
  
  Show submenu for Support

    - [Trust Center](https://trust.block64.com/)
    - [Service Health](https://status.block64.com/)
    - [Partners](https://www.block64.com/partners)
    - [Contact Us](https://www.block64.com/contact)
- [Pricing](https://www.block64.com/pricing)
- [Get Started Free](https://www.block64.com/free-trial)

Open main navigation

Close main navigation

- [Home](https://support.block64.com/)
- [Insights Portal](https://insights.block64.com/login)
- Platform
  
  Show submenu for Platform

    - [Block 64](https://www.block64.com/)
    - [Why Block 64?](https://www.block64.com/#:~:text=What%20makes%2CBlock%2064%20different)
- Solutions
  
  Show submenu for Solutions

    - [Unified Visibility](https://www.block64.com/solutions/unified-visibility)
    - [Cost Optimization](https://www.block64.com/solutions/cost-optimization)
    - [Proactive Security](https://www.block64.com/solutions/proactive-security)
    - [Compliance](https://www.block64.com/solutions/continuous-compliance)
- Learn
  
  Show submenu for Learn

    - [Quick Start Guides](https://support.block64.com/getting-started)
    - [Integrations](https://support.block64.com/documentation#integrations)
    - [Blog](https://www.block64.com/blog)
- Support
  
  Show submenu for Support

    - [Trust Center](https://trust.block64.com/)
    - [Service Health](https://status.block64.com/)
    - [Partners](https://www.block64.com/partners)
    - [Contact Us](https://www.block64.com/contact)
- [Pricing](https://www.block64.com/pricing)
- [Get Started Free](https://www.block64.com/free-trial)
- <https://support.block64.com/kb-tickets/new>
- [Customer Portal](https://customerportal.block64.com/tickets-view)
- [Submit a Support Request](https://support.block64.com/kb-tickets/new)

[Submit a Support Request](https://support.block64.com/kb-tickets/new?hsLang=en)

 How can we assist you today?

- There are no suggestions because the search field is empty.

1. [Block 64 Support Center](https://support.block64.com/?hsLang=en)
2. [Documentation](https://support.block64.com/documentation?hsLang=en)
3. [Discovery: General Knowledge](https://support.block64.com/documentation?hsLang=en#discovery-general-knowledge)

# Creating a Local Administrator with Remote Capabilities

This article provides two PowerShell scripts to create a secure local administrator account (`block_svc`) with remote access capabilities via WMI, RPC, SMB and WinRM. These are tailored for both domain-joined and standalone/cloud-hosted environments, with detailed rollback scripts.

---

#### Table of Contents

1. [Overview](https://support.block64.com/creating-a-local-administrator-with-remote-capabilities#Overview)
2. [Choosing the Right Script](https://support.block64.com/creating-a-local-administrator-with-remote-capabilities#ChoosingTheRightScript)
3. [Basic Script – AD Managed Environments](https://support.block64.com/creating-a-local-administrator-with-remote-capabilities#BasicScript)
4. [Advanced Script – Standalone or Cloud Hosted Environments](https://support.block64.com/creating-a-local-administrator-with-remote-capabilities#AdvancedScript)
5. [Technical Notes on Port Configuration and System Impact](https://support.block64.com/creating-a-local-administrator-with-remote-capabilities#TechNotes)
6. [Reversion Scripts](https://support.block64.com/creating-a-local-administrator-with-remote-capabilities#ReversionScripts)

---

#### 1. Overview

To facilitate secure remote access to Windows endpoints via WMI, RPC, and SMB, in scenarios where a domain Administrator account is unavailable, a local admin account can be established with the necessary privileges and firewall configurations. Block 64 offers two script options:

- **Basic Script**: For AD-managed devices using GPO to manage firewall rules.
- **Advanced Script**: For standalone/cloud-hosted devices (e.g., Azure, AWS, Workgroup) that require local firewall configuration.

**Benefits:**

- Automates account creation
- Sets required system policies
- Reduces manual misconfigurations
- Fully reversible with rollback scripts

**Important:**

- Always test scripts in a non-production environment
- Use a unique, complex password for `block_svc`
- Advanced Script opens WMI, RPC, SMB, and WinRM ports. Ensure this complies with your internal network policies before use.

> **⚠️** Please ensure that your system's PowerShell Execution Policy allows for script execution. You can verify or temporarily allow script execution using the following command in PowerShell:
> 
> **Verify**:  
> `Get-ExecutionPolicy -List`
> 
> **Allow** (If Restricted):  
> `Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned`

 To **run** these scripts manually:

- **Copy** and **paste** the script into a text file
- Save the file with a **.ps1** extension (e.g., CreateBlockSvc.ps1)
- Right-click the file and choose "**Run with PowerShell**"

---

#### 2. Choosing the Right Script

| Environment | Use This Script | Firewall Configuration |
| --- | --- | --- |
| Domain-joined with Active Directory | Basic Script | Managed via GPO |
| Standalone, Workgroup, or Cloud | Advanced Script | Opened locally by the script |

> 💡 Tip: If using the Basic Script, configure GPO to open required ports. See: [**How to Open Ports via GPO**](https://support.block64.com/how-to-open-up-ports-on-windows-firewall-via-gpo?hsLang=en)

---

#### 3. Basic Script – AD Managed Environments

This script only creates the account and enables TokenFilterPolicy. It does **not** modify firewall rules.

```
# Elevate script if not already running as administrator$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()$windowsPrincipal = New-Object System.Security.Principal.WindowsPrincipal($windowsIdentity)$adminRole = [System.Security.Principal.WindowsBuiltInRole]::Administratorif (-not $windowsPrincipal.IsInRole($adminRole)) {    $psi = New-Object System.Diagnostics.ProcessStartInfo "PowerShell"    $psi.Arguments = "-ExecutionPolicy Bypass -File `"$PSCommandPath`""    $psi.Verb = "runas"    [System.Diagnostics.Process]::Start($psi)    exit}Clear-HostWrite-Host "=== Block 64 Local Admin Account Creation Script ===" -ForegroundColor CyanWrite-Host "This script will:" -ForegroundColor WhiteWrite-Host "- Create a local admin user 'block_svc'" -ForegroundColor WhiteWrite-Host "- Apply remote access policy (TokenFilterPolicy)" -ForegroundColor WhiteRead-Host "Press Enter to continue..."# Set TokenFilterPolicy for remote UACtry {    Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" `        -Name "LocalAccountTokenFilterPolicy" -Value 1 -Force    Write-Host "TokenFilterPolicy applied successfully." -ForegroundColor Green} catch {    Write-Host "Error applying TokenFilterPolicy: $($_.Exception.Message)" -ForegroundColor Red}# Prompt for password and create the local user$Password = Read-Host "Enter a strong password for 'block_svc'"$SecurePassword = ConvertTo-SecureString $Password -AsPlainText -ForceRemove-Variable Passwordtry {    if (Get-LocalUser -Name "block_svc" -ErrorAction SilentlyContinue) {        Write-Host "User 'block_svc' already exists. Skipping creation." -ForegroundColor Yellow    } else {        New-LocalUser -Name "block_svc" -Password $SecurePassword -Description "Block64 service account"        Write-Host "User 'block_svc' created successfully." -ForegroundColor Green    }    Set-LocalUser -Name "block_svc" -PasswordNeverExpires $true    $adminGroupSID = New-Object System.Security.Principal.SecurityIdentifier("S-1-5-32-544")    $adminGroupName = $adminGroupSID.Translate([System.Security.Principal.NTAccount]).Value    Add-LocalGroupMember -Group $adminGroupName -Member "block_svc"    Write-Host "User 'block_svc' added to group: $adminGroupName" -ForegroundColor Green} catch {    Write-Host "Error creating user or adding to group: $($_.Exception.Message)" -ForegroundColor Red}Write-Host "`n=== Setup completed successfully ===" -ForegroundColor CyanRead-Host "Press Enter to exit..."
```

After execution, use the credential `block_svc` in Block 64 tools:

- **Domain:** *(Leave blank)*
- **Username:** `block_svc`
- **Password:** *(Same one used during script execution)*

---

#### 4. Advanced Script – Standalone or Cloud Hosted Environments

This script performs the following:

- Creates `block_svc` with admin rights
- Enables TokenFilterPolicy for remote login
- Detects OS language (English, Spanish, Portuguese)
- Enables only the matching firewall rules for:
  
    - WMI
    - RPC
    - SMB
    - WinRM
- Starts the `WinRM` service if not running
- Tests Remote Registry access

```
# Elevate script if not already running as administrator$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()$windowsPrincipal = New-Object System.Security.Principal.WindowsPrincipal($windowsIdentity)$adminRole = [System.Security.Principal.WindowsBuiltInRole]::Administratorif (-not $windowsPrincipal.IsInRole($adminRole)) {    $psi = New-Object System.Diagnostics.ProcessStartInfo "PowerShell"    $psi.Arguments = "-ExecutionPolicy Bypass -NoExit -File `"$PSCommandPath`""    $psi.Verb = "runas"    [System.Diagnostics.Process]::Start($psi)    exit}Clear-HostWrite-Host "=== Block 64 Local Admin Account Creation Script ===" -ForegroundColor CyanWrite-Host "This script will:" -ForegroundColor WhiteWrite-Host "- Create a local admin user 'block_svc'" -ForegroundColor WhiteWrite-Host "- Apply remote access policy (TokenFilterPolicy)" -ForegroundColor WhiteWrite-Host "- Enable essential firewall rules (WMI, RPC, SMB, WinRM)" -ForegroundColor WhiteWrite-Host "- Start WinRM service if not running" -ForegroundColor WhiteWrite-Host "- Test Remote Registry connectivity" -ForegroundColor WhiteRead-Host "Press Enter to continue..."# Set TokenFilterPolicy for remote UACtry {    Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" `        -Name "LocalAccountTokenFilterPolicy" -Value 1 -Force    Write-Host "TokenFilterPolicy applied successfully." -ForegroundColor Green} catch {    Write-Host "Error applying TokenFilterPolicy: $($_.Exception.Message)" -ForegroundColor Red}# Prompt for password and create the local user$Password = Read-Host "Enter a strong password for 'block_svc'"$SecurePassword = ConvertTo-SecureString $Password -AsPlainText -ForceRemove-Variable Passwordtry {    if (Get-LocalUser -Name "block_svc" -ErrorAction SilentlyContinue) {        Write-Host "User 'block_svc' already exists. Skipping creation." -ForegroundColor Yellow    } else {        New-LocalUser -Name "block_svc" -Password $SecurePassword -Description "Block64 service account"        Write-Host "User 'block_svc' created successfully." -ForegroundColor Green    }    Set-LocalUser -Name "block_svc" -PasswordNeverExpires $true    $adminGroupSID = New-Object System.Security.Principal.SecurityIdentifier("S-1-5-32-544")    $adminGroup = $adminGroupSID.Translate([System.Security.Principal.NTAccount]).Value.Split("\\")[-1]    Add-LocalGroupMember -Group $adminGroup -Member "block_svc" -ErrorAction Stop    Write-Host "User 'block_svc' added to local Administrators group ('$adminGroup')." -ForegroundColor Green} catch {    Write-Host "Error creating user or setting permissions: $($_.Exception.Message)" -ForegroundColor Red}# Detect system language to apply language-specific firewall rules$culture = (Get-Culture).NameWrite-Host "`nSystem culture detected: $culture" -ForegroundColor Cyanswitch -Regex ($culture) {    "^en" {        $displayNames = @(            "Windows Management Instrumentation (WMI-In)",            "Remote Event Log Management (RPC)",            "Remote Event Log Management (RPC-EPMAP)",            "File and Printer Sharing (SMB-In)",            "Windows Remote Management (HTTP-In)"        )    }    "^es" {        $displayNames = @(            "Instrumental de administración de Windows (WMI de entrada)",            "Administración remota de registro de eventos (RPC)",            "Administración remota de registro de eventos (RPC-EPMAP)",            "Compartir archivos e impresoras (SMB de entrada)",            "Administración remota de Windows (HTTP de entrada)"        )    }    "^pt" {        $displayNames = @(            "Instrumentação de Gerenciamento do Windows (WMI-In)",            "Gerenciamento Remoto de Log de Eventos (RPC)",            "Gerenciamento Remoto de Log de Eventos (RPC-EPMAP)",            "Compartilhamento de Arquivos e Impressoras (SMB-In)",            "Gerenciamento Remoto do Windows (HTTP-In)"        )    }    default {        Write-Host "Unsupported language '$culture'. Defaulting to English rules..." -ForegroundColor Yellow        $displayNames = @(            "Windows Management Instrumentation (WMI-In)",            "Remote Event Log Management (RPC)",            "Remote Event Log Management (RPC-EPMAP)",            "File and Printer Sharing (SMB-In)",            "Windows Remote Management (HTTP-In)"        )    }}# Enable relevant rulesWrite-Host "`nEnabling essential firewall rules..." -ForegroundColor Cyanforeach ($name in $displayNames) {    try {        Enable-NetFirewallRule -DisplayName $name -ErrorAction Stop        Write-Host "Enabled rule: $name" -ForegroundColor Green    } catch {        Write-Host "Could not enable rule '$name': $($_.Exception.Message)" -ForegroundColor Yellow    }}# Start WinRM if neededWrite-Host "`nEnsuring WinRM service is running..." -ForegroundColor Cyantry {    Start-Service -Name WinRM -ErrorAction Stop    Write-Host "WinRM service started successfully." -ForegroundColor Green} catch {    Write-Host "Could not start WinRM service: $($_.Exception.Message)" -ForegroundColor Yellow}# Remote Registry testWrite-Host "`nTesting Remote Registry connectivity..." -ForegroundColor Cyan$target = $env:COMPUTERNAMEtry {    $regTest = reg query "\\$target\HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion"    Write-Host "Remote Registry access is working." -ForegroundColor Green} catch {    Write-Host "Remote Registry test failed: $($_.Exception.Message)" -ForegroundColor Red    Write-Host "Hint: Ensure the 'RemoteRegistry' service is running and the firewall is not blocking access." -ForegroundColor Yellow}Write-Host "`n=== Setup completed successfully ===" -ForegroundColor CyanRead-Host "Press Enter to exit..."
```

#### ⚠️ **This script modifies the local Windows firewall and enables WMI, RPC, and SMB ports. Use only in trusted environments.**

After execution, use the credential `block_svc` in Block 64 tools:

- **Domain:** *(Leave blank)*
- **Username:** `block_svc`
- **Password:** *(Same one used during script execution)*

---

#### 5. Technical Notes on Port Configuration and System Impact

**Ports Opened by Advanced Script**

| Protocol | Ports |
| --- | --- |
| WMI | TCP 135 + dynamic |
| RPC | TCP 135, TCP 139 + dynamic RPC ports |
| SMB | TCP 445 |
| WinRM | TCP 5985 (HTTP) |
| NetBIOS (legacy) | UDP 137/138, TCP 139 |

 **System Changes Summary**

| Change | Scope | Description |
| --- | --- | --- |
| `block_svc` account | Local | New admin-level user |
| TokenFilterPolicy | System-wide | Enables remote use of local accounts |
| Group membership | Local group | Added to Administrators group |
| Firewall rules (Advanced Script) | Local | Enables WMI, RPC, SMB, WinRM |
| WinRM service | Local | Started if not already running |

 

---

#### 6. Reversion Scripts

These scripts ensure a clean rollback. Use them during offboarding or if local credentials are no longer needed.

### Reversion for Basic Script

> ✅ Use reversion scripts to safely remove `block_svc`, and undo TokenFilterPolicy.

```
# Elevate script if not already running as administrator$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()$windowsPrincipal = New-Object System.Security.Principal.WindowsPrincipal($windowsIdentity)$adminRole = [System.Security.Principal.WindowsBuiltInRole]::Administratorif (-not $windowsPrincipal.IsInRole($adminRole)) {    $psi = New-Object System.Diagnostics.ProcessStartInfo "PowerShell"    $psi.Arguments = "-ExecutionPolicy Bypass -File `"$PSCommandPath`""    $psi.Verb = "runas"    [System.Diagnostics.Process]::Start($psi)    exit}Clear-HostWrite-Host "=== Block 64 Local Admin Rollback Basic Script ===" -ForegroundColor CyanWrite-Host "This script will:" -ForegroundColor WhiteWrite-Host "- Remove the 'block_svc' local user if present" -ForegroundColor WhiteWrite-Host "- Remove the TokenFilterPolicy registry key if it exists" -ForegroundColor WhiteRead-Host "Press Enter to continue..."# Remove user 'block_svc'try {    Remove-LocalUser -Name "block_svc" -ErrorAction Stop    Write-Host "User 'block_svc' successfully removed." -ForegroundColor Green} catch {    Write-Host "User could not be removed or does not exist: $($_.Exception.Message)" -ForegroundColor Yellow}# Remove TokenFilterPolicytry {    Remove-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" `        -Name "LocalAccountTokenFilterPolicy" -ErrorAction Stop    Write-Host "TokenFilterPolicy registry key removed." -ForegroundColor Green} catch {    Write-Host "Registry key not found or could not be removed: $($_.Exception.Message)" -ForegroundColor Yellow}Write-Host "`n=== Rollback A completed ===" -ForegroundColor CyanRead-Host "Press Enter to exit..."
```

 

---

### Reversion for Advanced Script

> ✅ Use reversion scripts to safely remove `block_svc`, undo TokenFilterPolicy, and (in Advanced Script) close firewall ports.

```
# Elevate script if not already running as administrator$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()$windowsPrincipal = New-Object System.Security.Principal.WindowsPrincipal($windowsIdentity)$adminRole = [System.Security.Principal.WindowsBuiltInRole]::Administratorif (-not $windowsPrincipal.IsInRole($adminRole)) {    Write-Host "This script needs to be run as Administrator. Relaunching..." -ForegroundColor Yellow    $psi = New-Object System.Diagnostics.ProcessStartInfo "PowerShell"    $psi.Arguments = "-ExecutionPolicy Bypass -NoExit -File `"$PSCommandPath`""    $psi.Verb = "runas"    [System.Diagnostics.Process]::Start($psi)    exit}Clear-HostWrite-Host "=== Block 64 Local Admin Rollback Advanced Script ===" -ForegroundColor CyanWrite-Host "This script will:" -ForegroundColor WhiteWrite-Host "- Remove the 'block_svc' local user if present" -ForegroundColor WhiteWrite-Host "- Remove the TokenFilterPolicy registry key if it exists" -ForegroundColor WhiteWrite-Host "- Disable firewall rules for WMI, RPC, SMB, and WinRM" -ForegroundColor WhiteRead-Host "Press Enter to continue..."# Remove local usertry {    Remove-LocalUser -Name "block_svc" -ErrorAction Stop    Write-Host "User 'block_svc' successfully removed." -ForegroundColor Green} catch {    Write-Host "User could not be removed or does not exist: $($_.Exception.Message)" -ForegroundColor Yellow}# Remove TokenFilterPolicytry {    Remove-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" `        -Name "LocalAccountTokenFilterPolicy" -ErrorAction Stop    Write-Host "TokenFilterPolicy registry key removed." -ForegroundColor Green} catch {    Write-Host "Registry key not found or could not be removed: $($_.Exception.Message)" -ForegroundColor Yellow}# Detect system language for disabling appropriate rules$culture = (Get-Culture).NameWrite-Host "`nSystem culture detected: $culture" -ForegroundColor Cyanswitch -Regex ($culture) {    "^en" {        $displayNames = @(            "Windows Management Instrumentation (WMI-In)",            "Remote Event Log Management (RPC)",            "Remote Event Log Management (RPC-EPMAP)",            "File and Printer Sharing (SMB-In)",            "Windows Remote Management (HTTP-In)"        )    }    "^es" {        $displayNames = @(            "Instrumental de administración de Windows (WMI de entrada)",            "Administración remota de registro de eventos (RPC)",            "Administración remota de registro de eventos (RPC-EPMAP)",            "Compartir archivos e impresoras (SMB de entrada)",            "Administración remota de Windows (HTTP de entrada)"        )    }    "^pt" {        $displayNames = @(            "Instrumentação de Gerenciamento do Windows (WMI-In)",            "Gerenciamento Remoto de Log de Eventos (RPC)",            "Gerenciamento Remoto de Log de Eventos (RPC-EPMAP)",            "Compartilhamento de Arquivos e Impressoras (SMB-In)",            "Gerenciamento Remoto do Windows (HTTP-In)"        )    }    default {        Write-Host "Unsupported language '$culture'. Defaulting to English rules..." -ForegroundColor Yellow        $displayNames = @(            "Windows Management Instrumentation (WMI-In)",            "Remote Event Log Management (RPC)",            "Remote Event Log Management (RPC-EPMAP)",            "File and Printer Sharing (SMB-In)",            "Windows Remote Management (HTTP-In)"        )    }}# Disable the rulesWrite-Host "`nDisabling firewall rules..." -ForegroundColor Cyanforeach ($name in $displayNames) {    try {        Disable-NetFirewallRule -DisplayName $name -ErrorAction Stop        Write-Host "Disabled rule: $name" -ForegroundColor Green    } catch {        Write-Host "Could not disable rule '$name': $($_.Exception.Message)" -ForegroundColor Yellow    }}Write-Host "`n=== Rollback B completed ===" -ForegroundColor CyanRead-Host "Press Enter to exit..."
```

- [Getting Started](https://support.block64.com/getting-started?hsLang=en#main-content)

    - [Free Trial Onboarding](https://support.block64.com/getting-started?hsLang=en#free-trial-onboarding)
    - [Start Your Subscription](https://support.block64.com/getting-started?hsLang=en#start-your-subscription)
    - [Discovery Application Installation](https://support.block64.com/getting-started?hsLang=en#discovery-application-installation)
    - [Discovery Appliance Setup](https://support.block64.com/getting-started?hsLang=en#discovery-appliance-setup)
    - [Discovery Agent Deployment](https://support.block64.com/getting-started?hsLang=en#discovery-agent-deployment)
- [Insights Reports](https://support.block64.com/insights-reports?hsLang=en#main-content)

    - [IT Asset Management](https://support.block64.com/insights-reports?hsLang=en#it-asset-management)
    - [Security](https://support.block64.com/insights-reports?hsLang=en#security)
    - [Cloud & Infrastructure](https://support.block64.com/insights-reports?hsLang=en#cloud-infrastructure)
    - [Legacy Combine User Guide](https://support.block64.com/insights-reports?hsLang=en#legacy-combine-user-guide)
- [Troubleshooting](https://support.block64.com/troubleshooting?hsLang=en#main-content)

    - [Discovery: Insights Portal](https://support.block64.com/troubleshooting?hsLang=en#discovery-insights-portal)
    - [Insights Calculations](https://support.block64.com/troubleshooting?hsLang=en#insights-calculations)
    - [Discovery: Block 64 Windows Application](https://support.block64.com/troubleshooting?hsLang=en#discovery-block-64-windows-application)
    - [Discovery: BlockBox Appliance](https://support.block64.com/troubleshooting?hsLang=en#discovery-blockbox-appliance)
    - [Block 64 Discovery Agent](https://support.block64.com/troubleshooting?hsLang=en#block-64-discovery-agent)
- [Documentation](https://support.block64.com/documentation?hsLang=en#main-content)

    - [Insights: Integrations](https://support.block64.com/documentation?hsLang=en#insights-integrations)
    - [Privacy and Security](https://support.block64.com/documentation?hsLang=en#privacy-and-security)
    - [Block 64 API](https://support.block64.com/documentation?hsLang=en#block-64-api)
    - [Discovery: General Knowledge](https://support.block64.com/documentation?hsLang=en#discovery-general-knowledge)
- [FAQs](https://support.block64.com/faqs?hsLang=en#main-content)

    - [Security](https://support.block64.com/faqs?hsLang=en#security)
    - [Block 64 Discovery](https://support.block64.com/faqs?hsLang=en#block-64-discovery)
- [New Features & Updates](https://support.block64.com/new-features-updates?hsLang=en#main-content)

    - [New Features & Updates](https://support.block64.com/new-features-updates?hsLang=en#new-features-updates)
    - [Combine](https://support.block64.com/new-features-updates?hsLang=en#combine)
    - [Block 64 Discovery](https://support.block64.com/new-features-updates?hsLang=en#block-64-discovery)
    - [Remote Discovery Agent](https://support.block64.com/new-features-updates?hsLang=en#remote-discovery-agent)
    - [Combine API](https://support.block64.com/new-features-updates?hsLang=en#combine-api)
    - [BlockBox Virtual Appliance](https://support.block64.com/new-features-updates?hsLang=en#blockbox-virtual-appliance)

[![Logomark - dark](https://support.block64.com/hs-fs/hubfs/Logomark%20-%20dark.png?width=60&height=96&name=Logomark%20-%20dark.png "Logomark - dark")](http://block64.com)

300 Geary Ave, Toronto, ON M6H 2C5, Canada  
+1 800-875-5260  
[www.block64.com](https://www.block64.com/)

<https://www.linkedin.com/company/block-64/> <https://www.reddit.com/r/Block64/> <https://www.youtube.com/@block64corp> <https://www.block64.com/contact>