search for: w2k16

...> + "\x7b\xe9\x36\x4d\x25\xe3\xce\x11" ^ > + "\xbf\xc1\x08\x00\x2b\xe1\x03\x18" ^ > + (String.make 24 '\x00')) ]; > + (* Version is necessary for Windows-Kernel-Pnp in w10/w2k16 *) > + > [ "DriverDatabase"; "DriverPackages"; drv_inf_label; > "Configurations"; drv_config ], > [ "ConfigFlags", REG_DWORD 0_l; > -- > 2.11.0 Thanks Pavel, I will push this shortly. Rich. -- Richard Jones, Virtualizat...

Hi, We have a samba 4.2.2 setup compiled from source, single DC, internal DNS. We've been using this samba setup in production since version 4.0.3. All clients are Windows 7-x64. Since we upgraded to samba 4.2.0 back in march 2015, we are not able to join client machines to the domain using our sysprep unattended image, but joining machines via the manual procedure using the Windows GUI

hi All, I have a problem that is way beyond my Samba knowledge skills and capabilities. I would appreciate your advice. This is a VFX company with W10 clients and Windows and Linux servers. Currently, there is a project migrating shares from W2K16 to Linux. The Windows server (from this point of view) services the storage backend in a reliable way. The clients are workstations and render machines. In numbers: - Windows storage: 90TB - Windows WS: ~30 - Windows render machines: 7 Now there is a Linux server with Ubuntu 22.04 (samba 4...

Hello, I try to connect with Active Directory Users and Computers from a W2k16 to a Samba 4.8.3 DC. I get the following error message: https://thomas.glanzmann.de/static/63a3e0ba-8a9d-11e8-891f-f3ff022aacb0/screenshot-x1-2018-07-18-17_12_49.png --------------------------- Active Directory Domain Services --------------------------- Naming information cannot be located becau...

...e setup domain process uses IPv4 and IPv6 addressed to point to the ad. To summarize: - If I disable IPv6 on the to be syspreped machine, it works. - If I disable IPv6 on the Samba AD, it works. In between I tried a lot of things including disabling WINS, Netbios, use w2k8r2, use w2k16, adding fec0:0:0:ffff::1-3/64 to my AD to allow DNS to work bevor IPv4 was ready. All did not bring the expected results. The only thing that works is either disabling IPv6 on the to be syspred machine or disabling IPv6 on the SAMBA AD: interfaces = 10.101.0.1 I went with disabling IPv6 on the Sa...

On Wed, 18 Jul 2018 17:25:51 +0200 Thomas Glanzmann via samba <samba at lists.samba.org> wrote: > Hello, > I try to connect with Active Directory Users and Computers from a > W2k16 to a Samba 4.8.3 DC. I get the following error message: > > https://thomas.glanzmann.de/static/63a3e0ba-8a9d-11e8-891f-f3ff022aacb0/screenshot-x1-2018-07-18-17_12_49.png > > --------------------------- > Active Directory Domain Services > --------------------------- > Naming...