Adam's AD Admin

PowerShell 3 behavioural change

2013-05-17T00:06:00.000+01:00

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
False

In v3 the same test returns true....

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

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

cheers

Adam

Filesystem v 0.992

2012-10-04T23:51:00.000+01:00

Just over a year after I published the first version of this module, and too many revisions to count later, I am fast approaching 1000 downloads! This update takes the number of functions past 50 too! Thanks to everyone who have given me great feedback!

The latest release can be downloaded here. For more info on the module see here.

Bug Fix

removed the discovery error on load

Added Functions

get-sharePermission (not sure why it took so long for this one to appear)
get-NTFSBlockedInheritance - to compliment get-NTFSExplicitPermissions, this return the path of a folder if inheritance has been blocked

updated Function

get-NTFSExplicitPermissions - added an exclude parameter in the same way that get-NTFSPermission works

Cheers

Adam

Assigning Permissions - AGDLP

2012-06-04T23:22:00.000+01:00

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 is for account. It is the security principal that you log in with. It is the service account that runs a scheduled task on a server. It is the computer object in AD.

G is for Global Group. Basic principal number 1 is represent your user base by a group wherever you can. If 1 person in sales needs access to a drive, then most likely the others should have access too.

DL is for Domain Local Group. In the same way that a group represents users, so should a group represent resources. All access is given to the domain local group, ensuring that junior administrators don’t need to play with the ACL on a drive etc, they only have to add an object (Global Group) to a Domain Local Group.

P is for Permission. As mentioned in DL, permissions are assigned to the DL so that the ACL on an object is as simple as possible.

Example

So, lets walk though an example of this.

John is part of the sales group and the sales people have just been given a huge new server with loads of storage for brochure PDFs. John is working with the IT team to get everything set up for access for the whole team.

It has been decided that the Global Group “Sales – All Staff” (of which John is a member) is the best representation of the users that need access to the new drive.

A new file share has been created on the Server and a Domain local group called “Sales Brochures – Modify” has been created and assigned Read and Modify NTFS permissions to the file system and has also been given Read and Change Share permissions.

Whilst there, the IT guys created a “Sales Brochures – Read” Domain Local group and gave the group read to both NTFS and Share permissions.

So the A-G-DL-P looks like this :

Account (A)	Global Group (G)	Domain Local (DL)	Permissions (P)
John	Sales – All Staff	Sales Brochures – Modify	Change on share Modify on NTFS
		Sales Brochures – Read	Read on share Read on NTFS

There isn’t yet an A and G for the read only group, but it is very simple to add anyone read access now.

For those who are interested in what the difference is between a domain local and a global group (something that confused me for a long time) I’ll cover that off in the next blog post.

It’s a very simple process, but is often ignored. I urge administrators of security anywhere to follow this!

Cheers

Adam

quick look at get-NTFSExplicitPermissions

2012-06-04T07:40:00.001+01:00

get-NTFSExplicitPermissions

As one of favourite time saving functions of late, I thought I'd continue my recent trend of blogging again by giving a bit of insight to it's background.

One of the parts to my day job is looking after file servers. I don't do day to day admin work on them, more look at managing space and migrating data to new servers / volumes if required.

Now the problem with doing the data migrations and not being involved in the day to day admin work (ie assigning permissions creating shares etc) is that I have no control over how and where the permissions are assigned. I learnt how to assign permissions to file systems years ago in Novell environments, which was soon followed with the MCSE taught A-G-D-L-P model. (AGDLP? now that sound like a reasonable blog post for an AD Admin blog site!)

Anyway, I have since found that these early teaching on permission models are not implemented as thoroughly as I would like, where ever I seem to work - hence, get-NTFSExplicitPermissions.

This function allows you to return any permissions that have been assigned below the root of the folder structure, giving you exactly who would be affected if you move the data to somewhere else. It defaults to 3 levels deep so it doesn't take hours to run on deep tree structures.

To run it all you need is the path parameter (which is also works as positional parameter 0) and you are away....

get-NTFSExplicitPermissions -path e:\data

get-NTFSExplicitPermissions e:\data

and you get something like this :

PS C:\Users\Administrator> get-NTFSExplicitPermissions e:\data

path IdentityReference FileSystemRights AccessControlType

---- ----------------- ---------------- -----------------

e:\data BUILTIN\Administrators FullControl Allow

E:\data\2 CREATOR OWNER 268435456 Allow

