iCONTROL BOOT — WINDOWS x64 TEST VOSITALARI

Windows PowerShell 5.1 yoki PowerShell 7 yetarli. Python kerak emas.
ZIPni to'liq oching; Agent va deployment papkalarini birga saqlang.

1. BOSHLASH
   deployment\START-LAB.cmd faylini ikki marta bosing.
   1 — ZIP tekshirish; 2 — Windows preflight; 3 — Diskless preflight;
   4 — diagnostika ZIP; Q — chiqish.
   PowerShell security policy scriptni bloklasa, tashkilotingiz administratoriga
   murojaat qiling. Wrapper Bypass parametrini faqat shu jarayon uchun beradi.

2. ZIPNI TEKSHIRISH
   https://i-control.uz/uz/guide/boot sahifasidagi tayyor buyruq va SHA256'dan
   foydalaning. Buyruqdagi ZIP yo'li siz yuklagan faylga mos bo'lsin:

   .\deployment\lab-tools.ps1 -Action Verify -ArchivePath C:\Downloads\PACKAGE-NAME.zip -ExpectedSha256 SHA256-FROM-GUIDE

   Natija: archive_verified; exit 0. Xato: blocked; exit 2.
   ZIP ochilmaydi yoki ishga tushirilmaydi: hash, manifest, fayl nomlari,
   Windows runtime fayllari va ichki fayl hash/hajmlari tekshiriladi.
   Hash yaxlitlikni tekshiradi; imzolangan publisher sertifikati o'rnini bosmaydi.

3. WINDOWS PREFLIGHT — LABORATORIYASIZ
   Paket ochilgan papkada PowerShell:

   .\deployment\lab-tools.ps1 -Action Check -Mode Windows

   Windows 10+, x64 process/OS, PowerShell va shu akkauntdagi mahalliy DPAPI
   roundtrip tekshiriladi. Windows, registry, task va state o'zgartirilmaydi.
   ready: ushbu tekshiruvlar o'tdi; bu UI/PXE yoki AgentKey auth testi emas.

4. DISKLESS PREFLIGHT — LABORATORIYA TAYYOR BO'LGANDA
   Linux boot-controller, ikki test PC, matching controller manifestlari,
   private state disklar, tayyor image va doimiy kiosk profil kerak.
   To'liq tayyorlash tartibi: deployment\ICONTROL-BOOT.md.
   Kiosk akkauntining o'zida PowerShell'ni elevated oching; boshqa
   administrator akkauntiga o'tmang. Yo'llar boshqacha bo'lsa moslang:

   .\deployment\lab-tools.ps1 -Action Check -Mode Diskless -InstallDir C:\iControl\Agent -StateRoot P:\iControl

   Tekshiriladi: image policy, OS iSCSI target, private non-system disk,
   manifest/serial, firmware binding, scheduled task akkaunti va autologin/shell.
   Raw config, AgentKey, Credential Manager va saqlangan DPAPI kaliti o'qilmaydi.
   Noto'g'ri disk yoki binding: blocked; o'chirib qaytadan yaratishga urinmang.
   pending: agentning alohida setup/reboot gate'ini tugatish kerak.
   maintenance: state LUN kutilmaydi; agent kiosk/enrollment boshlamasligi kerak.
   Faqat UUID firmware identity avtomatik solishtiriladi; aniqlanmasa operator
   tekshiruvi kerak. Status agentning ichki startup gate'ini almashtirmaydi.

5. DIAGNOSTIKA HISOBOTI
   Menu'da 4 ni tanlang yoki yangi fayl yo'lini ko'rsating:

   .\deployment\lab-tools.ps1 -Action Report -Mode Diskless -InstallDir C:\iControl\Agent -StateRoot P:\iControl -OutputPath C:\Users\YOUR-USER\Desktop\iControl-support.zip

   Windows rejimi uchun -Mode Windows ishlating. Menu default holatda Desktop'ga
   yangi nomli ZIP yaratadi. Hisobot avtomatik yuborilmaydi; o'zingiz ko'rib,
   kerak bo'lsa support'ga bering. Mavjud ZIP ustiga yozilmaydi.
   Ichida: preflight.json, events.json va README.txt.
   events.json eng oxirgi 4 ta agent-*.log faylining har biridan ko'pi bilan
   256 KiB texnik kategoriya hisoblarini oladi. Raw loglar, token, AgentKey,
   config kontenti, user nomlari, SID, serial va DPAPI fayllari kiritilmaydi.
   Log mavjud bo'lmasa files_scanned=0; bog'langan/symlink fayllar o'qilmaydi.

6. UCHTA RESET — ALOHIDA QABUL TESTI
   Lokal DPAPI roundtrip keyingi resetlarda profil saqlanishini isbotlamaydi.
   Mos private disk va doimiy kiosk akkauntida:

   .\deployment\test-icontrol-boot-state.ps1 -Mode Begin -StateRoot P:\iControl

   Controller boshqaruvidagi har bir haqiqiy reset bootdan keyin, jami uch marta:

   .\deployment\test-icontrol-boot-state.ps1 -Mode Verify -StateRoot P:\iControl

   Exit 3 / pending_reboots: yana reset kerak. Exit 0 / verified: uch reset o'tdi.
   Exit 2 / blocked: sababini tekshiring, tarix va markerlarni o'chirmang.
   Ikkala PC alohida identity bilan ulanishi, qayta AgentKey so'ramasligi,
   maintenance exit, missing-disk block, UI, lock/unlock va test bron oqimi
   laboratoriyada alohida tekshiriladi.
