PC Won't Start a Session — What to Do

PC Won’t Start a Session — What to Do

Symptom: administrator clicks “Start Session” in the CRM, but nothing happens on the PC — the screen doesn’t lock, no timer appears.

When This Happens

• PC shows “online” status but the command doesn’t reach the agent
• Agent hung or running on an outdated version
• PC UUID in the CRM doesn’t match what’s in the agent (mismatch after reinstallation)
• Rate is deactivated or not assigned to the PC’s zone
• Client’s balance is insufficient for the selected rate
• Disk protection prevented the agent from executing the command (reboot required after removal)

Quick Checks — Under 5 Minutes

1. Check PC status in the Hall section — the card must be green (“Free”). Grey means offline — first restore the connection.

2. Confirm the selected rate is active — open Rates, find the rate and check its status. A deactivated rate is unavailable for launch.

3. Check the client’s balance — the client’s balance must cover the minimum rate cost. If not — top up or select a cheaper rate.

4. Try another PC — if a session starts on the neighboring machine, the problem is with that specific PC, not the rate or client.

5. Check the error message — the CRM shows an error code or text near the button. Write it down for diagnostics.

If That Doesn’t Help — Go Deeper

Restart the IZI Boot Agent

1. Go to the problem PC
2. Find the IZI Agent icon in the system tray (bottom right corner)
3. Right-click → Restart
4. Wait 15–20 seconds — the agent will restore its connection to the server
5. Return to CRM and try starting the session again

If there’s no tray icon — the agent is not running. Find the IZI Agent shortcut on the desktop or Start menu and run it as Windows administrator.

Check the Agent UUID

After reinstalling Windows or cloning an image, the UUID in the agent may not match the one recorded in the CRM. This is one of the most common causes of broken session launch with a correctly displayed online status.

1. Open Settings → Devices in the CRM
2. Find the PC, copy its UUID
3. On the PC itself, open IZI Agent settings (tray icon → Settings)
4. Compare the UUID — they must match character for character

If UUIDs don’t match: in the CRM, recreate the device record (new UUID), reinstall the agent with this UUID.

Check Disk Protection State

If disk protection was just removed via CRM — the agent requires a reboot for correct operation.

1. In the Hall section, click the PC → check the shield icon (disk protection)
2. If protection was just removed — reboot the PC via CRM: PC card → Restart
3. After reboot, the agent starts without protection and commands execute normally

Check the Agent Version

An outdated agent may ignore commands in the newer format from an updated CRM.

1. Open Settings → Devices
2. In the “Version” column, find the problem PC
3. If its version is behind the other machines — enable Auto-update client in the device card and reboot the PC

Check Agent Logs

On the problem PC, open the agent log:

• Path: C:\Program Files\IZI Agent\logs\ (or equivalent installation path)
• Open the latest .log file by date
• Look for lines with ERROR or FAILED near the session launch attempt time

Copy the errors found — they’ll speed up support diagnostics.

Prevention

• Enable Auto-update client on all PCs in the Devices section — the agent will update without administrator involvement.
• After creating a new disk image via IZI Boot, verify with a test session launch on one PC before deploying to the whole hall.
• If the club changed ISP or reconfigured the router — restart the agent on all machines.
• Periodically check in the Devices section that all PCs have the same agent version.

FAQ

See Also

• PC Offline in IZI — What to Do
• Session Stuck — How to End It
• IZI Boot — How the Agent Works on a PC
• Connecting Computers to IZI
• Common Errors and Codes in IZI