E:\data\2 NT AUTHORITY\SYSTEM FullControl Allow

E:\data\2 BUILTIN\Administrators FullControl Allow

E:\data\2 BUILTIN\Users ReadAndExecute, Synchronize Allow

E:\data\2 BUILTIN\Users CreateFiles, AppendData Allow

E:\data\users CREATOR OWNER FullControl Allow

E:\data\users NT AUTHORITY\SYSTEM FullControl Allow

E:\data\users BUILTIN\Administrators FullControl Allow

E:\data\users BUILTIN\Users ReadAndExecute, Synchronize Allow

E:\data\users BUILTIN\Users ...s, AppendData, Synchronize Allow

E:\data\users CORE\Adam Stone FullControl Allow

note the last line is where I have assigned myself the full control permission to the users folder. The rest of the permissions suggests that inheritance has been switched off on both e:\data\2 and e:\data\users as the default permissions are showing up as not inherited.

To increase the depth of the search, just use the recurse parameter...this will dig 10 folders deep from the root :

get-NTFSExplicitPermissions -path e:\data -recurse 10

Of course, you can filter the results in the same way as you would with the where clause... to remove NT AUTHORITY and BUILTIN results you can do this :

get-NTFSExplicitPermissions -path e:\data | Where {$_.IdentityReference -notlike "NT AUTHORITY*" -and $_.IdentityReference -notlike "BUILTIN*"}

this command run on the same folder as above returns :

path IdentityReference FileSystemRights AccessControlType

---- ----------------- ---------------- -----------------

E:\data\2 CREATOR OWNER 268435456 Allow

E:\data\users CREATOR OWNER FullControl Allow

E:\data\users CORE\Adam Stone FullControl Allow

This function has already saved me more time than it took to write!

The latest release can be downloaded here, and for more info on the module see here.

Oh, and thanks goes to Ivan for his input!

cheers

Adam

new-DFSrGroup

2012-05-31T23:18:00.001+01:00

New-DFSRGroup

This function contains pretty much everything about dfs-r groups. When you create a replication group from the GUI, have you ever noticed the steps that complete on the page after you click create? Ever paid any attention to what they are actually doing? Me neither, until I started looking at this new-dfsrgroup function. Assuming that there are 2 members to the replication group and all parameters have been entered, my function calls dfsradmin no less that 9 times to complete the task.

So how can we use the function? here are some examples....

new-dfsrgroup -name "rg2" -description "desc1" -Servers server1,server2 -folderpath e:\data\users -foldername Users

This command will invoke every part of the function and create a fully meshed replication group. Out of the parameters presented, only name and servers are mandatory. If you were to omit foldername eg :

new-dfsrgroup -name "rg2" -description "desc1" -Servers server1,server2 -folderpath e:\data\users

then the group will be created and the server will be added as members and connections will be created, but as there is no replication folder, members cannot be enabled. Essentially, the folderpath parameter in this example is ignored. If you were to keep the foldername and omit the folderpath :

new-dfsrgroup -name "rg2" -description "desc1" -Servers server1,server2 -foldername Users

then in addition to above a replication folder will be created, but still the members will not be enabled as no folderpath was supplied.

I could go on and on as this function has 10 possible parameters. You can control pretty much anything to do with the replication group creation.

This is straight out of the help file for the function :

PARAMETER Name

Mandatory - The name of the Group to create

Postition 0

PARAMETER Description

Optional - A description of the group

Postition 1

PARAMETER Servers

Mandatory - The servers that will be members in the group. The

first server in the list will be the primary server

Postition 2

PARAMETER FolderPath

Optional - The path to replicate. If not included, the group will

be created but replication not enabled

Postition 3

PARAMETER Foldername

Optional - The name of the folder to appear in the group.

If not included, the group will be created but replication not enabled

Postition 4

PARAMETER StagingSize

Optional - The size of the staging area - defaults to 4Gb

Postition 5

PARAMETER StagingPath

Optional - The path to the staging area - defaults to within the folder

path.

Postition 6

PARAMETER ConflitDeleteSize

Optional - The size of the Conflict and Deleted folder - default to 350mb

Postition 7

PARAMETER FileFilter

Optional - The file types to exclude from replication eg "*.txt,*.tmp"

Postition 8

PARAMETER FolderFilter

Optional - The subfolders to exclude from replication

Postition 9

You can download the module that contains this function here

I hope it helps dfs-r management, ask any questions in the comments!

cheers

Adam

Filesystem 0.99 update (DFS-R!)

