locked
There are no task sequence available for this computer RRS feed

  • Question

  • Hi,

    I am pretty new to SCCM and OSD. Used to be someone else done all the setup and I am just helping users deploying OS. Now I had to do the set up. I am stuck with getting "Unknown Computers" to run the Task Sequence. It was working two weeks ago and all of the sudden it stopped working. After boot into PE it prompt "There are no task sequence available for this computer"

    I checked for Duplicated GUID or UUID, Unknown Computer UUID huger and deleted "unknown" from DB and Management Console. I traced SMSTS.log and found Unknown Computer seems not pulling the Policy Assignments...

    Client GUID = , Netbios name = , State = Known TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    SMSTSUser:  TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Client Identity is not yet defined. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Using unknown machine GUID: 434896b5-45f5-4694-9de7-416ec8e0cdf0 TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=TRUE TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Computed HardwareID=2:2877D357ADF9F48070B9B5E5513B9880249AA5CF
    Win32_SystemEnclosure.SerialNumber=5CG8021V4Q
    Win32_SystemEnclosure.SMBIOSAssetTag=5CG8021V4Q
    Win32_BaseBoard.SerialNumber=PFKZT00WBAC0A3
    Win32_BIOS.SerialNumber=5CG8021V4Q
    Win32_NetworkAdapterConfiguration.MACAddress=<Not used on laptop> TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Hardware ID: 2:2877D357ADF9F48070B9B5E5513B9880249AA5CF TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Preparing the Client DDR Message TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
        Setting SourceID = b69e891f-2730-441d-aae6-eabef5266ee8. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Sending the Client DDR message. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Sending Report TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    <Report><ReportHeader><Identification><Machine><ClientInstalled>0</ClientInstalled><ClientType>1</ClientType><Unknown>1</Unknown><ClientID>GUID:d3171e78-3e58-432d-b547-fd85c8e12cb1</ClientID><ClientVersion>5.00.0000.0000</ClientVersion><NetBIOSName>Unknown</NetBIOSName><CodePage>437</CodePage><SystemDefaultLCID>1033</SystemDefaultLCID></Machine></Identification><ReportDetails><ReportContent>Inventory Data</ReportContent><ReportType>Full</ReportType><Date>20180523004015.000000+000</Date><Version>1.0</Version><Format>1.1</Format></ReportDetails><InventoryAction ActionType="Predefined"><InventoryActionID>{00000000-0000-0000-0000-000000000003}</InventoryActionID><Description>Discovery</Description><InventoryActionLastUpdateTime>20180523004015.000000+000</InventoryActionLastUpdateTime></InventoryAction>
    </ReportHeader>
    <ReportBody><Instance ParentClass="CCM_ClientIdentificationInformation" Class="CCM_ClientIdentificationInformation" Namespace="root\ccm" Content="New"><CCM_ClientIdentificationInformation><HardwareID1>2:2877D357ADF9F48070B9B5E5513B9880249AA5CF</HardwareID1></CCM_ClientIdentificationInformation></Instance><Instance ParentClass="Win32_NetworkAdapterConfiguration" Class="Win32_NetworkAdapterConfiguration" Namespace="root\cimv2" Content="New"><Win32_NetworkAdapterConfiguration><MACAddress>80:CE:62:9D:8C:68</MACAddress></Win32_NetworkAdapterConfiguration></Instance><Instance ParentClass="Win32_ComputerSystemProduct" Class="Win32_ComputerSystemProduct" Namespace="root\cimv2" Content="New"><Win32_ComputerSystemProduct><UUID>E19B8A10-F648-11E7-9A7E-0820E402E0E2</UUID></Win32_ComputerSystemProduct></Instance></ReportBody>
    </Report>
    TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Setting message signatures. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Setting the authenticator. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    CLibSMSMessageWinHttpTransport::Send: URL: xxxxxxx.xxxxxxxx.com:80  CCM_POST /ccm_system/request TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Request was successful. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Submitted new client identity: GUID:d3171e78-3e58-432d-b547-fd85c8e12cb1 TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    _SMSTSClientIdentity=GUID:d3171e78-3e58-432d-b547-fd85c8e12cb1 TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Preparing Policy Assignment Request. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
        Setting transport. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
        Setting site code = COL. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
        Setting client ID = 434896b5-45f5-4694-9de7-416ec8e0cdf0. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
       Setting site signing Certificate. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Setting SiteSigningCertificateContext TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Executing Policy Assignment Request. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Sending RequestAssignments TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Setting message signatures. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Setting the authenticator. TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    CLibSMSMessageWinHttpTransport::Send: URL: xxxxxxx.xxxxxxxx.com:80  CCM_POST /ccm_system/request TSPxe 5/22/2018 6:40:15 PM 1344 (0x0540)
    Request was successful. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    ::DecompressBuffer(65536) TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Decompression (zlib) succeeded: original size 274, uncompressed size 662. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Request client ID: 434896b5-45f5-4694-9de7-416ec8e0cdf0 TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Response client ID: 434896b5-45f5-4694-9de7-416ec8e0cdf0 TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Retrieving Policy Assignments: TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Successfully read 0 policy assignments. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Retrieving collection variable policy. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Found 0 collection variables. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Retrieving machine variable policy. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Found 0 machine variables. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Setting collection variables in the task sequencing environment. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Setting machine variables in the task sequencing environment. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    Exiting TSMediaWizardControl::GetPolicy. TSPxe 5/22/2018 6:40:16 PM 1344 (0x0540)
    WelcomePage::OnWizardNext() TSPxe 5/22/2018 6:40:16 PM 1552 (0x0610)
    Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 5/22/2018 6:40:16 PM 1552 (0x0610)
    CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (..\windes.cpp,165) TSPxe 5/22/2018 6:40:16 PM 1552 (0x0610)
    SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (..\tsremovablemedia.cpp,387) TSPxe 5/22/2018 6:40:16 PM 1552 (0x0610)
    No assigned task sequence. TSPxe 5/22/2018 6:40:16 PM 1552 (0x0610)

    The machine is being recognized as Unknown Computer and get the "(x64)Unknown Computer" GUID. Just not picking up any Policies. So I Googled a bit on this problem and found this Query for checking corrupted Policy. I can't seems to find any match..

    SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

    If I just run SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL I get

    PADBID
    16777232
    16777233
    16777234
    16777235
    16777236
    16777237
    16777238
    16777239
    16777240
    16777241
    16777242
    16777243

    Any idea where I should dig next? I am kind not sure what I should be look for now...

    Thank you.

    Wednesday, May 23, 2018 10:01 PM

