Start a Conversation

Solved!

Go to Solution

Moderator

 • 

342 Posts

5836

September 25th, 2019 09:00

Custom PC Naming with Dell Image Assist

Custom PC Naming with Dell Image Assist:

  • Create Custom Name: Use the Unattend.xml creator to add a static prefix/suffix with the Dell Service Tag for uniqueness. Names must be ≤ 15 characters and not all numeric. If no prefix/suffix is added, a “D” is prepended to numeric Service Tags.

  • Additional Customization: Dell Configuration Services offers more naming options during factory imaging. For local restores, use the Dell Image Assist toolset.

 

Image Assist - List of helpful links & articles

Moderator

 • 

342 Posts

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:

  1. Revert to the snapshot/checkpoint before capturing the image and recapture with a clean unattend.xml.
  2. Alternatively, mount your image using DISM.exe and update the unattend.xml, replacing 1234XYZ with Service_Tag.

Related: Troubleshooting domain join failures with Dell Image Assist 

Thanks,

Tyler

(edited)

November 5th, 2019 06:00

Working on my own naming convention within the IA form

1 Rookie

 • 

4 Posts

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

1 Rookie

 • 

2 Posts

May 16th, 2020 09:00

Any recorded ImageAssist webinar available for viewing? I missed last week's webinar.

Moderator

 • 

342 Posts

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

1 Rookie

 • 

4 Posts

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.

No Events found!

Top