RIS system naming problems

[Erick T]

I have RIS setup with a custom naming scheme for new systems imaged.
The format is "WS-%7MAC-%#", which is WS-, followed by 7 digits of the
MAC, followed by a sequential number. This works on most systems, but
there are some systems that always come up with the name format
"WS-%MAC", which is what I had it set to some months ago. The
difference between the two is in the hardware. The systems that work
are iPaq Celeron 500s, and the ones that don't work are Shuttle Athlon
XP cubes (SK41G). I don't see why one should work and one not... Any
thoughts?

Thanks,
Erick

 

[Oli Restorick [MVP]]

Which piece of software are you using to grab the MAC address and construct
the name?

 

[Erick T]

Oli,

Thanks for the response. I am using RIS custom naming in the AD Users
and Computers admin application. I think I've figured out the problem.
For some reason, the unique ID on the system was associated with an
existing computer account, so the name would be automatically set to
the existing account name. I'm not sure if that system had actually
been on the network or not.

What determines the unique ID for a system? I've been having other
problems relating to GPOs not applying, in additional to the naming
problems, and I'm wondering if it isn't more naming issues.

Thanks,
Erick

 

[Oli Restorick [MVP]]

Hi there

As I understand it, the unique ID is either the unique ID number specified
by the SMBIOS (system management BIOS) or, if that is not present, the MAC
address of the first network card padded with zeros.

That may well explain why only certain PCs are giving you the problem. My
current PC is actually a later Shuttle model than the one you have and it
doesn't have the GUID specified in the SMBIOS. The iPaqs will definitely
have the SMBIOS stuff programmed into them.

Oli

 

[Erick T]

Oli,

This makes sense, and explains the problem. It turns out that I can't
modify the Unique ID in the iPaqs. I understand the reason for not
being able to do that, but it certainly is a hassle.

Thanks for your help,
Erick