Trying to install Active Directory on a fresh install of Tumbleweed.
I’ve tried a couple times and the install goes immediately to 16% and stalls. I’ve waited 30 minutes. This is not a virtual machine. It’s a Dell Inspiron, E7250.
Active Directory is a Windows technology - I wasn’t aware that Microsoft had developed a version that ran on Linux.
Can you describe (a) where you obtained this, and (b) what process you’re following?
I’m guessing that what you’re probably doing is either installing SAMBA, or you’re trying to join your TW system to an Active Directory domain (which isn’t the same as installing AD on Linux - which I can’t find any reference for short of using SAMBA to emulate it).
@Pauly-Walnuts so it’s yast2-samba-provision
This package contains the YaST2 component to configure samba as an Active
Directory Domain Controller.
OK, yeah, I’d heard that SAMBA had that capability, so that’s what it is. It’s not Microsoft code, but SAMBA code.
From what I understand, the emulation is pretty good, but to understand the issue you’re having, we need to know if you’re trying to set it up as a standalone system or trying to join an existing AD forest. While it’s my understanding that doing that is supposed to work (and that a real AD installation “can’t tell the difference”), Microsoft has been known to make changes that break this kind of compatibility.
I’m trying to create a new forest. I just tried it on a virtualbox and I get the same issue. It gets to 16% and stalls. Again, I gave her a half hour…
The author is unknown.
Is LDAP similar?
LDAP is similar in some ways, and different in others. LDAP is a directory store (typically users and groups, but not necessarily exclusively so), whereas Active Directory has dependencies on DNS for service resource records and also is commonly used for systems management (LDAP can do this, but it’s not used that way in many instances).
A new forest shouldn’t be an issue, though - but if you’re looking for “simple” and don’t have multiple Windows machines that you’re also managing, then it might be overkill for what you’re trying to do.
That gets to the eventual question as to what your goal is in using SAMBA in this way? Are you looking to manage just user identity in a central location, or are you looking to manage (for example) file shares and work with Linux and Windows systems in a unified environment?
I’ve been able to duplicate what I think is the error you’re seeing - but would need to confirm a few details:
- What is the value that you’re using for the root domain name in the YaST module?
- What is the FQDN of the host you’re installing on?
- What is the domain functional level (probably doesn’t matter - but just in case. I’m testing with the value of 2008R2)
You can obfuscate the domain name and FQDN as long as you use the same obfuscation for both.
I also found that when running it (I started YaST from a terminal window), there’s a prompt in the terminal window to set and confirm the administrator password for some reason - and that’s probably why it’s hanging up at 16%).
AD’s dependence on DNS is one of the things that can make the setup a bit more complicated. There are benefits to it, but it does make things a lot more involved if you’ve never set it up before. DNS zones and names in AD have to match (in my case, it’s hanging up because my test system has a name of localhost.localdomain - and what AD is looking for for the realm is “localdomain.something” (ie, a proper DNS zone). It complains if the DNS zone is too short (as it is here - if it were “localdomain.local” it’d probably work) because the short name (“localdomain”) can’t match the realm name, but the two have to be related.
After I input a password in the terminal window that I started from, I actually get error messages in YaST telling me this. I suspect you’d see the same thing.
I forgot I had to install DNS. I retired some 15 years ago from the Windowz world. Getting old. And bored. Last version I touched, was 2008 R2 and only briefly. I was an MCSE on (If I recall) 2003?
Right now, I’m trying to configure DNS.
I did: sudo zypper in -t pattern dhcp_dns_server
Then I ran: sudo yast dns-server, and I’m told there is no such client module dns-server.
I really don’t want to do that manually.
If I’m understanding your 1st question correctly, it’s PaulyWalnuts.
The FQDN is PaulyWalnuts.rocks
Are you a fan of the Sopranos?
This is not intended to be available anywhere other than my home.
Yes, 2008r2.
When I run yast from the command prompt, I’m told that the network is currently handled by NetworkManager, or is completely disabled.
You know, like Whisky Tango Foxtrot, right?
You’ll need to probably also install the YaST package for managing DNS - yast2-dns-manager.
Root domain in AD is the DNS zone name (essentially). So if you have hostname Pauly.Walnuts.rocks, the root domain would be Walnuts.rocks, and then the NETBIOS domain name would be WALNUTS (going from memory at the moment).
Indeed I am. 
And Pauly always made me laugh.
Can you show the output (and command) that gives this? Please place it in preformatted tags (</> in the formatting toolbar in the forum editor - that’ll make it easier to read.
pauly@localhost:~> sudo yast dns-server
[sudo] password for root:
No such client module dns-server
pauly@localhost:~>
The module dns-server is missing as well.
I installed DNS using yast2 software manager, selecting patterns and scrolled down to DHCP and DNS Server.
Looks like those modules are no longer included in the newer releases of SUSE.
I meant for the message that the network is currently handled by NetworkManager or is completely disabled.
To start the dns-server module, you first need to install the yast2-dns-manager package. It appears that’s missing from your system. Installing it should pull in anything else - it’s a specific thing to the samba use of DNS (presumably for the Active Directory emulation).
I guess it’s back to the command prompt.
What version of SUSE are you running? I would think I could install an older version that still has the modules, then update it, but I can’t find any of the older releases.
DNS server and manager are python scripts.
Tried this, and got that:
pauly@localhost:~> sudo pip install dnspython
[sudo] password for root:
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try
zypper install python311-xyz, where xyz is the package
you are trying to install.
If you wish to install a non-rpm packaged Python package,
create a virtual environment using python3.11 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip.
If you wish to install a non-rpm packaged Python application,
it may be easiest to use `pipx install xyz`, which will manage a
virtual environment for you. Install pipx via `zypper install python311-pipx` .
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
[notice] A new release of pip is available: 23.3.2 → 24.0
[notice] To update, run: pip install --upgrade pip
Tried this, got that:
pauly@localhost:~> pip install --upgrade pip
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try
zypper install python311-xyz, where xyz is the package
you are trying to install.
If you wish to install a non-rpm packaged Python package,
create a virtual environment using python3.11 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip.
If you wish to install a non-rpm packaged Python application,
it may be easiest to use `pipx install xyz`, which will manage a
virtual environment for you. Install pipx via `zypper install python311-pipx` .
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
[notice] A new release of pip is available: 23.3.2 → 24.0
[notice] To update, run: pip install --upgrade pip
Tried this, got that:
pauly@localhost:~> sudo pip install git+https://github.com/rthalley/dnspython.git
[sudo] password for root:
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try
zypper install python311-xyz, where xyz is the package
you are trying to install.
If you wish to install a non-rpm packaged Python package,
create a virtual environment using python3.11 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip.
If you wish to install a non-rpm packaged Python application,
it may be easiest to use `pipx install xyz`, which will manage a
virtual environment for you. Install pipx via `zypper install python311-pipx` .
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
[notice] A new release of pip is available: 23.3.2 → 24.0
[notice] To update, run: pip install --upgrade pip
Gave up after trying this, that, those and the others and them:
pauly@localhost:~> sudo pipx install dnspython
No apps associated with package dnspython or its dependencies. If you are attempting to install a library,
pipx should not be used. Consider using pip or a similar tool instead.
pauly@localhost:~>
I run Tumbleweed, both on my main system and on the virtual system I’m using to test this out. Both are updated to relatively recent releases (within the past 2 weeks at most).
[quote]
DNS server and manager are python scripts.
Tried this, and got that:
pauly@localhost:~> sudo pip install dnspython
[sudo] password for root:
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try
zypper install python311-xyz, where xyz is the package
you are trying to install.
If you wish to install a non-rpm packaged Python package,
create a virtual environment using python3.11 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip.
If you wish to install a non-rpm packaged Python application,
it may be easiest to use `pipx install xyz`, which will manage a
virtual environment for you. Install pipx via `zypper install python311-pipx` .
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
[notice] A new release of pip is available: 23.3.2 → 24.0
[notice] To update, run: pip install --upgrade pip
I would probably not use pip to install this - what it shows here is a change in how python works (pretty much every distro does this AFAIK). I show yast2-dns-manager in the OSS repo.
Note that it’s yast2-dns-manager, not yast-dns-manager. That might be part of the issue here.
^@pauly@localhost:/etc> yast2-dns-manager
yast2-dns-manager: command not found
Can you send me a link to that in the repo? I’m not seeing it.
Unless I’m looking in the wrong area.
Are we having fun, yet?
Sure do appreciate your patients.
I just installed it from the repo:
$ zypper in yast2-dns-manager
Then launch yast2 with:
$ gnomesu -c '/sbin/yast2 dns-manager'
(or kdesu if you’re using KDE - or just launch YaST as root and you should see it in the list).
Glad to help out
