samba - Mar 2015 - samba 4.1.17 on raspberry pi as ad dc - final thoughts, success and follow up link

Hey List,

first, let me give a huge thanks to everyone who replied and helped.
I learned a lot and I could not have done it in any reasonable time 
frame without your suggestions and answers!

I started new from scratch to make sure no old configuration / data was 
screwing with further attempts.

It pretty much worked without problem. A few things that were done 
different ...

- samba 4.2, not 4.1.17
- no slapd installed
- no cups installed (cups will install avahi) - dont plan on using pi as 
print server
- my-domain.home instead of .local (or .lan or maybe .private)
- not getting confused by the issue ad member and ad d controller

see reported success here: 
https://lists.samba.org/archive/samba/2015-March/190057.html

Hi!

Did you managed to correctly deploy GPOs?

I'm  facing some issues with some types of gpo not being applied.

Thanks

Filipe Moreira
Enviado de um dispositivo m?vel

No dia 14/03/2015, ?s 10:50, Matthias Busch <catwiesel at gmx.net>
escreveu:
> Hey List,
> 
> first, let me give a huge thanks to everyone who replied and helped.
> I learned a lot and I could not have done it in any reasonable time frame
without your suggestions and answers!
> 
> I started new from scratch to make sure no old configuration / data was
screwing with further attempts.
> 
> It pretty much worked without problem. A few things that were done
different ...
> 
> - samba 4.2, not 4.1.17
> - no slapd installed
> - no cups installed (cups will install avahi) - dont plan on using pi as
print server
> - my-domain.home instead of .local (or .lan or maybe .private)
> - not getting confused by the issue ad member and ad d controller
> 
> see reported success here:
https://lists.samba.org/archive/samba/2015-March/190057.html
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

so far, I've only tried to deploy msi via gpo.

when I had initial gpo trouble it was because dns wasnt working quite 
right (when adding a new pc to the domain, it was not added to dns and 
hence could not gpoupdate)

so far, I've only tried to deploy msi via gpo.
what gpo type is troubling you? i could try and report back...

when I had initial gpo trouble it was because dns wasnt working quite 
right (when adding a new pc to the domain, it was not added to dns and 
hence could not gpoupdate)

does gpoupdate /force give any errors?