locked
Windows 10 1803 - sysprep problem computer name RRS feed

  • Question

  • Hi,
    I have problem to set computer name with sysprep with Windows 10 1803 (before with Windows 10 1709 it worked).
    Windows generate random name WIN-xxxx insteasd of my name what i set in my sysprep response file XML

    <ComputerName>UCXXXX</ComputerName>

    I don’t understand because domain joined works

    With the log of sysprep i juste see this but no info to resolve this :

    2018-05-17 17:27:56, Info       [0x060258] IBS    GenerateName: Failed to read the Key UserData\FullName\Value from Blackboard defaulting to WIN
    
    2018-05-17 17:27:56, Info       [0x060259] IBS    GenerateName: Failed to read the Key UserData\OrgName\Value from Blackboard
    
    2018-05-17 17:27:56, Info       [0x06025d] IBS    Callback_ComputerName_Validate:Computer name is WIN-RSBIBOU3CAD
    
    2018-05-17 17:27:56, Info       [0x06025a] IBS    Callback_ComputerName_Generate:Computer name [WIN-RSBIBOU3CAD] is valid.
    
    2018-05-17 17:27:56, Info                         [setup.exe] OrchestrateSetComputerNameOnline: Set the computer name to WIN-RSBIBOU3CAD



    Have you succeeded to sysprep new Windows 10 1803 with personnalize computer name ?
    If yes how you do this ?

    Regards.


    • Edited by Florentyyy Friday, May 18, 2018 2:53 PM syntax error
    Friday, May 18, 2018 10:24 AM

Answers

  • It's work with other sysprep.
    Maybe options what i use in my orgin sysprep are depreciate with W10 1803.

    I go to create new sysprep from ADK 1803

    Thanks

    • Marked as answer by Florentyyy Wednesday, May 23, 2018 2:47 PM
    Wednesday, May 23, 2018 2:47 PM

