Use ReadyBlue to Troubleshoot Issues Opening and Using Venn

ReadyBlue is a diagnostic tool that identifies what device issues could be preventing Venn from starting or working properly on a device.

When you generate remote diagnostics, the ReadyBlue Device Readiness Report can be found in the ReadyBlue folder within the diagnostics folder that is downloaded when you generate remote diagnostics. It will be named ready-blue-report-<date generated>.html.

End users can also run ReadyBlue themselves and share their Device Readiness Report with you.

ReadyBlue is only available for Windows.
The Device Readiness Report will not be included in the diagnostic folder for Mac devices.

Device Readiness Report

The Device Readiness Report opens to a summary view, which contains information about the device and the user and provides an overall determination of whether or not the device is ready to run Venn based on the tests that were run.

Under Status Summary, you can expand each section to see an overview of any checks that failed, checks that determined that optimization may be needed, and checks that were passed.

ReadyBlue_Device Readiness Report.png

You can use the table of contents at left to access details about the checks that the device failed or that were flagged as needing optimization. For example, for the report above, you may want to visit the Proxy Test and Performance sections to find out what specific checks failed in order to narrow down which issues could be causing Venn not to run properly.

Use the tables below to learn more about the checks within each category and common causes for failure and flagging:

If investigating common causes does not resolve the issue, contact Venn support for additional help troubleshooting.

ReadyBlue Network Checks

Section Check Description Common Failure/Flag Causes
Services Accessibility  DNS response time Checks if the device can locate and connect to a standard set of websites in an acceptable amount of time. 
  • Network connectivity issues
  • Excessive scanning from security software
  • Presence of malware
Communication with Venn's backend API hosts Checks if the device can communicate with Venn hosts so that Venn can perform background device compliance checks, execute Venn software updates, collect analytics, and complete connectivity status checks. 
  • Network connectivity issues
  • Firewall or security settings



Communication with Venn's Devices V2 API hosts
Communication with KMS V2 API hosts
Communication with additional required hosts
Private Company Gateway UDP traffic to Private Company Gateway dedicated IPs Checks if data can be sent over the company's unique PCG IPs using the UDP communication protocol. UDP is necessary for Venn to execute DNS queries and responses as well as for supporting services like VoIP and audio and video streaming.
  • Port blocking by firewalls on the device or network routers
  • UDP traffic restrictions or blocking by network administrators
Communication using WireGuard to Private Company Gateway IPs Checks if the device can communicate to the company’s unique PCG IPs over specified WireGuard ports. Venn uses the WireGuard VPN protocol to enable devices to communicate within the PCG. 
  • Port blocking by firewalls on the device or network routers
  • UDP traffic restrictions or blocking by network administrators
Pings are able to reach Private Company Gateway IP addresses Checks if ICMP pings can be sent to the company's unique PCG IPs. ICMP pings are used to troubleshoot network connectivity issues. Venn uses pings to measure latency to the closest data center.
  • Firewall settings
  • ICMP traffic restrictions or blocking by network administrators
Proxy Test Proxy detection using certificate validation and IP checks Checks if there are proxies detected by validating certificates and checking IPs for Venn hosts. Proxies and security tools can cause conflicts with Venn, preventing DNS resolution and causing other network-related interference within the Blue Border.
  • Conflicting antivirus or security software
  • Browser extensions or add-ons
  • Firewall or security settings
Google Workspace service URLs accessible Checks if URLs related to common services for Google and Microsoft Office 365 are accessible inside and outside of the Blue Border. 
  • Conflicting antivirus or security software
  • Browser extensions or add-ons
  • Outdated DNS cache
  • Firewall or security settings
Google Account services URL accessible
Microsoft Account services URL accessible

ReadyBlue Device Checks

Section Check Description Common Failure/Flag Causes
Minimum Requirements CPU type is supported Checks if the device meets minimum requirements to run Venn. Device does not meet minimum requirements and cannot be used to run Venn.
CPU has at least 2 cores
CPU speed meets the minimum required speed
Minimum 8GB of memory installed
Page file configured correctly or irrelevant. Checks if the device has appropriate physical and virtual memory to run Venn. 
  • Paging file not managed by the OS
  • If the paging file can’t be managed by the OS, insufficient RAM and/or insufficient size of the paging file
