samba - Dec 2012 - Samba AD DC migration and official packages

Hello:

Recently I have tried Samba AD DC (Samba4), because I want migrate our 
Samba 3 installation to Samba AD DC (Samba4). My tests were 
successfully, I could migrate a copy o f my samba 3 installation.

Now I want to migrate my real installation to Samba4 but my question is 
about packaging. For now there is not a  v4.0 stable Samba package in 
Debian Wheezy, and I don't want install a rc version.

  I can compile and install Samba 4 in Debian, but what about a future 
migration to official and stable packages provided by Debian? How 
painfull would it be such a migration?

Can someone confirm what archives does contain the essential domain data 
(Kerberos, LDAP, DNS, etc) to migrate in the future to a packaged Samba 
AD DC?

Any answer or suggestion is welcome

Thanks, Federico

PD: Sorry for my basic English

On 12/27/12, Federico Alberto Sayd <fsayd at uncu.edu.ar> wrote:
> Now I want to migrate my real installation to Samba4 but my question is
> about packaging. For now there is not a  v4.0 stable Samba package in
> Debian Wheezy, and I don't want install a rc version.
Release version is in experimental. You can backport it for testing
(it's very easy). I do the same but with package files changed a bit
to include smbd.

On Thu, 2012-12-27 at 13:42 -0300, Federico Alberto Sayd
wrote:
> Hello:
> 
> Recently I have tried Samba AD DC (Samba4), because I want migrate our 
> Samba 3 installation to Samba AD DC (Samba4). My tests were 
> successfully, I could migrate a copy o f my samba 3 installation.
> 
> Now I want to migrate my real installation to Samba4 but my question is 
> about packaging. For now there is not a  v4.0 stable Samba package in 
> Debian Wheezy, and I don't want install a rc version.
> 
>   I can compile and install Samba 4 in Debian, but what about a future 
> migration to official and stable packages provided by Debian? How 
> painfull would it be such a migration?
> 
> Can someone confirm what archives does contain the essential domain data 
> (Kerberos, LDAP, DNS, etc) to migrate in the future to a packaged Samba 
> AD DC?
The essential data to the DC is all in the private directory, and the
smb.conf is in etc.  The sysvol share (pointed at in smb.conf) is also
critical, and you should ensure you maintain xattrs when you move that
around.

Finally, the files in 'lock' should be moved to the Samba state
directory of your eventual debian install. 

I agree that the situation around official packages in all the
distributions is frustrating, and I hope we can get a cleaner solution
soon. 

Andrew Bartlett

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org

Beware, read the change logs of debian.

Because of the low stable version of debian samba ( 3.2.x ) 
debian has change some settings so samba4 matches with samba 3.2.x of debian. 

My advice is get the packages for enterprisesamba.org and use 3.6.x from then 
with samba4, or the the applicance from enterprise samba. 

Greetz, 

Louis

>-----Oorspronkelijk bericht-----
>Van: abartlet at samba.org [mailto:samba-bounces at lists.samba.org] 
>Namens Andrew Bartlett
>Verzonden: donderdag 27 december 2012 23:07
>Aan: Federico Alberto Sayd
>CC: samba at lists.samba.org
>Onderwerp: Re: [Samba] Samba AD DC migration and official packages
>
>On Thu, 2012-12-27 at 13:42 -0300, Federico Alberto Sayd wrote:
>> Hello:
>> 
>> Recently I have tried Samba AD DC (Samba4), because I want 
>migrate our 
>> Samba 3 installation to Samba AD DC (Samba4). My tests were 
>> successfully, I could migrate a copy o f my samba 3 installation.
>> 
>> Now I want to migrate my real installation to Samba4 but my 
>question is 
>> about packaging. For now there is not a  v4.0 stable Samba 
>package in 
>> Debian Wheezy, and I don't want install a rc version.
>> 
>>   I can compile and install Samba 4 in Debian, but what 
>about a future 
>> migration to official and stable packages provided by Debian? How 
>> painfull would it be such a migration?
>> 
>> Can someone confirm what archives does contain the essential 
>domain data 
>> (Kerberos, LDAP, DNS, etc) to migrate in the future to a 
>packaged Samba 
>> AD DC?
>
>The essential data to the DC is all in the private directory, and the
>smb.conf is in etc.  The sysvol share (pointed at in smb.conf) is also
>critical, and you should ensure you maintain xattrs when you move that
>around.
>
>Finally, the files in 'lock' should be moved to the Samba state
>directory of your eventual debian install. 
>
>I agree that the situation around official packages in all the
>distributions is frustrating, and I hope we can get a cleaner solution
>soon. 
>
>Andrew Bartlett
>
>-- 
>Andrew Bartlett                                
>http://samba.org/~abartlet/
>Authentication Developer, Samba Team           http://samba.org
>
>
>-- 
>To unsubscribe from this list go to the following URL and read the
>instructions:  https://lists.samba.org/mailman/options/samba
>
>

On 28/12/12 05:34, L.P.H. van Belle wrote:
> Beware, read the change logs of debian.
>
> Because of the low stable version of debian samba ( 3.2.x )
> debian has change some settings so samba4 matches with samba 3.2.x of
debian.
>
> My advice is get the packages for enterprisesamba.org and use 3.6.x from
then
> with samba4, or the the applicance from enterprise samba.
>
> Greetz,
>
> Louis
>
>
>
Thanks, I did not know of the existence of packages provided by 
enterprisesamba.org. For now there is only the appliance, I will wait 
for the samba4 packages.

Regards

Federico