Skip to main content

AADSites - Set-AADSubnet Syntax

This function is part of my AADSites module, which can be downloaded here.  For more info on the module see here.

This function allows you to change the description and location attributes of a subnet and also the site it is associated with.
NAME



Set-AADSubnet

SYNOPSIS


Sets the values of an AD subnet object


SYNTAX


Set-AADSubnet [-Identity] [[-description] ] [[-location] ] [[-site] ] []


DESCRIPTION


This function allows you to set the values of an AD Subnet.


You can supply any combination of site, description or location to set

PARAMETERS


-Identity
Mandatory - The name of the object you want to set.


Position 0.


-description


Optional - The description of the subnet you want to set


Position 2.


-location


Optional - The location of the subnet you want to set


Position 3.


-site


Optional - The site that the subnet belongs to.


Position 1.


-------------------------- EXAMPLE 1 --------------------------
Simple usage

PS C:\> set-AADSubnet -Identity 192.168.30.0/24 -Site "testsite1" -location "au/syd/ho1/lvl1" -description "Head office level 1 subnet"
-------------------------- EXAMPLE 2 --------------------------
Simple usage - using positional parameters.
PS C:\> set-AADSubnet 192.168.30.0/24 "testsite1" "au/syd/ho1/lvl1" "Head office level 1 subnet"
-------------------------- EXAMPLE 3 --------------------------
Simple usage - only supply one value to change
PS C:\> set-AADSubnet -Identity 192.168.30.0/24 -location "au/syd/ho1/lvl1"

Comments

Popular posts from this blog

Enable Powershell Remoting (WinRM) via Group Policy

I have been doing some testing on enabling WinRM via group policy, being that WinRM is the service that Powershell v2 sets up it remoting capabilities. Here are the GPO settings that you need to configure WinRM .... set the winrm service to auto start Computer Configuration \ Policies \ Windows Settings \ Security Settings \ System Services Windows Remote Management (WS-Management)  set Startup Mode to Automatic start the service incorporated in to the above - you may need a restart. create a winrm listener Computer Configuration / Policies / Administrative Templates / Windows Components / Windows Remote Management (WinRM) / WinRM Service / Allow automatic configuration of listeners IPv4 filter: * * is listen on all addresses, or if you only want a particular IP address to respond use an iprange eg 10.1.1.1-10.1.1.254 - don't forget that this IP range has to be valid for all hosts that fall in the scope of the GPO you are creating.  You can use 1...

Assigning Permissions - AGDLP

AGDLP It seems I have been mildly distracted away from the title of this blog site.   It does say AD Admin, but I seem to have been taken away by file system stuff.   I have to say, it has all been worthwhile, but it’s probably time I got back to the real heart of what I do. There are probably a million permission assigning advice pages, but I thought I would put another one out there after referring to AGDLP in my last post. So, what is this all about – AGDLP.   Well, it is something I learned in my MCSE 2003 studies and has become ingrained into my ideals since.   As a contractor, I get to move job often.   This enables me to forge opinions on how to configure things in a domain, and more importantly how NOT to configure things. AGDLP is definitely on the to do list…for anyone in any size domain or forest, as it follows some very basic principals.   I will explain these whilst I go through what AGDPL stands for. A A is for...

Finding out what 'SearchFlags' are set on you AD attributes

Whilst doing some research into indexed attributes, I posted this  a while back on how to find your index attributes.  Since then, I have looked a little deeper into what indexing really means and found this excellent explanation on the numbers that can be found in the searchflags attribute of a schema object. Using Florian’s reference, I built the following script (which is both powershell v1 and v2 compatible) to get the schema attributes from the forest schema and return (among other things) the breakdown of your attributes search flags. $forest = [System.DirectoryServices.ActiveDirectory.forest]::getcurrentforest() $schema = [ADSI]('LDAP://CN=Schema,CN=Configuration,dc=' + ($($forest).name -replace "[.]",",dc=")) $attributes = $schema.psbase.children | where {$_.objectClass -eq "attributeSchema"} $collection = @() foreach ($attr in $attributes){ $store = "" | select "Name","lDAPDisplayName","singlev...