Skip to content

ubuntu/adsys

Folders and files

NameName
Last commit message
Last commit date
Mar 20, 2025
Feb 26, 2025
Sep 13, 2024
Mar 27, 2025
Apr 24, 2025
Jan 28, 2025
Jun 27, 2022
Mar 26, 2025
Aug 30, 2024
Aug 2, 2023
Nov 26, 2024
May 31, 2023
Mar 18, 2025
May 25, 2023
Mar 8, 2024
Feb 14, 2025
Aug 19, 2024
Oct 2, 2020
Feb 24, 2021
May 10, 2024
Dec 9, 2024
Feb 14, 2025
Oct 26, 2023
Feb 14, 2025
Sep 14, 2022
Apr 28, 2025
Apr 28, 2025
Jul 26, 2023

Repository files navigation

adsys

Active Directory GPO support.

Code quality Code coverage Go Reference Go Report Card License

Documentation and Usage

The documentation and the command line reference is available on Read The Docs as well as the documentation for the current development release.

Installing development versions

For every commit on the main branch of the adsys repository, the GitHub Actions CI builds a development version of the adwatchd project. This is NOT a stable version of the application and should not be used for production purposes. However, it may prove useful to preview features or bugfixes not yet available as part of a stable release.

To get access to the build artifact you need to be logged in on GitHub. Then, click on any passing run of the QA workflow that has the Windows tests for adwatchd job, and look for the adwatchd_setup file.

Troubleshooting

If AD authentication works but adsys fails to fetch GPOs (e.g. you see can't get policies errors on login), please perform the following steps:

  1. Add the following to /etc/samba/smb.conf:
log level = 10
  1. Run sudo login {user}@{domain} in a terminal, replacing with your AD credentials

  2. Paste the output in the bug report

The adsysctl command can also be useful to fetch logs for the daemon and client:

# You can increase the amount of information that will be displayed by using a more verbose tag (-vv or -vvv).
# Note that this command will start a watcher that will print logs as they are generated, so you will need to perform
# actions (such as trying to login) while the command is running.
adsysctl service cat -v

Additionally, you can check the system journal to look at more logs about adsys: Remember that adsys runs with privileges, so you will need to run the following commands as root.

# You can use the -b flag to control how many boots the log will show (e.g. -b 0 will show the current boot only)
journalctl -b0 | grep adsys

# You can also get the logs of the individual units:
systemctl list-units | grep adsys # this will show all adsys related systemd units

# The -u flag will show the logs of the specified unit
journalctl -b0 -u adsysd.service # this command will only show the adsysd.service logs of the current boot