2012-05-31T01:35:00.000+01:00

Filesystem Update
Another update / bug fix for my module Filesystem. The latest release can be downloaded here. For more info on the module see here.

In update v0.99, DFS-r management has been released...with a couple of other changes :

NOTE: dfsradmin.exe is required to be installed for the DFSR functions to work

Updated

list-DFSRoots has been renamed to get-dfsroots due to list not being on the approved verb list (an alias exists to redirect list-dfsroots to get-dfsroots for now)

list-DFSLinks has been renamed to get-dfslinks due to list not being on the approved verb list (an alias exists to redirect list-dfslinks to get-dfslinks for now)
get-NTFSPermission - fixed issue with inherited only permissions

New DFS-r functions

add-dfsrGroupMember
disable-dfsrGroupMember

enable-dfsrGroupMember

get-DFSrGroup

get-dfsrGroupConnection

get-DFSRGroupfolder

get-dfsrGroupMember

new-DFSRgroup

new-dfsrGroupConnection

new-dfsrGroupFolder

new-dfsrPropagationReport

new-dfsrPropagationTest

remove-DFSRgroup

remove-dfsrGroupConnection

remove-DFSRGroupfolder

remove-dfsrGroupMember

remove-dfsrPropagationTest

Other New Function

get-NTFSExplicitPermissions - a great time saver when working out who has been assigned permissions below the root of a folder structure

In a separate post, I'll explain what goes on with new-dfsrgroup

cheers

Adam

Filesystem Module v0.98

2012-04-26T00:41:00.000+01:00

Filesystem Update
Another update / bug fix for my module Filesystem. The latest release can be downloaded here. For more info on the module see here.

In update v0.98, the follow has changed :

updated

get-dfslink (added path parameter to output object)

New function

list-DFSRoots
list-DFSLinks

As requested by Deas, the list functions have been added to list all DFS roots in a domain and subsequently, list all links in a dfs root. get-dfslink has been updated to add a path property to the object output.

Just for reference, I have started on my next update already.....Adding DFS-r management!

cheers

Adam

Filesystem 0.97

2012-03-15T21:25:00.000+00:00

Filesystem Update
Another update / bug fix for my module Filesystem. The latest release can be downloaded here. For more info on the module see here.

In update v0.97, the follow has changed :

updated

new-dfsroot (now supports standalone namespaces)

New function

get-fileshares (list all shares on a server)

Thanks goes to Steve for helping test this release.

cheers

Adam

Filesystem v0.96

2012-03-07T20:46:00.001+00:00

Filesystem - Update 4
This is my fourth update / bug fix for my module Filesystem. The latest release can be downloaded here. For more info on the module see here.

In update v0.96, the follow has changed :

updated

get-dfslink (now supports spaces in the link path)
get-dfslink (output now says "disabled" rather than "disbled")

Thanks again to everyone who has take the time to send feedback.

cheers

Adam

Filesystem Module update 3

2012-01-27T05:34:00.000+00:00

Filesystem - Update 3
This is my third update / bug fix for my module Filesystem. The latest release can be downloaded here. For more info on the module see here.

In update v0.94, the follow has changed :

added

get-ntfspermission

updated

add-ntfspermission (now has a domain parameter)
remove-ntfspermission (now has a domain parameter)
new-dfsroot (now has a version parameter)

Thanks to everyone who has take the time to send feedback. I have hopefully addressed all bugs reported.

One thing I have not changed is the name and would like to know how many other people have a name conflict with this module. Use the comments to to report back and even suggest a new name!

cheers

Adam

Filesystem Module update 1

2011-10-23T22:39:00.001+01:00

Filesystem - Update 1
This is my first update / bug fix for my module Filesystem. The latest release can be downloaded here. For more info on the module see here.

In version 0.91, the following has been changed :

Fixed

In new-fileshare, the path parameter now points to the share path rather than the parent path
Various help file updates

Added

New function : Get-diskspace
New function : Remove-fileshare

Updated

Add-NTFSpermission and remove-NTFSpermission now have a custom option. Any granular permission can be assigned to the file system this way. e.g. The read permission is actually made up of 3 granular permissions, read, listDirectory and ExecuteFile. These can now be assigned individually with Add-NTFSPermission -path d:\data -object adams -Permission custom -custom ListDirectory. The full list of permissions (from .net class [System.Security.AccessControl.FileSystemRights] ) are :

