none
USB Stick OSD - Unable to retrieve the machine name from SMS database. Fall back to the current local computer name. RRS feed

  • Question

  • Hello,

    SCCM CB (recent version) - deploying Windows 10

    I get this error in the Log:

    Setting machine name from SMS database.        TSMBootstrap   18.06.2020 11:59:28       1496 (0x05D8)

    Unable to retrieve the machine name from SMS database. Fall back to the current local computer name.                TSMBootstrap   18.06.2020 11:59:28       1496 (0x05D8)

    OSD works fine except it does not register with the previous imported computer name. Double checked the mac, everything is fine. No matter what type of hardware I try (laptop/old/new/desktop). Everytime the same result. Deploying it via PXE works perfectly - only the USB Stick does not work.

    Any ideas?

    Greetings, Stefan


    • Edited by ollyhal Monday, June 22, 2020 9:02 AM added pix
    Monday, June 22, 2020 9:00 AM

Answers

  • MediaType = FullMedia

    This is expected behavior as stand-alone media specifically assumes no connectivity to the site and does not attempt to connect to the site during the task sequence for most things.


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

    • Marked as answer by ollyhal Tuesday, June 23, 2020 5:50 PM
    Tuesday, June 23, 2020 5:11 PM
  • From https://docs.microsoft.com/en-us/mem/configmgr/osd/deploy-use/create-stand-alone-media: "Stand-alone media in Configuration Manager contains everything required to deploy the OS on a computer without a network connection."

    It's not an error, it's a warning. Also, out of context, it's meaningless which is exactly why I needed to review the entire log to properly tell you what's going on.

    It's the way it is because that's the way the devs designed it. It can't retrieve the name because it didn't even try which, as noted, is by design.

    If your systems have connectivity to the site, why are you using stand-alone media?

    Also, why do you care about the name of the system? Aren't you at least auto-generating the names in the first place?


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

    • Marked as answer by ollyhal Tuesday, June 23, 2020 5:50 PM
    Tuesday, June 23, 2020 5:46 PM

All replies

  • Can you please post the entire relevant portion from the smsts.log?

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

    Monday, June 22, 2020 5:57 PM
  • Hi,

    Thanks for posting in TechNet.

    1. Please help check the smsts.log to see if there is any further information. And also help check the network configuration and NAA are configured correctly.

    2. May we know if you are capturing the reference OS image from a computer that its computer name is longer than 15 characters? If yes, please change it to something shorter to have a try.

    Thanks for your time.

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, June 23, 2020 7:20 AM
  • 1. network cfg and NAA are correct - otherwise normal OSD would not work

    2. we are just deploying an OS image (overwriting the target disk), no capture. From the screenshots you can see that the desired name is just 7 characters long

    I don´t see in any particular passage in the SMSTS.LOG where you might find any more relevant data.. so I´ll provide you with the full log SMSTS.LOG

    Tuesday, June 23, 2020 7:45 AM
  • MediaType = FullMedia

    This is expected behavior as stand-alone media specifically assumes no connectivity to the site and does not attempt to connect to the site during the task sequence for most things.


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

    • Marked as answer by ollyhal Tuesday, June 23, 2020 5:50 PM
    Tuesday, June 23, 2020 5:11 PM
  • is this really the official answer?

    But why is it stated as an error in the log - it seems like the TS would try to connect to the database and fails for whatever reason. At least it´s that what the log says: "Unable to retrieve the machine name from SMS database"


    • Edited by ollyhal Tuesday, June 23, 2020 5:17 PM
    Tuesday, June 23, 2020 5:17 PM
  • From https://docs.microsoft.com/en-us/mem/configmgr/osd/deploy-use/create-stand-alone-media: "Stand-alone media in Configuration Manager contains everything required to deploy the OS on a computer without a network connection."

    It's not an error, it's a warning. Also, out of context, it's meaningless which is exactly why I needed to review the entire log to properly tell you what's going on.

    It's the way it is because that's the way the devs designed it. It can't retrieve the name because it didn't even try which, as noted, is by design.

    If your systems have connectivity to the site, why are you using stand-alone media?

    Also, why do you care about the name of the system? Aren't you at least auto-generating the names in the first place?


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

    • Marked as answer by ollyhal Tuesday, June 23, 2020 5:50 PM
    Tuesday, June 23, 2020 5:46 PM
  • first, thank you for clearing that up for me.

    It´s a customer, who wants it that way because only in a few locations he has a poor connectivity to the main site and does not want to put a DP into that location for just a few people.

    Regards, Stefan

    Tuesday, June 23, 2020 5:50 PM
  • How about using Peer Cache to deliver the content?

    Alternatively as eluded to, use a script to specify the device name from a set of rules or even prompt the person initiating the process for the name.


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

    Tuesday, June 23, 2020 6:04 PM
  • that would be a better solution - thx
    Tuesday, June 23, 2020 6:27 PM
  • Hi,

    Thanks for all your help to clarify the issue. Have a nice day!

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 25, 2020 2:25 AM