Displaying 20 results from an estimated 6000 matches similar to: "Samba migration to AD"
2023 Aug 28
3
Samba migration to AD
Il 27/08/2023 14:01, Trenta sis via samba ha scritto:
> Hi,
>
> I need to evaluate a migration of two samba DC to a native AD
> controller, reading wiki, appear that can join to windows 2008, but I
> can't find a full complete migration steps, anybody has experience
> about this migration from samba 4.4.5 to AD DC?
> What are the key on this migration?
>
> Thanks!
2023 Aug 31
1
Samba migration to AD
Thanks on wiki appears
https://wiki.samba.org/index.php/Joining_a_Windows_Server_2008_/_2008_R2_DC_to_a_Samba_AD
I understand that this can be used to migrate fist 2008r2 and the to
newer versions windows?
Any special requirement for initial join between 2008r2 and samba
(specific min version required to allow this join?)
Anybody has migrated with a successful result?
Thanks
Missatge de Fabio
2023 Aug 31
1
Samba migration to AD
Not really answering your question, but as context:
For a period of time, newer windows versions refused to join to Samba,
as they used a WMI method (which we don't support, being DCOM) to work
out what version we were.
We told MS, and they fixed that, which was nice of them.
Since then, we have also worked around the issue by being able to
increase our functional level preparation (which
2024 Jun 19
2
vfs_snapper
Am 17.06.24 um 16:06 schrieb Rowland Penny via samba:
>> The user is member of "domain admins", isn't that enough?
>
> No, because they would be classed as 'others'.
>
>>
>> Or does "SYNC_ACL" not yet work OK, because we miss the steps in
>>
>> https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs
>>
2016 Oct 30
3
Can't access to \\ip and some cname after migration from samba 3 to samba 4.4.5
Hi,
I'll try to give information asked in preious messages:
- We have only one samba Domain controller and one dns (bind in same samba
server)
- Our domain doesn't have any .local
- avahi is not running and we use debian lenny
- This is a samba 4 AD domain, migrated form samba 3 nt domain using
classic upgrade as it is described in samba wiki
- problem is reported in lan network, is not a
2016 Oct 26
3
Can't access to \\ip and some cname after migration from samba 3 to samba 4.4.5
Hi,
Recently we have migrated from samba 3 nt domain to samba 4 AD (4.4.5) and
we have detected that some applications are not working correctly, this
applications need to access to \\ip resource, with name works, but we have
some applications that needs to work only by ip
Also detected this problem with some cname in dns are not responding we use
bind9 + dlz, and we if we access from \\name
2018 Feb 06
2
after a couple of year of success is not possible to add workstations to domain
*//*
Il 05/02/2018 16:41, Rowland Penny ha scritto:
> On Mon, 5 Feb 2018 16:01:27 +0100
> "Massimo Donato - Adcom.it via samba" <samba at lists.samba.org> wrote:
>
>> */Hi all,
>> after a couple of year of successfully working samba AD DC is
>> not possible to add workstations to domain
>> since a few day ago in windows i get a messagge
2016 Oct 27
2
Can't access to \\ip and some cname after migration from samba 3 to samba 4.4.5
hi rowland,
after migration one of past migration tasks were generare reverse zone and
add alla and ptr manually.
I have made some additional tests and seemsthat if we shutdown samba domain
controller or disconnect network then we can access with \\ip with two
domain members server, and then if we reconnect network in samba ad server
we reproduces error with \\ip
any solution?
thanks
2018 Feb 08
4
domain provision again ?
thank you rowland,
Il 08/02/2018 10:41, Rowland Penny via samba ha scritto:
> On Thu, 8 Feb 2018 10:30:55 +0100
> Massimo Donato via samba <samba at lists.samba.org> wrote:
>
>> Hi to All,
>> i'm wondering to do again domain provision.
>> anyone that tryed this?
>> any idea on how to have the previous users profiles imported in the
>> new domain ?
2018 Feb 08
2
domain provision again ?
Hi to All,
i'm wondering to do again domain provision.
anyone that tryed this?
any idea on how to have the previous users profiles imported in the new
domain ?
do i have to rejoin all the workstations?
Kind regards
---
Questa email è stata esaminata alla ricerca di virus da AVG.
http://www.avg.com
2024 May 03
1
Clarification on Samba AD functional levels
Hello all,
Does Samba properly support 2012_R2 domains? If so, what is the earliest
version of Samba AD that supports it? I see that the most recent
versions support ad dc functional level = 2012_R2 in smb.conf but I am
unsure if I can safely run 2012_R2 functional level on older versions of
Samba.
A little background:
In my test environment I setup a Samba 4.20 AD Domain Controller with
2018 Feb 07
2
after a couple of year of success is not possible to add workstations to domain
*//*
Hi Denis,
Il 06/02/2018 20:05, Denis Cardon via samba ha scritto:
> Hi Massimo,
>
>> Il 05/02/2018 16:41, Rowland Penny ha scritto:
>>> On Mon, 5 Feb 2018 16:01:27 +0100
>>> "Massimo Donato - Adcom.it via samba" <samba at lists.samba.org> wrote:
>>>
>>>> */Hi all,
>>>> after a couple of year of successfully
2023 May 10
1
Joining Windows Server 2022 to Samba Domain
Hi,
I'm attempting to join a Windows Server 2022 to an existing domain Im running into issues as I am trying to migrate away from Samba DCs (:sad:)
I've been able to successfully join a Windows Server 2022 to a fresh domain without much trouble after following tranquil.it<https://samba.tranquil.it/doc/en/samba_advanced_methods/samba_add_windows_active_directory.html>'s guide as
2018 Feb 12
3
domain users issue
Hi,
If you try net group /domain "Domain Users" in samba domain with
domain users as primary group any user is showed, but If you try the
same in a native AD then users are listed, try this to reproduce the
error
Thanks
2018-02-12 20:24 GMT+01:00 Trenta sis <trenta.sis at gmail.com>:
> Hi Rowland,
>
> Not really sure if that is correct, tried with native AD and domain
2018 Feb 05
2
after a couple of year of success is not possible to add workstations to domain
*/Hi all,
after a couple of year of successfully working samba AD DC is not
possible to add workstations to domain
since a few day ago in windows i get a messagge complaining that the
account previously exists. ant that to try access with a different account.
after some investigation i found that the backupDC was in hardware fault.
the primary seems to work great, but still unable to add
2018 Feb 12
4
domain users issue
Hi,
Using a samba 4, and having users configured as primary group domain
users (513) we detected that then if you execute net group /domain
"Domain Users" then user is not showed in as member of domain users,
if you remove from primary group and assign another group then with
net group /domain "Domain Users" you can list this user as member.
This generates that for example
2018 Feb 12
2
domain users issue
Not possible, I do not have a Windows AD DC, but I don't doubt it
works, probably because windows has a similar work around to
'samba-tool group listmembers Domain\ Users' --> Correct this command
returns correctly the users
Can you create a file on the netapp that ends up belonging to
'username:Domain Users' ? --> Correct fiel created without issues
Does 'getent
2018 Feb 07
1
after a couple of year of success is not possible to add workstations to domain
Hi Massimo,
>>>
>>>> Il 05/02/2018 16:41, Rowland Penny ha scritto:
>>>>> On Mon, 5 Feb 2018 16:01:27 +0100
>>>>> "Massimo Donato - Adcom.it via samba" <samba at lists.samba.org> wrote:
>>>>>
>>>>>> */Hi all,
>>>>>> after a couple of year of successfully working samba AD DC
2018 Feb 12
2
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
Have you solved?
I have the sambe issue with NEtapp CDOT 9.1 P11, latest versions,
tried with AD and works It seems that domain users are not showed
correctly when tey are set as priamry bug, it seems a samba bug
Can you help?
Thanks<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table
style="border-top: 1px solid #D3D4DE;">
<tr>
<td
2018 Feb 13
2
high cpu usage samba 4 AD
OK, Thanks for your information.
If I remove this new group with 3500 users, I understand that load
will be recovered to normal usage, correct?
About upgrade if I have only one server with 4.4.5 the best option is
add another dc with 4.7 compiled, then transfer and upgrade (or join
old server) or upgrade actual 4.4.5 to 4.7 and then add a new dc?
I like to keep 2 dc with same config and fully