The vagrant-samba4-dc from silug

vagrant-samba4-dc's Introduction

This demonstrates a simple Samba 4 Active Directory proof-of-concept with two domain controllers and a single client.

The two domain controllers run Fedora 34, and the client runs CentOS Stream 8. The two domain controllers are using the stock Fedora packages.

To test, simply do the following on a system with Git, Bolt, Vagrant, and a Vagrant provider (VirtualBox or libvirt) installed:

git clone https://github.com/silug/vagrant-samba4-dc.git
cd vagrant-samba4-dc
vagrant up

vagrant-samba4-dc's People

Contributors

Stargazers

Watchers

vagrant-samba4-dc's Issues

On client, AD users and groups include domain information

AD users are in the form user@domain instead of just user.

Duplicate memory settings

During rebase/merge, duplicate settings for memory size were added to Vagrantfile.

Network systemd service missing

The network.service Unit file does not appear to ship by default in the Fedora 29 image used by vagrant.

Stack trace:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

# Update sysconfig
sed -i 's/\(HOSTNAME=\).*/\1dc1.samba4.local/' /etc/sysconfig/network

# Update DNS
sed -i 's/\(DHCP_HOSTNAME=\).*/\1"dc1"/' /etc/sysconfig/network-scripts/ifcfg-*

# Set the hostname - use hostnamectl if available
echo 'dc1.samba4.local' > /etc/hostname
if command -v hostnamectl; then
  hostnamectl set-hostname --static 'dc1.samba4.local'
  hostnamectl set-hostname --transient 'dc1.samba4.local'
else
  hostname -F /etc/hostname
fi

# Prepend ourselves to /etc/hosts
grep -w 'dc1.samba4.local' /etc/hosts || {
  sed -i'' '1i 127.0.0.1\tdc1.samba4.local\tdc1' /etc/hosts
}

# Restart network
service network restart


Stdout from the command:

/usr/bin/hostnamectl

Stderr from the command:

Redirecting to /bin/systemctl restart network.service
Failed to restart network.service: Unit network.service not found.