עברית
Motion
AccessibilityPrivacy
Case study09 / 152024 – 2025

Assessment Center IT Modernisation

One ready-made Windows installation, copied to every exam computer at the IDF's assessment center for colonels: identical, locked down and quick to restore.

Role
IT modernisation lead, end to end
Organisation
Tikshuv AKA – the C4I and digital branch of the IDF Personnel Directorate (AKA)
Period
2024 – 2025
Context
Military service at Tikshuv AKA
Team and credits
  • Idan Achrak — IT lead: image, setup kit, rollout; servers with Noam
  • Noam Shadmi — Co-built the servers: domain, shared drives, Exchange
The idea in one picture: one image and one setup kit on a USB stick, so every exam station gets the same system, the same apps and the same settings, managed from central servers. A diagram drawn from the project's files.

01 / The challenge

The assessment center for colonels is where the IDF assesses lieutenant-colonels for promotion to colonel. Candidates go through psychological tests and questionnaires, individual and group simulations and personal interviews, and the confidential results are one of the sources for promotion and placement decisions.

That puts the computers at the centre of a high-stakes day. Every candidate must get the same system, nothing may break or pop up in the middle of an exam, and a faulty computer has to be back in a known state quickly. Yet each computer was prepared on its own, one at a time, without one organised way to build it or restore it.

  • High-stakes, confidential assessments of officers
  • Every candidate needs an identical station
  • Computers prepared one at a time
  • No quick way back to a known state

02 / What I built

I moved everything that is the same on every computer into one unified Windows image: Hebrew Windows 10 Pro with Hebrew Office 2021, everyday tools, the same Start menu and taskbar, and exam-day settings built in. It installs from one USB stick with an answer file that answers every other setup question: the technician only picks the disk.

A short setup kit then does what differs from machine to machine: the station's own name and domain join, the IDF boot logo and a desktop-lockdown step, each one logged. Behind the stations is the server side, which Noam Shadmi and I set up together: a Windows Server domain controller, shared drives for the exam files and an Exchange mail server, running as virtual machines with a backup copy.

How it came together

  1. Aug 2024First plan, with an AI assistantA custom Hebrew ISO with Office built in. Office would not install that way, so I changed the method.
  2. May 2025Kit groundwork31 driver packages and the everyday tools collected for offline install, and a script that renames a computer and joins the domain in one step.
  3. 8 May 2025Kit V5: per-machine setupA 24-action menu that configured each laptop on its own. I tested it function by function and marked what worked.
  4. 26 May 2025Layout and boot logoThe shared Start menu and taskbar, and the IDF boot logo first tested on the reference laptop.
  5. 4 Jun 2025The image is builtKit V6 with 9 actions, the final answer file, sysprep and capture: a 16.6 GB bootable image, MerkazWin10.iso.
  6. 5 Jun 2025First stations from the imageLaptops installed from the image, then put through the kit's boot-logo and domain-join steps, each run logged.

03 / Highlights

01

One image, every station

Hebrew Windows 10 Pro and Hebrew Office 2021, with the same tools and settings, installed identically on every laptop from one USB stick.

02

Hands-off installation

Windows answers its own setup questions (language, keyboards, time zone, Wi-Fi and policies) from a prepared file while it installs. The technician only picks the disk.

03

A setup menu that records every step

One menu does the few steps that differ from computer to computer: its name and joining the center's network, the boot logo and locking the desktop. It also installs 31 driver packages, and every step is recorded.

04

Exam-day protections built in

Camera off, no surprise updates, no ads, pop-ups or Copilot, and 11 unneeded apps removed, all built into every station.

05

Central management

Every station is managed from the center's own servers: the shared exam files and the mail, with a backup copy.

06

AI-assisted engineering

I planned the build with Gemini and ChatGPT from my requirements, then tested it on real laptops and refined it version by version.

04 / Screens

