FluxDeployDocs
Topics: Answer Files

Answer Files

FluxDeploy uses a settings-driven approach to generate unattend.xml answer files. Rather than managing individual XML templates per recipe, all deployment answer file settings are configured globally in Settings > Deployment > Unattend Settings and applied to every deployment.

Configuration Sections

Computer Identity

  • Name Prefix - A prefix for auto-generated computer names (e.g., "WS-" produces "WS-001", "WS-002")
  • Product Key - Windows 10/11 product key for activation. Leave blank for volume license or KMS environments.
  • Windows Server Product Key - used only for Windows Server images (never the field above). See Deploying Windows Server.
  • Registered Owner / Organization - Displayed in System Properties

Local Administrator

  • Admin Password - The local administrator account password set during Windows setup
  • Auto-Logon - Enable automatic login after deployment with a configurable logon count (useful for FirstBoot task sequences that need an interactive session)

OOBE Settings

  • Skip EULA - Bypass the End User License Agreement screen
  • Skip OOBE Screens - Skip the out-of-box experience (privacy settings, Cortana, etc.)
  • Disable Windows Update during OOBE - Prevent Windows Update from running during initial setup, which can significantly delay first login

Regional Settings

  • Input Locale / Keyboard - Keyboard layout (e.g., 0409:00000409 for US English)
  • System Locale - Language for non-Unicode programs
  • User Locale - Date, time, and number formatting

Domain Join

  • Enable Domain Join - Toggle domain membership configuration
  • Domain Name - Active Directory domain FQDN
  • Organizational Unit (OU) - Target OU path for the computer account
  • Domain Account / Password - Credentials with permission to join machines to the domain

Windows Server

When the image is Windows Server the same settings produce a Server-shaped document: only the Windows Server Product Key (if set), no client-only OOBE elements, and the built-in Administrator is used instead of a second account. See Deploying Windows Server.

How It Works

During the deployment's answer file phase (Phase 12), the agent requests the rendered unattend.xml from the server via GET /api/images/{id}/answerfile. The server's AnswerFileService combines the global settings with machine-specific data (hostname, MAC address) to produce the final XML.

The rendered answer file is written to W:\Windows\Panther\unattend.xml, where Windows Setup reads it on first boot.

Security

  • Domain join credentials are stored encrypted in the server database
  • The answer file service sets XmlResolver = null to prevent XML External Entity (XXE) attacks
  • Answer file settings sync to relay servers via the manifest, allowing relays to render answer files independently

Note: The legacy per-recipe answer file template system has been removed. All unattend configuration is now centralized in Settings.