Streamlining Bare Metal Deployment: A Technician’s Schedule for MECM OS Implementation

Introduction

Deploying a new fleet of devices is a rite of passage for any IT team. Recently, we scoped a project to re-instigate Operating System Deployment (OSD) via MECM for a fresh fleet of 80 bare-metal devices. The goal - A zero-touch (or near zero-touch) deployment of Windows 10 22H2 that handles everything from domain joining to application installation.

Based on our recent Statement of Work (SOW), I’ve drafted this Implementation Schedule. Think of this as your technician’s checklist or runbook for replicating this success.

Phase 1: Assessment & Design (The Foundation)

Before we even touch the boot images, we need to ensure the house is in order. A failed OSD is often the result of poor network prep.

1. Infrastructure Audit

   1. Review MECM Infrastructure: Confirm the existing Management Point (MP) and Distribution Point (DP) are healthy.

   2. Resource Check: Ensure the server has sufficient CPU/RAM to handle multiple concurrent imaging sessions.

   3. Network Bandwidth: Assess the link capacity. Imaging 80 machines simultaneously can flood the network; planning for multicast or staggering builds is crucial here.

      
      

2. Network Services Configuration

   1. DHCP & DNS: Evaluate the current DHCP scope options. Ensure IP helpers are correctly pointing to the PXE-enabled Distribution Point.

   2. Firewall: Verify ports (UDP 67/68/69, 4011, etc.) are open between the client VLANs and the MECM server.

      
      

3. Design the Architecture

   1. Naming Convention: Decide on the logic for Hostname Entry (e.g., Asset Tag prompt vs. Serial Number logic).

   2. Domain Strategy: Confirm the target OU and Domain Controller connectivity for <Company domain>.

   3. Patch Management: Plan how the device will scan for updates immediately post-build.

      
      

Phase 2: Implementation (The Build)

This is where the hands-on work happens. We break this down into infrastructure config and Task Sequence (TS) creation.

1. PXE & OSD Configuration

   
   

   1. Enable PXE Support: Configure the PXE settings on the Distribution Point.

   2. Boot Images: Update and distribute the latest x86 & x64 Boot Images. Ensure network and storage drivers for the new fleet are injected into these images.

   3. DHCP Scope: Apply the final options (Option 66/67) or IP Helpers to support the rollout.

2. Task Sequence Creation

We are building a Task Sequence to deploy Windows 10 22H2. Here is the step-by-step logic required:

1. OS Package: Import the clean Windows 10 22H2 source files.

2. Customization Steps:

   1. Hostname: Add a script or UI++ step to prompt for the machine name.

   2. Domain Join: Configure the "Apply Network Settings" step to join company domain.

   3. Regional Settings: Hardcode the system locale and keyboard layout to Base Geolocation.

3. Application Injection:

   1. Add "Install Application" steps for the Basic suite.

4. Specific Apps: Ensure Microsoft Office and Sentinel One are packaged and added here.

5. Post-Deployment: Add a "Run Software Updates Scan" step to ensure the device patches immediately upon entering the OS.

   
   

Phase 3: Testing & UAT (The Validation)

Never deploy to 80 machines without validating on one.

1. Initial Pilot

Select a small control group (3-5 devices).

Run the PXE boot process and time the deployment.

Verify:

Did the device join the domain?

Is the region set to Base Geo location?

Are Office and Sentinel One installed and active?

Did the device pull the latest patches?

2. Issue Resolution

Monitor smsts.log for any driver failures or timeouts.

Adjust the Task Sequence based on errors (e.g., adding a restart step between application installs if needed).

Phase 4: Handover & Documentation (The Legacy)

The job isn't done until the paperwork is signed.

• As-Built Documentation: Create a document detailing the exact TS steps, driver versions used, and IP configurations.

• Cutover Runbook: A simple "How-To" guide for the Level 1 support team to re-image a machine in the future.

• Training: Walk the support team through the PXE boot process to ensuring they can support the new fleet.

  
  

Summary Checklist for Technicians

[ ] Assessment: Network & MECM Health Check.

[ ] Config: PXE Enabled & DHCP Options Set.

[ ] Content: Win10 22H2 & Drivers Distributed.

[ ] Task Sequence: Domain, Region, Apps configured.

[ ] Test: Pilot group validated.

[ ] Docs: As-Built created and handed over.

Ready to deploy? Double-check your drivers and happy imaging!