The IP helpers / options piece is typically an either/or feature.

Just looking at the issues you report Matt I wonder if there is a change in 
functionality if you make a note of the MAC address of a new piece of kit and 
import it into a collection to which there is a TS advertised?

Can you also verify that the TS is associated to a boot image AND that boot 
image has been deployed to the PXE enabled DPs?






Sent from Windows Mail





From: Kent, Mark
Sent: ‎Thursday‎, ‎9‎ ‎January‎ ‎2014 ‎15‎:‎32
To: [email protected]






You might need to set IP Helpers on your switches.  Also, options 66/67 may 
need to be set on your DHCP scopes to point to the boot server and boot file.

 


Mark Kent (MCP)

Sr. Desktop Systems Engineer

Computing & Technology Services - SUNY Buffalo State

 



From: [email protected] [mailto:[email protected]] On 
Behalf Of Lindenfeld, Ivan
Sent: Thursday, January 9, 2014 10:24 AM
To: [email protected]
Subject: [mssms] RE: Trying to get PXE booting and Multicast working, no success

 

Matt,

 

Is multicast enabled on your network?  It’s been a few years since we attempted 
this but I think there was also a DHCP or DNS setting that needed to be 
changed/added.

 

It’s not just SCCM setting unfortunately.

 


Ivan Lindenfeld

Sr. Systems Engineer

Enterprise Deployment / SCCM

Fidelity National Financial | Jacksonville, Florida

 



From: [email protected] [mailto:[email protected]] On 
Behalf Of Atkinson, Matt
Sent: Wednesday, January 08, 2014 7:54 PM
To: '[email protected]'
Subject: [mssms] Trying to get PXE booting and Multicast working, no success

 

Sorry if this is a wall of text but I’ve been struggling to get this up and 
running for the techs responsible for imaging.

 

We are migrating our imaging process from MDT over to SCCM. The server we were 
using for MDT is Server 2008 standard and has been added as a distribution 
point in SCCM it previously had the WDS role installed on it to distribute the 
MDT boot images over PXE. I put together an SCCM boot disc using the 
instruction posted by Johan here: 
http://www.deployvista.com/Default.aspx?tabid=70&EntryID=54

 

I’m trying to enable multicast and PXE using SCCM so I removed the WDS role 
from the server, waited a few minutes, then went to the DP properties in the 
SCCM console and checked the box to enable PXE and Multicast. I enabled the OS 
images, boot discs, and task sequences to be transported via PXE/Multicast. I 
can see that SCCM reinstalled the WDS role on the DP (I don’t see any other 
configuration when looking at WDS for boot images, figure it’s all handled 
within SCCM) but when I try and PXE boot a client machine on the same subnet it 
is unsuccessful. The SMSPXE.log entries from the DP are below. It basically 
gets a DHCP address and then says that no boot filename is received.

 

Not sure if I missed a step, or if there are problems because of previously 
having WDS installed on the box, or if I’ve got something completely wrong some 
where else. For what it’s worth, if I boot from the disc I created using the 
Johan instructions over PXE it works fine and I am able to complete task 
sequences. Also of note, these logs are from brand new computers that haven’t 
touched our domain yet and are not in SCCM. I have task sequences deployed to 
unknown computers and enabled unknown computer support on the PXE boot options 
of the DP.

 

Set media certificate in transport              SMSPXE               1/8/2014 
4:24:52 PM       3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:52 PM      
 3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:52 PM      
 3616 (0x0E20)

Client lookup reply: <ClientIDReply><Identification Unknown="1" 
ItemKey="16780046" ServerName="" 
ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

                SMSPXE               1/8/2014 4:24:52 PM       3616 (0x0E20)

PXE::CBootImageManager::FindMatchingArchitectureBootImage            SMSPXE     
          1/8/2014 4:24:52 PM       3616 (0x0E20)

Set media certificate in transport              SMSPXE               1/8/2014 
4:24:52 PM       3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:52 PM      
 3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:52 PM      
 3616 (0x0E20)

Client boot action reply: <ClientIDReply><Identification Unknown="0" 
ItemKey="16780046" ServerName="" 
ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
 LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" 
OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" 
Mandatory=""/></ClientIDReply>

                SMSPXE               1/8/2014 4:24:52 PM       3616 (0x0E20)

Client Identity: 83e8a7d9-ce03-41a1-8160-c24f7ed45a74               SMSPXE      
         1/8/2014 4:24:52 PM       3616 (0x0E20)

Set media certificate in transport              SMSPXE               1/8/2014 
4:24:52 PM       3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:52 PM      
 3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:52 PM      
 3616 (0x0E20)

PXE::CBootImageManager::FindMatchingArchitectureBootImage            SMSPXE     
          1/8/2014 4:24:56 PM       3616 (0x0E20)

Set media certificate in transport              SMSPXE               1/8/2014 
4:24:56 PM       3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:56 PM      
 3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:56 PM      
 3616 (0x0E20)

Client boot action reply: <ClientIDReply><Identification Unknown="0" 
ItemKey="16780046" ServerName="" 
ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
 LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" 
OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" 
Mandatory=""/></ClientIDReply>

                SMSPXE               1/8/2014 4:24:56 PM       3616 (0x0E20)

Client Identity: 83e8a7d9-ce03-41a1-8160-c24f7ed45a74               SMSPXE      
         1/8/2014 4:24:56 PM       3616 (0x0E20)

Set media certificate in transport              SMSPXE               1/8/2014 
4:24:56 PM       3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:56 PM      
 3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:24:56 PM      
 3616 (0x0E20)

PXE::CBootImageManager::FindMatchingArchitectureBootImage            SMSPXE     
          1/8/2014 4:25:04 PM       3616 (0x0E20)

Set media certificate in transport              SMSPXE               1/8/2014 
4:25:04 PM       3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:25:04 PM      
 3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:25:04 PM      
 3616 (0x0E20)

Client boot action reply: <ClientIDReply><Identification Unknown="0" 
ItemKey="16780046" ServerName="" 
ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
 LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" 
OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" 
Mandatory=""/></ClientIDReply>

                SMSPXE               1/8/2014 4:25:04 PM       3616 (0x0E20)

Client Identity: 83e8a7d9-ce03-41a1-8160-c24f7ed45a74               SMSPXE      
         1/8/2014 4:25:04 PM       3616 (0x0E20)

Set media certificate in transport              SMSPXE               1/8/2014 
4:25:04 PM       3616 (0x0E20)

Set authenticator in transport    SMSPXE               1/8/2014 4:25:04 PM      
 3616 (0x0E20)

PXE::CNotifyTimer::RegisterTimeout      SMSPXE               1/8/2014 4:33:50 
PM       3220 (0x0C94)

 

 

Thanks in advance.

-Matt

Reply via email to