search for: 2k12

Hi, I'm using samba-4.7.x I have some confusions over "map to guest=" options with setting SMB Signing 1. Set "*Server signing =auto*", "*map to guest=bad uid*" and set "client signing in windows 2k12 server group policy" to "Microsoft network client: Digitally sign communications (Always)” = *Disable*" SMB_Server is joined to Windows 2k12 Active Directory with user01. Windows PC is logged to windows 2k12 Activer Directory with user02. I login to share of my SMB_Server from Window...

I think one - maybe final? - problem. How can I tell the difference between drivers for "client" versions of Windows (eg. Windows 7) and server versions of Windows (eg. Windows 2008 Server)? It seems in many or most cases the drivers are identical, eg: $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat c2fdfc6a47fdc9dd25242441cdf1a68e viostor/2k12/amd64/viostor.inf 5ca2cadca2214b90196755dab06676f4 viostor/2k12/amd64/viostor.pdb 80c5ea60a69f37e965cb277383abd067 viostor/2k12/amd64/viostor.sys bbe250c13bf8...

Hi, I'm using samba-4.7.x I have some confusions over "map to guest=" options with setting SMB Signing 1. Set "*Server signing =auto*", "*map to guest=bad uid*" and set "client signing in windows 2k12 server group policy" to "Microsoft network client: Digitally sign communications (Always)” = *Disable*" SMB_Server is joined to Windows 2k12 Active Directory with user01. Windows PC is logged to windows 2k12 Activer Directory with user02. I login to share of my SMB_Server from Window...

...ba at lists.samba.org> wrote: > Hi, > > I'm using samba-4.7.x > I have some confusions over "map to guest=" options with setting SMB > Signing 1. Set "*Server signing =auto*", "*map to guest=bad uid*" and > set "client signing in windows 2k12 server group policy" to > "Microsoft network client: Digitally sign communications (Always)” = > *Disable*" SMB_Server is joined to Windows 2k12 Active Directory with > user01. Windows PC is logged to windows 2k12 Activer Directory with > user02. I login to share of my SM...

...maybe final? - problem. How can I tell the difference > between drivers for "client" versions of Windows (eg. Windows 7) > and server versions of Windows (eg. Windows 2008 Server)? > > It seems in many or most cases the drivers are identical, eg: > > $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* > bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat > c2fdfc6a47fdc9dd25242441cdf1a68e viostor/2k12/amd64/viostor.inf > 5ca2cadca2214b90196755dab06676f4 viostor/2k12/amd64/viostor.pdb > 80c5ea60a69f37e965cb277383abd067 viostor/2k12/amd64/vios...

...can I tell the difference > > between drivers for "client" versions of Windows (eg. Windows 7) > > and server versions of Windows (eg. Windows 2008 Server)? > > > > It seems in many or most cases the drivers are identical, eg: > > > > $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* > > bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat > > c2fdfc6a47fdc9dd25242441cdf1a68e viostor/2k12/amd64/viostor.inf > > 5ca2cadca2214b90196755dab06676f4 viostor/2k12/amd64/viostor.pdb > > 80c5ea60a69f37e965cb277383abd067 vio...

...te: > >> Hi, >> >> I'm using samba-4.7.x >> I have some confusions over "map to guest=" options with setting SMB >> Signing 1. Set "*Server signing =auto*", "*map to guest=bad uid*" and >> set "client signing in windows 2k12 server group policy" to >> "Microsoft network client: Digitally sign communications (Always)” = >> *Disable*" SMB_Server is joined to Windows 2k12 Active Directory with >> user01. Windows PC is logged to windows 2k12 Activer Directory with >> user02. I login t...

