none
Unknown computers no longer seeing task sequences RRS feed

  • Question

  • As the title states, our unknown computers are no longer seeing any task sequences that we deploy to our "All Unknown Computers" collection.  We connect to SCCM using the USB Boot Media we create through the console and do have unknown computer support checked off.  We did recently updated our SCCM environment to 1702, but we immediately tested OSD after and everything was working.

    We've deleted the corresponding "unknown" computer device that gets created during the initial OSD process. We have also tried deploying the task sequences to a separate collection querying for unknown computers.  All options so far have not been successful.  The SMSTS.log on the client just says that no task sequence is available for the device. 

    Any ideas?  Suggestions? 

    Wednesday, May 3, 2017 4:03 PM

Answers

  • I've seen the exact same issue (also using 1702). The problem for me was that some random client took the "x64 Unknown Computer" objects GUID as it's own GUID during a deployment.

    As this happened no other client (deployed as an unknown computer) was able to find any task sequences (as the computer was "known").

    I queried the SQL DB (System_DATA table) for the unknown guids (can be seen in your log file below) and found the offending client. Reinstallation of the client (and removing of the smscfg.ini + the SMS certs) resolved the issue, as the computer rejoined the SCCM-Environment with a proper GUID.

    I'll give this a go and report back,  thank you!
    • Marked as answer by Chhan Monday, May 8, 2017 11:07 PM
    Monday, May 8, 2017 8:20 PM

