Thin Clients with Same Computer Name - This ok?

[jmair]

I'm setting up 70 thin clients and will be keeping them in a workgroup with all the same computer names, however they will be given unique static IPs. Can anyone see issues with all these machines being on the network (but not on the domain) with the same computer name?

 

The function of these thin clients is to only act as a remote desktop connection client.

[plexer]

Ermm doesn't sound like a good idea to me tbh.

 

Ben

[PeterH]

I'm setting up 70 thin clients and will be keeping them in a workgroup with all the same computer names, however they will be given unique static IPs. Can anyone see issues with all these machines being on the network (but not on the domain) with the same computer name?

 

Can't see any major problems with that. As long as you don't need to be able to connect to the machines across the network. The only thing is, you'll need to disable the Computer Browser service otherwise you'll keep getting error messages about duplicate names on the network. I'd go into network connections and disable file and printer sharing for microsoft networks while you're at it.

[jmair]

I'm setting up 70 thin clients and will be keeping them in a workgroup with all the same computer names, however they will be given unique static IPs. Can anyone see issues with all these machines being on the network (but not on the domain) with the same computer name?

 

Can't see any major problems with that. As long as you don't need to be able to connect to the machines across the network. The only thing is, you'll need to disable the Computer Browser service otherwise you'll keep getting error messages about duplicate names on the network. I'd go into network connections and disable file and printer sharing for microsoft networks while you're at it.

 

Good idea on the Service and File/Print Sharing. Thank you kindly!

 

I'm in this debacle due to time constraints and an issue with the image shot at each of the machine. I can manually update/ give names to them at a later time.

[PotNoodleTech]

What make model of thin clients?

[jamesfed]

It would quickly muck up any DNS requests to the thin clients - to be honest though its so very easy to keep the names the same as their MAC address (or other unique ID) why bother the potential for hassle to occur?

[Axel]

What make model of thin clients?

 

If you have Axel terminals they will by default generate their own unique network name (based on their MAC address)

[CyberNerd]

We have a few hundred (linux)thin clients. The same name doesn't matter to us - but we do use the client name to attribute printers to locations; so IT1-xxxx gets the IT1 printer IT2-xxxx gets IT2 printer and so forth.