similar to: Samba 3 PDC to WS2012 AD Migration

Displaying 20 results from an estimated 10000 matches similar to: "Samba 3 PDC to WS2012 AD Migration"

2014 Sep 18
1
Samba 3 PDC to WS2012 AD migration
Hi, I have quite a difficult task to solve. I need to migrate from Samba 3 to WS2012 AD. I know the steps are Samba 3 to Samba 4 to WS2008 to WS2012R2. I managed to upgrade Samba 3 PDC to Samba 4 AD, but I am not able to move roles to WS 2008 as I have some DNS related problems. Is there any howto regarding Samba 4, DNS and Active Directory? Better, I would appreciate some lines describing
2015 Nov 06
0
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: > 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
2015 Nov 08
2
Re: [PATCH] v2v: virtio-win: include *.dll too
> On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: >> 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
2015 Nov 09
1
Re: [PATCH] v2v: virtio-win: include *.dll too
On Mon, 2015-11-09 at 18:08 +0300, Roman Kagan wrote: > On Sun, Nov 08, 2015 at 10:15:31AM +0200, Yan Vugenfirer wrote: > > > > > On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > > > > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: > > >> On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld
2015 Nov 09
0
Re: [PATCH] v2v: virtio-win: include *.dll too
On Sun, Nov 08, 2015 at 10:15:31AM +0200, Yan Vugenfirer wrote: > > > On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: > >> 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: >
2024 Apr 01
1
Bad SMB2 (sign_algo_id=1) signature for message
01.04.2024 13:56, Jones Syue ???: >> I can't say for sure but I *think* each time the client is windows server 2012. > > Looks good :) If run this script[1] to test multiple dialects, found only > SMB3_00 and SMB3_02 has this "(sign_algo_id=1)", and per doc[2] it could > be happend with ws2012 and ws2012r2. This *is* 2012 r2. The protocol version it negotiates is
2015 Nov 05
3
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
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
2015 Oct 29
0
Re: [PATCH] v2v: virtio-win: include *.dll too
> On 29 Oct 2015, at 10:28, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld 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
2015 Oct 29
2
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld 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. Roman is talking about what virt-v2v already does. This is good information:
2015 Oct 29
0
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
On Wed, 2015-10-28 at 14:53 +0300, Roman Kagan wrote: > On Wed, Oct 28, 2015 at 12:10:19PM +1100, Vadim Rozenfeld wrote: > > > > > To sum up, the packaging and naming policy of the virtio-win rpm and the > > > > > virtio-win iso therein are different and neither is clear. Hardcoding > > > > > the policy in v2v without actually knowing it appears
2018 Jun 20
0
Getting DFSR working after Samba was demoted (using dfsrmig)
Hi, I have a Samba server with an NT4 domain and want to end up with a Windows Server 2016-only Active Directory. As you've told me here before, I need a WS 2008 R2 as an intermediary. So right now I'm trying to get a healthy domain at the 2008 R2 domain level first. So don't worry about the WS 2016 for now. Most of it already works: I can do a classicmigrate to AD, then join the
2015 Oct 28
8
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
On Wed, Oct 28, 2015 at 12:10:19PM +1100, Vadim Rozenfeld wrote: > > > > To sum up, the packaging and naming policy of the virtio-win rpm and the > > > > virtio-win iso therein are different and neither is clear. Hardcoding > > > > the policy in v2v without actually knowing it appears risky at best. > > It's due to historical reasons mostly. The best
2018 Jun 12
2
Access denied
Hello, We're running Centos 7 with samba 4.7.1 and we have an AD on WS2012 R2, so all users and groups are already created on the AD. The idea is to logon with the credential from de AD to the samba file server. We configured the smb.conf, acording to the samba wiki, so this is the result: [global] security = ADS workgroup = MYDOMAIN realm = MYDOMAIN.COM
2018 Apr 24
1
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, Apr 23, 2018 at 06:25:03PM -0700, Stephen Hemminger wrote: > On Mon, 23 Apr 2018 12:44:39 -0700 > Siwei Liu <loseweigh at gmail.com> wrote: > > > On Mon, Apr 23, 2018 at 10:56 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > > On Mon, Apr 23, 2018 at 10:44:40AM -0700, Stephen Hemminger wrote: > > >> On Mon, 23 Apr 2018 20:24:56 +0300
2018 Apr 24
0
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, 23 Apr 2018 12:44:39 -0700 Siwei Liu <loseweigh at gmail.com> wrote: > On Mon, Apr 23, 2018 at 10:56 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > On Mon, Apr 23, 2018 at 10:44:40AM -0700, Stephen Hemminger wrote: > >> On Mon, 23 Apr 2018 20:24:56 +0300 > >> "Michael S. Tsirkin" <mst at redhat.com> wrote: > >>
2014 Jan 15
2
Windows Server DHCP + UEFI recipe
A small how-to for encapsulating option 210 inside option 43 on Windows DHCP servers would be welcome then :-) And as far as UEFI x86 system go, one would simply have to create another vendor class with the value PXEClient:Arch:00006 On Wed, Jan 15, 2014 at 12:05 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Jan 14, 2014 at 8:52 PM, Alexandre Blanchette > <blanalex at
2012 Dec 04
0
VGA passthrough over VNC
I''d like to be able to use OpenGL on a remote Windows box (WS2012), so I''ve been experimenting with Xen for the past few days. Most of the work-throughs for 3D acceleration with Windows that people post/blog are for local machines, that is the display is shown on the local screen. Is it possible to forward accelerated video through VNC or RDP with Xen? Thanks, --steve
2014 Jan 15
0
Windows Server DHCP + UEFI recipe
On Tue, Jan 14, 2014 at 8:52 PM, Alexandre Blanchette <blanalex at gmail.com> wrote: > I've found a way to support PXE booting both UEFI and BIOS architectures > with Windows Server DHCP. > > This method uses a feature introduced in WinServer 2012: DHCP policies. > > First, in the the DHCP console, at the IPv4 root of the server, create a > vendor class named
2014 Jan 19
0
Windows Server DHCP + UEFI recipe
I successfully encapsulated option 210 inside 43 with Microsoft DHCP servers. I followed the template in the PXELINUX documentation, at the "using vendor options, handcrafted" heading. On Wed, Jan 15, 2014 at 6:45 AM, Alexandre Blanchette <blanalex at gmail.com>wrote: > A small how-to for encapsulating option 210 inside option 43 on Windows > DHCP servers would be welcome
2004 May 24
0
samba 3 keeps trying to authenticate with the nt4 pdc using port 445
Hello, I'm running redhat enterprise as 3.2 with the included samba 3.0.2-6.3E. I'm trying to make this a domain member server in a nt4 domain. I've successfully joined the domain only after using the net join -p 139 option to force samba to use port 139, otherwise it kept trying to communicate over port 445. (I was watching the syn packets with tethereal). Typing wbinfo -g comes