bigbro.pro Posted October 28, 2020 Report post Posted October 28, 2020 Hello. two weeks i can't beat the problem of loading MDT via MECM. My configure in screenshot: for two weeks now i can't get this to work. After receiving the message that you see in the VM picture. Log from SMSPXE.log. according to this manual: I do not have an MDT task creation (Step 7.) WDS and MDT are located on the same server as mecm. I have a basic configuration. those. just installation and that's it. ============> Received from client: SMSPXE 10/28/2020 1:09:34 PM 19264 (0x4B40) Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 074B0A5E Sec Since Boot: 65535 Client IP: 192.168.010.141 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000 Addr: 00:15:5d:0a:4b:07: Magic Cookie: 63538263 Options: Type=53 Msg Type: 3=Request Type=60 ClassId: PXEClient Type=97 UUID: 002374205912170f44ba9769e42f645f9c Type=93 Client Arch: Intel x86PC Type=55 Param Request List: 03013c8081828384858687 SMSPXE 10/28/2020 1:09:34 PM 19264 (0x4B40) Prioritizing local MP http://sccmdp01-msk.corp.corp.ru. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Not in SSL. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Not in SSL. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Client lookup reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) 00:15:5D:0A:4B:07, 59207423-1712-440F-BA97-69E42F645F9C: Device is not in the database. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Prioritizing local MP http://sccmdp01-msk.corp.corp.ru. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Not in SSL. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Not in SSL. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) ============> REQUEST Reply to client ([192.168.010.141:68]) Len:348 SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Operation: BootReply (2) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 074B0A5E Sec Since Boot: 65535 Client IP: 192.168.010.141 Your IP: 000.000.000.000 Server IP: 192.168.010.026 Relay Agent IP: 000.000.000.000 Addr: 00:15:5d:0a:4b:07: BootFile: smsboot\x86\wdsnbp.com Magic Cookie: 63538263 Options: Type=53 Msg Type: 5=Ask Type=54 Svr id: 192.168.010.026 Type=97 UUID: 002374205912170f44ba9769e42f645f9c Type=60 ClassId: PXEClient Type=250 02010105040000000503020014040200ba062c436f6e66696775726174696f6e204d616e61676572206973206c6f6f6b696e6720666f7220706f6c6963792e0b0101 SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) <============ REQUEST Reply (end) SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) ============> Received from client: SMSPXE 10/28/2020 1:09:34 PM 19264 (0x4B40) Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 074B0A5E Sec Since Boot: 0 Client IP: 192.168.010.141 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000 Addr: 00:15:5d:0a:4b:07: Magic Cookie: 63538263 Options: Type=53 Msg Type: 3=Request Type=60 ClassId: PXEClient Type=97 UUID: 002374205912170f44ba9769e42f645f9c Type=93 Client Arch: Intel x86PC Type=250 0d0208000e010101020006050400000005ff Type=55 Param Request List: 03013c8081828384858687 SMSPXE 10/28/2020 1:09:34 PM 19264 (0x4B40) Getting boot action for unknown machine: item key: 2046820353 SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Prioritizing local MP http://sccmdp01-msk.corp.corp.ru. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Not in SSL. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Request using architecture 9. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Not in SSL. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply> SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Request retry. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Not in SSL. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply> SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) 00:15:5D:0A:4B:07, 59207423-1712-440F-BA97-69E42F645F9C: no advertisements found SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Prioritizing local MP http://sccmdp01-msk.corp.corp.ru. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Not in SSL. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Not in SSL. SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) ============> REQUEST Reply to client ([192.168.010.141:68]) Len:280 SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Operation: BootReply (2) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 074B0A5E Sec Since Boot: 0 Client IP: 192.168.010.141 Your IP: 000.000.000.000 Server IP: 192.168.010.026 Relay Agent IP: 000.000.000.000 Addr: 00:15:5d:0a:4b:07: BootFile: smsboot\x64\abortpxe.com Magic Cookie: 63538263 Options: Type=53 Msg Type: 5=Ask Type=54 Svr id: 192.168.010.026 Type=97 UUID: 002374205912170f44ba9769e42f645f9c Type=60 ClassId: PXEClient SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) <============ REQUEST Reply (end) SMSPXE 10/28/2020 1:09:34 PM 20964 (0x51E4) Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted October 28, 2020 Report post Posted October 28, 2020 have you created and deployed a task sequence in ConfigMgr yet ? Quote Share this post Link to post Share on other sites More sharing options...
bigbro.pro Posted October 29, 2020 Report post Posted October 29, 2020 (edited) if you're talking about "Task Sequence", then I don't have paragraph "Create MDT Task Sequence". look at the penultimate picture. so I didn't create any tasks. I have a separate MDT server, it works. OS can be installed. I created an unusual image installation task the result is unfortunately the same. - like the last picture in the last post Edited October 29, 2020 by bigbro.pro Quote Share this post Link to post Share on other sites More sharing options...
bigbro.pro Posted October 29, 2020 Report post Posted October 29, 2020 I found a solution. I could not even imagine that it is necessary to deploy this step to the device Collection of "Unknown Computers" Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted October 29, 2020 Report post Posted October 29, 2020 it's only necessary to deploy to the Unknown computers collection if those are your target, for example, in a New Computer type of scenario, if however you want to deploy to existing (known) computers then you can do so to via whatever collections they are members of. Quote Share this post Link to post Share on other sites More sharing options...