Solved!
Go to SolutionWindows 10 "Creators" v1703, sysprep ERROR unattend.xml "computer name" invalid
Hello,
I am having trouble with Dell Image Assist (DIA) since Microsoft pushed the "Creators" update. I am creating the image and right at the end, it fails. We use the service tag as part of our company naming scheme and when looking at the unattend.XML file I see an underscore when it is referencing
CF10-Service_Tag (text and error logs will be cleaned and added below).
I think it is the underscore it has an issue with and that is being added by DIA. Is there a fix for this?
UNATTEND.XML
schemas.microsoft.com/.../State" xmlns:xsi=" www.w3.org/.../XMLSchema-instance">
CF10-Service_Tag
Company Name
Eastern Standard Time
schemas.microsoft.com/.../State" xmlns:xsi=" www.w3.org/.../XMLSchema-instance">
Domain.local
Password
User
Domain.local
schemas.microsoft.com/.../State" xmlns:xsi=" www.w3.org/.../XMLSchema-instance">
0
schemas.microsoft.com/.../State" xmlns:xsi=" www.w3.org/.../XMLSchema-instance">
NOTIFY_NODIM_UAC_EnableLUA
1
NOTIFY_NODIM_UAC_ConsentPromptBehaviorAdmin
2
NOTIFY_NODIM_UAC_PromptOnSecureDesktop
3
CMDLINES4
4
schemas.microsoft.com/.../State" xmlns:xsi=" www.w3.org/.../XMLSchema-instance">
false
false
schemas.microsoft.com/.../State" xmlns:xsi=" www.w3.org/.../XMLSchema-instance">
0409:00000409
en-US
en-US
en-US
en-US
schemas.microsoft.com/.../State" xmlns:xsi=" www.w3.org/.../XMLSchema-instance">
I understand and had no Sysprep issues previously until Microsoft pushed this latest version. Now I am having an issue creating my image for deployment and it says the issue is with the computer name if I am reading the log correctly.
I am going to attempt to Sysprep once more without the dash and see if that works. I will update with the results later today.
Thank you for the quick reply. :)
tkoscielniak
1 Rookie
•
52 Posts
16032
0
Posted May 19th, 2017 10:00
Hello, Service_Tag is a variable ImageAssist uses that will be populated with the system serial number when the image is deployed through the ImageAssist process. That is a standard variable we use on most deployments.
tkoscielniak
1 Rookie
•
52 Posts
16032
0
Posted May 19th, 2017 11:00
Is the OS version you are using 1703 ?. Also when deploying the image, are you using the ImageAssist usb key ?.
tkoscielniak
1 Rookie
•
52 Posts
16032
0
Posted May 19th, 2017 11:00
Sorry, just saw your os is 1703
Sorry for the delayed response. Yes, this is correct to a point. I can still set computer name with Service_tag, but if I put a dash (-) at the end of the prefix, it fails. If I do not put a dash is succeeds.
Example:
The prefix is used for office location and then the service_tag for asset tracking.
TX1-Service_tag = Error with computer name in "unattend.xml" file during imaging.
TX1Service_tag = No error with computer name during imaging.
The dash makes it much easier to read. I have not tested with another separator (ie underscore) yet and will most likely not get to it until next quarters system image update or a critical update from Microsoft or another vendor we use.
Dell Image Assist
26 Posts
16032
1
Posted June 1st, 2017 08:00
I would like to know if you are using Dell Image Assist USB thumb drive to deploy the image to a computer? if so then you can boot to the DIA USB thumb drive on the computer that is in the failed state. Press F8 with in the GUI and send in the logs.
Please send to the US_OSImaging@Dell.com mailbox so that we can trouble shoot
thank you,
Daniel
MBELBAGRA
1 Message
16032
0
Posted May 29th, 2017 04:00
I confirm,
When you set the option in ImageAssist to generate computer name automatically, Sysprep works fine, but when you set computer name with Service_tag, sysprep failed
last update of ImageAssist and Windows 10 creator update (1703)