> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/quick-start/bare-metal-with-vmware-workstation.md).
# Bare metal with VMware Workstation
This guide uses VMware Workstation Pro 26.0.1 to test DeployR bare-metal deployments.
Create a new virtual machine with these settings:
* **Memory:** 4 GB minimum. Allocate more for larger operating system images.
* **Processors:** 4 virtual processors.
* **Storage:** 250 GB virtual disk.
* **CD/DVD:** Mount the DeployR ISO from the `boot` folder.
* **Network Adapter:** Bridged.
The default VMware settings worked for this test. Use BIOS firmware to follow the boot flow shown below.
During OSD, DeployR will automatically download and install drivers from the VMware Tools package. They can be added as a content item inside DeployR or enabled via the "Inject Drivers from Cloud" step.
### Network setup
In **Virtual Network Editor**, map the bridged network to the physical adapter connected to your lab network. This places the VM on the same subnet as the DeployR server. It also enables PXE booting when available.
Review the VM settings, then power on the VM.
### Boot options
Press `Esc` during startup to open **BIOS Boot Manager**. Select PXE boot when it is available. Otherwise, boot from the mounted DeployR ISO for a quick test.
Configure your PXE environment before using network boot. See [Configuring PXE booting](/deployr/deployment-methods/configuring-pxe-booting.md).
### Expected deployment flow
With iPXE configured, the VM boots from the 2Pint 2PXE Server.
The boot process loads the configured DeployR boot image.
WinPE then starts. When bootstrap debugging is enabled, a minimized PowerShell prompt appears in the lower-left corner. For debug options, see [Task Sequence debugging](/deployr/troubleshooting/task-sequence-debugging.md).
DeployR displays its splash screen, initializes networking, and gathers device information. It then displays the configured authentication prompt. Sign in with credentials permitted by your DeployR authentication configuration.
Later on in the TS, when grabbing drivers from the cloud, it will detect your on VMware and download the VMware tools package, extract and apply the drivers.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.2pintsoftware.com/deployr/quick-start/bare-metal-with-vmware-workstation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
