Have you checked out the logs for PXE so you can at least rule that out?
SMSPXE.log.
Mike D-
From: dahe...@scana.com
To: mssms@lists.myitforum.com
Subject: [mssms] OSD + PXE assistance
Date: Thu, 24 Jul 2014 23:21:24 +0000
Posted this also in the mdt-osd forum…
I am seeing an issue where newly created device objects in VMware aren’t seeing
a required TS that is being applied to a collection in which they are a part of.
Current environment.
SCCM 2012 R2 running SQL 2012 on Windows 2012. DPs, PXE, and WDS running on
separate Windows 2012 server. Using Microsoft Orchestrator for automation.
We are in the process of stress testing our automation job and these are the
steps that are taking place. Microsoft Orchestrator initiates 5 builds at 1
minute intervals and is performing these steps below.
1.
Creates VM template in VMware
2.
Creates device object in SCCM with unique mac and name.
3.
Creates a rule in the ‘OS Provisiong’ collection for device assignment where TS
is assigned.
4.
Initiates membership update to all systems and then ‘OS Provisioning’
collection.
5.
Verifies the device object is present in ‘OS Provisioning’ collection.
6.
Starts up the VMware virtual machine.
At this point, most of the VM’s start running the TS to start the OS
deployment. Intermittently and usually the 4th machine will fail upon start
with the “Operating System not found” message. The other Windows servers will
finish successfully. If I wait a sec and then reboot the machine that had
the OS not found, it will boot just fine and start the OS installation.
All signs seem to point me to a PXE issue, but I don’t know for sure…. Any
ideas??
