similar to: Windows search indexing

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 https://www.redhat.com/archives/libguestfs/2015-November/msg00065.html Currently the product variant (eg.

This makes several changes to the handling of virtio-win drivers: The VIRTIO_WIN_DIR environment variable has been renamed VIRTIO_WIN (but you can still use the old name). You can point the VIRTIO_WIN either at a RHEL virtio-win directory (ie. /usr/share/virtio-win), OR at a loopback-mounted virtio-win ISO, OR at the virtio-win.iso file itself. In the latter case, libguestfs is used to open the

Refactor copying of virtio windows drivers into the guest so that the matching of the drivers to the guest os flavor and copying the files happens one next to the other in a single function, and no guestfs handle (nor any other irrelevant info) is leaked outside. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- v2v/convert_windows.ml | 77 ++++++++++------- v2v/utils.ml |

Refactor copying of virtio windows drivers into the guest so that the matching of the drivers to the guest os flavor and copying the files happens one next to the other in a single function, and no guestfs handle (nor any other irrelevant info) is leaked outside. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- changes since v1: - former patch #3 - updated usage of string functions

This makes several changes to the handling of virtio-win drivers: The VIRTIO_WIN_DIR environment variable has been renamed VIRTIO_WIN (but you can still use the old name). You can point the VIRTIO_WIN either at a RHEL virtio-win directory (ie. /usr/share/virtio-win), OR at a loopback-mounted virtio-win ISO, OR at the virtio-win.iso file itself. In the latter case, libguestfs is used to open the

Hi all I'm running since a couple of years a samba ver 3.0.33-3.29.el5_6.2 On a Red Hat 5 with kernel 2.6.18. Samba is member of a domain, with short name BNNAS03; some shares are using domain users, some are anonymous, open to a list of IPs. Suddenly is happening that, from my win7 computer is all ok if I call is with \\bnnas03 I see all shares, I can access and so on. If I call with

This is a strange problem and it is almost certainly a consequence of faulty Windows server configuration but as it is not under my jurisdiction I need a firm starting point before asking the Windows admin to start digging for the problem. The situation is, as far as I know, this: Win2003 AD with a backup domain controller, and a Win2008 R2 file server. There are a large number of users with

I am trying to establish 2 way trust relationship between samba domain and Win2008 AD domain. The trust relationship is established and even verified by both side, but when I try to access samba resources from win2008 domain, it prompts for username and password. However, I can access the win2008 resources from the samba domain without the prompting of username and password. My win2008 is

My AD server is Win2003. And my linux server is ubuntu. Samba version is 2:3.6.3-2ubuntu2.12 and 2:4.1.6+dfsg-1ubuntu2.14.04.7. They are join into the Win2003 AD as normal smb servers (not DC). After Win2003 DC autoupdate last week, I can't use smbclient access all samba server with NTLMv2: ~$ smbclient //172.16.3.13/share -U testuser Enter DOMAIN\testuser's password: session setup

Hello everyone, Below are some buildbot numbers for the week of 3/06/2016 - 3/12/2016. Thanks Galina "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green): buildername | builds | changes | status change ratio

Hello everyone, Below are some buildbot numbers for the last week of 3/13/2016 - 3/19/2016. Thanks Galina "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green): buildername | builds | changes | status change ratio

On 17/03/15 10:13, Sense Zeng wrote: > And use ntlm_auth fail too: > > ntlm_auth --username=testuser > password: > NT_STATUS_LOGON_FAILURE: Logon failure (0xc000006d) > > > 2015-03-17 7:30 GMT+00:00 Sense Zeng <opaperjam at gmail.com>: > >> My AD server is Win2003. And my linux server is ubuntu. Samba version is >> 2:3.6.3-2ubuntu2.12 and

Hi, Is it possible to "upgrade" my S4 DC which was provisioned win2003 type to win2008? Thanks, Robert

When does File Replication using NTFRS or DFS-R will be availabe? Does anybody already work on this item? Here would be some first documentation for this team in case it hasn't started yet: - NTFRS: http://technet.microsoft.com/en-us/library/cc759297(v=ws.10).aspx - SYSVOL replication: http://technet.microsoft.com/de-de/library/dd640019(v=ws.10).aspx - NTFRS migration to DFS-R:

While using SAMBA 3.5.4 as a primary domain controller for Windows Workstations I have problems with offline files synchronization. While using Windows XP everything works great, there is still no problems with machines with XP. Problems started with Vista Business, there is a lot of synchronization conflicts. Windows 7 also have problems with proper offline files synchronization. Most

Hello everyone, Below are some buildbot numbers for the last week of 6/19/2016 - 6/25/2016. Please see the same data in attached csv files: The longest time each builder was red during the last week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed

Premise: I posted the same question to the linux-cifs mailing list. I absolutely don't want to cross-posting, but I am not sure if the problem is related to the cifs client or to the Samba server. If you think that this post is an unnecessary duplicate, feel free to delete it. Hi all, I have a strange problem trying to re-share, via Samba, a CIFS mount. Let first explain my network

We have tested Xen for 3.0.3 rc5. In the testing we mainly focus on retesting the issues of the rc3. Following is the detail status: One new issue found in 3.0.3 rc5: 1. IA32 PAE Win2003 will crash HVM domain with more than 4GB memory assigned on IA32e HV. The issue won''t appear every time. Booting IA32 PAE Win2003 HVM domain for several times with more than 4GB memory will reproduce the

And use ntlm_auth fail too: ntlm_auth --username=testuser password: NT_STATUS_LOGON_FAILURE: Logon failure (0xc000006d) 2015-03-17 7:30 GMT+00:00 Sense Zeng <opaperjam at gmail.com>: > My AD server is Win2003. And my linux server is ubuntu. Samba version is > 2:3.6.3-2ubuntu2.12 and 2:4.1.6+dfsg-1ubuntu2.14.04.7. They are join into > the Win2003 AD as normal smb servers (not

Please forgive the cross-post; I'm not sure where this issue lies. Samba 3.5.1, CentOS 5.5 x86_64 PDC with Win2K, WinXP, Win2003 and Win7 32-bit domain members, tdbsam backend. Cygwin 1.7.7. All basic functionality seems to be fine, except... On Win2K, WinXP and Win2003, a "DIR /Q" on a mapped share always displays the owner as "BUILTIN\Administrators", but a