All replies

  • If you share the complete SMSTS log file, I can take a look at it.

    Wednesday, May 3, 2017 11:37 PM
  • Have you confirmed that the devices in case are unknown? And just to be sure, you should have checked in the checkbox for unknown computer support on your boot media.

    Thursday, May 4, 2017 3:29 AM
  • Hi Narcoticoo,

    Yes, these devices do not exist in SCCM.  And we do have unknown computer support checked, sorry for the earlier wording.

    Friday, May 5, 2017 4:34 PM
  • Post the complete SMSTS log file as Kerwin requested.
    • Edited by Emmanuel R Friday, May 5, 2017 5:39 PM
    Friday, May 5, 2017 5:39 PM
  • If you share the complete SMSTS log file, I can take a look at it.

    ==============================[ TSBootShell.exe ]============================== TSBootShell 5/5/2017 8:48:37 AM 840 (0x0348)
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSBootShell 5/5/2017 8:48:37 AM 840 (0x0348)
    Debug shell is enabled TSBootShell 5/5/2017 8:48:37 AM 840 (0x0348)
    Waiting for PNP initialization... TSBootShell 5/5/2017 8:48:37 AM 884 (0x0374)
    RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM TSBootShell 5/5/2017 8:48:37 AM 884 (0x0374)
    WinPE boot path: D:\SOURCES\BOOT.WIM TSBootShell 5/5/2017 8:48:37 AM 884 (0x0374)
    Booted from removable device TSBootShell 5/5/2017 8:48:37 AM 884 (0x0374)
    Found config path D:\ TSBootShell 5/5/2017 8:48:37 AM 884 (0x0374)
    Booting from removable media, not restoring bootloaders on hard drive TSBootShell 5/5/2017 8:48:37 AM 884 (0x0374)
    D:\WinPE does not exist. TSBootShell 5/5/2017 8:48:37 AM 884 (0x0374)
    D:\_SmsTsWinPE\WinPE does not exist. TSBootShell 5/5/2017 8:48:37 AM 884 (0x0374)
    Executing command line: wpeinit.exe -winpe TSBootShell 5/5/2017 8:48:37 AM 884 (0x0374)
    The command completed successfully. TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
    Setting offline Windows drive and OS root directory to TS envirtonment. TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
      Processing volume D:\  TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
      Volume D:\ is not a local hard drive. TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
      Processing volume C:\  TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
    pOs != NULL, HRESULT=80070490 (e:\nts_sccm_release\sms\framework\osdcore\offlineos.cpp,89) TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
    Unable to find a Windows system root at C:\ TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
      Processing volume E:\  TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
    OfflineRegistry::Init("E:\WINDOWS") TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
    Loading offline registry hive "E:\WINDOWS\system32\config\software" into HKLM\OfflineRegistry1 TSBootShell 5/5/2017 8:48:45 AM 884 (0x0374)
    Loading offline registry hive "E:\WINDOWS\system32\config\system" into HKLM\OfflineRegistry2 TSBootShell 5/5/2017 8:48:46 AM 884 (0x0374)
    CurrentControlSet is mapped to ControlSet001 TSBootShell 5/5/2017 8:48:47 AM 884 (0x0374)
      Volume E:\ is a valid volume with Windows system root at E:\WINDOWS. TSBootShell 5/5/2017 8:48:47 AM 884 (0x0374)
    Settinge offline Windows drive and OS root directory to boot shell environment variables TSBootShell 5/5/2017 8:48:47 AM 884 (0x0374)
    _OSDDetectedWinDrive='E:\', _OSDDetectedWinDir='E:\WINDOWS' TSBootShell 5/5/2017 8:48:47 AM 884 (0x0374)
    Unloading offline SOFTWARE registry hive TSBootShell 5/5/2017 8:48:47 AM 884 (0x0374)
    Unloading offline SYSTEM registry hive TSBootShell 5/5/2017 8:48:47 AM 884 (0x0374)
    Starting DNS client service. TSBootShell 5/5/2017 8:48:47 AM 884 (0x0374)
    Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:D:\ TSBootShell 5/5/2017 8:48:47 AM 884 (0x0374)
    The command completed successfully. TSBootShell 5/5/2017 8:48:47 AM 884 (0x0374)
    ==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:D:\ TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL' TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Current OS version is 10.0.15063.0 TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Unable to open PXE registry key. Not a PXE boot. TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Media Root = D:\ TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    WinPE boot type: 'Ramdisk:SourceIdentified' TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Failed to find the source drive where WinPE was booted from TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Executing from Media in WinPE TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Verifying Media Layout. TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    MediaType = BootMedia TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    PasswordRequired = false TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Found network adapter "Intel(R) Ethernet Connection (2) I219-LM" with IP Address 0.0.0.0. TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Running Wizard in Interactive mode TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Loading Media Variables from "D:\sms\data\variables.dat" TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    no password for vars file TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Activating Welcome Page. TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    Loading bitmap TSMBootstrap 5/5/2017 8:48:47 AM 1508 (0x05E4)
    WelcomePage::OnWizardNext() TSMBootstrap 5/5/2017 8:48:53 AM 1508 (0x05E4)
    Loading Media Variables from "D:\sms\data\variables.dat" TSMBootstrap 5/5/2017 8:48:53 AM 1508 (0x05E4)
    no password for vars file TSMBootstrap 5/5/2017 8:48:53 AM 1508 (0x05E4)
    Spawned thread 1604 to download policy. TSMBootstrap 5/5/2017 8:48:53 AM 1508 (0x05E4)
    Entering TSMediaWizardControl::GetPolicy. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00' TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00' TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    If current logging settings specify more logging details to be preserved, udpate these settings in TS environment TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Current LogMaxSize is saved to TS environment since it has not been saved before TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Current LogMaxHistory is saved to TS environment since it has not been saved before TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Current LogLevel is saved to TS environment since it has not been saved before TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Current LogEnabled is saved to TS environment since it has not been saved before TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Current LogDebug is saved to TS environment since it has not been saved before TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting to TS environemnt _OSDDetectedWinDrive=E:\ TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting to TS environemnt _OSDDetectedWinDir=E:\WINDOWS TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    UEFI: true TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Loading variables from the Task Sequencing Removable Media. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Loading Media Variables from "D:\sms\data\variables.dat" TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting SMSTSMP TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSMediaGuid TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSBootMediaPackageID TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSBootMediaSourceVersion TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSBrandingTitle TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSCertSelection TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSCertStoreName TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSDiskLabel1 TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSHTTPPort TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSHTTPSPort TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSIISSSLState TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSMediaCreatedOnCAS TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSMediaPFX TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSMediaSetID TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSMediaType TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSPublicRootKey TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSRootCACerts TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSSiteCode TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSSiteSigningCertificate TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSStandAloneMedia TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSSupportUnknownMachines TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSTimezone TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSUseFirstCert TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSx64UnknownMachineGUID TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting _SMSTSx86UnknownMachineGUID TS environment variable TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Importing certificates to root store... TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Importing certificates to root store TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Added certificate to store or replaced matching certificate in store. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Support Unknown Machines: 1 TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Custom hook from X:\\TSConfig.INI is  TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    No hook is found to be executed before downloading policy TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Authenticator from the environment is empty. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Need to create Authenticator Info using PFX TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Initialized CStringStream object with string: 5BF587DF-EA21-4F00-95D3-1815CC8FE488;2017-05-05T16:48:53Z. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Current time info: . TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Getting MP time information TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Set authenticator in transport TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Requesting client identity TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting message signatures. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Setting the authenticator. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    CLibSMSMessageWinHttpTransport::Send: URL: sccm.server:80  CCM_POST /ccm_system/request TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Error. Received 0x80072ee7 from WinHttpSendRequest. TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    unknown host (gethostbyname failed) TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9171) TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    sending with winhttp failed; 80072ee7 TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Will retry in 5 second(s) TSMBootstrap 5/5/2017 8:48:53 AM 1604 (0x0644)
    Retrying... TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    CLibSMSMessageWinHttpTransport::Send: URL: sccm.server:80  CCM_POST /ccm_system/request TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Request was successful. TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    ::DecompressBuffer(65536) TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Decompression (zlib) succeeded: original size 443, uncompressed size 2516. TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    -60 -60 TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Server time zone info: 480, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60 TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Client Identity:  TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Netbios name:  TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Current time: 2017-05-05 16:48:59.718 TZ:Pacific Standard Time Bias:0480 TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Time zone: 480,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,Pacific Standard Time, TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Bias=480,StandardBias=0,DaylightBias=0 TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    StandardDate.wYear=0,wMonth=0,wDayOfWeek=0,wDay=0,wHour=0,wMinute=0,wSecond=0,wMilliseconds=0 TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    DaylightDate.wYear=0,wMonth=0,wDayOfWeek=0,wDay=0,wHour=0,wMinute=0,wSecond=0,wMilliseconds=0 TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    StandardName=Pacific Standard Time,DaylightName= TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Adjusting the system time: -3599.054 seconds TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Time zone: 480,0,-60,0,11,0,1,2,0,0,0,0,3,0,2,2,0,0,0,, TSMBootstrap 5/5/2017 9:48:59 AM 1604 (0x0644)
    Bias=480,StandardBias=0,DaylightBias=-60 TSMBootstrap 5/5/2017 9

    StandardDate.wYear=0,wMonth=0,wDayOfWeek=0,wDay=0,wHour=0,wMinute=0,wSecond=0,wMilliseconds=0 TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    DaylightDate.wYear=0,wMonth=0,wDayOfWeek=0,wDay=0,wHour=0,wMinute=0,wSecond=0,wMilliseconds=0 TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    StandardName=Pacific Standard Time,DaylightName= TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Adjusting the system time: -3599.054 seconds TSMBootstrap 5/5/2017 8:48:59 AM 1604 (0x0644)
    Time zone: 480,0,-60,0,11,0,1,2,0,0,0,0,3,0,2,2,0,0,0,, TSMBootstrap 5/5/2017 9:48:59 AM 1604 (0x0644)
    Bias=480,StandardBias=0,DaylightBias=-60 TSMBootstrap 5/5/2017 9:48:59 AM 1604 (0x0644)
    StandardDate.wYear=0,wMonth=11,wDayOfWeek=0,wDay=1,wHour=2,wMinute=0,wSecond=0,wMilliseconds=0 TSMBootstrap 5/5/2017 9:48:59 AM 1604 (0x0644)
    DaylightDate.wYear=0,wMonth=3,wDayOfWeek=0,wDay=2,wHour=2,wMinute=0,wSecond=0,wMilliseconds=0 TSMBootstrap 5/5/2017 9:48:59 AM 1604 (0x0644)
    StandardName=,DaylightName= TSMBootstrap 5/5/2017 9:48:59 AM 1604 (0x0644)
    New time: 2017-05-05 15:49:00.663 TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Current time: 2017-05-05 15:49:00.656 TZ: Bias:0480 TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Set media certificate in transport TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Set authenticator in transport TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    CLibSMSMessageWinHttpTransport::Send: URL: sccm.server:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Request was successful. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    New MP settings: TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
        site=CN1,CN1, MP=http://sccm.server, ports: http=80,https=443 TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
        certificates are received from MP. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Unknown machine GUIDs: 243e1d5e-dfc6-4a8c-83af-5b26e0fc93c6 1fb1fb9c-01f4-4a00-9c80-8a8c665720fb TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
        MP specific X86 unknown machine GUID is received at run time TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
        MP specific X64 unknown machine GUID is received at run time TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Downloading policy from http://sccm.server. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Initializing HTTP transport. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
       Setting URL = http://sccm.server. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
       Setting Ports = 80,443. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
       Setting CRL = false. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
       Setting Server Certificates. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Set authenticator in transport TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
       Setting Media Certificate. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Preparing Client Identity Request. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
        Setting transport. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
        Setting SourceID = 5BF587DF-EA21-4F00-95D3-1815CC8FE488. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
        Setting site code = CN1. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
        Setting SMBIOS GUID = 4C4C4544-0042-3910-804E-B7C04F4A4832. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
        Adding MAC Address 48:4D:7E:FB:60:0D. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Executing Client Identity Request. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Requesting client identity TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Setting message signatures. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Setting the authenticator. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    CLibSMSMessageWinHttpTransport::Send: URL: sccm.server:80  CCM_POST /ccm_system/request TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Request was successful. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    ::DecompressBuffer(65536) TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Decompression (zlib) succeeded: original size 442, uncompressed size 2516. TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    -60 -60 TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Server time zone info: 480, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60 TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Client Identity:  TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Netbios name:  TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Client GUID = , Netbios name = , State = Known TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    SMSTSUser:  TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    Using unknown machine GUID: 1fb1fb9c-01f4-4a00-9c80-8a8c665720fb TSMBootstrap 5/5/2017 8:49:00 AM 1604 (0x0644)
    GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Computed HardwareID=2:3591976AE1F845642AB09D53F3DAE169EBC609E5
     Win32_SystemEnclosure.SerialNumber=
     Win32_SystemEnclosure.SMBIOSAssetTag=<empty>
     Win32_BaseBoard.SerialNumber=
     Win32_BIOS.SerialNumber=
     Win32_NetworkAdapterConfiguration.MACAddress=48:4D:7E:FB:60:0D TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Hardware ID: 2:3591976AE1F845642AB09D53F3DAE169EBC609E5 TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Preparing the Client DDR Message TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Setting SourceID = 5BF587DF-EA21-4F00-95D3-1815CC8FE488. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Sending the Client DDR message. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Sending Report TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    <Report><ReportHeader><Identification><Machine><ClientInstalled>0</ClientInstalled><ClientType>1</ClientType><Unknown>1</Unknown><ClientID>GUID:8c2e69a4-d9c0-46df-b9ad-1ad563c90275</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>20170505154901.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>20170505154901.000000+000</InventoryActionLastUpdateTime></InventoryAction>
     </ReportHeader>
     <ReportBody><Instance ParentClass="CCM_ClientIdentificationInformation" Class="CCM_ClientIdentificationInformation" Namespace="root\ccm" Content="New"><CCM_ClientIdentificationInformation><HardwareID1>2:3591976AE1F845642AB09D53F3DAE169EBC609E5</HardwareID1></CCM_ClientIdentificationInformation></Instance><Instance ParentClass="Win32_NetworkAdapterConfiguration" Class="Win32_NetworkAdapterConfiguration" Namespace="root\cimv2" Content="New"><Win32_NetworkAdapterConfiguration><MACAddress>48:4D:7E:FB:60:0D</MACAddress></Win32_NetworkAdapterConfiguration></Instance><Instance ParentClass="Win32_ComputerSystemProduct" Class="Win32_ComputerSystemProduct" Namespace="root\cimv2" Content="New"><Win32_ComputerSystemProduct><UUID>4C4C4544-0042-3910-804E-B7C04F4A4832</UUID></Win32_ComputerSystemProduct></Instance></ReportBody>
    </Report>
     TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Setting message signatures. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Setting the authenticator. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    CLibSMSMessageWinHttpTransport::Send: URL: sccm.server:80  CCM_POST /ccm_system/request TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Request was successful. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Submitted new client identity: GUID:8c2e69a4-d9c0-46df-b9ad-1ad563c90275 TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Preparing Policy Assignment Request. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Setting transport. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Setting site code = CN1. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Setting client ID = 1fb1fb9c-01f4-4a00-9c80-8a8c665720fb. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
       Setting site signing Certificate. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Setting SiteSigningCertificateContext TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Executing Policy Assignment Request. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Sending RequestAssignments TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Setting message signatures. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Setting the authenticator. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    CLibSMSMessageWinHttpTransport::Send: URL: sccm.server:80  CCM_POST /ccm_system/request TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Request was successful. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    ::DecompressBuffer(65536) TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Decompression (zlib) succeeded: original size 68217, uncompressed size 362964. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Request client ID: 1fb1fb9c-01f4-4a00-9c80-8a8c665720fb TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Response client ID: 1fb1fb9c-01f4-4a00-9c80-8a8c665720fb TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
    Retrieving Policy Assignments: TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {80a960e0-a6f0-4807-aab5-b4a43560926f}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {f55d07f5-10b4-484f-bd32-5503a8a89e69}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {6b72c713-d4d1-4135-9934-ec6d2d3f603b}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {8e72b946-9259-406e-96d8-e4b1616f00a1}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {5d84dbfa-cdd5-4406-9491-86d206c1342f}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {bdad6386-eb67-4a86-938e-ceb8875255a2}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {068b6de8-060f-434f-b573-58c0f4e3d018}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {d0e430eb-184b-4d50-aa51-e0b8c0075b3f}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {e2ac876f-3088-4f1d-a840-40f8993c3c04}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {3366d44e-6093-45b9-9864-957fe9e07640}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {44d3663b-2af5-4e4b-891e-95f93ae95640}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {cc3ba8b3-2794-49d2-ae92-88e02dd4f020}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {5f38a508-0da5-4a84-ae79-276a039e852c}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {014868d5-357b-40da-8446-7b896d921871}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {f7e59df4-eb85-43e7-a17c-ce8791f67e29}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {94bb7e4d-e085-4691-808b-d248c4b12c32}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {c13bbc02-cc07-4939-8b6c-0c6a0c84c560}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {d13de2c1-d05b-4237-b3e4-b72e23dab410}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {a58b6719-1747-4017-8abb-fb7cadc1791d}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {a8b8c310-e279-4264-8194-9c73c9fcb6cd}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {95aaefe8-b283-4a77-a3eb-ab88a091b4af}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {f70ed798-6f70-40dd-8321-26a278db4d84}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {a30d2535-29ff-4e02-b079-b37a474a9ec0}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {4006be7a-8aad-4e99-ba61-dc61fd58b2da}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {e995e49a-83c7-4ac4-9af8-dc0a1bb68dfb}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {6d2d83de-5d2a-427d-ac32-19cda9a40a04}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment CN120000-CN100003-3B5BFFE2. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment Windows/All_Windows_Client_Server/VI/VS. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {240040B0-AD2E-4E9C-8FC8-C9CE34A93FE5}/101. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {F82A7C7C-41D3-4C8D-A0BF-7C73A0251C7E}/3. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {F82A7C7C-41D3-4C8D-A0BF-7C73A0251C7E}/8. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {F82A7C7C-41D3-4C8D-A0BF-7C73A0251C7E}/15. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {F82A7C7C-41D3-4C8D-A0BF-7C73A0251C7E}/17. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {F82A7C7C-41D3-4C8D-A0BF-7C73A0251C7E}/18. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {F82A7C7C-41D3-4C8D-A0BF-7C73A0251C7E}/20. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {415ba953-67fb-4d93-b09e-7924e0888333}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {45bbac54-f348-423a-915c-3a34b8ecfb5f}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {cba19cda-62fb-4bf9-9a60-07c040037142}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {19ffbbdf-038c-49bc-a507-3d907415277f}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {871ce403-6a36-419e-84eb-9812df234ec9}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {240040B0-AD2E-4E9C-8FC8-C9CE34A93FE5}/200. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment SRC10000. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {C6FB7AB5-CF3E-429A-9E4D-C95E79B349FF}/3. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {CN100116}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment ScopeId_EAE80406-A68B-4F32-8601-002228FC18D9/OperatingSystem_826cd761-2db7-47e4-b42c-eb3aa5775ec1/VI/VS. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment ScopeId_EAE80406-A68B-4F32-8601-002228FC18D9/Baseline_4373ff68-250e-451c-a55f-8c2472da5b29/VI/VS. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment WRC10000. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_5b099549-9f21-4ef0-a09b-0294e402f6f2/VI/VS. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/Application_5b099549-9f21-4ef0-a09b-0294e402f6f2/CA. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {3CAB397C-F78E-435A-AFB0-B98072BDD254}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {fad86eda-76d1-41ab-9ebe-910f0b958acf}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {F82A7C7C-41D3-4C8D-A0BF-7C73A0251C7E}/9. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {9AB02D78-11BB-4D4D-A698-E9AD6B1B7EC3}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment {69750f07-1d6c-40ed-aadf-374bc19a1784}. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment GLOBAL/Platform_Settings/VI/VS/L. TSMBootstrap 5/5/2017 8:49:01 AM 1604 (0x0644)
        Processing Policy Assignment Windows/All_Windows_Client_Serv

        Processing Policy Assignment Windows/All_x64_Windows_7_Client/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/All_x86_Windows_7_Client/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/All_x64_Windows_8_Client/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/All_x86_Windows_8_Client/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/All_x64_Windows_8.1_Client/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/All_x86_Windows_8.1_Client/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/Application_73719535-1754-4cc3-b57b-b3a52c8bac31/CA. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment FEC10000. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {4f4a13cb-2f8d-4bc1-b805-0feb63ba5102}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_f81e6568-f16e-4feb-8634-229255c21c71/VI/VS. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_62ae2872-5945-4f9c-bcdf-e057f93de3ae/VI/VS. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/Application_62ae2872-5945-4f9c-bcdf-e057f93de3ae/CA. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {BEE1C738-4E1B-4A40-8263-E0AACB2EED60}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/Application_b02f95f5-2441-4da7-8909-88f6dc3e9c9e/CA. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {46728165-9AFF-4B32-831B-DC7178751BA2}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {CF8475D5-2F09-4940-A333-A73622BC9EB6}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {3CD5AEBB-519F-4E89-A6EB-394B62DF241B}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_f7cbc99c-e0d9-4ee5-9835-9ee8de644201/VI/VS. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/Application_f7cbc99c-e0d9-4ee5-9835-9ee8de644201/CA. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_3d20bed1-642f-4bca-9a05-ddd8398f6533/VI/VS. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {744F687F-692F-4F1C-A2F4-7F78CDB804F4}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/Application_f81e6568-f16e-4feb-8634-229255c21c71/CA. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {3793D5C7-0965-4D10-A35C-C6B3A0EE6AF3}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {3EA7EFB6-F20F-4268-BE46-84FD8779D2DC}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {3E24E220-CE67-428D-B035-3AFA8D52490C}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment CN120342-CN10055E-E0E0C736. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/AuthList_B46E1242-3FFE-47B9-86F7-1BF1E67AF688/VI. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_b987a739-93d0-4f16-8af9-6a1a0712ee52/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/AuthList_2CF48005-0436-4DC7-9CDE-F449F47A8352/VI. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/AuthList_542C76B9-2903-4B04-B5F6-EE646577875D/VI. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/AuthList_607A351E-21A6-428E-8D83-FD3DC1C03DCE/VI. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/AuthList_3D9E55B8-96D5-4EF2-8809-F6480D7D06E5/VI. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {04CB742C-50C8-49A5-94AE-1617189001D0}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {179780C2-04D3-46B0-A54E-2B97EE5D41C4}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {6035C82F-20A4-4ED4-804F-83D53BDBFDE2}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {EE53B4A1-B73E-4442-A803-ECE8C754740D}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {26D4D93C-6BDA-495A-A6EC-8A09E8BB3B59}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {F82A7C7C-41D3-4C8D-A0BF-7C73A0251C7E}/4. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {F82A7C7C-41D3-4C8D-A0BF-7C73A0251C7E}/25. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_a5646156-7d71-4796-af59-3f6f5e430f0c/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_feacfce3-7363-401d-b0ad-982ad5db0208/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_4f02f7a8-84c3-49ec-82d7-5dded186de00/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/All_x64_Windows_Vista/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/All_x64_Windows_XP_Professional/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_cd7981ad-826b-4e89-86c8-eb461b02f4cf/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/x86_Embedded_Windows_7/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_7524abe8-28aa-4b20-b3b3-05125c71ab98/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/All_x86_Windows_Embedded_8_Standard/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment Windows/All_x86_Windows_Embedded_8.1_Industry/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_75acddb7-f313-4b22-8f08-8cf272424f6b/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_60c548ca-133d-4c2c-b510-cc993cdb67c5/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_38ea8a8d-0a17-4d30-8b1e-391f6f19e0c1/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_b3576a2f-9594-4158-b9ad-ec3b0d8056ea/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_73719535-1754-4cc3-b57b-b3a52c8bac31/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_b02f95f5-2441-4da7-8909-88f6dc3e9c9e/VI/VS/L. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_a19d8606-0963-4a59-8495-942d779c6855/VI/VS. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_ffd87743-0271-4100-b541-7cdf3754c7d6/VI/VS. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/Application_ffd87743-0271-4100-b541-7cdf3754c7d6/CA. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/DeploymentType_7cd99eae-0799-4989-b6d9-e9bbe6872c43/VI/VS. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/RequiredApplication_ccc4590c-09c7-45e1-bb18-d379004f325c/VI/VS. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/Application_ccc4590c-09c7-45e1-bb18-d379004f325c/CA. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {55A280B3-2832-4BDF-A1BA-F6CFD5DE645F}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {F021E220-A0BC-481F-B56A-97CB9AE94528}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment {30975632-a766-4884-885f-b61d68dec409}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment ScopeId_B5554BE4-E860-4B44-AF6E-15A2FD073116/AuthList_12af4cf4-f793-4ffb-a0bd-eafc960d2431/VI. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Processing Policy Assignment SCE10000. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Successfully read 122 policy assignments. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Retrieving collection variable policy. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Downloading policy body {CN100116}. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Preparing Policy Body Request. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Setting transport. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
        Setting policy location = http://<mp>/SMS_MP/.sms_pol?{CN100116}.12_00. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Executing Policy Body Request. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    CLibSMSMessageWinHttpTransport::Send: URL: sccm.server:80  GET /SMS_MP/.sms_pol?{CN100116}.12_00 TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Request was successful. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    ::DecompressBuffer(65536) TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Decompression (zlib) succeeded: original size 1667, uncompressed size 16878. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Expected Hash size: 32, Computed Hash size: 32  TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Request location: HTTP://<MP>/SMS_MP/.SMS_POL?{CN100116}.12_00 TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Response ID: {CN100116} TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Reading Policy Body. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Parsing Policy Body. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Found 0 collection variables. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Retrieving machine variable policy. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Found 0 machine variables. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Setting collection variables in the task sequencing environment. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Setting machine variables in the task sequencing environment. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    Exiting TSMediaWizardControl::GetPolicy. TSMBootstrap 5/5/2017 8:49:08 AM 1756 (0x06DC)
    WelcomePage::OnWizardNext() TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    Loading Media Variables from "D:\sms\data\variables.dat" TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    no password for vars file TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    No assigned task sequence. TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    Setting wizard error: There are no task sequences available for this computer. TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    Skipping Confirmation Page. TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    Skipping Task Sequence Selection Page. TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    Skipping Variables Selection Page. TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    Skipping Resolve Progress Page. TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    Activating Finish Page. TSMBootstrap 5/5/2017 8:49:08 AM 1508 (0x05E4)
    Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 5/5/2017 8:49:10 AM 840 (0x0348)
    The command completed successfully. TSBootShell 5/5/2017 8:49:10 AM 840 (0x0348)
    Successfully launched command shell. TSBootShell 5/5/2017 8:49:10 AM 840 (0x0348)


    • Edited by Chhan Friday, May 5, 2017 9:44 PM removed serial #
    Friday, May 5, 2017 7:15 PM
  • Hi all,

    Did you resolve this issue?

    Regards,

    Craig


    MCTS | MCITP | MCSA

    Saturday, May 6, 2017 10:02 AM
  • Can you please run this query on your SCCM DB and provide us the results?

    select
    Decommissioned0,IsTombstoned,PkgProgram,CollectionID,AvailableSched,UnavailableSched,MandatorySched,
    PresentTime,ExpirationTime,TimeEnableFlag,OfferFlags,PkgFlags,ProgramFlags,TS_Type,BootImageID,TS_Flags
    from UnknownSystem_DISC sd
    join ResPolicyMap rpm on rpm.MachineID=sd.ItemKey
    join SoftwarePolicy sp on rpm.PADBID=sp.PADBID
    join ProgramOffers po on sp.OfferID = po.OfferID
    join vSMS_TaskSequencePackage tspkg on tspkg.PkgID = sp.PkgID AND (ISNULL (tspkg.BootImageID, '') != '')
    where sd.SMS_Unique_Identifier0='1fb1fb9c-01f4-4a00-9c80-8a8c665720fb'

    Monday, May 8, 2017 8:52 AM
  • Can you please run this query on your SCCM DB and provide us the results?

    select
    Decommissioned0,IsTombstoned,PkgProgram,CollectionID,AvailableSched,UnavailableSched,MandatorySched,
    PresentTime,ExpirationTime,TimeEnableFlag,OfferFlags,PkgFlags,ProgramFlags,TS_Type,BootImageID,TS_Flags
    from UnknownSystem_DISC sd
    join ResPolicyMap rpm on rpm.MachineID=sd.ItemKey
    join SoftwarePolicy sp on rpm.PADBID=sp.PADBID
    join ProgramOffers po on sp.OfferID = po.OfferID
    join vSMS_TaskSequencePackage tspkg on tspkg.PkgID = sp.PkgID AND (ISNULL (tspkg.BootImageID, '') != '')
    where sd.SMS_Unique_Identifier0='1fb1fb9c-01f4-4a00-9c80-8a8c665720fb'

    Hi Kerwin, thank you so much for your help!  Here are the SQL Results you request:

    Decommissioned0 IsTombstoned PkgProgram CollectionID AvailableSched UnavailableSched MandatorySched PresentTime ExpirationTime TimeEnableFlag OfferFlags PkgFlags ProgramFlags TS_Type BootImageID TS_Flags
    0 0 * SMS000US    2014-09-22 14:46:00.000 2014-09-22 14:46:00.000 8193 9306112 0 152084496 2 CN1004A3 0
    0 0 * SMS000US    2014-01-31 12:04:00.000 2014-01-31 12:04:00.000 8193 11403264 0 152084496 2 CN100038 1
    0 0 * SMS000US    2014-02-06 16:26:00.000 2014-02-06 16:26:00.000 8193 9306112 0 152088592 2 CN100038 1
    0 0 * SMS000US    2016-07-27 16:27:00.000 2016-07-27 16:27:00.000 8193 12451840 0 152084496 2 CN1004A3 0
    0 0 * SMS000US    2014-10-02 15:41:00.000 2014-10-02 15:41:00.000 8193 9306112 0 152084496 2 CN1003E0 0
    0 0 * SMS000US    2015-12-22 16:58:00.000 2015-12-22 16:58:00.000 8193 9306112 0 152084496 2 CN100004 0
    0 0 * SMS000US    2015-11-03 13:51:00.000 2015-11-03 13:51:00.000 8193 12451840 0 152084496 2 CN1003E0 0
    0 0 * SMS000US    2016-04-18 09:38:00.000 2016-04-18 09:38:00.000 24577 12451840 0 152084496 2 CN1004A3 0
    0 0 * SMS000US    2016-03-08 10:32:00.000 2016-03-08 10:32:00.000 8193 12451840 0 152084496 2 CN1004A3 0
    0 0 * SMS000US    2016-03-21 11:43:00.000 2016-03-21 11:43:00.000 24577 12451840 0 152084496 2 CN1004A3 0
    0 0 * SMS000US    2016-03-27 11:28:00.000 2016-03-27 11:28:00.000 24577 12451840 0 152084496 2 CN1004A3 0
    0 0 * SMS000US    2016-07-26 10:31:00.000 2016-07-26 10:31:00.000 8193 12451840 0 152084496 2 CN1004A3 0
    0 0 * SMS000US    2016-09-09 13:35:00.000 2016-09-09 13:35:00.000 8193 12451840 0 152084496 2 CN1004A3 0
    0 0 * SMS000US    2016-09-09 13:36:00.000 2016-09-09 13:36:00.000 8193 12451840 0 152084496 2 CN1004A3 0
    0 0 * SMS000US    2017-01-11 13:38:00.000 2017-01-11 13:38:00.000 8193 277676032 0 152084496 2 CN100004 0
    0 0 * SMS000US    2017-05-02 19:22:00.000 2017-05-02 19:22:00.000 8193 9306112 0 152084496 2 CN100004 0
    0 0 * SMS000US    2017-02-06 11:07:00.000 2017-02-06 11:07:00.000 8193 277741568 0 152084496 2 CN100004 0
    0 0 * SMS000US    2017-03-07 16:45:00.000 2017-03-07 16:45:00.000 8193 12451840 0 152084496 2 CN100004 0
    0 0 * SMS000US    2017-04-10 11:10:00.000 2017-04-10 11:10:00.000 8193 277741568 0 152084496 2 CN100004 0

    Monday, May 8, 2017 3:08 PM
  • I've cleaned up the deployments made to the "All Unknown Computers" Collection.  These are the new results:

    Decommissioned0 IsTombstoned PkgProgram CollectionID AvailableSched UnavailableSched MandatorySched PresentTime ExpirationTime TimeEnableFlag OfferFlags PkgFlags ProgramFlags TS_Type BootImageID TS_Flags
    0 0 * SMS000US    2017-05-08 08:51:00.000 2017-05-08 08:51:00.000 8193 277741568 0 152084496 2 CN100004 0

    Monday, May 8, 2017 4:01 PM
  • I've seen the exact same issue (also using 1702). The problem for me was that some random client took the "x64 Unknown Computer" objects GUID as it's own GUID during a deployment.

    As this happened no other client (deployed as an unknown computer) was able to find any task sequences (as the computer was "known").

    I queried the SQL DB (System_DATA table) for the unknown guids (can be seen in your log file below) and found the offending client. Reinstallation of the client (and removing of the smscfg.ini + the SMS certs) resolved the issue, as the computer rejoined the SCCM-Environment with a proper GUID.

    • Proposed as answer by FKaufmann Friday, June 2, 2017 8:31 AM
    Monday, May 8, 2017 7:03 PM
  • This one deployment is not marked for PXE/Media.

    When you create a deployment, under the "Deployment Settings", on "Make available to the following", you need to select one that has "media and PXE."

    Monday, May 8, 2017 8:09 PM
  • I've seen the exact same issue (also using 1702). The problem for me was that some random client took the "x64 Unknown Computer" objects GUID as it's own GUID during a deployment.

    As this happened no other client (deployed as an unknown computer) was able to find any task sequences (as the computer was "known").

    I queried the SQL DB (System_DATA table) for the unknown guids (can be seen in your log file below) and found the offending client. Reinstallation of the client (and removing of the smscfg.ini + the SMS certs) resolved the issue, as the computer rejoined the SCCM-Environment with a proper GUID.

    I'll give this a go and report back,  thank you!
    • Marked as answer by Chhan Monday, May 8, 2017 11:07 PM
    Monday, May 8, 2017 8:20 PM
  • This one deployment is not marked for PXE/Media.

    When you create a deployment, under the "Deployment Settings", on "Make available to the following", you need to select one that has "media and PXE."


    Hi Kerwin,  we do have this setting already enabled.
    Monday, May 8, 2017 8:20 PM
  • From the query result that you posted, the OfferFlags is 0. It could be that I just did not correctly line-up the column names with values. Can you please let me know what the OfferFlags value is?

    Also, can you also please run this query?

    select * from UnknownSystem_DISC

    Monday, May 8, 2017 10:22 PM
  • I've seen the exact same issue (also using 1702). The problem for me was that some random client took the "x64 Unknown Computer" objects GUID as it's own GUID during a deployment.

    As this happened no other client (deployed as an unknown computer) was able to find any task sequences (as the computer was "known").

    I queried the SQL DB (System_DATA table) for the unknown guids (can be seen in your log file below) and found the offending client. Reinstallation of the client (and removing of the smscfg.ini + the SMS certs) resolved the issue, as the computer rejoined the SCCM-Environment with a proper GUID.

    I'll give this a go and report back,  thank you!

    Sure enough, this was the problem.  I deleted the device with the same object GUID as the x64 unknown computer and everything is working now.  Thank you everyone who assisted!
    Monday, May 8, 2017 11:08 PM
  • Sorry Ichhan,

    can you should me the SQL SCRIPT that identifies Systems using GUID belonging to x64 Unknow - having the same issue here


    RDunne76

    Thursday, May 11, 2017 1:38 PM
  • Sorry Ichhan,

    can you should me the SQL SCRIPT that identifies Systems using GUID belonging to x64 Unknow - having the same issue here


    RDunne76

    Hi RDunne76,

    I created a WQL query that looked for any device with the matching x64 unknown GUID.

    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SMSUniqueIdentifier = "<INSERT x64 unknown GUID>"

    the x64 unknown computer GUID can be found in your SMSTS.log file during OSD.

    Wednesday, May 17, 2017 3:18 PM
  • Wow... How does this even happen?  I'm pretty sure this just resolved the issue I was having as well. 

    https://social.technet.microsoft.com/Forums/en-US/6d78b186-3025-4753-bcbb-d209bf1213ca/sccm-marking-all-clients-as-known?forum=ConfigMgrCBOSD

    I just looked and I saw a client imaged recently with the same CM UID as my unknown x64 computers object.  What a coincidence. 


    • Edited by James JLO Thursday, May 18, 2017 3:12 AM
    Thursday, May 18, 2017 3:11 AM
  • For now, you need to do the following:

    1. Delete all the records under the Unknown Machine collections for all sites.

    2. Set the CreatedUnknownDDR value to 0 (HKLM\Software\Microsoft\SMS\COMPONENTS\SMS_DISCOVERY_DATA_MANAGER). Do this for all sites. Restart the SMS Executive service on all sites. This should force the creation of new Unknown Machine records.

    Wait a while for new policies to be generated for the new Unknown Machine records.

    3. With an unknown machine, do not use the "Previous" button on the Task Sequence client wizard.

    The really important part is #3. This is what is causing the Unknown Machine GUID to be registered as the client ID. When you are in the Task Sequence client wizard, do not use the "Previous" button.

    The "Previous" button is enabled in 1702, which allows you to restart the TS client wizard in case of a failure or if you need to select a different TS. It has an undesirable side effect for unknown machines, causing the TS pick the Unknown Machine GUID and use it for client registration.


    • Proposed as answer by miguelanyez Tuesday, May 23, 2017 8:18 PM
    Tuesday, May 23, 2017 1:24 AM
  • For now, you need to do the following:

    1. Delete all the records under the Unknown Machine collections for all sites.

    2. Set the CreatedUnknownDDR value to 0 (HKLM\Software\Microsoft\SMS\COMPONENTS\SMS_DISCOVERY_DATA_MANAGER). Do this for all sites. Restart the SMS Executive service on all sites. This should force the creation of new Unknown Machine records.

    Wait a while for new policies to be generated for the new Unknown Machine records.

    3. With an unknown machine, do not use the "Previous" button on the Task Sequence client wizard.

    The really important part is #3. This is what is causing the Unknown Machine GUID to be registered as the client ID. When you are in the Task Sequence client wizard, do not use the "Previous" button.

    The "Previous" button is enabled in 1702, which allows you to restart the TS client wizard in case of a failure or if you need to select a different TS. It has an undesirable side effect for unknown machines, causing the TS pick the Unknown Machine GUID and use it for client registration.


    "Workaround" explained by Kerwin solved correctly the issue. Applied in SCCM CB 1702 when a technician press "Previous" button and stopped working task sequence for unknown computers.
    Tuesday, May 23, 2017 8:21 PM
  • This happened exactly in our environment as well. After deleting the computer with the same GUID as the "x64 unknown computer" everything worked fine again.

    Thank you so much for this hint!

    Friday, June 2, 2017 8:32 AM
  • Seems I had the same issue. This worked for me:

    First Kerwin Medinas query to get the x64 unknown computer ID.

    select * from UnknownSystem_DISC

    Then I modified to find the computer name

    select * from System_DISC where System_DISC.SMS_Unique_Identifier0 = '<INSERT x64 unknown GUID>'

    Then I just deleted the computer object from console and task sequences started working again. I'll just reimage the one with the broken agent for now.

    /prostrate to the people figuring this out. :)


    • Edited by Neverest Friday, June 2, 2017 12:11 PM
    • Proposed as answer by Shane Kinzer Tuesday, August 1, 2017 10:05 PM
    Friday, June 2, 2017 12:09 PM
  • For now, you need to do the following:

    1. Delete all the records under the Unknown Machine collections for all sites.

    2. Set the CreatedUnknownDDR value to 0 (HKLM\Software\Microsoft\SMS\COMPONENTS\SMS_DISCOVERY_DATA_MANAGER). Do this for all sites. Restart the SMS Executive service on all sites. This should force the creation of new Unknown Machine records.

    Wait a while for new policies to be generated for the new Unknown Machine records.

    3. With an unknown machine, do not use the "Previous" button on the Task Sequence client wizard.

    The really important part is #3. This is what is causing the Unknown Machine GUID to be registered as the client ID. When you are in the Task Sequence client wizard, do not use the "Previous" button.

    The "Previous" button is enabled in 1702, which allows you to restart the TS client wizard in case of a failure or if you need to select a different TS. It has an undesirable side effect for unknown machines, causing the TS pick the Unknown Machine GUID and use it for client registration.


    Hi, how do you delete all records under All unknown computers collection. The delete button is greyed out when you select the x86 or x64 unknown computer item.
    Wednesday, June 21, 2017 12:33 PM
  • Thank you, It worked great but i had an issue with one of the dp's not sending out dhcp. Turned out that it had disabled request to pxe in wds. 4 hours later and everything is now working!!
    • Proposed as answer by krs187uk Thursday, July 20, 2017 11:08 PM
    Thursday, July 20, 2017 11:08 PM
  • Seems I had the same issue. This worked for me:

    First Kerwin Medinas query to get the x64 unknown computer ID.

    select * from UnknownSystem_DISC

    Then I modified to find the computer name

    select * from System_DISC where System_DISC.SMS_Unique_Identifier0 = '<INSERT x64 unknown GUID>'

    Then I just deleted the computer object from console and task sequences started working again. I'll just reimage the one with the broken agent for now.

    /prostrate to the people figuring this out. :)


    Thank you!    

    This worked for me!  

    I was pulling my hair out over this one.  


    Tuesday, August 1, 2017 10:07 PM
  • select * from UnknownSystem_DISC

    select * from System_DISC where System_DISC.SMS_Unique_Identifier0 = '<INSERT x64 unknown GUID>'


    I see guids in smsts.log, my DB shows me 6 guids since I have 6 unknown computer x86 and x64 now, but when I query the guides, DB shows me only unknown, and none of existing computer.

    So, unknown computer record still does not hook up TS, after I even upgraded to 1706 and redistibuted Boot images.


    Please remember to mark my post as an answer, if I really helped you out, or vote if usefull. Thank you!

    Tuesday, September 19, 2017 10:27 AM
  • Since I had this issue as well, a word regarding the root cause: Our primary server had run out of disk space, thus components like the management point didn't function properly any more. I assume that a machine that was accepted as unknown computer to that time kept the unknown computer SMS GUID and caused the process to stop. Our environment is on 1710.

    Kerwin, Neverest, many thanks for the helpful queries, they allowed us to identify the culprit.


    Monday, January 29, 2018 12:31 PM
  • we are also seeing machines being deleted from console but not being removed from the database. (also 1710) have checked disk space on primary - not an issue.

    the query below shows 2 entries, the only differing field in the timestamp.

    SELECT gcs.Name0, gna.MACAddress0

    FROM v_GS_COMPUTER_SYSTEM gcs
    JOIN v_GS_NETWORK_ADAPTER gna ON gcs.ResourceID = gna.ResourceID

    WHERE gna.MACAddress0 = '<MAC ADDRESS>'

    View - v_r_system however doesn't show any entries.

    tried : 

    select * from UnknownSystem_DISC

    and

    select * from System_DISC where System_DISC.SMS_Unique_Identifier0 = '<INSERT x64 unknown GUID>'

    but no entries showed 

    any ideas what might be causing this?


    AROVBUKAY

    Thursday, March 8, 2018 3:33 PM
  • The Previous button was causing it for us.  Since we cannot prevent users from using this button. Is there a more proactive way to prevent this? 

    I read an article about BannedGUIDs registry key on the WDS server, but the SMBIOS_GUID was different in my case. This issue caused by duplicate SMS_UUIDs.
    Thursday, March 15, 2018 9:11 PM
  • You just need to upgrade to more recent versions which does not have this problem.

    Tuesday, March 20, 2018 11:59 PM
  • An Alternative fix is:

    1. Open an elevated command prompt and run Sc \\computername stop "ccmexec"
    2. From the problem device delete the file C:\windows\smscfg.ini
    3. Delete the device from SCCM
    4. Run the System Discovery again to re-add that device
    5. Right-click on the device > Install Client > select all options to reinstall

    Friday, April 27, 2018 10:17 PM
  • Just had this same issue on my primary site. Liked to have pulled all my hair out. I used your solution to find the offending client in the System_DATA table. Here's another strange bit - the offending GUID was written in the row without the 'GUID:' prefix, which made my SQL where filter containing that prefix fail to find it. Fortunately, I did scroll through the table rows and this row missing the prefix caught my eye. This client was an unused and removed machine, so I just deleted the device and all is working again.

    Friday, May 3, 2019 7:07 PM