AppendData
ChangePermissions
CreateDirectories
CreateFiles
Delete
DeleteSubdirectoriesAndFiles
ExecuteFile
FullControl
ListDirectory
Modify
Read
ReadAndExecute
ReadAttributes
ReadData
ReadExtendedAttributes
Synchronize
TakeOwnership
Traverse
Write
WriteAttributes
WriteData
WriteExtendedAttributes

cheers

Adam

AADSites Module - Update 2

2011-10-21T11:24:00.000+01:00

AADSites - Update 2
This is my second update / bug fix for my module AADSites. The latest release can be downloaded here. For more info on the module see here.

This is, in real terms, quite a big update! Not for those who are using MSAD management pack, for those who use quest tools! This update adds quest support - just open up your quest powershell console and load the AADSites module and it will find the quest snappin.

Thanks goes to Shay for taking the time to give me feedback on this module!

As always please post any feedback to this page!

In version 0.92, the following has been changed :

Fixed
Issue in set-AADSitelink where a null value caused an error

Added
Quest tools are now supported!

Updated
As quest tools are now supported, either MSAD or the quest tools need to be loaded before this module is loaded. If you have both loaded, the MSAD module will be used.

Updated : V0.992 Filesystem Powershell module

2011-09-20T07:10:00.000+01:00

Update : version 0.992 now available including DFS-r

Hot on the heals of my AD sites module, I have been looking at some file system functions. This module is driven primarily by my own needs, but after a prompt on the powergui website from someone after a way of managing DFS with powershell (thanks packetboy), this is what I have come up with. All help files are included with examples, but I will publish the help and examples over time.

Requirements

This module has been built on a Windows 2008 R2 platform and therefore the DFS functions will be based around the 2008 R2 version of DFSUTIL. This is not to say that it is not compatible with anything earlier, it has just not been tested.
Installation and use

Download the zip file and extract to your modules folder. This can be found by running "explorer $pshome\modules" from a PowerShell console. To use, run "import-module Filesystem"

Command list and Help

To retrieve the list of commands and get help, as with all PowerShell functions and cmdlets use the built in get-command and get-help.

Get-command -module filesystem will list all the commands from the module

Get-help get-dfsroot -full will display the full help file

Included functions

add-DFSlinkABEPermission
add-DFSLinkTarget
add-DFSRootTarget
Add-NTFSPermission
disable-DFSLinkTarget
disable-DFSrootABE
enable-DFSLinkTarget
enable-DFSrootABE
get-DFSLink
get-DFSlinkABEPermission
get-dfsroot
get-DFSRootABEStatus
get-shareConnection
new-DFSLink
new-DFSroot
new-FileShare
remove-DFSLink
remove-DFSlinkABEPermission
remove-DFSLinkTarget
remove-DFSRoottarget
Remove-NTFSPermission
set-ntfsInheritance
set-sharepermission
test-fileshare

Please let me know any feedback in the comments, and of course, test in a development environment before using in production.

The module can be downloaded here.

cheers

Adam

AADSites - Update 1

2011-09-20T04:59:00.002+01:00

This is the first update / bug fix for my module AADSites. The latest release can be downloaded here. For more info on the module see here.

AADSites - Update 1

In version 0.91, the following has been changed :

Fixed
Issue in confirm-AADSitelink where a null value caused an error

Added
Each of get-aadsite, get-aadsitelink, and get-aadsubnet now no longer require an identity to be supplied. If identity is null, then all objects are returned.

Updated
Help files have been tweaked in most functions

cheers

Adam

AADSites - Confirm-AADSite Syntax

2011-09-12T22:42:00.003+01:00

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 check the options of a site are correct.

NAME

Confirm-AADSite

SYNOPSIS

Confirms the values provided match the configured site settings

SYNTAX

Confirm-AADSite [-Identity] [[-SiteLinks] ] [[-description] ] [[-location] ] []

DESCRIPTION

This function allows you to validate the settings of an AD Site.
You can supply any combination of sitelinks, description or location to check
and the function will return true or false whether the values match or not.

PARAMETERS

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

-SiteLinks
Optional - The sitelinks of the site you want to confirm
Accepts 1 or more sitelinks, comma separated.
Position 1.

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

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

