Skip to main content

AADSites - New-AADSite Syntax

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

This function enables you to create a new site.  On Create options available to set include the site links that the site is a member of, the location field and the description.



Create a new AD site object


New-AADSite [-name] [[-SiteLinks] ] [[-Location] ] [[-Description] ] []


This function enables you to create a new AD Site.
You can supply any combination of sitelinks, description or location to add to the new site


Mandatory - The name of the object you want to create.
Position 0.

Optional - The sitelinks of the site you want to add it to
Position 1.

Optional - The location of the site you want to set
Position 3.

Optional - The description of the site you want to set
Position 2.

-------------------------- EXAMPLE 1 --------------------------
Simple usage
new-AADSite -name mainsite1 -Sitelinks "sitelink 1" -location "au/syd/office1" -description "Site description"
-------------------------- EXAMPLE 2 --------------------------
Simple usage - using positional parameters. Also, using multiple sitelinks.
new-AADSite Sitename "sitelink 1,sitelink 2" "au/syd/office1" "Site description"
-------------------------- EXAMPLE 3 --------------------------
Simple usage - only supply one value to set on creation
new-AADSite -name Sitename -location "au/syd/office1"


Popular posts from this blog

PowerShell 3 behavioural change

It's taken me way too long to get into PowerShell 3, I guess opportunity hasn't shown it's self until now and so, here, my V3 journey begins.

I was asked to debug a script that would run fine in PS v2 and not in v3.  The issue was a that a variable length was being checked and was failing in v3.  This is why...

In v2 if a variable is undefined, this test returns false

PS C:\windows\system32> $var.length -eq 0

In v3 the same test returns true....

PS C:\windows\system32> $var.length -eq 0

Not a biggie, but as in this case, a script has broken so something to consider!



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 - 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 -, - …

compare-object in Powershell - comparing mulitple values

I'm starting to use compare-object more and more, and one thing I noticed, is that you can compare 2 objects based on multiple attributes. here is how it is constructed...
Compare-Object -ReferenceObject $object1 -DifferenceObject $object2 -Property a,b,c,d,eIf a,b,c and d are the same, but e is different, compare object will return a difference. In the following example, I use "-eq $null" as a check because by default compare-object returns $null if the objects are the same.
#create an array of objects to check against

$collection = @()
foreach ($entry in ("aaaaa","bbbbb","ccccc","ddddd")){
   $store = "" | select "a","b","c","d","e"
   $store.a = $entry*1
   $store.b = $entry*2
   $store.c = $entry*3
   $store.d = $entry*4
   $store.e = $entry*5
   $collection += $store

#create an object similar to those in the array
$object = "" | select "a","b…