Here is where I had forgotten my first config file. I am uncertain if I had documented this though, but I added this for good measure: sudo setsebool -P samba_export_all_rw 1 Instead of duplicating that content, just read the linked post. sudo ln -s /var/server1/shares/bgstack15 /home/bgstack15Īnd now I could log in as my domain user! So now it was time for setting up Samba with FreeIPA auth. I knew I would need –force-join because I was using the same hostname as before, and as is typical, I failed to remove the old host.īefore logging in, I set up my user’s home directory to use the data drive with a symlink. Time sudo ipa-client-install -force-join -mkhomedir - principal=domainjoin -password=SEEKEEPASS sudo dnf -setopt=install_weak_deps=False install ipa-server-trust-ad ipa-client I mounted up my data drive’s logical volumes to /var/server1.Īnd now came time for FreeIPA! With CentOS 8, FreeIPA is now in a “module” repository and since I need ipa-server-trust-ad, I have to use the full module (DL1). Sudo dnf -setopt=install_weak_deps=False install screen p7zip Sudo dnf -setopt=install_weak_deps=False install bc bind-utils cifs-utils cryptsetup dosfstools epel-release expect firewalld git iotop mailx man mlocate net-tools nfs-utils parted python3-policycoreutils rpm-build rsync strace sysstat tcpdump telnet vim wget sudo dnf -setopt= install_weak_deps=False install bgscripts-core bash-completion expect I copy-pasted in the value from my workstation’s /etc/ipa/ca.crt to /etc/pki/ca-trust/source/anchors/. I had to load up my root ca cert, before I joined it to IPA, so dnf could get through my transparent proxy.
Then, I followed a bunch of steps, loosely in order, to replicate my previous setup. So, after collecting my thoughts and config files and practicing on a vm, and selecting a downtime window, I shut down my file server, removed its OS drive, stuck in the new one, and installed CentOS 8 minimal. Those are my notes before doing any work on the production system.
I wrote down the items I wanted to make sure get set up on the new install. And now it is running instance 4 on that exact same platform, a Dell Precision Workstation 490.īefore I was ready to schedule the downtime window, I practiced all the possible configs on a CentOS 8 vm. Thankfully, when I was migrating my entire infrastructure to Linux 3+ years ago, I architected my file server with an OS drive and a data drive.Īnd from my vast stores of old hard disks, I pulled out a drive whose record indicates that it previously was the “C:\” drive for that exact same hardware, from 2015-2017. With the recent slowdown in packages for CentOS 7, I have been preparing to update at least my main file server to CentOS 8.
0 kommentar(er)