-------------------------- EXAMPLE 1 --------------------------
Simple usage
confirm-AADSite -Identity mainsite1 -Sitelinks "sitelink 1" -location "au/syd/office1" -description "Site description"
-------------------------- EXAMPLE 2 --------------------------
Simple usage - using positional parameters. Also, using multiple sitelinks.
confirm-AADSite Sitename "sitelink 1,sitelink 2" "au/syd/office1" "Site description"
-------------------------- EXAMPLE 3 --------------------------
Simple usage - only supply one value to check
confirm-AADSite -identity Sitename -location "au/syd/office1"

AADSites - Confirm-AADSitelink Syntax

2011-09-12T22:36:00.001+01:00

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 confirm the options of a sitelink are correct.

NAME

Confirm-AADSitelink

SYNOPSIS

Confirms the values provided match the configured sitelink settings

SYNTAX

Confirm-AADSitelink [-Identity] [[-Sites] ] [[-cost] ] [[-frequency] ] [[-description] ] []

DESCRIPTION

This function allows you to validate the settings of an AD Sitelink.
You can supply any combination of sites, cost, frequency or description to check
and the function will return true or false whether the values match or not.

PARAMETERS

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

-Sites
Optional - The sites of the sitelink you want to confirm.
Accepts 1 or more sites, comma separated.
Position 1.

-cost
Optional - The cost of the sitelink you want to confirm
Position 2.

-frequency
Optional - The frequency of replication the sitelink (in minutes) you want to confirm
Position 3.

-description
Optional - The description of the sitelink you want to confirm
Position 4.

-------------------------- EXAMPLE 1 --------------------------
Simple usage
confirm-AADSitelink -Identity sitelinkname -Sites "testsite1,testsite2" -cost 50 -frequency 30 -description "Main sitelink"
-------------------------- EXAMPLE 2 --------------------------
Simple usage - using positional parameters.
confirm-AADSitelink sitelinkname "testsite1,testsite2" 50 30 "Main sitelink"
-------------------------- EXAMPLE 3 --------------------------
Simple usage - only supply two values to check
confirm-AADSitelink -identity sitelinkname -cost 50 -frequency 30

AADSites - Confirm-AADSubnet Syntax

2011-09-12T22:32:00.001+01:00

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 confirm the options of a subnet are correct.

NAME

Confirm-AADSubnet

SYNOPSIS

Confirms the values provided match the configured subnet settings

SYNTAX

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

DESCRIPTION

This function allows you to validate the settings of an AD Subnet.
You can supply any combination of site, description or location to check
and the function will return true or false whether the values match or not.

PARAMETERS

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

-description
Optional - The description of the subnet you want to confirm
Position 2.

-location
Optional - The location of the subnet you want to confirm
Position 3.

-site
Optional - The site that the subnet belongs to.
Position 1.

-------------------------- EXAMPLE 1 --------------------------
Simple usage
confirm-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.
confirm-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 confirm
confirm-AADSubnet -Identity 192.168.30.0/24 -location "au/syd/ho1/lvl1"

AADSites - Get-AADServicesObject Syntax

2011-09-12T22:28:00.000+01:00

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

This function returns a sites and services object with the specified name and type.

NAME

Get-AADServicesObject

SYNOPSIS

Returns an AD object that matches the name and type supplied

SYNTAX

Get-AADServicesObject [-Identity] [-Type] []

DESCRIPTION

Returns an AD object, if one exists, that matches the name and type.
Returns $null if nothing found

PARAMETERS

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

-Type
Mandatory - The type of the object to check.
Accepts site, subnet or sitelink.
Position 1.

-------------------------- EXAMPLE 1 --------------------------
Simple usage
get-AADServicesObject -identity Sitename -type Site
-------------------------- EXAMPLE 2 --------------------------
Simple usage
get-AADServicesObject -identity Sitelinkname -type Sitelink
-------------------------- EXAMPLE 3 --------------------------
Simple usage
get-AADServicesObject -identity 10.0.1.0/24 -type subnet

AADSites - Get-AADsite Syntax

2011-09-12T22:24:00.000+01:00

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

This function returns all attributes of an AD site.

NAME

Get-AADsite

SYNOPSIS

Returns the AD site object that matches the name supplied

SYNTAX

Get-AADsite [-Identity] []

DESCRIPTION

Returns the AD site object, if one exists, that matches the name given
Returns $null if nothing found

PARAMETERS

-Identity
Mandatory - The name of the object you want to return.
Position 0.
-------------------------- EXAMPLE 1 --------------------------
Simple usage
get-AADSite -identity Sitename

AADSites - Get-AADsitelink Syntax

2011-09-12T07:47:00.002+01:00

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

