ClearOS Bug Tracker


View Revisions: Issue #22691 All Revisions ] Back to Issue ]
Summary 0022691: Restore of an AD environment fails without Windows Networking
Revision 2019-01-14 03:50 by NickH
Description If you are doing a v6 config backup to a v7 restore and you are using the Active Directory Connector, then the restore will complete but leave an invalid Samba configuration. The symptoms are that in the Winbind section of smb.conf you will see something like:
# Winbind
idmap config * : backend = rid
idmap config * : range = 20000000-29999999

instead of:
# Winbind
idmap config MYDOMAIN : backend = rid
idmap config MYDOMAIN : range = 20000000-29999999
idmap config * : backend = tdb
idmap config * : range = 30000000-39999999

"testparm -s" complains at this and the Accounts System stays off-line.

Th way to get the restore to work is to install Windows Networking (Samba) first. There is no need to initialise it or choose between Standalone or Master/Slave. It just needs to be installed.

If you forget to install it and do your configuration restore, then there is no direct way back apart from a complete re-installation. You cannot get away with installing Windows Networking (Samba) after a restore then restoring again.

Although filed as an app-configuration-backup bug, it may end up as an app-samba bug with something needing to be moved from app-samba to one of the lower level packages like app-smba-core.
Revision 2019-01-08 12:05 by NickH
Description If you are doing a v6 config backup to a v7 restore and you are using the Active Directory Connector, then the restore will complete but leave an invalid Samba configuration. The symptoms are that in the Winbind section of smb.conf you will see something like:
# Winbind
idmap config * : backend = rid
idmap config * : range = 20000000-29999999

instead of:
# Winbind
idmap config MYDOMAIN : backend = rid
idmap config MYDOMAIN : range = 20000000-29999999
idmap config * : backend = tdb
idmap config * : range = 30000000-39999999

"testparm -s" complains at this and the Accounts System stays off-line.

Th way to get the restore to work is to install Windows Networking (Samba) first. There is no need to initialise it or choose between Standalone or Master/Slave. It just needs to be installed.

If you forget to install it and do your configuration restore, then there is no direct way back apart from a complete re-installation. You cannot get away with installing Windows Networking (Samba) after a restore then restoring again.

Although filed as an app-configuration-backup bug, it may end up as an app-samba bug with something needing to me moved from app-samba to one of the lower level packages like app-smba-core.
Revision 2019-01-08 10:31 by NickH
Description If you are doing a v6 config backup to a v7 restore and you are using the Active Directory Connector, then the restore will complete but leave an invalid Samba configuration. The symptoms are that in the Winbind section of smb.conf you will see something like:
# Winbind
idmap config * : backend = rid
idmap config * : range = 20000000-29999999

instead of:
# Winbind
idmap config MYDOMAIN : backend = rid
idmap config MYDOMAIN : range = 20000000-29999999
idmap config * : backend = tdb
idmap config * : range = 30000000-39999999

"testparm -s" complains at this and the Accounts System stays off-line.

Th way to get the restore to work is to install Windows Networking (Samba) first. There is no need to initialise it or choose between Standalone or Master/Slave. It just needs to be installed.

If you forget to install it and do your configuration restore, then there is no direct way back apart from a complete re-installation. You cannot get away with installing Windows Networking (Samba) after a restore then restoring again.