similar to: Samba 4.9, Group Policy, Drive Map

<?xml version="1.0" encoding="utf-8"?> <Drives clsid="{8FDDCC1A-0C3C-43cd-A6B4-71A6DF20DA8C}"><Drive clsid="{935D1B74-9CB8-4e3c-9914-7DD559B7A417}" name="W:" status="W:" image="2" changed="2019-01-21 18:36:07" uid="{6524E6E3-E107-48CC-9973-406E16B5F34D}" userContext="1"

user configuration -> Preferences -> Windows Settings -> Drive Maps Item Level Targeting -> Security Group, Domain Users On 1/21/2019 11:09 AM, Luke Barone via samba wrote: > Where is the policy targeting - the user or the computer? > > > On Mon, Jan 21, 2019 at 7:51 AM Marco Shmerykowsky PE via samba < > samba at lists.samba.org> wrote: > >> I seem

Hai, If you dont mind to share the OS and Samba version you are using? Because we dont see this much: > Thanks. Just ran "samba-tool ntacl sysvolrest" and that seems > to have fixed the issue. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Shmerykowsky PE via samba > Verzonden: maandag

I seem to be having trouble getting group policies to map a drive. When I drilled down thru the logs I get an "Access Denied" message. I can navigate to the share via the computer browser and map a drive the "old fashion way" with any issues. Files can be read and written. The group policy doesn't seem to take. Suggestions? Thank you.

OK, the preference is set correctly. Have you run a "samba-tool ntacl sysvolcheck" on your first domain controller? That will check the permissions. If you have additional domain controllers, ensure you're connecting to the one holding the PDC Emulator role (typically your first DC) in your GPMC. If the sysvolcheck says everything is fine, and you only have one domain controller,

OK, remove the Item Level Targeting - that should hit all Domain Users anyways. Can you extract the .XML file that is made from that policy? Go to your SYSVOL\<domain>\Policies\<GUID for Policy>\User\Preferences\Drives, and open up "Drives.xml". Copy and paste the contents of that file into the mailing list. On Mon, Jan 21, 2019 at 10:23 AM Marco Shmerykowsky PE via samba

On 1/2/2019 11:59 AM, Rowland Penny via samba wrote: > On Wed, 2 Jan 2019 10:43:32 -0500 > Marco Shmerykowsky PE <marco at sce-engineers.com> wrote: > >>> /etc/hostname >> >> machine123 >> >>> /etc/hosts >> >> 127.0.0.1 localhost >> 127.0.1.1 machine123.company-internal.company.com machine123 > > The

I'm trying to get an Samba AD setup. I thought I had RSAT working, but when I launch the server manager I get the error message: "Error - Cannot manage the operating system of the target computer" I can ping the computer and the internal DNS seems to be working. I can manually create shares & I can browse netlogon and sysvol of the AD server. Am I missing something or is this

On 2019-02-17 10:54 am, Rowland Penny via samba wrote: > On Sun, 17 Feb 2019 10:37:48 -0500 > Marco Shmerykowsky <marco at sce-engineers.com> wrote: > > >> >> Seems I can map a drive from the command line. (Didn't check that >> - it was 2:00am and I was tired with fighting this stuff) > > Time you went to bed ;-) > > its 15:45 Sun here. >

I tried the NTLM setting. No change. When I try to browse the network, I get the following error: "internal is not accessible. You might not have permission to use this network resource. The list of servers for this workgroup is not currently available." Here is the smb.conf from the AD machine. [global] netbios name = MACHINE251 realm = INTERNAL.DOMAIN.COM

On 6/3/2015 11:43 AM, Ryan Ashley wrote: > James, I cloned it using git. I installed it to a private partition > (/samba) back when I was first testing Samba4. It is in the path and > this worked for ages, but recently just stopped. No errors, no warnings, > nothing. Just dead. > > The GP in question is the default domain policy. I already tried > unlinking it and it fails on

Hi all! I have a AD domain based on Samba 4.7.6.I created a group policy that installs CA certificate as trusted root CA. The policy works when security filtering is set to Authenticated Users. But when I remove Apply permission of Authenticated Users in Delegation tab (Read permission remains) and add Domain Computers to Security Filtering, policy is not applied anymore. I am a newbe in AD but

On 2019-02-17 10:17 am, Rowland Penny via samba wrote: > On Sun, 17 Feb 2019 09:53:56 -0500 > Marco Shmerykowsky <marco at sce-engineers.com> wrote: > >> I tried the NTLM setting. No change. >> >> When I try to browse the network, I get the following error: >> >> "internal is not accessible. You might not have permission to >> use this

Hi all, Since I have upgraded to Samba 4.2.11 I got errors when updating group policy objects (GPO) on my clients (all Windows 7 Professional). When running "gpupdate" from the command line on Windows 7 Pro Domain-Joined clients it states not to be able to resolve the domain controller. According to what I see from the logs it looks like it's related to resolving accounts. I am

Thanks. Will check. I should have added that everything was working fine on the old winNT style samba domain setup. Its something related to the new samba AD setup On February 17, 2019 8:17:03 AM EST, Rowland Penny via samba <samba at lists.samba.org> wrote: >On Sun, 17 Feb 2019 07:51:24 -0500 >Marco Shmerykowsky via samba <samba at lists.samba.org> wrote: > >> In

Sorry for that email, but i'm really confused about the subject. Starting point: in current configuration (Samba, NT mode) some portable system have CSC enabled, and when go to another site... is another site, eg does not fined the domain, so simply CSC 'work'' as expected. Now that i'm moving computer to the new domain, that is the same domain across all sites, i'm not

Hai marco, I've looked for a good example. http://www.mustbegeek.com/how-to-map-network-drive-using-group-policy/ Only, i say use \\FQDN\share not \\HOSTNAME\share Basicly, the above site says, ( the importent part ) Note that drive maps actions are all based on the drive letter. Action ?Create? and ?Update? will not work if the drive letter already in use. In this case, the action

Hello, i configured group policy via RSAT in my samba 4.1.13 implementation the policy applies correctly to my windows 7 clients but not to my windows XP clients. when i run gpupdate /force in windows XP it replies that the policies are apply correctly .... when i run ./samba-tool ntacl sysvolcheck ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception -

I have been fighting a strange issue with Samba for over a year now, and I am at my wits end. For some reason, clients are unable to get group policy settings from the servers. It honestly appears to be the Windows 7 systems just deciding they don't want to, but they're not terminators. The systems can ping both Samba servers and can even map the sysvol shares to a drive and navigate them.

Am 09.08.2016 um 22:18 schrieb Achim Gottinger via samba: > > > Am 09.08.2016 um 21:48 schrieb Rainer Meier via samba: >>> I think the 10.0.06 entry was created during domain creation. I'd skim >>> thru dns records from an windows machine if possible and delete all >>> occurences of unwanted ip adresses. I assume the gpo's still can not be >>>