CentOS diskless clients authenticate to windows AD
I am working on using diskless clients with CentOS. I have the diskless clients working fine. My next step is to have the clients boot up and authenticate with their host name which is aready in AD.
I have sucessfully built non-diskless client machines using CentOS and joined them to my domain. I used one of these machines to build the diskless image.
My thoughts are that I need to put the correct files/directories into a files.custom file in the snapshot folder.
I'm looking for any thoughts/help on this project.
Randy
I have sucessfully built non-diskless client machines using CentOS and joined them to my domain. I used one of these machines to build the diskless image.
My thoughts are that I need to put the correct files/directories into a files.custom file in the snapshot folder.
I'm looking for any thoughts/help on this project.
Randy
ASKER
Arnold,
Thanks for your reply. I have gotten past the last stumbling block. I just needed to get the right combination of files into the files.custom folder.
To answer your question, yes, each will have it's own mount point. I do understand that there will be some individual customization of files for each client that I want to add.
My next task is to configure the netboot so that hosts are not IP specific.
Thanks for your reply. I have gotten past the last stumbling block. I just needed to get the right combination of files into the files.custom folder.
To answer your question, yes, each will have it's own mount point. I do understand that there will be some individual customization of files for each client that I want to add.
My next task is to configure the netboot so that hosts are not IP specific.
netboot uses the MAC address and not the IP.
The issue is with assigning/setting the hostname. The network can be set by DHCP as long as the hostname is loaded which might be the stumbling block you are addressing.
The issue is with assigning/setting the hostname. The network can be set by DHCP as long as the hostname is loaded which might be the stumbling block you are addressing.
ASKER
Your sort of correct....
When you create the host using netboot, you have to enter in an IP or IP subnet. A file is created in the /tftpboot/linux-install/px
I can rename the file to the MAC address, so as to eliminate the IP requirement. Then the entry dissappears in the netboot software....not really a big deal.
I will now create a snapshot folder for each host and set the name inside of there.
Your right, I could do it by DHCP, however our DHCP is being done by the Cisco router, and I don't want to put any requirements on it to handle that.
Make any sense? Lol!
When you create the host using netboot, you have to enter in an IP or IP subnet. A file is created in the /tftpboot/linux-install/px
I can rename the file to the MAC address, so as to eliminate the IP requirement. Then the entry dissappears in the netboot software....not really a big deal.
I will now create a snapshot folder for each host and set the name inside of there.
Your right, I could do it by DHCP, however our DHCP is being done by the Cisco router, and I don't want to put any requirements on it to handle that.
Make any sense? Lol!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm not able to do it through netboot as the IP has already been assigned by DHCP by the time the pxe process starts.
Basically my requirement was to have the diskless clients boot up and maintain a separate host name that is already in active directory, without the use of a static IP. This would then allow the user to log in using their AD username and password.
The stumbling block after that was to figure out a way to do this without using a pre assigned IP by netboot. I have accomplished this by renaming the file to the MAC address, thus always retaining the same snapshot and in conjunction, the same hostname. Obviously, the downfall is that if a system is replaced, the file must be updated with the correct MAC address.
Your last suggestion using the rarp map MAC to IP I do believe would work.
I am going to close this out and award points as you have been helpful and given me some new areas to explore with this project.
Thanks for your help Arnold.
Basically my requirement was to have the diskless clients boot up and maintain a separate host name that is already in active directory, without the use of a static IP. This would then allow the user to log in using their AD username and password.
The stumbling block after that was to figure out a way to do this without using a pre assigned IP by netboot. I have accomplished this by renaming the file to the MAC address, thus always retaining the same snapshot and in conjunction, the same hostname. Obviously, the downfall is that if a system is replaced, the file must be updated with the correct MAC address.
Your last suggestion using the rarp map MAC to IP I do believe would work.
I am going to close this out and award points as you have been helpful and given me some new areas to explore with this project.
Thanks for your help Arnold.
ASKER
Thanks again.
Does each diskless client have an NFS mount point where it can store its configuration? i.e. /etc?
Presumably you do not want to configure each diskless client.