Answers

  • Hi Jason,

    Got this thing figured out. So the problem IS there was an invisible computer hugging Unknown Computer's GUID. And the solution is to recreate a new Unknown Computer record. 

    1. LOCAL MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_DISCOVERY_DATA_MANAGER on your primary site server. Set the value to 0

    2. re-start the SMS_EXECUTIVE service

    3. disable PXE on each DP wait for 5 minute and enable it again. 

    This creates a new set of X64 and X86 Unknown Computer GUID as default to setup new unknown computers. The old one is still stuck in there though. It can be deleted via SQL but haven't had the need to.

    Cheers 

    • Marked as answer by HenryT11 Wednesday, May 30, 2018 5:37 PM
    Wednesday, May 30, 2018 5:37 PM

All replies

  • > "and deleted "unknown" from DB"

    What exactly does this mean? Deleting anything from the DB is unsupported.

    This looks like you are PXE booting as well, correct?

    If so, have you validated that the cert assigned to the PXE enabled DP is good?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, May 23, 2018 11:23 PM
  • So when PXE boot into PE and the Task Sequence Failed the computers GUID gets Unknown value for NetBios_name0. In Configuration Manager Console it only show the most recent Unknown computer. The previous one doesn't always show in Assets and Compliance > Devices. I checked it up in System_Disc table by SELECT * FROM System_DISC WHERE Netbios_Name0 = 'Unknown' and run the Delete query to remove them. 

    ItemKey SMS_Unique_Identifier0                            Netbios_Name0 Name0
    16777637 GUID:eed9eea7-8919-48a8-bdea-76e5ab95e966 Unknown Unknown
    16777638 GUID:403567a1-a533-4909-a0ac-9c1b7b22b7b6 Unknown Unknown
    16777639 GUID:d3171e78-3e58-432d-b547-fd85c8e12cb1 Unknown Unknown
    16777642 GUID:83fbbead-c861-4ab2-a1cc-7127cf8b59a0 Unknown Unknown

    Regarding to the Certificate I am not very sure how to validate it but I did import the cert created from Root CA. If the Cert is not working the PXE boot and OS deployment for Known computer should fail too right? Before 2 weeks ago Unknown Computer imaging was working. Don't believe we made any change during this time other than working on the Task Sequences.

    Any idea what I am missing or where to look?

      

    Wednesday, May 23, 2018 11:45 PM
  • That's unsupported and a terrible thing to do in general and could possibly be the root cause of your issue.

    So is your site configured to use HTTPS client communication?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, May 23, 2018 11:58 PM
  • Thank you for the quick reply. Okay I will try avoid to work with DB directly but just FYI this issue started before I start poking SQL DB. I am using HTTP client communication at the moment.
    Thursday, May 24, 2018 1:52 AM
  • What version of SCCM are you using?

    Thursday, May 24, 2018 5:42 AM
  • Have you reviewed the deployment to make sure that it is valid?

    Have you tried creating a new deployment for the task sequence targeted to the All Unknown Computers collection?

    And (as asked by Kerwin also) what version of ConfigMgr?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, May 24, 2018 2:17 PM
  • I am using SCCM Version 1710.

    I have confirmed I have distributed the task sequence to the DP and Deployed the task sequence to the All Unknown Computer Collection. I also tried to remove the deployment and redeployed them but didn't help

    My account is not verified yet but here is a screenshot.

    https://drive.google.com/open?id=1T9fC2ovWrWSfhqT7Po6cpeULt5_RdNzC

    These task sequence is also deployed to a Known Computer collection and shows up in Windows PE. 

    Please let me know if there is any other information you need. Thank you!

    Thursday, May 24, 2018 2:52 PM
  • If you check smspxe.log on the PXE enabled DP, what GUIDs are listed for the unknown computer objects? These are shown after the WDS service is cycled on the DP but you may be able to find them in the existing log also assuming it hasn't rolled over yet.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, May 24, 2018 3:02 PM
  • I just ran the PXE boot again. Here is the SMSPXE.log for the checking in. It showed the x64 unknown computer guid 434896b5-45f5-4694-9de7-416ec8e0cdf0. 

    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:07:18 AM 8076 (0x1F8C)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    SMSPXE 5/24/2018 8:07:19 AM 8076 (0x1F8C)
    80:CE:62:9D:8C:68, E19B8A10-F648-11E7-9A7E-0820E402E0E2: device is not in the database. SMSPXE 5/24/2018 8:07:19 AM 8076 (0x1F8C)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 5/24/2018 8:07:19 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:07:19 AM 8076 (0x1F8C)
    Request using architecture 0. SMSPXE 5/24/2018 8:07:19 AM 8076 (0x1F8C)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    SMSPXE 5/24/2018 8:07:19 AM 8076 (0x1F8C)
    Request retry. SMSPXE 5/24/2018 8:07:19 AM 8076 (0x1F8C)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>e634881e-6b2f-4d4c-8e4c-71d06aedfc6c</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="COL20026" OfferIDTime="5/22/2018 5:32:00 PM" PkgID="COL0003A" PackageVersion="" PackagePath="http://xxx.xxx.com/SMS_DP_SMSPKG$/COL00005" BootImageID="COL00005" Mandatory="0"/></ClientIDReply>
    SMSPXE 5/24/2018 8:07:20 AM 8076 (0x1F8C)
    80:CE:62:9D:8C:68, E19B8A10-F648-11E7-9A7E-0820E402E0E2: found optional advertisement COL20026 SMSPXE 5/24/2018 8:07:20 AM 8076 (0x1F8C)
    Getting boot action for unknown machine: item key: 2046820353 SMSPXE 5/24/2018 8:07:22 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:07:22 AM 8076 (0x1F8C)
    Request using architecture 9. SMSPXE 5/24/2018 8:07:23 AM 8076 (0x1F8C)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>434896b5-45f5-4694-9de7-416ec8e0cdf0</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="COL20026" OfferIDTime="5/22/2018 5:32:00 PM" PkgID="COL0003A" PackageVersion="" PackagePath="http://xxx.xxx.com/SMS_DP_SMSPKG$/COL00005" BootImageID="COL00005" Mandatory="0"/></ClientIDReply>
    SMSPXE 5/24/2018 8:07:26 AM 8076 (0x1F8C)
    80:CE:62:9D:8C:68, E19B8A10-F648-11E7-9A7E-0820E402E0E2: found optional advertisement COL20026 SMSPXE 5/24/2018 8:07:26 AM 8076 (0x1F8C)
    Looking for bootImage COL00005 SMSPXE 5/24/2018 8:07:26 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:07:26 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:07:26 AM 8076 (0x1F8C)
    Report Body: <ReportBody><ClientID>434896b5-45f5-4694-9de7-416ec8e0cdf0</ClientID><StateMessage MessageTime="20180524150726.000000+000" SerialNumber="1"><ClientID>434896b5-45f5-4694-9de7-416ec8e0cdf0</ClientID><Topic ID="PXE Boot Client" Type="601" IDType="601"/><State ID="100" Criticality="0"/><UserParameters Flags="32" Count="4"><Param>80:CE:62:9D:8C:68</Param><Param>E19B8A10-F648-11E7-9A7E-0820E402E0E2</Param><Param>10.1.20.66</Param><Param>COL</Param></UserParameters></StateMessage></ReportBody>
    SMSPXE 5/24/2018 8:07:26 AM 8076 (0x1F8C)
    Looking for bootImage COL00005 SMSPXE 5/24/2018 8:07:42 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:07:42 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:07:42 AM 8076 (0x1F8C)
    Report Body: <ReportBody><ClientID>434896b5-45f5-4694-9de7-416ec8e0cdf0</ClientID><StateMessage MessageTime="20180524150742.000000+000" SerialNumber="1"><ClientID>434896b5-45f5-4694-9de7-416ec8e0cdf0</ClientID><Topic ID="PXE Boot Client" Type="601" IDType="601"/><State ID="100" Criticality="0"/><UserParameters Flags="32" Count="4"><Param>80:CE:62:9D:8C:68</Param><Param>E19B8A10-F648-11E7-9A7E-0820E402E0E2</Param><Param>10.1.20.66</Param><Param>COL</Param></UserParameters></StateMessage></ReportBody>
    SMSPXE 5/24/2018 8:07:42 AM 8076 (0x1F8C)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 5/24/2018 8:08:06 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:08:06 AM 8076 (0x1F8C)
    Request using architecture 0. SMSPXE 5/24/2018 8:08:09 AM 8076 (0x1F8C)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    SMSPXE 5/24/2018 8:08:09 AM 8076 (0x1F8C)
    Request retry. SMSPXE 5/24/2018 8:08:09 AM 8076 (0x1F8C)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>e634881e-6b2f-4d4c-8e4c-71d06aedfc6c</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="COL20026" OfferIDTime="5/22/2018 5:32:00 PM" PkgID="COL0003A" PackageVersion="" PackagePath="http://xxx.xxx.com/SMS_DP_SMSPKG$/COL00005" BootImageID="COL00005" Mandatory="0"/></ClientIDReply>
    SMSPXE 5/24/2018 8:08:09 AM 8076 (0x1F8C)
    80:CE:62:9D:8C:68, E19B8A10-F648-11E7-9A7E-0820E402E0E2: found optional advertisement COL20026 SMSPXE 5/24/2018 8:08:09 AM 8076 (0x1F8C)
    Getting boot action for unknown machine: item key: 2046820353 SMSPXE 5/24/2018 8:08:10 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:08:10 AM 8076 (0x1F8C)
    Request using architecture 9. SMSPXE 5/24/2018 8:08:10 AM 8076 (0x1F8C)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>434896b5-45f5-4694-9de7-416ec8e0cdf0</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="COL20026" OfferIDTime="5/22/2018 5:32:00 PM" PkgID="COL0003A" PackageVersion="" PackagePath="http://xxx.xxx.com/SMS_DP_SMSPKG$/COL00005" BootImageID="COL00005" Mandatory="0"/></ClientIDReply>
    SMSPXE 5/24/2018 8:08:10 AM 8076 (0x1F8C)
    80:CE:62:9D:8C:68, E19B8A10-F648-11E7-9A7E-0820E402E0E2: found optional advertisement COL20026 SMSPXE 5/24/2018 8:08:10 AM 8076 (0x1F8C)
    Looking for bootImage COL00005 SMSPXE 5/24/2018 8:08:10 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:08:10 AM 8076 (0x1F8C)
    Prioritizing local MP http://xxx.xxx.com. SMSPXE 5/24/2018 8:08:11 AM 8076 (0x1F8C)
    Report Body: <ReportBody><ClientID>434896b5-45f5-4694-9de7-416ec8e0cdf0</ClientID><StateMessage MessageTime="20180524150811.000000+000" SerialNumber="1"><ClientID>434896b5-45f5-4694-9de7-416ec8e0cdf0</ClientID><Topic ID="PXE Boot Client" Type="601" IDType="601"/><State ID="100" Criticality="0"/><UserParameters Flags="32" Count="4"><Param>80:CE:62:9D:8C:68</Param><Param>E19B8A10-F648-11E7-9A7E-0820E402E0E2</Param><Param>10.1.20.66</Param><Param>COL</Param></UserParameters></StateMessage></ReportBody>
    SMSPXE 5/24/2018 8:08:11 AM 8076 (0x1F8C)

    Thanks

    Thursday, May 24, 2018 3:45 PM
  • Hello Don,

    I only see an optional advertisement from the log. Is this correct?

    If so, normaly when it is optional you need to have an extra action to start this deployment like pressing F12 again to start this optional deployment.

    can you change the deplyoemnt from optional to mandatory?

    Hope it helps,

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help.

    Thanks,

    EduardoMendes

    Thursday, May 24, 2018 3:57 PM
  • Hi Eduardo,

    Yes, we purposely set it up this way as Boot from PXE is our first option in BIOS boot sequence. If it's set to mandatory anyone who boot computer while connected to network will get stuck in this cycle.

    When doing PXE boot it prompts for F12 and after press F12 it successfully boots to Windows PE. It's just after it get to Windows PE there is no task sequence available. It was working like 12 days ago. The only change during this time is created few new task sequence and used hyper-v VM to do test OS deployment. 


    Thanks

    Thursday, May 24, 2018 4:09 PM
  • Can you please check the activation time of the deployment and make sure that it is not set to some time in the future?

    Thursday, May 24, 2018 8:58 PM
  • Kerwin, The Schedule when this deployment will become available is set to May/22/2018. This new date is when I re-deployed the task sequence to the Unknown Computer Collection. Thanks.
    Thursday, May 24, 2018 9:54 PM
  • Don,

    could you please just confirm two things:

    1. that you have an IP boundary set for the IP address assigned to your VM?

    2. once it gets to WinPE it has the correct time/date set?

    Hope it helps,

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help.

    Thanks,

    EduardoMendes

    Thursday, May 24, 2018 10:03 PM
  • Edurardo,

    Thanks for the suggestion regarding to boundary. This is where it gets weird but it has been like this since SCCM was first set up. We set up 10.9.30.30-220 range group for any computers in this DHCP range to report to it's local management point at 10.9.30.249. But in the SMSTS.log it shows it was talking to another management point in another city. This happens to both known and unknown computer. It two weeks ago it was still working for both type now only works for known computer. The unknown computer just gets no task sequence. 

    For the date and time they are correct on the computer. I am suspecting the issue was caused by using VM to test and some how screwed up the unknown computer OS deployment. So I am currently using physical computer to test. Have been trying to solve this for a week now LOL.

    Thanks

    Thursday, May 24, 2018 11:05 PM
  • Boundaries are irrelevant for deployment applicability.

    So does a physical system work?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, May 25, 2018 1:35 AM
  • No. I tried both VM and multiple Physical Computers. If it's an Unknown Computer, not already in SCCM Devices list, it will all get "no task sequence available for this computer" 

    Please let me know if there is a log that will give me some clue. I checked and posted SMSTS.log. SMSPXE.log is all normal PXE boot has no issue. I checked MP_Policy.log, No error. Any suggestions?

    Just a crazy idea. This is a semi production SCCM set up like 5 weeks ago. Most computer is registered to it already but other than the software center itself there is no application or TS has been deployed other than test computers. Do you think deleting every registered device in the Device list will fix this problem? And will this cause big problem?

    Thanks

    Friday, May 25, 2018 3:48 PM
  • No, that's not a step I would take.

    If you delete all of the task sequence deployments, will the system PXE boot?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, May 25, 2018 4:00 PM
  • Thanks for the quick reply Jason. Currently there is 1 task sequence assigned to Unknown computer collection and test collection. The computers either known or unknown will boot from PXE. It will load Windows PE. Just after that for unknown computer there is no Task Sequence available. known computer sees the task sequence. Are you asking me to try remove all task sequence to see if without any Task Sequence will computer still boot from PXE?
    Friday, May 25, 2018 4:16 PM
  • Almost, don't remove the task sequences, just remove (or disable) their deployments and see if any system (known and unknown) will PXE boot.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, May 25, 2018 4:23 PM
  • Just did the test after removed the Task Sequence from the Unknown Computers it does not boot with PXE any more. SMSPXE.log below for the boot. no advertisements found. Good sign?

    Getting boot action for unknown machine: item key: 2046820353 SMSPXE 5/25/2018 9:31:23 AM 8076 (0x1F8C)
    Using values from 'AllowedMPs' key. SMSPXE 5/25/2018 9:31:23 AM 8076 (0x1F8C)
    Prioritizing local MP xxx.xxx.com. SMSPXE 5/25/2018 9:31:23 AM 8076 (0x1F8C)
    Request using architecture 9. SMSPXE 5/25/2018 9:31:23 AM 8076 (0x1F8C)
    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 5/25/2018 9:31:24 AM 8076 (0x1F8C)
    Request retry. SMSPXE 5/25/2018 9:31:24 AM 8076 (0x1F8C)
    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 5/25/2018 9:31:24 AM 8076 (0x1F8C)
    28:D2:44:6D:4E:DA, E928AA81-520D-11CB-94A7-F73E0E511DB4: no advertisements found SMSPXE 5/25/2018 9:31:24 AM 8076 (0x1F8C)
    Using values from 'AllowedMPs' key. SMSPXE 5/25/2018 9:31:24 AM 8076 (0x1F8C)
    Prioritizing local MP xxx.xxx.com. SMSPXE 5/25/2018 9:31:24 AM 8076 (0x1F8C)

    Friday, May 25, 2018 4:34 PM
  • Expected at least.

    Now add a non-hidden deployment targeted at the all unknown computers collection (which I assume contains your two unknown computer objects) with an available time of yesterday and without a deadline.

    Then try to PXE boot an unknown system and let us know what happens.

    Also, what version of the ConfigMgr binaries are contained in the boot image and what WinPE version is the boot image that you are using? You can quickly see this by right-clicking on the boot image in the console and choose update distribution points -- you don't have to finish the wizard as the first page of the wizard will tell you the version of the ConfigMgr client agent in the boot image itself.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, May 25, 2018 5:09 PM
  • The Boot Image information as follow

    Current Windows ADK version: 10.0.16299.0

    Current production client version: 5.00.8577.1115

    Version:10.0.16299.15 OS Version: 10.0.16299.15 Client version: 5.00.8577.1115 

    For the PXE boot test it boots to Windows PE but still shows no task sequence available. This is kind weird. It picks up the advertisement but then saying there is no task sequence... 

    In the SMSTS.log still states Successfully read 0 policy assignments... 

    Decompression (zlib) succeeded: original size 274, uncompressed size 662. TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Request client ID: 434896b5-45f5-4694-9de7-416ec8e0cdf0 TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Response client ID: 434896b5-45f5-4694-9de7-416ec8e0cdf0 TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Retrieving Policy Assignments: TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Successfully read 0 policy assignments. TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Retrieving collection variable policy. TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Found 0 collection variables. TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Retrieving machine variable policy. TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Found 0 machine variables. TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Setting collection variables in the task sequencing environment. TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Setting machine variables in the task sequencing environment. TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)
    Exiting TSMediaWizardControl::GetPolicy. TSPxe 5/25/2018 11:25:25 AM 1644 (0x066C)

    Thanks for the advice though I though this would fixed the problem. Any where else I could check?

    Friday, May 25, 2018 6:29 PM
  • Unless Kerwin has any ideas here (he wrote most of the code), then it's time to open a support case as there's something else going on here that's difficult (if not impossible) to pick out in a forum.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, May 25, 2018 7:28 PM
  • How would I open up a support case with Microsoft? So far have not done it before.
    Friday, May 25, 2018 7:34 PM
  • Start at https://support.microsoft.com/en-us/contactus/

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, May 25, 2018 7:46 PM
  • Hi Jason,

    Got this thing figured out. So the problem IS there was an invisible computer hugging Unknown Computer's GUID. And the solution is to recreate a new Unknown Computer record. 

    1. LOCAL MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_DISCOVERY_DATA_MANAGER on your primary site server. Set the value to 0

    2. re-start the SMS_EXECUTIVE service

    3. disable PXE on each DP wait for 5 minute and enable it again. 

    This creates a new set of X64 and X86 Unknown Computer GUID as default to setup new unknown computers. The old one is still stuck in there though. It can be deleted via SQL but haven't had the need to.

    Cheers 

    • Marked as answer by HenryT11 Wednesday, May 30, 2018 5:37 PM
    Wednesday, May 30, 2018 5:37 PM
  • Makes sense. I've heard of this (or similar) happening before but haven't had to specifically handle. It's kind of what I thought was going on as well which is why I was asking you to compare the GUIDs of the various objects. This sounds like a great blog post (hint). Maybe Kerwin will see this as well and add his thoughts.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, May 30, 2018 5:47 PM
  • Hallo Don

    it seems that I have a similar issue to the one that you experienced

    were these steps all that you did to repair this error

    https://social.technet.microsoft.com/Forums/en-US/0daaf22b-0e00-4100-948e-8625d149012f/cb1802-there-are-no-task-sequences-available-for-this-computer?forum=ConfigMgrCBOSD

    Wednesday, May 15, 2019 6:28 AM
  • Set which value to 0?
    Wednesday, July 29, 2020 7:34 PM