similar to: samba-4-10 as Win2k16 member

On 24/03/2020 18:56, Dipl.-Ing. P?ter Varkoly via samba wrote: > Hi, > > I want to join samba 4.10.13 to an Win2k16 Server as member. The join > was succesfully: > net ads join -U administrator > Using short domain name -- CRANIX > Joined 'ADMIN' to dns domain 'cranix.win' > > wbinfo -u lists all users. But wininfo -u <username> delivers following

What is the compatibility level of samba-4-10.13? When I try to replicate Win2k12RC2 or Win2k16 I got everytime the error:DsAddEntry failed with status WERR_ACCESS_DENIED info (8567, 'WERR_DS_INCOMPATIBLE_VERSION') Thanks a lot. -- Dipl.-Ing. P?ter Varkoly Greuleinweg 37. D-90411 N?rnberg

Hi, I'm using samba 4.6.15 and 4.8.9 as AD server on a lot of openLeap 42.3 server. The server have numerous group directories in /home/groups. This drirectory will be provided by a share: [groups]         comment = Shared directories of groups you are member in.         path = /home/groups         inherit permissions = Yes         inherit acls = Yes         browseable = Yes        

Hi! I'm using 4.10.13 as AD and have the issue that winbind does not show correct the group membership of some users. # Global parameters[global] ldap server require strong auth = no netbios name = admin realm = XXXX.LOKAL workgroup = XXXX dns forwarder = 8.8.8.8 server role = active directory domain controller idmap_ldb:use rfc2307 = Yes

Hi, after installing a samba-4.8.9 AD-Server there is/are an A-Records created for the domain delivering the ip-address(es) of the AD-server. This ip can be changed vie "samba-tool dns update" but after restarting the AD-server the ip-address of the server will be added again. Can this be prohibited or is this necessary to the functionality of the AD-server. Thanks! -- Dipl.-Ing.

Hi, I've detected a very strange behavior on samba 4.8.9 and 4.10.6. After setting a new password for a user with samba-tool the old password remains valid. The user can use both passwords. After setting the third password become the first password invalid: :~ # samba-tool user setpassword extisadm --newpassword=12AbCdEf Changed password OK :~ # samba-tool user setpassword extisadm

Thanks a lot! Am 08.05.19 um 17:05 schrieb Rowland Penny via samba: > On Wed, 8 May 2019 16:16:58 +0200 > Peter Varkoly <peter at varkoly.de> wrote: > >> Hi, >> >> [global] >>         netbios name = admin >>         realm = <LONG-DOMAIN> > I do hope that '<LONG-DOMAIN>' is the dns domain in uppercase Yes it is. > >>

Am Donnerstag, den 03.10.2019, 14:13 +0100 schrieb Rowland penny via samba: > On 03/10/2019 13:43, Dipl.-Ing. P?ter Varkoly via samba wrote: > > Hi, > > > > after installing a samba-4.8.9 AD-Server there is/are an A-Records > > created for the domain delivering the ip-address(es) of the AD- > > server. > > This ip can be changed vie "samba-tool dns

Am Montag, den 16.03.2020, 15:17 +0000 schrieb Rowland penny via samba: > > After deciphering the above, Sorry. evolution has reformatted my text :-( > it is a known feature, only when a user > logs in can you be sure to get a full list of the users groups. Very strange. I've recreated a new user and put it in all groups and he was inmediately in all groups. What does mean to

Hi, How can the SOA record of a domain be changed? I need to decrease expire and minttl Thanks. -- P?ter Varkoly Greuleinweg 37. D-90411 N?rnberg

On Wed, 8 May 2019 16:16:58 +0200 Peter Varkoly <peter at varkoly.de> wrote: > Hi, > > [global] >         netbios name = admin >         realm = <LONG-DOMAIN> I do hope that '<LONG-DOMAIN>' is the dns domain in uppercase >         workgroup = <DOMAIN> >         dns forwarder = 8.8.8.8 >         server role = active directory domain

Hi List I've update updated from samba-4.10 to samba-4.11. After the update I can not manga the dns entries by samba-tool and can not connect with net rpc. I get the error message: NT_STATUS_CONNECTION_REFUSED. I use the bind9 backend. samba-tool dns zonelist localhost Failed to connect host 127.0.0.1 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 127.0.0.1 (127.0.0.1)

Return the right osinfo short IDs for the majority of Windows versions since Windows XP. --- lib/inspect-osinfo.c | 60 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) diff --git a/lib/inspect-osinfo.c b/lib/inspect-osinfo.c index 816d317f1..f93f7ac52 100644 --- a/lib/inspect-osinfo.c +++ b/lib/inspect-osinfo.c @@ -69,6 +69,66 @@ guestfs_impl_inspect_get_osinfo

Return the right osinfo short IDs for the majority of Windows versions since Windows XP. --- Changes from v1: - used the new win2k19 osinfo ID lib/inspect-osinfo.c | 63 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+) diff --git a/lib/inspect-osinfo.c b/lib/inspect-osinfo.c index 816d317f1..e0d19c672 100644 --- a/lib/inspect-osinfo.c +++ b/lib/inspect-osinfo.c @@

During conversion we copy the necessary drivers to the directory "%systemroot%\Drivers\Virtio", adding it to the DevicePath registry value. As documented in [1], this should be enough for Windows to find device drivers and successfully install them. However, it doesn't always happen. Commit 73e009c04 ("v2v: windows: Document use of pnputil to install drivers.") describes

On Thu, Mar 09, 2023 at 03:47:10PM +0200, Andrey Drobyshev wrote: > On 3/8/23 22:52, Richard W.M. Jones wrote: > > On Wed, Mar 08, 2023 at 08:05:35PM +0200, Andrey Drobyshev wrote: > >> During conversion we copy the necessary drivers to the directory > >> "%systemroot%\Drivers\Virtio", adding it to the DevicePath registry > >> value. As documented in

During conversion we copy the necessary drivers to the directory "%systemroot%\Drivers\Virtio", adding it to the DevicePath registry value. As documented in [1], this should be enough for Windows to find device drivers and successfully install them. However, it doesn't always happen. Commit 73e009c04 ("v2v: windows: Document use of pnputil to install drivers.") describes

v1 discussion: https://listman.redhat.com/archives/libguestfs/2023-March/031001.html v1 -> v2: * Omit redirecting output to a separate log with "%~dpn0.log". Andrey Drobyshev (1): convert_windows: add firstboot script to install drivers with pnputil convert/convert_windows.ml | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) -- 2.31.1

On Wed, Mar 08, 2023 at 08:05:35PM +0200, Andrey Drobyshev wrote: > During conversion we copy the necessary drivers to the directory > "%systemroot%\Drivers\Virtio", adding it to the DevicePath registry > value. As documented in [1], this should be enough for Windows to find > device drivers and successfully install them. > > However, it doesn't always happen.

I've been experiencing problem with the drivers not always being installed. This patch merely implements the solution offered by Richard in the commit 73e009c04 ("v2v: windows: Document use of pnputil to install drivers."). The solution wasn't implemented back then, but rather added merely as a comment. Thus I wonder is there some issues which it may cause? The most obvious