duffney

[DSCLocalConfigurationManager()]
Configuration LCM_HTTPPULL 
{
    param
        (
            [Parameter(Mandatory=$true)]
            [string[]]$ComputerName,

            [Parameter(Mandatory=$true)]
            [string]$guid

duffney

configuration HTTPPullServer
{
    # Modules must exist on target pull server
    Import-DSCResource -ModuleName xPSDesiredStateConfiguration

    Node WS2016P3
    {
        WindowsFeature DSCServiceFeature
        {
            Ensure = "Present"

duffney

$StaleGroupsobj | where MemberCount -eq '0'`
 | select Name,MemberCount,MemberofCount,DaysSinceChange`
 | where MemberOfCount -eq '0' | where DaysSinceChange -GE '190'| ft

duffney

$StaleGroupsobj = @()
$DC = (Get-ADDomain).DNSroot
$Groups = (Get-ADGroup -Filter * -Server $DC).name

Foreach ($Group in $Groups){
    $Group = Get-ADGroup -Filter {Name -eq $Group} -Properties Name, DistinguishedName, `
        GroupCategory, GroupScope, whenCreated, whenChanged, member, `
        memberOf, sIDHistory, SamAccountName, Description -Server $DC |
    Select-Object Name, DistinguishedName, GroupCategory, GroupScope, `
        whenCreated, whenChanged, member, memberOf, SID, SamAccountName, `

duffney

<#
    This is a PowerShell function wrapping the ADMT executable to abstract out migrating Active Directory users.

    Read all the ADMT docs, and all the code and comments below before considering using this : )

    The COM object was covered nicely by Jan Egil Ring:
        http://blog.powershell.no/2010/08/04/automate-active-directory-migration-tool-using-windows-powershell/
        
        Unfortunately, the COM object does not support Include files, a critical requirement for us.