All replies

  • I'm having this exact same issue.  I deployed an image that is Windows 10 v1703 x64 (fully patched) and the computer gets renamed correctly and joined to my domain.  When I deploy an image that is Windows 10 v1803 x64 (fully patched), the computer DOES NOT get renamed correctly but it still joins my domain.  Like yours, my computer gets renamed to WIN-XXXX.  I am able to change the name manually so I don't believe there's a name conflict in AD when it goes to rename it.  If I look in C:\Windows\Panther\unattend.xml, the name set in the <ComputerName> tag is set correctly so I'm not sure what the problem could be.

    In a test environment, I deployed an image that is only a base install of Windows 10 v1803 x64 with no updates at all and the computer DOES get renamed correctly and joined to my test domain.  I'm still trying to figure out why it gets renamed correctly in my test environment and not in my live environment.


    • Edited by T3chGuy007 Friday, May 18, 2018 2:47 PM
    Friday, May 18, 2018 2:43 PM
  • At ease i'm not alone.Exactly same situation, i think it's not work when upgrade with windows update.

    Works only with new installation from scratch, with the new ISO 1803.

    But not acceptable in professional environment, to restart new installation with the new ISO every 6 months (with many many modifications to do in our image)

    Friday, May 18, 2018 2:57 PM
  • I actually did a clean install of Windows 10 v1803 x64 on both of the systems that I'm testing with.  The only difference that I can find is the one in my test environment does not have any 1803 patches.  It is just a base install with like Chrome and Firefox installed.  The one that doesn't rename correctly is fully patched with the latest v1803 patches and all of my software installed.
    Friday, May 18, 2018 3:04 PM
  • With your W10 1803 (not patches where it's work) : You have doing installation from scratch with ISO 1803 ? Or update from 1709 ?
    Friday, May 18, 2018 3:24 PM
  • On both systems, I did a clean install of Windows 10 v1803 x64 from an ISO.  Neither system was an upgrade from v1703 or v1709.
    Friday, May 18, 2018 3:35 PM
  • ooh bad news.. That means problem comes from an windows update.

    And in Windows 10 we can't choose what updates to install (all or nothing)

    Friday, May 18, 2018 4:42 PM
  • I believe I found out why v1803 was not renaming the PC correctly.  When I built the reference image for my live environment, I set the name of the PC to what it was going to be called in AD after my reference image was deployed to it.  In my test environment though, I left it with whatever random name Windows used when I did the clean install of v1803.  Apparently, in v1803, if the computer is configured with the same name as specified in your .xml file, it skips renaming it and applies a random name.  If the name of the PC is set to something random, then during OOBE, it will change it to what you have specified in your .xml.  

    I verified this works because on the PC in my live environment, I renamed it to something random, ran sysprep, shutdown the PC, uploaded the image, and then deployed the image.  After the deployment was finished, the PC was joined to my domain with the correct name.  In my test environment, I changed the PC from the random name to the name that was specified in the .xml and after I deployed the test reference image, it was joined to my domain but with a random name.  I also verified that if the name of the PC is set to what it was going to be called in AD and the PC is running v1703, it still renames it.  This must be a change in v1803.
    • Proposed as answer by Al Raymond Wednesday, August 1, 2018 7:18 PM
    Friday, May 18, 2018 8:24 PM
  • Thanks for your complete tests.

    I'm going to do new tests.

    In my case the name is not same as image but i realized that i have 2 same unattend.xml (in C:\Windows\Panther and C:\Windows\System32\sysprep).

    I go to try to use only C:\Windows\Panther

    Saturday, May 19, 2018 10:06 AM
  • It's work with other sysprep.
    Maybe options what i use in my orgin sysprep are depreciate with W10 1803.

    I go to create new sysprep from ADK 1803

    Thanks

    • Marked as answer by Florentyyy Wednesday, May 23, 2018 2:47 PM
    Wednesday, May 23, 2018 2:47 PM
  • Ok.  I was using ADK for Windows 10 v1803 as well.  Glad to know it is working for you too!
    Wednesday, May 23, 2018 3:15 PM
  • If you want i can send my last sysprep who it's work
    Wednesday, May 23, 2018 3:19 PM
  • Can you send it please. I am experiencing this same problem.  I will download the latest ADK
    Wednesday, June 6, 2018 3:45 PM
  • THANK YOU. 

    This is what is causing this behaviour for me as well. 

    I have a machine prestaged in AD. I sysprep/capture on that machine, upload it, attach an xml, and then bring it back down on the same machine. It is skipping the computer rename stating that it already is named. It is then given a name of WIN- later on. 

    If I image a different prestaged machine, it gets named fine. 


    Wednesday, June 6, 2018 8:19 PM
  • Hello!

    we have the same problem.

    pre sysprep: Hostname "XYZ800"

    Sysprep + Unattend.xml (computername XYZ800)

    C:\Windows\Panther\setupact.log

    2018-06-14 13:02:19, Info       [0x060259] IBS    GenerateName: Failed to read the Key UserData\OrgName\Value from Blackboard
    2018-06-14 13:02:19, Info       [0x06025d] IBS    Callback_ComputerName_Validate:Computer name is WIN-FFHHNMUC57Q
    2018-06-14 13:02:19, Info       [0x06025a] IBS    Callback_ComputerName_Generate:Computer name [WIN-FFHHNMUC57Q] is valid.
    2018-06-14 13:02:19, Info                         [setup.exe] OrchestrateSetComputerNameOnline: Set the computer name to WIN-FFHHNMUC57Q
    2018-06-14 13:02:19, Info       [0x070035] DIAG   CallBack_DiagnosticDataGeneration: Called with notification for Initialization


     C:\Windows\Panther\UnattendGC\setupact.log

    2018-06-14 13:02:49, Info                         [Shell Unattend] ComputerName in unattend [XYZ800] matches the current ComputerName [XYZ800]
    2018-06-14 13:02:49, Info                         [Shell Unattend] Skipping setting the same ComputerName
    2018-06-14 13:02:49, Info                         [Shell Unattend] ProductKey set
    2018-06-14 13:02:49, Info                         [Shell Unattend] TimeZone: Time zone set to 'W. Europe Standard Time'
    2018-06-14 13:02:49, Info                         [Shell Unattend] Exiting 'specialize' pass with status 0x00000000

    final Hostname WIN-FFHHNMUC57Q :|


    if hostname (unattend.xml) is changed to e.g. XYZ801. all works fine.

    Thanks


    • Edited by Klü Thursday, June 14, 2018 12:21 PM
    Thursday, June 14, 2018 12:20 PM
  • We are seeing this exact same thing, and this is for sure an issue. The next step is to be sure Microsoft knows it is an issue. 
    Wednesday, August 1, 2018 7:19 PM
  • Exact same issue here.  I built a W10 box from scratch, applied 1803, syspreped, uploaded into WDS.  When we push the image down, the tech is prompted for a computer name, and it has always worked, however, today the machine name is WIN-XXXXX regardless of what is typed in the computer name prompt. 

    I keep my unattend.xml extremely light.  I've never had to put a COMPUTERNAME setting in the Windows-Shell-Setup blank, as the WDS prompts for it and it has always worked.

    I need to automate this process as much as possible, as the people that deploy these machines in other remote offices don't have a ton of compute knowledge, and renaming a computer post image will not sit well with them, not to mention the fact that you need elevated privileges.  My only other option is to image this pre 1803 and that will require every imaged box to receive a 2+ gig update.

    Thanks for this topic, hopefully we will get resolution soon.



    -Scott

    Monday, August 6, 2018 1:54 PM
  • Hi,

    Do you use FOG ?

    Tuesday, August 28, 2018 7:28 AM
  • Is anyone having any success with getting a prompt for computername working? I also have done this for years..now with windows 10 it is no longer working no matter what trick I use. i was leaning towards doing something with setupcomplete.cmd ....thoughts? 
    Wednesday, September 19, 2018 1:48 AM
  • Hi T3chGuy007

    You have saved me hours of frustration....literally word for word what had happened on my scenario.
    Thanks to you I can now get some sleep (it's 02:23am in Australia) right now..

    Thanks so much for sharing your experience ;-) 

    Saturday, December 1, 2018 3:24 PM