7 Replies Latest reply on Jul 6, 2016 8:41 AM by dynamozappa

    Re-naming Win 10 computer fails


      I am using LD Management Suite v. 9.6 SP2. I have captured a Win 10 image and i'm trying to redeploy it to a computer using Sysprep. With my Win 7 images i have always used the %ldHostname% variable inserted into my sysprep file...which seems to work just fine. With this new Win 10 image I cannot seem to get it to rename the computer successfully. It just generates a random name instead. I have tried using %ldDeviceID% and %ldDisplayname% but i have had no luck with it.


      Does anyone know how to successfully re-name a machine that has Win 10 on it. I do know about the device name prompt that lets you change the name on the fly. But that is not feasible in a 40 computer lab. I need the process as automated as possible.


      any help would make my boss happy.



        • 1. Re: Re-naming Win 10 computer fails
          Rick.Smith1 Expert

          I am deploying windows 10 without this issue using 9.6 SP2 also.


          The variable we use is %ldHostname% which is assigned to "Computer"."Device Name".


          The specialized section of my unattend file for this setting is:




          I am assuming you already have Inventory records for these devices in LANDESK.


          You might try injecting the script then stopping (or pausing) the template item long enough to check in WinPE if the file name was also injected. We got thrown off during one issue where LANDESK was injecting the unattend correctly with the computer name, but we had another process overwriting it due to some customized code.


          Hope that helps.

          • 2. Re: Re-naming Win 10 computer fails
            riccafer Apprentice

            Check if it is present on the image another unattend.xml created from your vendor (Dell, HP,...). Here you can find the possible path of unattend.xml and the search order Methods for Running Windows Setup

            • 3. Re: Re-naming Win 10 computer fails

              Hey rictersmith and riccafer,


              thanks for the reply. Yes. I am doing it the same way. I add the computer into inventory via the Bare Metal utility. Then during the provisioning process i inject the sysprep file (unattend.xml). I use the variable %ldHostname% in the Specialized section of unattend.xml


              It's funny you say that about your issue with injecting the unattend.xml file. I was trying it again this morning and i got the fatal sysprep error (the one that says it could not process the specialized section of the file). I have had this issue in the past too and in researching it i found that LANDesk appends to the unattend.xml file that gets injected. I can't recall what it edits in the sysprep file but maybe that is happening here. While troubleshooting this in the past, i have found my unattend file to be completely blank after a certain section. Do you happen to know what LD appends to the unattend.xml file?


              And regarding the link you sent, riccafer, it says that you can explicitly specify what unattend file to use....which is what i do. Here is my sysprep command:

              c:\windows\System32\sysprep\sysprep.exe /oobe /generalize /reboot /unattend:c:\unattend.xml


              So i don't think it is using another unattend file.


              thanks for the help.



              • 4. Re: Re-naming Win 10 computer fails
                Rick.Smith1 Expert



                This is the link explaining a bit about CTOS. Check the section about the specialize section, which is what I believe you were referring to.

                How to troubleshoot the Configure Target OS (CTOS) action in Provisioning templates


                Here is some things you should check about the unattend injection.

                How to troubleshoot Inject Script action during OS Provisioning


                When you generalize and seal your image you are specifying the unattend file location and the unattend to use. I am assuming that you are using the LDMS Inject Script action item and copying it to C:\unattend.xml and that no other unattend files exist in any other location.

                We use the path C:\Windows\Panther\unattend.xml, since that is the first place Windows checks by default. (Technically second if you count the registry)

                Here is some information about the search order: https://technet.microsoft.com/en-us/library/cc749415(v=ws.10).aspx

                You are placing it in the location Windows checks last. If any other unattend file happens to exist elsewhere, then that file will be used first.

                Hope that helps.


                • 5. Re: Re-naming Win 10 computer fails

                  Hey Rick,


                  I forgot to mention that i inject my unattend file in two places: C:\Windows\Panther\unattend.xml and C:\unattend.xml.

                  I'll take a look at those links.



                  • 6. Re: Re-naming Win 10 computer fails

                    It looks like the unattend.xml file that i injected is there in both the places that i injected it. I checked it during the provisioning process. When i looked at the unattend file the computername field was populated with this string: {1582B238-801F-3C4F-9D66-62154BE98BEC}.


                    Not sure where that is coming from but at least i know that Landesk is passing something to the unattend file.


                    Also, the machine is joining the domain and i am not doing that in any other part of the provisioning process. I do that with the unattend file.





                    • 7. Re: Re-naming Win 10 computer fails

                      so this morning i created a new public variable called %CompName% which pointed to "Computer"."Device Name" which is the same as %Hostname%


                      I plugged this new public variable into my unattend.xml and it seems to rename the computer properly. gonna do further testing but as of now...it works.


                      go figure.