Windows Administration

• FACEIT Anti-Cheat: Fix the Restart Loop by Disabling the Wi-Fi Adapter

  FACEIT Anti-Cheat: Fix the Restart Loop by Disabling the Wi-Fi Adapter FACEIT Anti-Cheat can get stuck repeatedly asking you to restart to "complete the installation." On affected machines, disabling the onboard Wi-Fi adapter stops the loop and lets the Anti-Cheat launch normally. Quick fix: disable the onboard Wi-Fi adapter in Device Manager (Network adapters → right-click the wireless adapter → Disable device), then relaunch the Anti-Cheat. Symptoms When you launch FACEIT Anti-CheaFew readers

• 🛠️ Running the Native TPM Pre-Attestation Task & Checking Measured Boot

  🛠️ Running the Native TPM Pre-Attestation Task & Checking Measured Boot Here is the complete manual guide to running the built-in health check and verifying your system's Measured Boot logs, script-free. 📋 Step 1: Find and Trigger the Built-In Task Windows already maintains this task natively. You just need to locate and wake it up. Press Win + R, type taskschd.msc, and hit Enter to open Task Scheduler. In the left sidebar, navigate through the foldersFew readers

ggRock Administration

• Converting your Array from RAID0-RAID10 and RAID10-RAID0

  ## This article details steps necessary to convert from a RAID0 Array configuration to a RAID10 redundant configuration and back again. ### **Problem** If you did not configure a rFew readers

• ggRock Server NIC speed checking

  ## This article describes steps necessary to check the NIC speed of your ggRock Server using the ifconfig command. ### **Check ggRock Server NIC Speed** 1. Access the server consolFew readers

• Active Directory Support

  Enabling Active Directory Support in ggRock This guide outlines the steps to enable Active Directory (AD) Support for your system images within the ggRock Web UI. Once configured, any machine booting from the modified image will automatically attempt to bind to your AD domain. ⚠️ Critical Requirement: NetBIOS Naming Conventions Before enabling Active Directory, ensure your Machine Names in ggRock adhere to Microsoft NetBIOS standards. Failure to follow these rules will prevent machFew readers

ggRock Troubleshooting

• Keep Writebacks doesn't get Enabled

  **Problem:** Keep writeback fails to get enabled even after enabling it multiple times. ![](https://storage.crisp.chat/users/helpdesk/website/-/a/f/d/6/afd6941e8bc7d800/image-26_1yFew readers

• When using a RAID 5 Array, space is not displayed appropriately in the ggRock Web UI Array Tab

  ### **Problem** The ggRock Array is configured as RAID 5. After RAID parity, the Array usage/free space is misrepresented which may result in running out of space on the array premFew readers

• ggRock Machines missing from Machines tab after Linux Kernel Update - HTTP 5xx Server Error No More network devices

  This article details linux administration tasks necessary if a Linux kernel update results in an inability for ggRock to function. ### **Problem** ggRock Machines are missing from Few readers

• Booting Many ggRock Machines at Once Results in a large portion of the PCs not loading data on boot (files missing on System and Games drive

  Problem Restarting numerous PCs, all load normally, however some are missing data (missing files from Games or System image drives in Windows). Solution Access the Grafana logging facility NOTE: Refer to the Stats Article for information on how to access the Grafana*** logging facility to monitor performance of your ggRock Server. If you have enabled VMs on your ggRock server, set the network log toFew readers

• Cannot delete old snapshots to free up space (Internal Server Error)

  **Problem** When attempting to delete snapshots, "Internal Server Error" may be displayed at the top-right corner of the ggRock Web UI. The ggRock Log may contain the following errFew readers

• Getting Device Ready Boot Loop After Image Creation

  ### Problem After creation of a new image using the ggRock Image Creation Tool (In this case, Windows 10 Education Edition Build 21H1), the system's boot loop (In this case, AlienwFew readers

• Diskless PCs Fail to PXE Boot After a Meraki/Cisco Switch Firmware Upgrade (STP Edge-Port / PortFast Fix)

  Diskless PCs Fail to PXE Boot After a Meraki/Cisco Switch Firmware Upgrade (STP Edge-Port / PortFast Fix) Diskless client PCs stop PXE booting fleet-wide because the switch's access ports no longer forward traffic immediately on link-up. The fix is to mark those ports as edge ports (PortFast / BPDU Guard). Field Detail Applies to ggRock + ggLeap diskless deployments behind a managed switch Affected switches | Meraki-managed Catalyst, Cisco IOS-XE, and any switch runnFew readers

• ggRock client fails to connect to the server (SignalR negotiate returns 405)

  ggRock client fails to connect to the server (SignalR negotiate returns 405) A redirect in the ggRock server's Nginx config can stop the ggRock client from communicating with the server, which appears as the client failing to start and looping. This article explains why it happens, how to confirm it, and how to fix it. Symptoms The ggRock client fails to start and immediately shuts down, looping on every boot. The client cannot communicate with the ggRock server, so any function thFew readers

• Grafana shows N/A and Prometheus won't stay running (duplicate command-line flag)

  Grafana shows N/A and Prometheus won't stay running (duplicate command-line flag) When Prometheus exits on startup with a "flag cannot be repeated" error, Grafana panels show N/A or no data. This is usually caused by the same flag being set in two places. This article shows how to confirm it and fix it so it survives future updates. Symptoms Grafana panels show N/A or display no statistics. The Prometheus service won't stay running; systemctl status prometheus shows it failedFew readers

• Troubleshooting ggRock Client Agent Not Starting at Boot

  🛠️ Troubleshooting: ggRock Client Agent Not Starting at Boot In some cases, especially during trial installations or new deployments, a client machine may fail to appear under the Hardware tab in the ggRock UI. This is often caused by the ggRock Client Agent not launching at system boot due to a missing registry entry under HKEY_CURRENT_USER. This article walks you through how to identify and resolve this issue quickly. ❓ Symptoms Machines do not appear in the ggRock **HardwarFew readers

ggRock Settings

• ggRock Settings Graphical Overview

  Few readers

ggRock Array

• ggRock ZFS Array Planner

  ggRock Array PlannerFew readers

ggRock Installation

• III. - 🐧 Install Debian Linux 13

  This guide walks you through installation of the Debian OS on your ggRock server. Table of Contents I. -📥 How to Download Debian and Rufus II. - 💾 Create a Bootable Debian Installer III. - 🐧 Install Debian Linux 🎯 You Are Here [**IV. - 🖥 Install the ggRock Server ApplicaFew readers

Debian Server OS Administration

• 🌐 Set System Language/Locale to en_US.UTF-8 (Required for ggRock)

  ### ❗ Problem The ggRock Server Application **requires the system locale to be set to** `en_US.UTF-8` to function properly. Using a different locale may cause: * Errors on the **ArFew readers

Debian Server OS Troubleshooting

• ggRock Server Offline - Disk Full

  GGRock Server Offline — Disk Full (Log Files) Applies to: GGRock servers running on Debian Linux Signs / Symptoms Unable to access the GGRock Web UI or Debian control panel — locally or via port 443 / 9090 Login attempts return: "The server didn't respond in time. Please try again later." Root Cause The /var/log partition has filled up with oversized logFew readers

Previous articles