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

.. meta::
 :description: Deploying your workstations via WADS
 :keywords: Documentation, Deployment, WAPT, WADS

.. |date| date::

.. |enterprise_feature| image:: wapt-resources/icon_wapt_enterprise.png
  :scale: 3%
  :alt: WAPT Enterprise feature only

.. _wapt_wads:

#########################################################
Deploying your workstations via WADS |enterprise_feature|
#########################################################

WADS for WAPT Automated Deployment Services was developed to provide a simple solution for Operating System deployments via WAPT.

.. hint::

  As of |date|, only the deployment of Windows versions is available.

WADS mode of operation
**********************

Schematically, deploying an :abbr:`OS (Operating System)` involves **3** steps:

1. Importing the different media and files required for the deployment, such as Operating System :mimetype:`.iso` images, driver packs and configuration files.

.. figure:: wapt-resources/wapt_wads_media-import_flow-diagram.png
  :align: center
  :alt: Flow diagram for importing the files required for the WADS deployment

  Flow diagram for importing the files required for the WADS deployment

1. Creating the boot support.

.. figure:: wapt-resources/wapt_wads_media-boot_flow-diagram.png
  :align: center
  :alt: Flow diagram for creating the booting support for the WADS deployment

  Flow diagram for creating the booting support for the WADS deployment

3. Launching the deployment on the target host using the network or a USB stick.

.. figure:: wapt-resources/wapt_wads_media-boot-launch_flow-diagram.png
  :align: center
  :alt: Flow diagram for using the boot support in the WADS deployment

  Flow diagram for using the boot support in the WADS deployment

Difference between WADS and other solutions
===========================================

* **Classic** deployment solution.

.. figure:: wapt-resources/wapt_wads_classic-deployment_flow-diagram.png
  :align: center
  :alt: Flow diagram for a classic OS deployment

  Flow diagram for a classic OS deployment

* **WADS** deployment solution.

.. figure:: wapt-resources/wapt_wads_wads-deployment_flow-diagram.png
  :align: center
  :alt: Flow diagram for a WADS deployment

  Flow diagram for a WADS deployment

.. hint::

  * The WADS operating mode respects the recommanded method of the OS vendor.
  
  * With WADS, all functionnalities are grouped on the same WAPT Server.
  
  * Therefore, there is no need to set up any additional infrastructure other than the WAPT Server.

Software differences
--------------------

.. list-table:: Differences between WADS and other methods
  :header-rows: 1
  :widths: auto
  :align: center

  * - WADS deployment Server
    - Standard MDT method
    - Benefit
  * - Uses iPXE
    - Uses :abbr:`CIFS (Common Internet File System)` file server protocol
    - No need to setup a file server and no need to open additional ports
  * - No :abbr:`OS (Operating System)` image configuration needed
    - Requires manually editing an answer file configuration
    - Simplicity, all configurations are provided by WAPT
  * - Uses HTTPS to download the Windows OS image
    - Uses CIFS to download the Windows OS image
    - The target hosts may be deployed over the internet using the USB stick method
  * - The WADS method embeds all necessary files
    - The MDT method requires assembling files from different sources
    - The deployment, the configuration and the OS updates are bundled into one WAPT software package