Solved!
Go to SolutionDT
DELL-Tyler M
Moderator
•
350 Posts
•
3 Points
0
6158
September 25th, 2019 09:00
Computer names with Image Assist
Image Assist provides two options for naming computers.
- Auto generate name: This uses Windows default auto-naming. e.g. DESKTOP-ILJECHA
Custom Name: Here, you can add a prefix or suffix to the Dell service tag, with a max of 15 characters. Note: If a prefix or suffix is not added, a “D” will be prepended to the service tag to prevent all-numeric service tags from breaking Windows, which does not support all numeric computer names.
Additional customization: Dell Deployment Services offers more naming options during factory imaging. Contact your Dell sales rep to learn more or join our weekly live webinar. www.dell.com/imagingwebinar
Related Articles:
Contact us for more information.
If you do not already have a Dell contact, use the Global Imaging Contact Sheet to get started.
Learn More with Live Webinars.
See Dell Configuration Services Imaging & Provisioning Webinar for webinar schedules and registration details.
every Thursday from 9:30AM-10:30AM CST (3:30-4:30 UTC/GMT)
(edited)
5019
0
Posted November 5th, 2019 06:00
Working on my own naming convention within the IA form
4355
0
Posted May 12th, 2020 20:00
Hi Tyler,
this is first time I am using Dell ImageAssist, I am impressed with the available tools and I have a problem getting the custom computer name.
At one point I was getting the prefix WS in front of the Service Tag, but something happened and I am only getting that generic WS1234XYZ.
The unattend.xml has: WSService_Tag
I copy the unatted.xml from C:\Windows\Panther.
To give you the complete picture, after I get my Dell_Captured_Image.wim I use the boot.wim generated by the ImageAssist installed with /deploy as I want to use the WDS.
After importing the boot.wim and the Dell_Captured_Image.wim, I use the unattend.xml together with the Dell_Captured_Image.wim
Two things stopped working, the Custom Computer Name and it doesn't join the domain anymore.
What I am doing wrong?
Thanks a lot!
Roberto
4328
0
Posted May 16th, 2020 09:00
Any recorded ImageAssist webinar available for viewing? I missed last week's webinar.
4312
0
Posted May 18th, 2020 06:00
@talt - our weekly webinars are not recorded. Please join us for one sometime. Thursdays 9:30-10:30 CST (UTC-06:00) https://www.dell.com/community/ImageAssist/Dell-Configuration-Services-Factory-Imaging-amp-Provisioning/td-p/7386282
Thanks,
TM
4061
0
Posted July 14th, 2020 14:00
Thanks Tyler!
Unfortunately I did not receive a notification for your reply.You are right, at one point I restored the image into a VM. I created several captures since my post and the computer name got fixed.
I still cannot figure out why it fails the domain.
The service account and the OU I am using is working for our Lenovo fleet. The service account has right to create an object on that particular OU.
The driver packs for my 3 models are also saved on a shared network drive. This time I also copied them to C:\Out-of-Box Drivers.
I am capturing right now another image using Dell_IAX and let you know. I will still use the Dell PXE boot created with ver.8 as I don't have MDT or SCCM at this point.
One other bug I had was the boot sequence being modified. The SSD is pushed the last one on my boot sequence if I use Dell PXE boot. Since ver.10 doesn't have this option, I guess I have to wait for the new tools.
DELL-Tyler M
Moderator
•
350 Posts
•
3 Points
4340
1
Posted May 13th, 2020 13:00
Hi Robert,
The computer naming issue arises from the captured image being booted or restored in a VM and then recaptured with the previously processed unattend.xml. This is because during OOBE, the ‘Service_Tag’ variable in the unattend.xml is replaced with 1234XYZ when the source machine is a VM. This prevents Windows setup from crashing due to long VM serial numbers.
2 fixes:
Related: Troubleshooting domain join failures with Dell Image Assist
Thanks,
Tyler
(edited)