Thanks for this tutorial, but there is no buildin replication of sysvol between multiple instances (normaly you should use minimal 2 different samba ad servers for redundance > first with "create", second with "join" during the installation process) and no reverse-lookupzone in dns. Missing replication function of sysvol is not a turnkey problem, it´s missing in samba (see samba wiki). There are alternatives with rsync, but that´s not really the same because it is not bidirectional. But I like the samba ad server nevertheless and I use separate domain accounts for every debian server I want connect with ssh to - no more local accounts on my debian servers, instead, a central user administration (automatable with ansible and samba-tool or pdbedit).
hmm domain had a "-" in it, that caused a problem. removed it, still can't connect to the domain :/ guess ill have to redo it tomorrow. but this is already huge, will be very nice for our small funeral home with a maximum of 5 to 6 users and virtual machines *edit* When i disabled TCP IPv6 protocol it worked instantly. not sure if this is a good way of fixing it ;c thanks a lot for sharing!
If you're NOT running on-perm Microsoft Exchange this will work without issues. Linux based AD server lacks the necessary attributes for Exchange unfortunately.
Hey not sure if you're checking comments, but I follow this and it didn't work. I have a brand new proxmox server, no existing domain, pretty much a clean environment. I can't connect to the domain using RSAT, and I can't join to it from my windows VM. I'm not using an external domain, it's just one I made up COMPANY.local - when I enter the domain name it hangs for a bit, then fails. Any tips? Edit: I had ipv6 enabled. I disabled it and it worked.
edit: template not showing? shell -> pveam update thats already a super helpful video, but for some reason the turnkey container is not shown for me under templates. do i have to enable or add more templates somewhere? running proxmox 7.1-10
thank you for this! Works great with PMX v7.1 . Very fast and low impact. And Proxmox Backup Server has no issues backing it up! Great video!!
Thanks for this! I'm using v17 now, so I disabled resolvconf (systemctl disable resolvconf) and rebooted and the thing just worked, finally!
I'm very glad you posted this video. Didn't know I was looking for this, but sure glad I found it.
Thanks for the demo and info, have a great day
Hey nice, since GPOS are just interpretted as xml files by the gpclient they work also, wonderfull.
Excellent vid. very informative - Thank You
Great video!!!
I used this to deploy my Windows AD DC on my 3-node Proxmox HA cluster.
Thank for sharing proxmox turnkey templates i hope you make more videos like these!
Very good video and very needed. I'm glad you did a good job covering this container. Keep them coming :)
I tried setting up samba adds manually for months. I had no idea you could do it with a container, because of course you can lol.
Thanks for this tutorial, but there is no buildin replication of sysvol between multiple instances (normaly you should use minimal 2 different samba ad servers for redundance > first with "create", second with "join" during the installation process) and no reverse-lookupzone in dns. Missing replication function of sysvol is not a turnkey problem, it´s missing in samba (see samba wiki). There are alternatives with rsync, but that´s not really the same because it is not bidirectional. But I like the samba ad server nevertheless and I use separate domain accounts for every debian server I want connect with ssh to - no more local accounts on my debian servers, instead, a central user administration (automatable with ansible and samba-tool or pdbedit).
Why you should not make a reverse lookupzone, will that mess with samba ?
Very nice video, TNX.
Do you have tested to join an existing domain? I ask if its possible to get another dc without the fee for another 2022 server license..
Wonderful!
Flawless!
Thank you very good video
hmm domain had a "-" in it, that caused a problem. removed it, still can't connect to the domain :/
guess ill have to redo it tomorrow. but this is already huge, will be very nice for our small funeral home with a maximum of 5 to 6 users and virtual machines
*edit*
When i disabled TCP IPv6 protocol it worked instantly. not sure if this is a good way of fixing it ;c
thanks a lot for sharing!
If you're NOT running on-perm Microsoft Exchange this will work without issues. Linux based AD server lacks the necessary attributes for Exchange unfortunately.
Hey not sure if you're checking comments, but I follow this and it didn't work. I have a brand new proxmox server, no existing domain, pretty much a clean environment. I can't connect to the domain using RSAT, and I can't join to it from my windows VM. I'm not using an external domain, it's just one I made up COMPANY.local - when I enter the domain name it hangs for a bit, then fails. Any tips? Edit: I had ipv6 enabled. I disabled it and it worked.
edit: template not showing?
shell -> pveam update
thats already a super helpful video, but for some reason the turnkey container is not shown for me under templates. do i have to enable or add more templates somewhere? running proxmox 7.1-10
did you find this out?
You lost me at Windows!