samba.git/source4/setup/provision_self_join_modify.ldif, branch talloc-2.3.3

s4-provision Perform 'modify' operations as system

2011-09-13T05:37:12+00:00

We need this so that we can modify the cn=configuration partition when
we are setting up a new subdomain.

The serverReference on our ${SERVERDN} is in that partition, and
without this change creating a new subdomain fails due to ACLs.

Andrew Bartlett

s4-provision Add initial support for joining as a new subdomain

2011-09-13T05:37:11+00:00

To do this we need to reorganise a lot of the provision code, so that
we can create the framework for the inbound replicaton of the config
and schema partitions and then add in the new subdomain locally.

Andrew Bartlett

provision: reorganize attributes so that we don't attribute with DN syntax that depends on non present object

2011-04-30T12:51:16+00:00

Autobuild-User: Matthieu Patou 
Autobuild-Date: Sat Apr 30 14:51:16 CEST 2011 on sn-devel-104

s4:provision - remove the "servicePrincipalName" creation on the DC object

2010-10-31T18:44:07+00:00

This is now done by the "samba_spnupdate" script.

s4:provision: move Samba4 specific DNS stuff to its own file

2010-06-26T07:50:56+00:00

metze

s4:provision: don't use hardcoded values for 'nextRid' and 'rIDAvailablePool'

2010-06-26T07:50:54+00:00

On Windows dcpromo imports nextRid from the local SAM,
which means it's not hardcoded to 1000.

The initlal rIDAvailablePool starts at nextRid + 100.

I also found that the RID Set of the local dc
should be created via provision and not at runtime,
when the first rid is needed.
(Tested with dcpromo on w2k8r2, while disabling the DNS
 check box).

After provision we should have this (assuming nextRid=1000):

rIDAllocationPool: 1100-1599
rIDPrevAllocationPool: 1100-1599
rIDUsedPool: 0
rIDNextRID: 1100

rIDAvailablePool: 1600-1073741823

Because provision sets rIDNextRid=1100, the first created account
(typically DNS related accounts) will get 1101 as rid!

metze

s4:provision_self_join_modify.ldif - Point out that account "dns" is s4 specific

2010-01-10T21:48:04+00:00

s4-provision: don't hard wire the creation of the RID Set object

2010-01-08T02:03:00+00:00

We now create it automatically in the samldb module when the first
user is created. 

The creation of the dns user also had to move to the _modify.ldif as
it now relies on the fSMO role being setup for the RID Manager

Pair-Programmed-With: Andrew Bartlett

s4-provision: use DNS name, not domain name

2009-09-11T07:14:01+00:00

The SPNs end in the DNS domain name

s4/provision: add the nTDSDSA GUID based DNS entries and SPNs

2009-09-11T04:07:22+00:00

The DNS entries and SPNs are needed for samba<->samba DRS
replication. This patch adds them for a standalone DC configure. A
separate patch will add them for the vampire configure