Attune automates and orchestrates processes to streamline deployments, scaling, migrations, and management of your systems. The Attune platform is building a community of sharable automated and orchestrated processes.
You can leverage the publicly available orchestrated blueprints to increase your productivity, and accelerate the delivery of your projects. You can open-source your own work and improve existing community orchestrated projects.
The Attune Community Edition can be downloaded for free from our ServerTribe website. You can learn more about Attune through ServerTribe's YouTube Channel.
To clone this project into your own instance of Attune, follow the Clone a GIT Project How To Instructions.
This Project contains the following Blueprints.
The Windows worker can run Linux commands using Windows Subsystem for Linux.
Performs basic tests for the built node.
Sets up the "plain" WinPE skeleton files on Windows Worker at C:\WinPE_amd64.
This folder can be copied and then it's .\media\sources\boot.wim file can be modified for an automated unattended Windows install.
This folder works for both BIOS and UEFI boot methods.
The Windows worker can run Linux commands using Windows Subsystem for Linux.
| Name | Type | Script Reference | Comment |
|---|---|---|---|
| Automation Worker Windows Base Directory | Text | automationworkerwindowsbasedirectory |
Base directory for deploying temporary files to build the ISO on a Windows Worker. eg. "C:/attune_auto_installer" |
| Automation Worker Windows Node | Windows Node | automationworkerwindowsnode |
The Windows automation worker node used to perform tasks to create the ISO. |
| Automation Worker Windows User: Administrator | Windows Credential | automationworkerwindowsuseradministrator |
Administrator user on the Windows Automation Worker node. |
| Drivers and Autounattend Drive Letter | Text | driversandautounattenddriveletter |
The Windows drive letter containing the drivers and autounattend.xml as a single letter. This will be different for each install method. D for "Single ISO" E for "Dual ISO" X for "WinPE ISO" |
| Is BIOS Boot | Text | isbiosboot |
|
| Is UEFI Boot | Text | isuefiboot |
|
| Is Win10 BIOS | Text | iswin10bios |
|
| Is Win10 UEFI | Text | iswin10uefi |
|
| Is Windows Server | Text | iswindowsserver |
|
| Is Windows Workstation | Text | iswindowsworkstation |
|
| Is WinPE Kickstart | Text | iswinpekickstart |
Set TRUE for WinPE kickstarts and FALSE for Single ISO and Dual ISO kickstarts. |
| Is Win Server BIOS | Text | iswinserverbios |
|
| Is Win Server UEFI | Text | iswinserveruefi |
|
| Kickstarted Boot Loader is BIOS | Text | kickstartedbootloaderisbios |
|
| Kickstarted Boot Loader is UEFI | Text | kickstartedbootloaderisuefi |
|
| Kickstarted Operating System Name | Text | kickstartedoperatingsystemname |
Set as: "Windows 10", "Windows Server 2016", "Windows Server 2019", "Windows Server 2022" |
| New OS Node | Basic Node | newosnode |
The New OS to be built. |
| New OS Node Subnet | Network IPv4 Subnet | newosnodesubnet |
Subnet used by the new operating system to be built. |
| New OS Organisation Name | Text | newosorganisationname |
Organisation name for the new operating system being created. |
| New OS Windows Node | Windows Node | newoswindowsnode |
|
| New OS Windows TimeZone | Text | newoswindowstimezone |
Get the full list using the PowerShell command: Get-TimeZone -ListAvailable |
| New OS Windows User: Administrator | Windows Credential | newoswindowsuseradministrator |
administrator user on the New OS to be built. |
| Post Install Setup Script Drive Letter | Text | postinstallsetupscriptdriveletter |
The Windows drive letter containing the Post Install PowerShell setup script post_install_setup.ps1 as a single letter as seen by the Windows installer. This will be different for each install method. D for "Single ISO" E for "Dual ISO" C for "WinPE ISO" |
| Samba Server IP Address | Text | sambaserveripaddress |
|
| Windows Folder On Samba | Text | windowsfolderonsamba |
The Windows folder on the Samba server. This parameter is used by startnet.cmd and can take these values: - windows10 - windows2016 - windows2019 - windows2022 |
| Automation Worker Windows Base Directory Share Path | Text | automationworkerwindowsbasedirectorysharepath |
Base directory for deploying temporary files to build the ISO on a Windows Worker. eg. "/c$/attune_auto_installer" |
| Name | Type | Comment |
|---|---|---|
| Post Install Setup PowerShell Script | Version Controlled Files | This file is called by the "" section in the autounattend.xml file. This script is run once post installation of the WIndows operating system. |
| Test File | Version Controlled Files | Test file for testing push files. |
| Win11 ISO | Large Archives | Download from https://www.microsoft.com/en-us/software-download/windows11 Please select the English (United States) version. |
| Win2016 ISO | Large Archives | Download from https://www.microsoft.com/en-us/evalcenter/download-windows-server-2016. |
| Win2019 ISO | Large Archives | Download from https://www.microsoft.com/en-us/evalcenter/download-windows-server-2019. |
| Win2022 ISO | Large Archives | Download from https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2022. |
| Windows Unattended config v2 | Version Controlled Files | |
| WinPE startnet.cmd | Version Controlled Files | The startnet.cmd is run by WinPE. This script: 1. Installs drivers from "attune_drivers". 2. Sets the IP address. 3. Mounts the Samba server that hosts the extracted Windows ISOs as the "Z" drive. 4. Runs Windows setup.exe. The Mako parameter "windowsFolderOnSamba" can have these values: - windows10 - windows2016 - windows2019 - windows2022 |
| Win10 ISO | Large Archives | Download from https://www.microsoft.com/en-us/software-download/windows10ISO/. Please select the English (United States) version. |
The collective power of a community of talented individuals working in concert delivers not only more ideas, but quicker development and troubleshooting when issues arise.
If you’d like to contribute and help improve these projects, please fork our repository, commit your changes in Attune, push you changes, and create a pull request.
Please feel free to raise any issues or questions you have.
Thank you