search for: syncforegroundpolici

Displaying 5 results from an estimated 5 matches for "syncforegroundpolici".

Did you mean: syncforegroundpolicy
2014 Jan 24
1
Win7 login script not running
I?ve got a 4.1.3 Samba PDC Server on Debian Wheezy. It?s running in Classic mode ? all existing clients are Windows XP Pro. I?m installing a Windows 7 Pro 64-bit PC, and have managed to join it to the domain, but can?t get the user?s login script to run. The login scripts work fine on XP. The pertinent sections of smb.conf contain: logon script = %U.bat logon drive = G: [netlogon] path =
2010 Nov 09
1
Windows 7 problems
Hi, I have upgraded to Samba 3.5.6 for Windows 7 Pro compatibility. I am in a test phase to evaluate the behavior of Windows 7 in a Samba PDC environment. I have one Samba server as a PDC with tdbsam backend (no LDAP at all), and I applied the reg and patch as described in the wiki. I have a couple of questions related to Windows 7 : - opening a domain session on the Win7 client takes a
2020 Oct 28
4
GPO fail and sysvol perm errors
Good morning Chris > -----Oorspronkelijk bericht----- > Van: Sonic [mailto:sonicsmith at gmail.com] > Verzonden: dinsdag 27 oktober 2020 21:07 > Aan: L.P.H. van Belle > CC: samba at lists.samba.org > Onderwerp: Re: [Samba] GPO fail and sysvol perm errors > > On Tue, Oct 27, 2020 at 4:01 AM L.P.H. van Belle via samba > <samba at lists.samba.org> wrote: > >
2020 Oct 26
7
GPO fail and sysvol perm errors
> It's needed after every GPO addition and edit. There must be a root > cause to hunt down somewhere. Or is it a bug in 4.13.0 ? Yes, and no. Yes, its a bug. No, in my opionion its an old setting thats just needs some updating. Try this. samba-tool ntacl set "O:LAG:BAD:P(A;OICI;0x001f01ff;;;BA)(A;OICI;0x001200a9;;;SO)(A;OICI;0x001f01
2005 Jul 07
0
Migration: server with smb 2.2 -> new server, 2.2 too, weird issues
Hello all at the samba list. The other day there was a migration of server; the old one had Samba 2.2 (.6) working normally. Every user logged in the domain without problems, their SIDs and the domain SID were right, everything was ideal. But a server update was needed, and a new server was installed, also with Samba 2.2 (.12). The difference in version is not important this time as other