WSNAME

[Praxi]

Hi all,

I've been searching around on the forums with little luck for a topic similar to mine. Heres the issue, doing unattended installs of XP Pro, and I have a batch process that runs wsname and restarts and then joins the domain. the domain join us a runonce task, I'm using a autoitscript thats doing WMI? commands (The script was pulled from the autoit User submissions. It was basically a GUI LDAP browser with a join domain, I just stripped out the GUI bits). The Autoit WMI is returning error 8525 on SOME machines (seems repeatable, once I get it on a machine, I will allways get it on the same machine). I haven't had any luck figuring out exactly what that error is. So I started poking around on the machine, and I noticed the netbios name is different than the computer name. I checked the wsname log file, and it thinks everything is fine. I am unsure if I am even barking up the right tree with thinking I'm having problems with wsname. The only thing I have that indicates issues with the computer name, if I tried to join AD by hand, it would generate errors.

A popup that says the name change failed (name was all ready changed, it was just a join ad at this point), and then some event viewer errors, 5788 & 5799. "Attempt to update HOST service Principal Names (SPNs) of the computer object in the Active Directory failed. The updated values were 'HOST /071PBRKJT21' and 'HOST /OED-3FFFd908464'. The following error occurred: The parameter is incorrect." The OED-* is the randomly generated name from the unattended, and currently the netbios name of the PC in question. I've searched for those event ID's and they don't seem to make a whole lot of sense in the fact it works on some, and fails on others.

Should I be waiting for certain processes or services to start before I attempt to do the rename? Any ideas anyone can think of? My goal here is to have a computer renamed to a section number + serial number and then a successful join domain.

[iamtheky]

Symptoms point towards disjointed namespace.

http://support.microsoft.com/kb/258503

[Praxi]

Ya I looked at that, but why would I be getting that when I reimage 4 machines at the same time, they have no existing computer objects in the domain. 2 of the machines work, and 2 don't.

Symptoms point towards disjointed namespace.

http://support.microsoft.com/kb/258503

[iamtheky]

I noticed the netbios name is different than the computer name.

so 2 names per computer

4 computers

Are all 8 names different? if there are duplicates anywhere in that equation i would think it begins there.

Edited May 27, 2009 by iamtheky

[Praxi]

The 2 machines that worked, the computer name matches the netbios name. The 2 machines that did not, the names do not match. I have verified that all the computer names are different. I have not verified the netbios names are all unique, I would assume so though, as they are just the randomly generated names during the unattended portion of the XP install.

[iamtheky]

you will probably have to explain what you are seeing in the machines where there are discrepancies between the host/netbios name.

Is it trying to make a ridiculous long host name and truncating it to the first 15 characters for NetBios?

Making sure the name is not all numbers?

[Praxi]

Here is an example of the final computer name '071PBRKJT21'. Here is what the netbios name looks like for the same machine 'OED-3FFFd908464'. During the unattended, the name starts off as that randomly generated string OED-3FFFd908464. As a post install task, I use WSNAME to rename it to 071PBRKJT21 (Cost Center + Serial Number). The machines that are working joining the domain, have both their computer name and netbios name changed to something like 071PBRKJT21. The machines that aren't working joining the domain, have the mismatch in name after the wsname runs. Is my explanation legible or am I not explaining myself correctly?

Thanks for the help so far, its appreciated