Alright, so I made a rookie mistake and forgot to add the client that I manually added to a deployment collection. Once I did that it was able to PXE boot successfully. I booted 2 other new unknown computers and they were able to PXE boot without issue.
The only other thing that didn't seem to work was multicast. I've got scheduled multicast enabled and the clients didn't not attempt to wait to download for the timeout duration or minimum number of clients, each started their own download of the OS wim file. Anyone have any troubleshooting links for multicasting? From: [email protected] [mailto:[email protected]] On Behalf Of Atkinson, Matt Sent: Thursday, January 09, 2014 9:22 AM To: [email protected] Subject: RE: [mssms] RE: Trying to get PXE booting and Multicast working, no success I just restarted WDS and there is no change. I'm not even totally sure the machine is getting DHCP. Before when I was successfully using WDS I would get a response back on the screen telling me the network config (IP, subnet mask, gateway). Now I am not getting that, it goes from requesting DHCP.... to no boot file received PXE-E53. I just don't why it worked fine before I attempted to let SCCM control the PXE booting. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Matthias Berroth Sent: Thursday, January 09, 2014 8:54 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Trying to get PXE booting and Multicast working, no success After removing, did you restart WDS? Sometimes I had this kind of issue after deleting the computer objects. WDS restart helped for me From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Atkinson, Matt Sent: Donnerstag, 9. Januar 2014 17:46 To: '[email protected]' Subject: RE: [mssms] RE: Trying to get PXE booting and Multicast working, no success The error below was being caused by a device already listed as an unknown computer. I removed all of the unknown computers from SCCM and was able to successfully import this device. However it still is not able to PXE boot, same information in the SMSPXE.log file as I entered below. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Atkinson, Matt Sent: Thursday, January 09, 2014 8:22 AM To: '[email protected]' Subject: RE: [mssms] RE: Trying to get PXE booting and Multicast working, no success Alright, so I wasn't able to add the machine to SCCM manually. Entered the MAC address and a name, but get this error at the end of the wizard: [cid:[email protected]]Error: Following computers have not been imported: Name: TestPXE MAC Address: 74:46:A0:BC:EE:E2 SMBIOS GUID: Source Computer: Choose Target Collection: User Driven Installation Errors The SMS Provider reported an error.ConfigMgr Error Object:instance of SMS_ExtendedStatus{ Description = "Unable to save changes"; ErrorCode = 2152205056; File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspsite.cpp"; Line = 1296; Operation = "ExecMethod"; ParameterInfo = "SMS_Site"; ProviderName = "WinMgmt"; StatusCode = 2147749889;}; From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Atkinson, Matt Sent: Thursday, January 09, 2014 8:15 AM To: '[email protected]' Subject: RE: [mssms] RE: Trying to get PXE booting and Multicast working, no success Do I need the IP helpers even though the devices are on the same subnet? I thought that was only needed if we need to PXE boot across subnets, which we would never need to do. I'll try adding the device to SCCM instead of having it be an unknown computer. Boot image has been distributed to PXE enabled DP, and is the boot disc required for the task sequence we want to run. Will report back results in a few minutes. -Matt From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Thursday, January 09, 2014 8:01 AM To: '[email protected]' Subject: RE: [mssms] RE: Trying to get PXE booting and Multicast working, no success +1 ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Thursday, January 09, 2014 9:32 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Trying to get PXE booting and Multicast working, no success The IP helpers? Definitely need them. The DHCP options? No, no, no! In fact, setting DHCP options can interfere with successful PXE booting when IP helpers are in place. I highly recommend that DHCP options not be utilized. Cheers, Trevor Sullivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Thursday, January 9, 2014 9:28 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Trying to get PXE booting and Multicast working, no success 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]> [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Thursday, January 9, 2014 10:24 AM To: [email protected]<mailto:[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]> [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 ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
<<inline: image001.png>>