10 screens
The deployment workflow in two lanes: "Build once" on a reference laptop (Windows, software offline, one desktop for all, generalise and capture, bootable USB), then "Every station" (boot from the USB, hands-off install, IDF boot logo, join the domain, desktop lockdown, ready station)
01 How it works: the image is built once on a reference laptop and put on one USB stick; every station installs from it hands-off and is finished by a few logged kit steps. Each card names the file it comes from. A diagram drawn from the project's files.
Before vs after: kit V5, "Every laptop set up one by one, by script", 24 menu actions and 1,142 lines; in the middle what moved into the image and what is new in it; kit V6, "One image + a short kit", 9 menu actions and 459 lines
02 From per-PC setup to one image: everything that is the same on every computer moved into the image, and the kit kept only what differs per machine. Counts read from the two kit versions.
Eight cards titled "Ready for exam day": camera off, no surprise updates, no ads or pop-ups, no Copilot or Cortana, telemetry off, 11 apps removed, joins the center's Wi-Fi, hardened by default
03 Ready for exam day: eight protections that the answer file sets on every station while Windows installs, with nothing to configure by hand. Each card is checked against the answer file.
The exam-center environment: a server host with two virtual servers (domain and exam files; mail server) and a backup, the center network and exam Wi-Fi in the middle, and on the right the exam stations and the USB stick that installs or restores any of them
04 The exam-center environment: two virtual servers, set up by Noam Shadmi and me, run the domain, the shared drives and the mail; every station runs the same image and joins the domain under its own name. Server roles are read from the servers' names and the kit; addresses and names are left out.
What is inside the unified image, "Windows 10 Pro For Merkaz": six facts on the left, and on the right the Start menu tiles and the taskbar every user gets, laid out right to left as Hebrew Windows shows them
05 Inside the unified image: Windows 10 Pro 22H2 in Hebrew, Hebrew Office 2021, three everyday tools, and the same Start menu and taskbar for every user. The Start menu is re-drawn from the exported layout file and the answer file.
A console window, "Administrator: Merkaz-V6.bat", showing the kit's Setup menu and the driver installer's progress bar at package 16 of 31
06 The setup kit: one menu, one key per task, and 31 driver packages installed silently with a progress bar. An illustration: the menu text is copied from the script, and the progress lines are made with the script's own formula.
A black boot screen with the IDF emblem above the centre
07 What a station shows at power-on: the IDF emblem in place of the laptop maker's logo. Re-rendered at the exact position the boot-logo installer recorded on a station.
The laptop model and the 31 driver and firmware packages grouped by maker: Intel drivers 16, Dell apps 7, Realtek drivers 3, firmware updates 5
08 Hardware and drivers: Dell Latitude 5450-class laptops, and the 31 driver and firmware packages (3.8 GB) the kit keeps offline for them. The model is read from the BIOS package name and the boot-logo logs.
Four steps titled "AI-assisted, human-verified": plan with an AI assistant (with the real prompt), test it for real, iterate the kit, verify on the laptops
09 AI-assisted, human-verified: I planned the build with Gemini and ChatGPT, then tested every step on real laptops. The prompt lines are copied from my own planning notes.
Timeline from August 2024 to 5 June 2025: first plan with an AI assistant, kit groundwork, kit V5, layout and boot logo, the image is built, first stations from the image
10 From the first plan to the first stations. Dates come from the files themselves: the planning notes, the kit's file dates, the ISO, the image metadata and the kit's logs.

05 / Impact

44stations installed from one image
20 minto prepare a station, instead of 4–6 hours by hand
1choice by hand while Windows installs: the technician only picks the disk
9steps to set up each computer, down from 24

The center's IT went from preparing each computer on its own to one organised, repeatable workflow: build the image once, install any station from one USB stick, and finish it with a few logged steps. 44 stations in 16 rooms were installed from the image, and about 12 assessment cycles of four days each ran on them. Preparing a station took 20 minutes instead of 4–6 hours by hand, and stations were reinstalled from the USB stick 7 times.

On every station a candidate gets the same system, apps and settings, with the exam-day protections built in. A faulty station goes back to the known state from the same USB stick, and every step leaves a log, so what happened on each laptop can be checked. As the common setup moved into the image, setting up each computer shrank from 24 steps to 9.

06 / Role and tech

I was in charge of modernising the assessment center's IT, from the plan to the rollout. I worked out what the stations need on an assessment day, then planned, tested and built the whole station side on my own: the unified Windows image and its answer file, the setup kit and its logs, and the one-step domain join. Noam Shadmi and I set up the server side together: the domain controller, the shared drives and the Exchange mail server.

I used Gemini and ChatGPT as planning partners: I wrote my requirements as a prompt and asked for the exact commands, then tried the plan on real hardware. When the first method failed, I moved to the standard enterprise method (a reference laptop, sysprep and a captured image), tested the kit function by function, and verified the rollout in the logs. The AI made me faster; the design, the testing and the result are mine.

Tech

  • Windows 10 Pro 22H2
  • autounattend.xml
  • Sysprep
  • Windows ADK (OSCDIMG)
  • PowerShell
  • Batch
  • Office Deployment Tool
  • Active Directory
  • Windows Server 2022
  • Microsoft Exchange
  • VirtualBox
  • HackBGRT
  • Office LTSC 2021
  • Gemini
  • ChatGPT

How it's built

The image is Hebrew Windows 10 Pro 22H2, set up on a reference laptop, generalised with sysprep and captured as one install.wim. The Windows ADK's OSCDIMG built the 16.6 GB bootable ISO around it, with an autounattend.xml answer file that sets the language and runs four PowerShell phases for network, policies and clean-up. The kit is a menu-driven Batch script plus a PowerShell domain-join script; Office installs offline through the Office Deployment Tool, and HackBGRT sets the boot logo. The servers run Windows Server 2022 with Active Directory and Exchange, as VirtualBox virtual machines. Installed, it takes 40.5 GB on each station, all of it from one USB stick.

I turned the assessment center's computers from one-off setups into one repeatable process.

Build the image once, install any station from one USB stick and check every step in the logs.

Chapters