samba - Jan 2015 - 4.1 to 4.2 Member Server Upgrade Precaution?

Hi all,

We are currently using 4.1.15, 2 DC and 1 samba member server.

When moving to 4.2, do we still need to compile the samba member server as
follows?
./configure --with-ads --with-shared-modules=idmap_ad
Thanks for answering.

Kinglok, Fong

Hello,

Am 16.01.2015 um 11:11 schrieb Kinglok, Fong:
> We are currently using 4.1.15, 2 DC and 1 samba member server.
> 
> When moving to 4.2, do we still need to compile the samba member server as
follows?
> ./configure --with-ads --with-shared-modules=idmap_ad
> Thanks for answering.
There will be no changes in the compile options in 4.2. But you should
wait, until 4.2 is released and not use the RCs. They are not for
production environments.

More important is to update your 4.1 DCs to 4.1.16, because this version
fixes a security issue in AD:
https://www.samba.org/samba/history/samba-4.1.16.html

Regards,
Marc

Hi,
> Marc Muehlfeld <mmuehlfeld at samba.org> ? 2015?1?17? 00:16 ???
> 
> Hello,
> 
>> Am 16.01.2015 um 11:11 schrieb Kinglok, Fong:
>> We are currently using 4.1.15, 2 DC and 1 samba member server.
>> 
>> When moving to 4.2, do we still need to compile the samba member server
as follows?
>> ./configure --with-ads --with-shared-modules=idmap_ad
>> Thanks for answering.
> 
> There will be no changes in the compile options in 4.2. But you should
> wait, until 4.2 is released and not use the RCs. They are not for
> production environments.
> 
> More important is to update your 4.1 DCs to 4.1.16, because this version
> fixes a security issue in AD:
> https://www.samba.org/samba/history/samba-4.1.16.html
> 
> Regards,
> Marc
> 
> 
Thank you for answering.

One more question, to configure 4.1 samba member server, I need to start smbd
and winbindd respectively.  However, in 4.2 winbind is used instead of winbindd.
Do I still need to start winbindd or use samba binary?

Kinglok, Fong