Operating system installed on a solid state drive Checks if the device meets minimum requirements to run Venn. Device does not meet minimum requirements and cannot be used to run Venn.
Disk size greater than 128GB
Minimum of 3GB of disk space available. Checks if the device has enough disk space to install and run Venn.
  • Insufficient device storage
  • Size/number of installed programs and applications
  • Size/number of files stored on the device
Operating system version is supported. Checks if the device’s operating system is supported by Venn.
  • Operating System has not been updated
  • Device doesn’t have space or meet requirements for a supported Operating System
Performance Disk read speed greater than 201MB per second Checks if the disk speed is likely to cause performance issues. These issues would not prevent Venn from working, but they would result in a degraded experience.
  • System overloaded with background processes or tasks
  • Disk drivers not up-to-date
  • Fragmentation if the device has a HDD
  • Disk performance issues (may require replacement)
Disk write speed greater than 101MB per second
Disk latency is less than 0.6 milliseconds
Disk queue length within acceptable range of 1 or less
Disk response is less than 0.8ms
CPU usage below 80% on average Checks if the availability of CPU or RAM is likely to cause performance issues. These issues would not prevent Venn from working, but they would result in a degraded experience.
  • System overloaded with background processes or tasks
  • Insufficient CPU or RAM on the device for the user’s work (may require upgrade)
Minimum of 300MB of memory free
Time Check  Computer clock keeps time accurately Checks if the computer clock is correct. An incorrect time can cause  issues with authentication.
  • Clock is manually set to the wrong time
  • Issues with automatic update from internet servers
System Management  Powershell execution policies for all scopes set properly Checks if PowerShell scripts are able to run so that Venn can perform necessary administrative tasks. PowerShell execution policies are set to restricted for one or more of the following scopes:
  • MachinePolicy
  • UserPolicy
  • Process
  • CurrentUser
  • LocalMachine
WMI functioning Checks if Windows Management Instrumentation (WMI) is functioning. WMI allows Venn to query, monitor, and configure system components.
  • Interference from antivirus or security software
  • Issues with the operating system or updates that have not been installed
  • The WMI service was stopped or disabled
  • The WMI repository, namespaces, or classes are corrupted
  • The user account doesn’t have the necessary permissions to access WMI
  • Dependent services such as RPC (Remote Procedure Call) aren’t running

ReadyBlue Compatibility Checks

Section Check Description Common Failure/Flag Causes
Software Microsoft Office software version compatible with Venn Checks if the correct version of Microsoft Office is installed and that no conflicting software is detected. Outdated version of Microsoft Office is downloaded on the device
Microsoft Office architecture version compatible with Venn
Full-Device VPN Full-Device VPN not detected Checks if a full-device VPN is running on the device, which can prevent the internet traffic from connecting to the Private Company Gateway. Full-device VPN is installed on the device
Antivirus One active antivirus product Checks if more than one antivirus product is running on the device. Multiple antivirus products are installed on the device

ReadyBlue Secure Enclave Checks

Section Check Description Common Failure/Flag Causes
Venn Disk Venn Disk file created Checks if the Venn disk can be created and mounted. 
  • Insufficient disk space
  • Lack of administrative privileges 
  • Outdated operating system
  • The necessary drivers for the disk or storage controller may not be installed or may be outdated
  • Software such as encryption tools or backup utilities might be conflicting with disk operations
Venn Disk file mounted
Drive letter V: available Checks if the letter “V” is available for drive assignment. There is already a drive labeled with the letter V on the computer
Browser Session Test Open URL in Secure Enclave browser Checks if a browser session can open and DNS hosts can resolve inside of the Secure Enclave.
  • Network connectivity issues
  • Excessive scanning from security software
  • Presence of malware
  • Network connectivity issues
  • Firewall or security settings
DNS Test DNS hosts resolve
Google Drive hosts resolve
Microsoft 365 hosts resolve

Was this article helpful?