Diagnostics v2 → IGEL / eLux / Citrix Client Check Loading config...

Client Readiness Check

This version is designed to be opened directly from an IGEL OS 12 or eLux 7 client. It cannot read protected OS settings on its own, but it can validate browser-visible signals, show likely client family, test basic readiness, and generate a report for support or operations.

Environment Checking...

Detected client Checking...

Overall readiness Checking...

Current browser Checking...

Local helper agent Checking...

Selected baseline Checking...

Checks

These checks stay inside the browser sandbox. They are useful for first-line readiness validation, but not for deep policy inspection. For IGEL UMS, Scout/eLux, or local client settings, this page should later be paired with a management backend or local helper.

About the checks

Client family – identified via User Agent. Low confidence is expected on generic Linux clients without an IGEL-specific UA string.
Browser and protocol – HTTPS or localhost is required for a secure context. HTTP triggers a warning.
Display and resolution – validated against the configured minimum (default 1280×800).
Locale and timezone – compared against expectations in config. A mismatch produces a warning, not a failure.
Endpoint tests – use no-cors fetch. A reachable URL always reports OK regardless of HTTP status code — this is a browser sandbox limitation.
Local helper agent – if the agent is running on localhost:38765, deeper OS-level checks for network, certificates, and smartcard become available.

Config

Config source pending... ?env=Pilot&baseline=igel-os12&endpoint=Portal|https://portal.example.local/

Report

Running checks...

Tip: this page now reads client-readiness-config.json by default. You can also override values with URL parameters such as ?env=Pilot, ?client=igel, or ?endpoint=Gateway|https://example.com/.