This function returns all the attributes of an AD Sitelink.

NAME

Get-AADsitelink

SYNOPSIS

Returns the AD sitelink object that matches the name supplied

SYNTAX

Get-AADsitelink [-Identity] []

DESCRIPTION

Returns the AD site object, if one exists, that matches the name given
Returns $null if nothing found
PARAMETERS

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

-------------------------- EXAMPLE 1 --------------------------
Simple usage
get-AADSitelink -identity Sitename

AADSites - Get-AADsubnet Syntax

2011-09-12T07:45:00.000+01:00

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

This function returns all attributes of an AD subnet.

NAME

Get-AADsubnet

SYNOPSIS

Returns the AD subnet object that matches the name supplied

SYNTAX

Get-AADsubnet [-Identity] []

DESCRIPTION

Returns the AD subnet object, if one exists, that matches the name given

Returns $null if nothing found

PARAMETERS

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

-------------------------- EXAMPLE 1 --------------------------
Simple usage
get-AADSubnet -identity 10.0.1.0/24

AADSites - Move-AADSubnetToSite Syntax

2011-09-12T07:41:00.000+01:00

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

This function moves a subnet to a different site. This can be useful to adjust the site topology slightly, or preparation for removal of a site.

NAME

Move-AADSubnetToSite

SYNOPSIS

Move a subnet to a different site

SYNTAX

Move-AADSubnetToSite [-Identity] [-site] []

DESCRIPTION

Move a subnet to a different site
Returns true if successful and false if not.

PARAMETERS

-Identity
Mandatory - The name of the subnet you want to move.
Position 0.

-site
Mandatory - The name of the site to move to.
Position 0.

-------------------------- EXAMPLE 1 --------------------------
Simple usage
move-AADSubnetToSite -identity 192.168.1.0/24 -site Sitename
-------------------------- EXAMPLE 2 --------------------------
Simple usage - using positional parameters
move-AADSubnetToSite 192.168.1.0/24 Sitename

AADSites - New-AADSite Syntax

2011-09-12T07:37:00.000+01:00

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.

NAME

New-AADSite

SYNOPSIS

Create a new AD site object

SYNTAX

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

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

PARAMETERS

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

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

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

-Description
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"

AADSites - New-AADSiteLink Syntax

2011-09-12T07:31:00.000+01:00

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 sitelink. Options available to set on create include the sites that are members of the site linkt, the description, cost and frequency of replication.

NAME

New-AADSiteLink
SYNOPSIS

Creates a new AD sitelink object
SYNTAX

New-AADSiteLink [-name] [-Sites] [[-cost] ] [[-frequency] ] [[-description] ] []

DESCRIPTION

This function enables you to create a new AD Sitelink.

You can supply any combination of sites, cost, frequency or description to set

PARAMETERS

-name
Mandatory - The name of the object you want to create.
Position 0.
-Sites
Optional - The sites you want to add to the site link.
Accepts 1 or more sites, comma separated.
Position 1.
-cost
Optional - The cost of the sitelink you want to set
Position 2.
-frequency
Optional - The frequency of replication the sitelink (in minutes) you want to set
Position 3.
-description
Optional - The description of the sitelink you want to set
Position 4.
-------------------------- EXAMPLE 1 --------------------------
Simple usage
new-AADSitelink -name sitelinkname -Sites "testsite1,testsite2" -cost 50 -frequency 30 -description "Main sitelink"
-------------------------- EXAMPLE 2 --------------------------
Simple usage - using positional parameters.
new-AADSitelink sitelinkname "testsite1,testsite2" 50 30 "Main sitelink"
-------------------------- EXAMPLE 3 --------------------------
Simple usage - only supply two values to set
new-AADSitelink -name sitelinkname -cost 50 -frequency 30

AADSites - New-AADSubnet Syntax

2011-09-12T07:27:00.000+01:00

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 AD subnet. Options you can set on create include the site that the subnet is a member of, the location field and the description.

NAME

New-AADSubnet

SYNOPSIS

Creates a new AD subnet object

SYNTAX

New-AADSubnet [-name] [-Site] [[-Description] ] [[-Location] ] []

DESCRIPTION

This function enables you to create a new AD Subnet.

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

PARAMETERS

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

-Site
Mandatory - The site that the subnet belongs to.
Position 1.
-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.

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

new-AADSubnet -name 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.

new-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

new-AADSubnet -name 192.168.30.0/24 -location "au/syd/ho1/lvl1"