Michael Brown wrote: > > This is correct. Changing the computer name in Windows is a non-trivial > operation, and will affect things like domain membership. Also, you > cannot > (without the use of various complicated tricks) share a single target disk > image between multiple machines, so there is generally no problem with > having > the computer name embedded within the disk image. >
Agreed. Hopefully the SAN target software has some sort of copy-on-write functionality. I believe that there are commercial drivers who change the computer name as per some parameter table (possibly iBFT, possibly proprietary). The AD membership and possibly even some commercial products' licensing systems might be broken by hacked-in changes made by a driver. If copy-on-write is available, simply renaming each computer and then domain-joining could be an option. > I don't understand what you mean here. > I think "lsq726" is saying that only one of the DNS servers from the DHCP response is making it into Windows' static IP configuration details, as set by sanbootconf. I could be mistaken. - Shao Miller _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
