similar to: Permission Issues with GPO

Let me guess. You accessing your server like : \\servername\netlogon of \\servername\sysvol Well thats protected by windows these these days. Try with \\servername.domain.tld\netlogon or \\servername.domain.tld\sysvol Does that work? Yes, There is a whole chaper of this on the list somewhere.. Best is to read howto override this. https://adsecurity.org/?p=1405 and for you

Here are my (little) view regarding shares accesses. I write that to clarify things. And it could really be of-topic as Louis seems to have gave solution. There are 2 levels of authorisation for accessing shares: the share level and FS level. For Sysvol I would keep everyone or replace it by "authenticated users" in paranoid mode as the latter refuse non-authenticated users. They are

On 17/11/15 16:57, Viktor Trojanovic wrote: > Hi Mathias, > > Thanks for replying. It seems you're describing the situation on the > AD DC. Computer and user mode access to my DC works fine and without > any issues but I can't access the shares of my *member* server *in > computer mode*. In user mode, it all works just fine. > > Viktor > > On 17.11.2015

Hi Mathias, The problem is not the GPO itself. The GPO containers are stored, as they should be, in the file system under sysvol/AD-DOMAIN/Policies, and they are being accessed correctly by the respective users and computers. Maybe my question isn't phrased perfectly but my problem is that any *computer GPO* that is accessing my file server (Samba Member), fails with an access denied

On 25.01.2016 14:13, Viktor Trojanovic wrote: > Hi Ole, > > Unless you want to add functionality that is new since 1511, I don't > think that's necessary. I have already added a Win10 machine to a domain, where only Win7 clients were joined before that. I have managed this domain from Win7 only, so far. Therefore I believe that e.g. the Windows Update policy is not fit for

Viktor, thanks again! Now that I did this (added the Win10 1511 ADMX files to the central store), I probably will have to recreate the policies that will be applied to Win10 machines, right? Ole On 21.01.2016 17:16, Viktor Trojanovic wrote: > Hi Ole, > > I've been using Samba with Win10 clients for a while now, so I'm happy > to share some of my findings. > > See

Hey, If your GPO are stored in AD (they are not template GPO with all GPO information in some file, I think this kind of non-pure-AD GPO are stored in ADMX files, not sure). In GPMC.msc you have to define which entities would receive the GPO. Once created the GPO, once it is set up, you have in the right panel two parts. The bottom part is to define to whom this GPO would be applied. In that

Hai Viktor, > > Before posting my share permissions, can you please elaborate what you > mean with "have you removed authenticated users from your share"? I > never had any rights for "authenticated users" on any of my shares. Ah sorry, yes, that was "everybody" ( my error ) keep it > > Maybe I'm setting up shares in the wrong way? >

Hi Mathias, Thanks for replying. It seems you're describing the situation on the AD DC. Computer and user mode access to my DC works fine and without any issues but I can't access the shares of my *member* server *in computer mode*. In user mode, it all works just fine. Viktor On 17.11.2015 17:19, mathias dufresne wrote: > Here are my (little) view regarding shares accesses. I

On 17.11.2015 18:05, Rowland Penny wrote: > On 17/11/15 16:57, Viktor Trojanovic wrote: >> Hi Mathias, >> >> Thanks for replying. It seems you're describing the situation on the >> AD DC. Computer and user mode access to my DC works fine and without >> any issues but I can't access the shares of my *member* server *in >> computer mode*. In user

Hi list, Today, I spent most of the day figuring out why my password policies set via GPO are not applied on a domain level, just to find out that this is not one of the many occasions where Windows is the problem but it's really Samba, for a change. Apparently, password policies can only be changed using samba-tool and not via GPO. IMO, the FAQ is not very clear here.

Hi list, This might or might not be a Samba related post. Feel free to ignore it in case it is too far off-topic My current understanding is that ... a) I need those new templates in order to fully integrate Win10 clients in an AD domain (i.e. with compatible policies). b) I can only modify policies based on Win10 admx files from Win10 machines (i.e. with the RSAT tools for Win10). Are there

On 16.11.2015 14:44, Rowland Penny wrote: > On 16/11/15 13:25, Ole Traupe wrote: >> >> >> Am 16.11.2015 um 14:06 schrieb Viktor Trojanovic: >>> >>> >>> On 16.11.2015 13:48, Viktor Trojanovic wrote: >>>> See replies below >>>> >>>> On 16.11.2015 12:39, Rowland Penny wrote: >>>>> On 16/11/15 11:19,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hallo, when I do an "samba-tool gpo list username" I get an "faild access check on OU=name,......". But not if I do a "samba-tool gpo listall" then everything is ok. Is this normal? If I take "administrator" as username I didn't get this message. Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2

Othere thing. IF you domain name is like domain.tld By default, Windows does not send updates to top-level domains. If thats the case you should change it to a single-lable dns. https://support.microsoft.com/en-us/kb/300684 Greetz, Louis > -----Oorspronkelijk bericht----- > Van: Viktor Trojanovic [mailto:viktor at troja.ch] > Verzonden: maandag 16 november 2015 15:45 > Aan:

Hai, I suggest you dont remove the "Register DNS" checkbox from the network" option. If you setup if correct, when you join a computer to the domain, It wil automatily registere the computer en the AD DNS. And todo so you need the "Register DNS" checkbox from the network" For example, i use for now an dhcp server ! the DHCP server i use it NOT in any of the MS

Ok, > I am getting the DNS register warning message on > *all* win clients, not just that one. Good info, so, this confirms its not a bug but an incorrect setting. Type ipconfig /all on a pc. Post the output, i suspect, incorrect dnsdomain or dns search domain. Also. Check if the PTR records are set to the correct server ips. This does not change on its own. Ldbsearch from below

See comments inline. On Sun, 10 Feb 2019 at 16:33, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 10 Feb 2019 14:13:27 +0100 > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > > I'm currently reviewing my own backup strategy for Samba and I > > realize it is not in line with best practices provided in the Wiki. ( >

On 1/6/23 8:11 AM, Dawson Greeley via samba wrote: > Hi, Im attempting to apply a few group policy settings but they dont seem to be applying on the machine in question, or some settings I cannot see in the GPME. > > > 1. Settings applied to openssh dont seem to create the required config files in /etc/ssh/sshd_config.d/ for ssh to actually pick up on these changes. Is there a

See replies below On 16.11.2015 12:39, Rowland Penny wrote: > On 16/11/15 11:19, Viktor Trojanovic wrote: >> So I ran a samba-tool ntacl sysvolcheck, and the following error >> message came up: >> >> --------------------snip-------------------- >> ERROR(<class 'samba.provision.ProvisioningError'>): uncaught >> exception - ProvisioningError: