Update deployments/automation/FOG Project.md

deployments/automation/FOG Project.md

@@ -125,3 +125,182 @@ At this point, you will be prompted to login to the website hosted by FOG Projec
     
     - /etc/vsftpd.conf <=> /etc/vsftpd.conf.1777937213
     - /etc/exports <=> /etc/exports.1777937213
+
+## Disorganized Next Steps (Under Construction)
+
+After DHCP is correctly pointing clients to the FOG server (Options 66/67 or `next-server`/`filename`), the next phase is **PXE boot workflow + host registration and image management**—not user authentication at boot.
+
+Short answer: **No, you do not need to create a PXE login user.** FOG does not use traditional authentication during PXE boot. Instead, it uses a **menu-driven iPXE environment** and **host registration + task assignment** from the web UI.
+
+---
+
+## What Actually Happens After DHCP is Set
+
+Once DHCP is configured:
+
+1. Client boots → gets IP + bootfile
+2. Loads **iPXE from FOG**
+3. Connects to FOG server
+4. Displays **FOG PXE menu**
+5. From there:
+
+   * Register host
+   * Deploy image
+   * Run tasks
+
+---
+
+## Recommended Next Sections for Your Document
+
+You should continue with something like this:
+
+---
+
+### Validate PXE Boot
+
+Before doing anything else, confirm PXE is working end-to-end.
+
+* Boot a test machine on the same network
+* Ensure:
+
+  * It gets an IP from DHCP
+  * It downloads `undionly.kpxe` (BIOS) or `snponly.efi` (UEFI)
+  * It reaches the **FOG iPXE menu**
+
+Expected result: You see a FOG menu (not a login prompt)
+
+---
+
+### Register a Host in FOG
+
+FOG needs to know about devices before imaging.
+
+#### Option 1: Register via PXE Menu (most common)
+
+From the PXE menu:
+
+* Select: **Perform Full Host Registration and Inventory**
+* Enter:
+
+  * Hostname
+  * Optional description/location
+
+This creates a host object in FOG.
+
+#### Option 2: Pre-create in Web UI
+
+* Go to: `FOG Management → Hosts → Create New Host`
+* Add:
+
+  * MAC address
+  * Hostname
+
+---
+
+### Create and Capture an Image
+
+Before deploying, you need an image stored in FOG.
+
+#### Create Image Definition
+
+* Navigate: `Images → Create New Image`
+* Set:
+
+  * Name
+  * Image Type:
+
+    * `Single Disk - Resizable` (most common)
+  * Storage group (default is fine)
+
+---
+
+#### Assign Image to Host
+
+* Go to the host you registered
+* Set the **Image** field to your new image
+
+---
+
+#### Capture Image (Upload from a reference machine)
+
+On your “golden image” machine:
+
+1. Boot via PXE
+2. Register it (if not already)
+3. In Web UI:
+
+   * Select host
+   * Click **Capture**
+4. Reboot machine → it uploads disk to FOG
+
+---
+
+### Deploy Image to a Host
+
+Once an image exists:
+
+1. Assign image to target host
+2. Schedule a **Deploy Task**
+3. Boot target machine via PXE
+
+No login required — it will automatically start imaging if a task is assigned.
+
+---
+
+## Important Clarification (This Answers Your Question Directly)
+
+> “Do we need to set up a user to login via PXE?”
+
+**No.** FOG uses:
+
+* MAC address identification
+* Task-based automation
+* Optional menu interaction
+
+There is:
+
+* ❌ No PXE login system by default
+* ❌ No per-user authentication during boot
+* ✅ Central control via the web UI
+
+---
+
+## Optional (Advanced Sections You Might Add Later)
+
+If you want to make your doc more complete:
+
+### Secure the Environment
+
+* Change default credentials (`fog/password`)
+* Enable HTTPS (you skipped this earlier)
+* Restrict PXE boot via VLANs or DHCP policies
+
+### UEFI vs BIOS Handling
+
+* BIOS → `undionly.kpxe`
+* UEFI → `snponly.efi`
+
+### Automating Deployments
+
+* Auto-assign hosts
+* Use host groups
+* Schedule multicast deployments
+
+### Storage Optimization
+
+* Separate `/images` to a larger disk
+* NFS tuning
+
+---
+
+## Suggested Next Heading for Your Doc
+
+```md
+### Validate PXE Boot and Access FOG Menu
+```
+
+followed by:
+
+```md
+### Register Hosts and Prepare Images
+```