Skip to main content

AADSites - Remove-AADsite syntax

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

To start the help files, I have chosen the function that has the most logic to deal with.  Remove-AADsite has to deal with linked subnets, child objects such as servers including domain controllers.

If you have subnets associated to the site, remove-AADsite will warn you as such but offer -force:$true as an override
If you have child server objects (not DC's) within the site, remove-AADsite will warn you as such but offer -force:$true as an override
If you have child domain controller objects within the site, remove-AADsite will advise you to move the DC's out of the site before continuing. No override.
The -confirm:$false switch is availale to supress the confirm prompt.


NAME
Remove-AADsite

SYNOPSIS
Removes the AD site object that matches the name supplied


SYNTAX
Remove-AADsite [-Identity] [[-force] ] [[-confirm] ] []


DESCRIPTION
Removes the AD site object, if one exists, that matches the name given.
If there are configured domain controllers in the site, the site will not be removed.
If there are server objects in the site (that are not DC's), the command requires -force:$true option to remove the site.
If there are subnets associated with the site, the command requires -force:$true option to remove the site.
Returns True if the the site has been removed, False if not.


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

-force
Optional - Set to true if you want to ignore warnings and remove the site
Position 1.

-confirm
Optional - Set to false if you want to remove the site without being
prompted
Position 2.

-------------------------- EXAMPLE 1 --------------------------

Simple usage

PS C:\> remove-AADSite -identity Sitename
-------------------------- EXAMPLE 2 --------------------------

Simple usage - remove a site without being prompted to confirm

PS C:\> remove-AADSite -identity Sitename -confirm:$false

-------------------------- EXAMPLE 3 --------------------------

Simple usage - force the removal of a site with associated subnets or non DC servers
PS C:\> remove-AADSite -identity Sitename -force:$true
Labels:

Comments

Post a Comment

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 10.1.1.1 -
2 comments
Read more

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 account.   It is the securit
2 comments
Read more

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 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
Post a Comment
Read more