Configuration driven Active Directory management.
Define subnets using configuration. Subnets are assigned to sites in the configuration scope of a forest.
These allow computers to detect, what site they are part of and thus the most efficient domain controller to speak with for authentication purposes. Other services too will use this for network traffic optimization.
Defining any subnet in configuration causes the ADMF to assume all subnets are defined in configuration, generating delete tasks for any undefined subnets!
[
{
"SiteName": "ContosoEU",
"Name": "10.20.0.0/24",
"Description": "Server subnet Contoso Europe Datacenter",
"Location": "Europe > Germany > Frankfurt"
}
]
Create configuration based off current subnet configuration:
$allSubnets = Get-ADReplicationSubnet -Filter * -Properties Description | Select-Object *, @{
Name = "SiteName"
Expression = { ($_.Site | Get-ADObject).Name }
}
$allSubnets | Select-Object SiteName, Name, Description, Location | ConvertTo-Json
Name of the site the subnet should be assigned to.
Subnet to assign. Must be a subnet in the following notation:
<ipv4address>/<subnetsize>
E.g.:
1.2.3.4/24
Description to add to the subnet.
Location, where the subnet is at.