.. Reminder for header structure:
  Parts (H1)          : #################### with overline
  Chapters (H2)       : ******************** with overline
  Sections (H3)       : ====================
  Subsections (H4)    : --------------------
  Subsubsections (H5) : ^^^^^^^^^^^^^^^^^^^^
  Paragraphs (H6)     : """""""""""""""""""""

.. meta::
  :description: Quickstart - Installing WAPT Server on Windows
  :stickwords: Quickstart,WAPT,Server,Install,Windows

.. |date| date::

.. role:: red

.. _quickstart_wads_linux:

###########################
Quickstart - WADS for Linux
###########################

|

****************************************************************
Deploying a Linux machine in the domain, with offline connection
****************************************************************


In this example, we will deploy a Linux machine because the computer is not eligible for Windows 11.
If you have a workstation that does not meet the Windows 11 requirements, you can recycle it as a Linux workstation.
The workstation already exists in the infrastructure, so you will need to retrieve it from the WAPT inventory.

Because your workstation is listed in the inventory, you can export it to OS Deploy using the :ref:`wads button <export_selected_host_button>`.


You can rename the hosts by using :kbd:`F2` keyboard touch

Requirements
============

  - A configured DHCP server.
  - The WAPT server must be able to exchange with the machine to be deployed.
  - Have a dns resolution with a domain controller from the console.
  - User with local administrator rights on the WAPT server.
  - User who signed the exe files ( Tools > Sign deploy file) and configuration files.

.. note::
  Official WADS documentation :ref:`here <wapt_ghosting_hosts>`


|

Creating a XML configuration
============================

- Go to the configuration panel in *OS DEPLOY*.

.. figure:: wapt-resources/WAPT-Configuration_panel.png
  :align: center
  :alt: Configuration panel

  Configuration panel

- Click on the :kbd:`+`.
- Choose a configuration name. (1)
- Uncheck the :guilabel:`For Windows` box (2)
- Don't choose a iso.
- Choose a configuration file by clicking on the document icon (in this quickstart we recommend **djoin**, so we don't have to create the machine account in Active Directory). (3)
- Choose a IPXE File Script ( *\\wapt\\templates\\wads_template\\linux\\ipxescript\\debian\\debian.ipxe*). (4)

.. figure:: wapt-resources/create_a_configuration_in_WADS_linux.png
  :scale: 75%
  :align: center
  :alt: Create a configuration in WADS for Linux

  Create a configuration in WADS for linux

- Save, you have created a configuration in WAPT. (5)

|

ADD the djoin for you desktop
=============================



* Right-click > :guilabel:`Select a Configuration`, take the configuration you have done previously and :kbd:`OK`.

- Right-click on the computer to be deployed → :guilabel:`prepare Djoin` (this allows you to specify in your Active Directory the Organizational Unit where your new machine will be registered).

  * Fill in the domain. (1)
  * Fill in the domain controller. (2)
  * Click on :guilabel:`Connect to Domain and Reload OU`. (3)
  * Prefer the :guilabel:`overwrite` option in order to re-register the computer if necessary. (4)
  * Select your desired Organization Unit. (5)
  * Save. (6)

.. figure:: wapt-resources/Edit_Djoin_linux.png
  :scale: 75%
  :align: center
  :alt: Edit Djoin for linux

  Edit Djoin for linux

- The comment :guilabel:`Exist` appears in the Djoin column.
- Select the computer to be deployed > Right-click start Deploy, an **X** appears in the :guilabel:`waiting to deploy` column.

|

On the computer to be deployed
==============================

* **Turn off the machine**

* Start the computer and **charge the boot menu** (Use F10 or F12 when the computer starts up ), select network or similar.

* Once finished, **the machine will restart automatically**.

* Once the reboot is complete, your machine is ready to go. You can log in with a domain user.

**WADS deployment is complete and your machine is registered in your WAPT inventory.**

.. note::

  If you computer don't appear in the right OU, you can identify in the console, and do a right-click :guilabel:`Windows Computer management` → :guilabel:`Update AD Group Policies on hosts`.


