Ivanti Automation powered by RES

Home 

Bare Metal OS deployment using WDS and Ivanti Automation

When deploying new workstations or servers, Bare Metal OS deployment usually is the first task that is performed. This task can easily be carried out by combining Microsoft Windows Deployment Services (WDS) and Ivanti Automation.

Microsoft Windows 2008 R2 has built-in capabilities of PXE, TFTP imaging and prestaging that can be automated using Ivanti Automation. This is a highly cost-effective solution that does not need any manual intervention. Workstations and servers can be deployed directly where they need to be used, without a staging process and additional transportation.

Desired behavior

Ideally, zero-touch OS deployment using WDS and Ivanti Automation occurs according to the following scenario:

  1. A new computer that is to be deployed is prestaged (enrolled), in order to determine its configuration. Prestaged computers are also called "known" computers.
  2. After being prestaged, the computer is booted and the PXE server will pick up the request. The end user must not be involved in this process by having to press F12 or any other buttons that interfere with the boot process.
  3. Preferably the NIC is the first in the boot-sequence.
  4. WDS is configured so the computer is assigned a predefined name and joined to a domain.
  5. After OS deployment, the Ivanti Automation Agent is configured either to join a Ivanti Automation Team or to execute a predefined Ivanti Automation Module that cleans up the installation or further configures the computer.
  6. After deployment, the PXE configuration should be set in such a way that the end user is not tempted to press F12. Unknown computers must not be served by PXE to avoid unintentional imaging of those computers.

Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other