search for: classicupgrades

I have an old Centos5/Samba3.5 domain with LDAP backend that I am attempting to migrate to the latest Samba 4.2 on Centos 7.1. Samba in both cases has been installed using Sernet packages. I had successfully run the classicupgrade process, but in subsequent testing found that in the 3.5 domain all the computer accounts have the posixAccount class and therefore have a uidNumber.

Am 10.04.2018 um 18:46 schrieb Rowland Penny via samba: > Thanks for the updates, I just wish more people would report errors & > typo's I can send some more, this time from classicupgrade. Again I do not want to do these changes myself, a samba expert should have a look. Feedback for wiki page Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade) Tried on Devuan 1 with

Hello Samba list! Well, my situation is quite the same than this one from a previous post: https://lists.samba.org/archive/samba/2017-May/208201.html I have to make a classicupgrade from a Samba 3 NT server to Samba 4 AD, and meanwhile the office name changed, so I would try to profit of this upgrade to change domain name. So far from the different tests i've made, i could run the

Dear samba list after a classic upgrade i lose the printer drivers uploaded in NT Domain mode the drivers files are still present in print$ share but enumdrivers rpcclient command list no drivers... did i forgot a file in the dbdir during classicupgrade call or this data are not handled during classicupgrade ? Thanx

Hi, I'm going classicupgrade our samba3 to samba4 next weekend, and suddenly realised something: I intent to keep my samba3 PDC machine called 'filehost' as a member server, to only serve files. However, after classicupgrade my new (freshly installed) DC1 will of course have the netbios name from my 'old' samba3 machine. ('filehost') Meaning I end up with two

No sorry, really no idea for this. But i'll try a wild guess... If you have a test setup, try the following. keep the computer UIDs and change the user uids. i did read this somewhere. samba generates SIDs the same way as you would normally generate GUID's and store them in a database. maybe this sid change because of the change uid. Greet, Louis >-----Oorspronkelijk

I can see in the docs that a domain rename is not recommended/supported by Samba for an already provisioned domain. However, what I can't work out is if this is not possible during the classicupgrade step either? Does this make any difference, or would it present the same difficulties as renaming an already provisioned Samba AD? It case what I'm asking is not quite clear - I have a

Hello: First, sorry for my English. I'm testing samba4 rc5. I have compiled and installed samba4 and now I'm trying to simulate an upgrade from my samba3 site to my samba4 test installation. I have setup a isolated network and I have replicated server and clients, copied my samba3 ldap contents and tdb files. But, when I run samba-tool classicupgrade following to the docs,

Hello, I'm talking about re-writing the classicupgrade HowTo since over a year now. :-) Now, after three rainy vacation days, it's finaly done: A complete and comprehensive re-write of the classicupgrade HowTo: https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 Some other mentionable documentation changes, I had done during the last week: *

On Thu, 26 Apr 2018 18:29:39 +0200 Klaus Hartnegg via samba <samba at lists.samba.org> wrote: > Am 10.04.2018 um 18:46 schrieb Rowland Penny via samba: > > Thanks for the updates, I just wish more people would report errors > > & typo's > > I can send some more, this time from classicupgrade. > > Again I do not want to do these changes myself, a samba

Hi, we might have encountered a possible python 3 bug in samba 4.11. We are using the sernet-samba packages. While the classicupgrade works on centos6 (using python 2) it fails on centos8 (using python3) with a classic python3 bug message: # samba-tool domain classicupgrade --dbdir=pdc-files/ --realm=ad.xxx.de --dns-backend=SAMBA_INTERNAL pdc-files/smb.conf INFO 2019-09-25 06:15:34,366 pid:12017

Am 06.06.2018 um 12:41 schrieb Rowland Penny via samba: > I think that 'standalone' machines will continue Thank you very much for clarification. This means that SMB1 and PDC are the problems, not lack of AD. But if we later need to switch to AD, is there a method like classicupgrade to do it? Currently classicupgrade of a standalone server Samba 3 creates a standalone server Samba

Hi all. Problems resolved! I found the samba process that was increasing the memory after I ran the netstat from PID and I discovered that the process opened 88/464 tcp/udp port. After I ran tcpdump program in my DC server listening udp 88 port and I found many clients machines sending traffic a lot to my DC server. I blocked the ips from clients machines by iptables and the samba process

Hi, I'm having trouble with the classic upgrade. We have three samba servers: Server1: CentOS 5/Samba 3.6 (with smbldap-tools) Server2: CentOS 6/Samba Version 4.2.14-SerNet-RedHat-23.el6 Server3: CentOS 7/Samba Version 4.2.14-SerNet-RedHat-23.el7 Server 1: CentOS 5/Samba 3.6 (with smbldap-tools) Serves our OpenLDAP backend for centralised authentication (LDAP replicated to two other servers

Hi Team, *I'm migrating to samba4 (samba 4.0.7) and doing "Upgrading In Place" **and running classicupgrade; *I have installed openldap-devel...as im migrating database from ldap.* * *while doing this am getting the following error message:* # /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/samba-backup/ --use-xattrs=yes --realm=mydomain.com/samba-backup/smb.conf

All, I am getting ready to tackle a classicupgrade. Test runs have gone well. I am just wondering about the Windows client machines after the upgrade. Do I need to remove the previously applied registry changes: DomainCompatibilityMode DNSNameResolutionRequired Do I need to dis-join, and re-join the clients? Current setup is: Single Server: Samba NT4/PDC LDAPsam New setup is: Single Server:

> It looks like Domain Users does not have a gidNumber attribute, '100' > is the default ID set by Samba in idmap.ldb on a DC. can i change this id or is better if i change id in my userers/folders ?? > How did you carry out the classicupgrade and what from ? like wiki.samba.org suggest in classicupgrade and i used samba 4.9.1 compiled from source -- *Corrado Ravinetto *

Hi, I have a problem during the classicupgrade. The problem was discussed in march on this list, but there seems to be nosolution. Can anyone help? ... Setting password for administrator Administrator password has been set to password of user 'root' idmapping sid_to_xid failed for id[0]=S-1-5-32-544: NT_STATUS_NONE_MAPPED set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER.

Hi all, Is this something I should report in bugzilla? In my smb3.conf I have vfs object = recycle full_audit crossrename and when doing a classicupgrade, I'm getting a segmentation fault. It doesn't finish. (tried 4.1.2, 4.1.3, 4.1.4) When removing the line, the classicupgrade finishes successfully. It's easy to get around, but wouldn't it be nicer not to crash..?

Hey everyone... I'm testing samba3 to samba4 migration and I'm having a problem with group migration. Basically, when I run classicupgrade, he keeps warning about group membership. I increase log level and it tells that the group that some users belongs to don't exist. Is there anyway to tell samba classicupgrade to import groups first and then do the rest? Kind regards, Bruno