...f --git a/v2v/v2v_unit_tests.ml b/v2v/v2v_unit_tests.ml index 95d8430..8e8957d 100644 --- a/v2v/v2v_unit_tests.ml +++ b/v2v/v2v_unit_tests.ml @@ -164,116 +164,116 @@ let test_virtio_iso_path_matches_guest_os ctx = let paths = [ (* Paths from the virtio-win 1.7.4 ISO. *) - "Balloon/2k12/amd64/WdfCoInstaller01011.dll", None; + "Balloon/2k12/amd64/WdfCoInstaller01011.dll", Some win2k12_64; "Balloon/2k12/amd64/balloon.cat", Some win2k12_64; "Balloon/2k12/amd64/balloon.inf", Some win2k12_64; "Balloon/2k12/amd64/balloon.pdb&quot...

...> > between drivers for "client" versions of Windows (eg. Windows 7) > > > and server versions of Windows (eg. Windows 2008 Server)? > > > > > > It seems in many or most cases the drivers are identical, eg: > > > > > > $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* > > > bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat > > > c2fdfc6a47fdc9dd25242441cdf1a68e viostor/2k12/amd64/viostor.inf > > > 5ca2cadca2214b90196755dab06676f4 viostor/2k12/amd64/viostor.pdb > > > 80c5ea60a69f37e96...

v2 -> v3 - Don't make a special case for WdfCoInstaller* files. There is a difference of opinion about whether copying these is necessary, but it seems like it is not harmful. Rich.

Since v1: - Fix a bug in the calculation of lc_basename. By luck this doesn't affect anything given the contents of the current ISO. - Don't copy the WdfCoInstaller*.dll files. Rich.

...est_os ctx = (* Windows OSes fake inspection data. *) let make_win name major minor variant arch = { inspect_defaults with @@ -262,591 +262,149 @@ let test_virtio_iso_path_matches_guest_os ctx = ] in let paths = [ - (* Paths from the virtio-win 1.7.4 ISO. *) - "Balloon/2k12/amd64/WdfCoInstaller01011.dll", None; - "Balloon/2k12/amd64/balloon.cat", Some win2k12_64; - "Balloon/2k12/amd64/balloon.inf", Some win2k12_64; - "Balloon/2k12/amd64/balloon.pdb", Some win2k12_64; - "Balloon/2k12/amd64/balloon.sys", Some win2...

https://github.com/rwmjones/libguestfs/tree/rewrite-virtio-copy-drivers Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html

On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > On Wed, 2015-10-28 at 14:53 +0300, Roman Kagan wrote: > > 1) tell which devices can be configured > Not sure that I fully understated your question. but if you are going to > create some sort of off-line automatic virtio-win drivers update > utility, then it shouldn't be too complicated. Firs of all you will

Patch 1 moves the v2v/fake-virtio-win and v2v/fake-virt-tools directories to the recently created test-data/ hierarchy. This is just refactoring with no functional change at all. Patches 2-4 then extend the available (fake) virtio-win drivers: - Patch 2 adds all of the drivers from the virtio-win RPM. - Patch 3 adds all of the drivers from the virtio-win ISO (which are different from the

...ilesystem metadata in the Properties window (specifically the General tab for info like "Size" and "Contains: n Files, n Folders") for top-level directories via Windows Explorer and very slow recursive directory listing on the command line in PowerShell on Windows Server 2k8 and 2k12 clients mounting the share. Much slower than the same clients querying the same top-level directories via the same methods on the data sets' old home on the NetApp. "Very slow" means tens of minutes to complete for the Samba share vs tens of seconds for the same operation on the Net...

...only the user name but If I use Samba 4.1.x or 4.3.0 in my Domain Controler I watch in Squid LOG domain\\user name and Squidguard Authentication not work. How can I use Samba 4.3 in my DC and only apear in Squid LOG the name user whitout domain? Summing up: If I have a DC with Windows 2k8 or 2k12 ou DC with a Samba 4.2.x, the LOG of Squid show only username and NTLM Authentication of the Squid and Squidguard work perfecly but if I have a DC with Samba 4.1.x or 4.3.0 the LOG of Squid show "domain\\user name" and NTLM Authentication of the Squid work but Squidguard don´t work. At...

Am 15.01.2018 um 11:35 schrieb Denis Cardon via samba: > Yes, when switching, it is much safer to clean up your /var/lib/samba. > Be sure to recreate the /var/lib/samba/private folder after cleanup, > that folder is not recreated automatically most of the time. > > There is nothing very complicated in what you wanted to do. Just be > sure to double check the replication before

...amp;& - extension <> "pdb" && extension <> "sys" then - raise Not_found; - - (* Using the full path, work out what version of Windows - * this driver is for. Paths can be things like: - * "NetKVM/2k12R2/amd64/netkvm.sys" or - * "./drivers/amd64/Win2012R2/netkvm.sys". - * Note we check lowercase paths. - *) - let pathelem elem = string_find lc_path ("/" ^ elem ^ "/") >= 0 in - let arch = - if pathelem...

...the log). Raised at file "src/oUnitAssert.ml", line 45, characters 8-27 Called from file "list.ml", line 73, characters 12-15 Called from file "list.ml", line 73, characters 12-15 Called from file "src/oUnitRunner.ml", line 46, characters 13-26 path Balloon/2k12/amd64/WdfCoInstaller01011.dll should not match win2k12_64 expected: false but got: true ---------------------------------------------------------------------- Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http:...