Linux has come a long way toward being more user friendly in the last few years, and Fedora 20 is no exception. One area in which it shines is its incredibly smooth integration with Active Directory through realmd. What makes realmd (and sssd) so powerful is that because PAM uses them as part of its authentication chain, any existing application that uses PAM for authentication has automatic access to Active Directory after the machine is joined to the domain.
However, because this is a relatively new addition, there is not a lot of accurate information on the web about how to perform many everyday tasks. There are also a lot of out of date guides or guides that assume you are using local accounts or manually performing ldap lookups.
This guide is designed to make setting up a network of Fedora 20 servers integrated with Active Directory simple and hassle free. It makes the following assumptions:
- You have already installed 2 Active Directory domain controllers, named dc1 and dc2
- You have chosen the domain name corp.mydomain.com and the NT name CORP
- You have created yourself a regular account username, and a domain administrator account username.da
- We will be installing 1 server per major service or application
Table Of Contents
There are a lot of articles on the web that will tell you how to specify a kickstart file when installing Fedora 20 in BIOS mode, but when I had to recently install a number of systems in UEFI mode, I had trouble finding any resources. When you have to install more than a couple systems, making a custom image for each one with a ks.cfg file at the root is highly impractical so being able to specify a kickstart file is important.
Installing in BIOS mode is easy. Just press <escape> at the installation menu and you are greeted with a
prompt that allows you to send custom parameters to the installer. However if you choose to boot your installation in UEFI mode, you are greeted with the Grub 2 screen and pressing escape doesn’t work. Instead, highlight the Install Fedora 20 option (but don’t press <enter>) and press e to edit the menu option. This will bring you into a fullscreen editor with the following text.
linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora 20 x86_64 quiet
If you want to specify a custom kickstart file that has a repo configured in it, you can replace the inst.stage2 parameter with a ks parameter.
linuxefi /images/pxeboot/vmlinuz inst.ks=nfs:10.0.0.1:/kickstart/machinename-ks.cfg quiet
Press F10 to continue booting with the updated grub menu and the installation will proceed exactly as if you had used the old method of typing linux ks=nfs:10.0.0.1:/kickstart/machinename-ks.cfg.