Problem regarding imaging and netbios name

[amfony]

hello gang,

i have a new problem which seems to have stumped me. I recently updated an already created image (Ghost), created a new image of that system then rolled it out to approx 30 client computers. the procedure i use is this:

1 Install O/S and apps

2 Configure (using a specifically created admin account) profile to copy to default user

3 run sysprep (with the option left on to regenerate sids)

4 and whilst the computer is DOWN (as in before it boots to create new sids and follow my sysprep.inf answer file) i ghost that image.

So theorectically i can rollout fresh images that havent finshed initializing or joined domains yet, to ensure these are REALLY individual images. sysprep then continues and domain attachment is automated via sysprep.inf so i end up with computers ready to rock and roll.

My problem now stems from the fact that on my LAST set of images, the netbios name seems to have been copied across to every image. Now this is peculiar as when i look at each computer in the my computer properties, computer name, more, netbios name, it actually says the computer unique name. As expected ofcourse. But when i ping a recently imaged computer from another computer with the command "ping -a NEWIMAGE1" i recieve a reply from the correct ip adress, but of the netbios name of the host image computer before sysprep was run on it.

Let me say that bit again, the host image (the computer my image was created from) had a computer name of 'Image010306Builda', and such a netbios name of the same up 2 15 characters ofcourse. Sysprep was run on this computer to regerate sids and the like. When this computer shutdown after sysprep i imaged it. My new images all got new computer names (during the sysprep procedure). But now when i interogate these computers they have the same netbios name as the originaal host computer, whilst their own netbios name configuration IS their own (correct) dns computer name.

i cant seem to find the cause of this. I had a WINs server in operation but removed it for clarity sake, it did not have any records regarding my issue anyway.

Any help please, especially from S.O.E admins or anyone really. Thanks alot guys.

[Unique Touch]

Hi amfony,

This may sound strange but we had exactly the same issue at our DR site recently.

You'll find all the machines are pinging via WINS instead of DNS i.e. WKS001 instead of WKS001.domain.co.uk)

Anyway, the fix the engineering team implemented was to script in an "ipconfig /release" and "ipconfig /release" upon the final boot (after our image was rolled and had at least once booted into windows).

Try that on one machine and then try pinging...you should be able to via DNS and resolve name correctly.

What I couldn't understand was a reboot was NOT resolving the issue...it required a forced ipconfig release and renew. Very strange indeed.

Please post an update here whatever the outcome.

Many thanks

[amfony]

i tried but no dice. under every circumstance i get the same reply. i even ran sysprep again on a image client machine, removed ut from domain, uninstalled the nic, rebooted, searched registry, i disabled netbios expliocilty from the nic, (its disabled by dhcp by default) and no dice. i am at a loss

[+BudMan MVC]

Where are you resolving these names from? Your machine? Every other machine on the network? Where?

Sounds like you have a cached entry or lmhost/host entry in where ever your trying to access these machines from.. What does a nbtstat -A IPADDRESS of the machine in question show?

What does your cache show on the machine your doing these queries from? nbtstat -c

What does the machine in question show for nbtstat -n show?

[amfony]

Sorry for the late reply guys! but i am back now

Sorry budman i should have been more specific, from the newly created image (lets name it CLTIMG) when i ping it self, i get returned its proper "dns" fqdn (and proper address), when i type the command "ping -a IPADDRESS OF SELF" i get the CORRECT DNS name relpy again. Now this is what i expect as i have disabled netbios via DHCP options.

When i ping from ANOTHER (any other) computer to the CLTIMG via its proper name, i get a correct and legitmate dns response (my ddns is working fine and all records are correct for the new images), from anyother computer when i type "ping -a IPADDRESSOFCLTIMG" i get resolved back "ORIGINALIMG" (being the image i copied to rollout to client machines) and the ip address of the CLTIMG box.

Sorry if i am not very clear, but when resolving from it self, the CLTIMG thinks everything is ok. When resolving netbios from another computer it gives me the wrong computername.

I did go through pretty much nbtstat had to aoffer me budman and to confuse me even further when i typed "nbtstat -a CLTIMGIPADDRESS" i get the CORRECT netbios name returned to me.

in the cache if the CLTIMG i get nothing the domain name (which is wierd as i shudnt have any entries here is my netbios is disabled) and nbtstat -n gives me once again my correct computer name.

Interesting no?

I am thinkning along the lines that sysprep itself didnt quite work as supposed to rather then any configuration errors. What is your line of thniking budman? and others ofcourse?

Thanks guys and sorry again about the late reply

[JiveMasterT]

Did you try to do a ipconfig /flushdns? I've seen similar problems and that helped. I think that was on a windows 2003 enterprise server box though... not sure what system you are running.

[amfony]

the system is Windows XP service pack 2 with all subsequent updates. and yes i have done that many a time already , thanks JiveMasterT

[MazX_Napalm]

So you saying that you build the system, add it to the domain and then sysprep?

I always leave the pc out of the domain, sysprep, image. I leave the join domain and computer name to the mini setup.

[UnaBonger]

I've built plenty of machines and joined them to a domain for tweaking before ghosting, BUT I always remove them from the domain and remove the comp account in AD prior to actually making the image. I havent seen any odd issues form doing so and usually use sysprep to have them prompt for a new name prior to joining the domain on first boot after applying the image...

The problem as it sounds to me is more of a DNS issue than a workstation issue... Maybe try removing the DNS entry for the particular machine that your pinging then renew the IP of that machine and have a new DNS record created. Then of course ping it from somethign else... OR, maybe remove the problem machine from the domain, remove the comp account in AD, rename it and rejoin the domain... Either of these will basically allow DHCP to update DNS with a new record for that machine, and hopefully resolve your problem.

[amfony]

ok that could be the problem, the fact that i DONT remove the computer from the domain b4 sysprep-ing. I was under the assumption that a reseal on sysprep was the equivalent of "making the system ready to be used by end users", and therefore assumed all naming and domain membership was revoke and nullified before sysprep was finshed its job. As well as re-sid-ing.

Now ill have to test this tomorrow, but just a thought. I too, have built plenty of computers, it seems in error with my mistake regarding the domain. But i have now in a prodcution environemnt 95% of my images running well. As in NOT WITH THIS PROBLEM. i dont feel that my procedure this time was any different from the other systems i have built then imaged.

I called micro$oft, with a capital SOFT, and i explained my issue, as soon as i mentioned "3rd party deployment application" they washed theirs hands of the problem and said "we cant guarentee anything with 3rd party products".

As for UnaBonger, the records i have delted and to no avail, the first post actually refers to new ip lease and that was no dice either.

[amfony]

Im back wit the results, I did create a new image with removing the domain, this didnt seem to fix it.

I have recoursed back to creating a brand new installation of XP from my custom install CD. Customised, removed from domain as suggested in this thread and imaged. This works.

Unfortunatley i cannot pin point the problem, but a work around will do until i get more time to investigate. Thanks for all your help guys with this issue.

Sincerley

Amfony