iControl Boot — Diskless va Windows testi 1-qism: Windows’da ZIP va DPAPI tekshiruvi. 2-qism: laboratoriyada ikki PC, alohida identity va uchta reset sinovi. Windows build va native DPAPI tekshiruvi o‘tgan. PXE, interfeys va uchta resetdan keyingi ishlash laboratoriyada tekshiriladi. 1-QISM · WINDOWS TEST PAKETI Windows 10/11 x64 test PC yoki VM va Windows PowerShell 5.1 / PowerShell 7 yetarli. Python o‘rnatish kerak emas. 1. ZIPni yuklab oling. Paketni to‘liq oching. Agent/ va deployment/ papkalarini birga saqlang. deployment/START-LAB.cmd faylini ikki marta bosib vositalar menyusini ochishingiz mumkin. 2. Arxivni tekshiring. Paket ochilgan papkada PowerShell oching va quyidagi buyruqni nusxalang. Fayl nomi va SHA256 tayyor; ZIP Downloads’dan boshqa joyda bo‘lsa ArchivePath’ni moslang. Natija: archive_verified, exit 0. $zip = "$env:USERPROFILE\Downloads\iControl-agent-boot-lab-1.4.88-win-x64-20261101T073451Z-9250b86b.zip" $expected = 'de947c7c48b3ef2d6cfa74fa8aad6dddd0b0f4c4207082a0ff189f50e2791384' if ((Get-FileHash -LiteralPath $zip -Algorithm SHA256).Hash -ieq $expected) { powershell.exe -NoLogo -NoProfile -ExecutionPolicy Bypass -File .\deployment\lab-tools.ps1 -Action Verify -ArchivePath $zip -ExpectedSha256 $expected } else { throw 'ZIP SHA256 mismatch' } 3. Natijaga qarab davom eting. Hash, manifest, xavfli fayl yo‘llari va ichki fayllar yaxlitligi tekshiriladi; hech narsa extract yoki execute qilinmaydi. blocked / exit 2 bo‘lsa, ZIP va yo‘lni tekshiring. Bu Windows agent paketi. Linux boot-controller va PXE/iSCSI infratuzilmasi 2-qism uchun alohida tayyorlanadi. LABORATORIYASIZ WINDOWS TESTI Oddiy Windows 10/11 x64 kompyuter yoki VM uchun 8 qadam. PowerShell 5.1 yoki 7 bilan ZIP, Windows preflight, DPAPI va diagnostikani ketma-ket tekshiring. 1. ZIPni yuklab, oching. Yuqoridagi ZIP tugmasidan yangi paketni yuklang. Downloads ichida iControl-Lab papkasiga oching. Uning ichida Agent va deployment papkalari ko‘rinsin. Bu yo‘riqnomadagi buyruqlar shu joylashuvdan foydalanadi. 2. ZIP yaxlitligini tekshiring. PowerShell ochib, quyidagi tayyor buyruqni nusxalang. ZIP nomi va SHA256 tayyor yozilgan; ZIP Downloads’dan boshqa joyda bo‘lsa $zip yo‘lini moslang. Natija archive_verified bo‘lishi kerak. Hash mos kelmasa, shu paket bilan davom etmang. hardware_verified:false va ui_launch_verified:false laboratoriya hamda interfeys qabul testi hali alohida ekanini bildiradi. cd "$env:USERPROFILE\Downloads\iControl-Lab" $zip = "$env:USERPROFILE\Downloads\iControl-agent-boot-lab-1.4.88-win-x64-20261101T073451Z-9250b86b.zip" $expected = 'de947c7c48b3ef2d6cfa74fa8aad6dddd0b0f4c4207082a0ff189f50e2791384' if ((Get-FileHash -LiteralPath $zip -Algorithm SHA256).Hash -ieq $expected) { powershell.exe -NoLogo -NoProfile -ExecutionPolicy Bypass -File .\deployment\lab-tools.ps1 -Action Verify -ArchivePath $zip -ExpectedSha256 $expected } else { throw 'ZIP SHA256 mismatch' } 3. Windows preflight’ni bajaring. deployment\START-LAB.cmd faylini ikki marta bosing va 2 — Windows preflight’ni tanlang. Administrator sifatida ochish shart emas. windows, architecture, powershell va dpapi bandlari passed, umumiy status ready bo‘lishi kerak. blocked chiqsa, o‘sha banddagi hint’ni o‘qing. Menyu bir amal bajaradi; keyingi tekshiruv uchun uni qayta oching. 4. DPAPI sinov faylini yarating. Win + R orqali powershell.exe -NoProfile -ExecutionPolicy Bypass oching va quyidagi buyruqni bajaring. Bypass faqat shu PowerShell jarayoniga tegishli. dpapi-test.bin yaratiladi va DPAPI test file created chiqadi. Bu haqiqiy AgentKey’ga tegmaydigan sinov ma’lumoti. So‘ng PowerShell oynasini yoping. & { $ErrorActionPreference = 'Stop' cd "$env:USERPROFILE\Downloads\iControl-Lab" . .\deployment\boot-acceptance-tools.ps1 $path = "$env:USERPROFILE\Downloads\iControl-Lab\dpapi-test.bin" $data = [Text.Encoding]::UTF8.GetBytes('icontrol-lab-test') [IO.File]::WriteAllBytes($path, (Protect-IControlAcceptanceData $data)) 'DPAPI test file created' } 5. Yangi PowerShell oynasida tekshiring. Xuddi shu Windows akkauntida Win + R orqali powershell.exe -NoProfile -ExecutionPolicy Bypass bilan yangi oyna oching. Quyidagi buyruq DPAPI OK chiqarishi kerak. Test faylini hozircha o‘chirmang. & { $ErrorActionPreference = 'Stop' cd "$env:USERPROFILE\Downloads\iControl-Lab" . .\deployment\boot-acceptance-tools.ps1 $path = "$env:USERPROFILE\Downloads\iControl-Lab\dpapi-test.bin" $data = Unprotect-IControlAcceptanceData ([IO.File]::ReadAllBytes($path)) if ([Text.Encoding]::UTF8.GetString($data) -ceq 'icontrol-lab-test') { 'DPAPI OK' } else { throw 'DPAPI test failed' } } 6. Oddiy Windows restart’dan keyin takrorlang. Ishlaringizni saqlab, kompyuterni Restart qiling. O‘sha Windows akkauntiga kiring va yangi PowerShell oynasida quyidagi buyruqni yana bajaring. Yana DPAPI OK kutiladi. Bu oddiy lokal restart testi; diskless reset qabul testi laboratoriyada alohida o‘tkaziladi. & { $ErrorActionPreference = 'Stop' cd "$env:USERPROFILE\Downloads\iControl-Lab" . .\deployment\boot-acceptance-tools.ps1 $path = "$env:USERPROFILE\Downloads\iControl-Lab\dpapi-test.bin" $data = Unprotect-IControlAcceptanceData ([IO.File]::ReadAllBytes($path)) if ([Text.Encoding]::UTF8.GetString($data) -ceq 'icontrol-lab-test') { 'DPAPI OK' } else { throw 'DPAPI test failed' } } 7. Diagnostika ZIP’ini yarating. START-LAB.cmd’ni qayta oching, 4 — Diagnostics ZIP, keyin W — Windows’ni tanlang. Desktop’da yangi iControl-support-....zip yaratiladi. Ichida preflight.json, events.json va README.txt bo‘lsin. Agent hali ishlatilmagan kompyuterda files_scanned:0 odatiy. Hisobot lokal qoladi va avtomatik yuborilmaydi. 8. Sinov faylini tozalang. Barcha tekshiruvlar tugagach, PowerShell’da quyidagini bajaring. Faqat shu yo‘riqnomada yaratilgan dpapi-test.bin o‘chiriladi. ZIP, paket va diagnostika hisobotini saqlab qo‘yishingiz mumkin. Remove-Item -LiteralPath "$env:USERPROFILE\Downloads\iControl-Lab\dpapi-test.bin" Muvaffaqiyat mezoni: archive_verified → ready → yangi oynada va oddiy restart’dan keyin DPAPI OK → diagnostika ZIP’i yaratilishi. PXE va uchta diskless reset sinovi laboratoriya bosqichida bajariladi. AVTOMATIK PREFLIGHT Tekshiruv read-only: Windows sozlamalari, disk, task, marker va identity o‘zgartirilmaydi. AgentKey hamda config kontenti o‘qilmaydi. 1. Windows tekshiruvi. Laboratoriyasiz boshlang. OS/process x64, PowerShell va shu Windows akkauntidagi mahalliy DPAPI roundtrip tekshiriladi. powershell.exe -NoLogo -NoProfile -ExecutionPolicy Bypass -File .\deployment\lab-tools.ps1 -Action Check -Mode Windows 2. Diskless tekshiruvi. Laboratoriya tayyor bo‘lganda kiosk akkauntining o‘zida PowerShell’ni elevated oching. Image policy, OS iSCSI target, private disk/serial, manifest, UUID firmware binding, scheduled task akkaunti va autologin/shell tekshiriladi. powershell.exe -NoLogo -NoProfile -ExecutionPolicy Bypass -File .\deployment\lab-tools.ps1 -Action Check -Mode Diskless -InstallDir C:\iControl\Agent -StateRoot P:\iControl 3. Statusni o‘qing. ready / exit 0 — shu rejimdagi tekshiruvlar o‘tdi. pending / exit 3 — agentning alohida setup yoki reboot bosqichi kerak. maintenance / exit 3 — maintenance boot aniqlandi. blocked / exit 2 — hint’dagi sababni bartaraf eting. Preflight agentning startup gate’i yoki uchta reset qabul testini almashtirmaydi. UUID firmware identity aniqlanmasa, operator tekshiruvi kerak. 2-QISM · DISKLESS LABORATORIYA Linux boot-controller, ikkita test PC, tayyor Windows maintenance image, doimiy kiosk profil va har PC uchun private state disk kerak. 1. Pilot image tayyorlang. Agent/ papkasini image ichidagi C:\Lab\Agent manziliga ko‘chiring. iCafe billing/lock autostartni faqat pilot image’da o‘chiring. Windows shell explorer.exe, autologin va administrator huquqli kiosk akkaunt oldindan tayyor bo‘lsin. 2. Image’ga agentni joylashtiring. Paketdagi deployment papkasidan skriptlar birga tursin. Buyruqni administrator sifatida bajaring. LAB\Kiosk va YOUR-PILOT-API.example qiymatlarini o‘z test akkauntingiz va pilot API manzilingizga almashtiring; IQN prefix controller bilan bir xil bo‘lsin. .\deployment\prepare-icontrol-boot-image.ps1 ` -AgentBuildDir C:\Lab\Agent ` -KioskUser 'LAB\Kiosk' ` -IqnPrefix 'iqn.2026-10.uz.i-control.lab' ` -StateRoot P:\iControl ` -ServerUrl 'https://YOUR-PILOT-API.example' ` -ICafeDisabledOnPilotImage 3. Shared image’ni toza saqlang. AgentKey, club enroll token, boshqa PC config yoki DPAPI fayllarini umumiy image’ga nusxalamang. Batafsil shartlar ZIP ichidagi deployment/ICONTROL-BOOT.md’da. HAR PC UCHUN IDENTITY Oddiy bootda controller OS diskni LUN 0 va shu PC’ning private state diskini LUN 1 orqali beradi. Maintenance bootda state disk ulanmaydi. 1. Controller manifestini oling. station-identity pc01 orqali pc01.boot-station.json yarating. pc02 uchun alohida manifest kerak; har faylni mos test PC’ga xavfsiz administrator yo‘li orqali ko‘chiring. 2. State diskni tekshiring. Kutilgan serial bilan mos keladigan bo‘sh private diskni qo‘lda tayyorlab, P: harfini bering. Boot yoki system diskni tanlamang. Quyidagi skript diskni formatlamaydi. 3. Manifestni o‘rnating. Agent to‘xtatilgan bo‘lsin. Alohida administrator akkauntidan bajaring; pc02’da uning o‘z manifestini tanlang. .\deployment\initialize-icontrol-boot-state.ps1 -ManifestPath C:\Setup\pc01.boot-station.json -StateRoot P:\iControl 4. Agentni ishga tushiring. Kiosk akkauntida birinchi boot binding yaratadi va reboot talab qiladi. Keyingi alohida bootda gate o‘tgach per-PC provisioning orqali ulang. Har PC tizimda alohida identity bo‘lib ko‘rinsin. DPAPI · UCHTA RESET Testni agent ishlaydigan kiosk akkauntida bajaring. Private disk, Windows profil va akkaunt o‘zgarmasligi kerak. 1. Testni boshlang. ZIP ochilgan papkada bir marta Begin buyrug‘ini bajaring. .\deployment\test-icontrol-boot-state.ps1 -Mode Begin -StateRoot P:\iControl 2. Uch marta haqiqiy reset qiling. Controller boshqaruvidagi har bir reset bootdan keyin Verify buyrug‘ini bajaring. Bir bootda takroriy chaqirish yangi reset sifatida sanalmaydi. .\deployment\test-icontrol-boot-state.ps1 -Mode Verify -StateRoot P:\iControl 3. Natijani o‘qing. Exit 3 / pending_reboots — yana alohida reset kerak. Exit 0 / verified — uch reset testi o‘tdi. Exit 2 / blocked — disk, manifest, akkaunt yoki DPAPI sababini tekshiring. Xato bo‘lsa test tarixi va markerlarni o‘chirib gate’ni chetlab o‘tmang. Muammoni mavjud qaydlar bilan tekshiring. DIAGNOSTIKA ZIP’I Muammo bo‘lsa START-LAB menyusida 4 ni tanlang yoki buyruq orqali yangi hisobot yarating. 1. Hisobotni yarating. Quyidagi buyruq diskless uchun. Oddiy Windows tekshiruvi uchun -Mode Windows ishlating. Mavjud ZIP ustiga yozilmaydi; boshqa nom tanlang. Menyu avtomatik yangi nom bilan Desktop’ga saqlaydi. powershell.exe -NoLogo -NoProfile -ExecutionPolicy Bypass -File .\deployment\lab-tools.ps1 -Action Report -Mode Diskless -InstallDir C:\iControl\Agent -StateRoot P:\iControl -OutputPath "$env:USERPROFILE\Desktop\iControl-support.zip" 2. Ichidagi ma’lumotlar. preflight.json — ruxsat etilgan statuslar; events.json — oxirgi 4 ta agent logining har biridan ko‘pi bilan 256 KiB bo‘yicha kategoriya hisoblari; README.txt — hisobot chegaralari. Xom log, token, AgentKey, config kontenti, user nomi, SID, serial yoki DPAPI fayli yo‘q. 3. O‘zingiz ko‘rib ulashing. Hisobot lokal yaratiladi va avtomatik yuklanmaydi. Kerak bo‘lsa support’ga yuboring. files_scanned=0 bo‘lsa, o‘qiladigan agent loglari topilmadi; bu bloklangan holat haqida preflight olishga to‘sqinlik qilmaydi. YAKUNIY TEKSHIRUV Quyidagi natijalarni ikkala test PC uchun ham qayd qiling. 1. Identity va ulanish. pc01 va pc02 alohida ko‘rinadi; uch resetdan so‘ng agent qayta AgentKey so‘ramasdan ulanadi. 2. Maintenance va bloklash. Maintenance bootda agent sessiya/kiosk boshlamasdan chiqadi. State disk yo‘q yoki manifest boshqa PC’niki bo‘lsa startup bloklanadi. 3. Test sessiyasi. Pilot klubda alohida test sessiyasi, lock/unlock va bron oqimini tekshiring. 4. Muammoni yuborish. Qadam, JSON status/exit code, Windows versiyasi va test PC nomini qayd qiling. AgentKey, token va DPAPI fayllarini yubormang.