# setup script to generate new ssh keys at boot Sudo apt remove -purge gnome-initial-setup gnome-online-accounts update-manager-core -y # Remove some of the initial setup packages Sudo sed -i '16 s/.*Prompt.*/Prompt=never/' /etc/update-manager/release-upgrades Sudo sed -i 's/APT::Periodic::Update-Package-Lists "1"/APT::Periodic::Update-Package-Lists "0"/' /etc/apt//20auto-upgrades Sudo systemctl unmask sleep.target suspend.target hibernate.target hybrid-sleep.target # Prevent ctrl-alt-del from causing a reboot Sudo apt clean & sudo apt -y autoremove -purge # apply any system updates & remove any obsolete packages The first few changes I made were generic system wide changes. We can then ssh into the system for the majority of the next configuration items. With that complete we can find our IP address - either from the vCenter Server > VM > Summary tab, or by typing ip addr at that terminal session. We’ll do this by entering sudo apt install openssh-server -y. I entered a good password, selected require password to log in and didn’t enable Active Directory (we’ll do that later).Īfter the final reboot, we’ll login as our template-admin user, launch the terminal and install sshd, so that we can use it for the rest of the configuration. For my name I entered template-admin and for computer name I entered. During the install I skipped the file check (just to save time) and selected ‘Install Ubuntu’ and accepted defaults. I find this is the easiest way to install operating systems from ISO image. I then selected ‘launch remote console’ to open the VMware Remote Console. Advanced > Configuration Parameters > Add Configuration Params > Name: devices.hotplug, value false - this is based on a recommendation here:, I’m adding it to the Linux VM for similar reasons.New Network: 192.168.37.0 - this is the port group I use for VDI desktops.Guest OS Version: Ubuntu Linux (64-bit).You’ll want to specify something that is capable of running on the versions of ESXi available in your environment. Since I’m able to run this version, and knowing 6.5/6.7 reach end of support in just a few months, I decided to go with the latest available. I typically only visit compatibility levels when VMs are initially created. Compatible with: ESXi 7.0 U2 and later (vmx-19) - my test hosts for VDI are running the latest available 7.0 release. ![]() The VDI is pretty obvious, the g01 is for golden image #1 and then the last part is the OS name. ![]() ![]() VM Name: vdi_g01_ubuntu-2004 - this is my naming convention for VDI golden images.The first step was creating a virtual machine. This blog post will outline those steps to create a Ubuntu 20.04 Desktop for use as a Horizon 7.13 non persistent pool. I kept some notes on the steps I followed on my desktop, but after seeing a funny tweet this week ( ), I decided I should share this document. Any information about configuring this to use Active Directory would be most appreciated.I recently built a new Ubuntu Desktop 20.04 machine to be used as an instant clone golden image for a Horizon 7.13 environment. I am missing the winbind_krb5_localauth.so plugin for the winbind configuration and cannot find it as a part of the samba/krb5 packages provided by Ubuntu. So it boils down to either understanding how SSSD is trying to autodiscover the AD site (this way I can ask the central IT folks the correct question) or configuring this to use samba/winbind like I have on the CentOS/RHEL side. I do additionally see a failed startup of sssd-pam that mentions the sssd configuration contains the pam module, but it is trying to be socket activated? Pam_sss(login:account): Access denied for user 4 (System error) Using getent password I am able to retrieve information from a user in the active directory: authenticates successfully then fails with an system error 4 pam_sss(login:auth): authentication success logname= uid=0 euid=0 tty=/dev/pts/0 ruser= rhost= not autodiscover AD site value using DNS and ad_site option was not set in configuration. ![]() I can successfully join the realm realm join -v -user=myjoinuser I have attempted a few tries using SSSD directly which returns me domain information when I do the join, but I am not able to login using a domain account. I am looking to configure SSSD with samba and winbind, similar to. Most of the Ubuntu systems that I have had to build use default configurations or I have been able to figure out what the RHEL->Ubuntu equivalent of that configuration would be. I would like to first mention that I have more experience with the CentOS/RHEL world than I do with configuration of Ubuntu.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |