DHCP issue

[Addiss77]

We do image lots of the same brand and model(xp) computers at the same time and connect to the internet and activate them with out changing the computer name or running SID... We're having a problem getting the ip address or connecting to the internet, I think because all computers having the same name since the they have the same image... please advise how I can accomplish this (image all -> connect to the internet (with out changing computer name or run SID) and activate xp for all of the computers.....

Thanks

 

[Noway2]

While I am not an expert in Windows networking, something doesn't sound right in your post. From what I recall from studying SAMBA, in a windows domain, when a host comes on line, it sends a broadcast in an attempt to grab its network host name. If that name is challenged, or returned as claimed by the name server, it has to choose another name. I would assume that some mechanism to randomize the names would be in place.

Perhaps the following link might be of some help:

http://technet.microsoft.com/en-us/library/bb727005.aspx

 

[cajuntank]

Couple of things. To do imaging properly, you need to sysprep your machine before creating your base image. This ensures that when the machine comes up, it will follow certain aspects of machine naming and SID generation following Microsoft best practices. Do a google search on Sysprep and a little reading will give you everything you'll need to know. Past activation, having individual computers with the same SID is not that big of a deal. Having computers joined to a domain with the same SSID is bad. I took over the management of a school district and found out this is what they were doing. It wasn't that big of a deal when they were on Novell, but it was when we migrated over to Microsoft. If you have all Dells or all HPs, etc..., using OEM media to create your base image is also not that big of a deal. You might have problems if you use DELL OEM media on a HP machine or simular. I always use volume license media myself; but of course, you would need a volume license key.

 

[IRudebwoy]

Well, DHCP uses the Hardware (MAC) address to obtain an IP address from the DHCP server. This, in itself, should not prevent your PCs from getting to the internet.

But as Norway2 hinted, duplicate names on a Windows/Samba network is a problem. And like cajuntank expressed, sysprep is essential for imaging Windows desktops to ensure the hardware is recognized properly on the target PC. Not running sysprep on the source PC may be at the root of your issues.

 

[itsp1965]

The question is what type of OS are you using for imaging your machines and what type of DHCP server are you using. From what I recall Windows OSses after XP has a particular issue obtaining IP addresses from a non-Windows based DHCP server. Had this issue with Vista obtaining IPs from a RedHat DHCP server and had to apply a registry tweak to make it work

 

[Addiss77]

Thanks for the reply...
we imaging 100s of systems using power quest per day... the images os are xp... we don't join these system to the domain... since we need to activate the operating system we're using ipcop as a firewall and DHCP... the imaged system SID are the same...my problem is after 5 or 6 system ipcop will stop giving ip address and we have to wait 5 to 10 min to activate or connect another system to internet...

 

[IRudebwoy]

Look at the logs of your DHCP server to see if its exhausting it's pool of addresses.

 

[itsp1965]

I agree with IRudebwoy. You previously failed to mention that this would work for 5-6 machines and then stop for a period of time. Check your DHCP address pool in order to make sure you aren't running out of addresses