On Thursday 18 March 2010 12:15:02 lsq726 wrote: > The first is the sanbootconf does not support DHCP-012 option name > So BOOT'S CLIENT computer name is the same.
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. > On this point has been made based on the sanbootconf-0.9.2 modifications, > you can refer to Hope to get this feature added to the official > sanbootconf, make it better and easier. see attachment > Modify by hbxfwjww. > Blogļ¼http://hi.baidu.com/%C1%F7%D0%C7%CE%DE%D3%EF I'm sorry; I can't read the Chinese there. Could you provide a rough translation of what has been modified? I'll happily accept useful contributions to sanbootconf. > The second is to install SANBOOTCONF client can only be a DNS from DHCP, > the DHCP server on the other DNS be ignored Want the client to obtain DHCP > server all the DNS information I don't understand what you mean here. Michael _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
