Command to set a scheduled task monthly or weekly:

From CMD, not PowerShell (though you can call CMD commands from inside of PowerShell)

schtasks /create /ru SYSTEM /sc monthly /mo first /d SAT /tn Scheduled_Restart /sd "01/01/2016" /ed "12/31/2017" /st "22:00" /tr "shutdown /r /t 30"

schtasks /create /ru SYSTEM /sc WEEKLY /mo 1 /d SAT /tn Scheduled_Restart /sd "01/01/2016" /ed "12/31/2017" /st "22:00" /tr "shutdown /r /t 30"

SCHTASKS /Create [/S system [/U username [/P [password]]]] [/RU username [/RP password]] /SC schedule [/MO modifier] [/D day] [/M months] [/I idletime] /TN taskname /TR taskrun [/ST starttime] [/RI interval] [ {/ET endtime | /DU duration} [/K] [/XML xmlfile] [/V1]] [/SD startdate] [/ED enddate] [/IT | /NP] [/Z] [/F] [/HRESULT] [/?]

 

Description:

                Enables an administrator to create scheduled tasks on a local or remote system.

 

Parameter List:

/S	system	Specifies the remote system to connect to. If omitted the system parameter defaults to the local system.
/U	username	Specifies the user context under which SchTasks.exe should execute.
/P	[password]	Specifies the password for the given user context. Prompts for input if omitted.
/RU	username	Specifies the "run as" user account (user context) under which the task runs. For the system account, valid values are "", "NT AUTHORITY\SYSTEM" or "SYSTEM". For v2 tasks, "NT AUTHORITY\LOCALSERVICE" and "NT AUTHORITY\NETWORKSERVICE" are also available as well as the well known SIDs for all three.
/RP	[password]	Specifies the password for the "run as" user. To prompt for the password, the value must be either "*" or none. This password is ignored for the system account. Must be combined with either /RU or /XML switch.
/SC	schedule	Specifies the schedule frequency. Valid schedule types: MINUTE, HOURLY, DAILY, WEEKLY, MONTHLY, ONCE, ONSTART, ONLOGON, ONIDLE, ONEVENT.
/MO	modifier	Refines the schedule type to allow finer control over schedule recurrence. Valid values are listed in the "Modifiers" section below.
/D	days	Specifies the day of the week to run the task. Valid values: MON, TUE, WED, THU, FRI, SAT, SUN and for MONTHLY schedules 1 - 31 (days of the month). Wildcard "*" specifies all days.
/M	months	Specifies month(s) of the year. Defaults to the first day of the month. Valid values: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC. Wildcard "*" specifies all months.
/I	idletime	Specifies the amount of idle time to wait before running a scheduled ONIDLE task. Valid range: 1 - 999 minutes.
/TN	taskname	Specifies the string in the form of path\name which uniquely identifies this scheduled task.
/TR	taskrun	Specifies the path and file name of the program to be run at the scheduled time. Example: C:\windows\system32\calc.exe
/ST	starttime	Specifies the start time to run the task. The time format is HH:mm (24 hour time) for example, 14:30 for 2:30 PM. Defaults to current time if /ST is not specified.
/RI	interval	Specifies the repetition interval in minutes. This is not applicable for schedule types: MINUTE, HOURLY, ONSTART, ONLOGON, ONIDLE, ONEVENT. Valid range: 1 - 599940 minutes. If either /ET or /DU is specified, then it defaults to 10 minutes.
/ET	endtime	Specifies the end time to run the task. The time format is HH:mm (24 hour time) for example, 14:50 for 2:50 PM. This is not applicable for schedule types: ONSTART, ONLOGON, ONIDLE, ONEVENT.
/DU	duration	Specifies the duration to run the task. The time format is HH:mm. This is not applicable with /ET and for schedule types: ONSTART, ONLOGON, ONIDLE, ONEVENT. For /V1 tasks, if /RI is specified, duration defaults to 1 hour.
/K	kill	Terminates the task at the endtime or duration time. This is not applicable for schedule types: ONSTART, ONLOGON, ONIDLE, ONEVENT. Either /ET or /DU must be specified.
/SD	startdate	Specifies the first date on which the task runs. The format is mm/dd/yyyy. Defaults to the current date. This is not applicable for schedule types: ONCE, ONSTART, ONLOGON, ONIDLE, ONEVENT.
/ED	enddate	Specifies the last date when the task should run. The format is mm/dd/yyyy. This is not applicable for schedule types: ONCE, ONSTART, ONLOGON, ONIDLE, ONEVENT.
/EC	ChannelName	Specifies the event channel for OnEvent triggers.
/IT	interactive	Enables the task to run interactively only if the /RU user is currently logged on at the time the job runs. This task runs only if the user is logged in.
/NP	No password is stored.	The task runs non-interactively as the given user.
/Z	delete after run	Marks the task for deletion after its final run.
/XML	xmlfile	Creates a task from the task XML specified in a file. Can be combined with /RU and /RP switches, or with /RP alone, when task XML already contains the principal.
/V1	pre-Vista	Creates a task visible to pre-Vista platforms. Not compatible with /XML.
/F	force	Forcefully creates the task and suppresses warnings if the specified task already exists.
/RL	level	Sets the Run Level for the job. Valid values are LIMITED and HIGHEST. The default is LIMITED.
/DELAY delaytime	delay	Specifies the wait time to delay the running of the task after the trigger is fired. The time format is mmmm:ss.
/HRESULT	Result Code	For better diagnosability, the process exit code will be in the HRESULT format.

 

Modifiers:

Valid values for the /MO switch per schedule type:

MINUTE:              1 - 1439 minutes.
HOURLY:              1 - 23 hours.
DAILY:   1 - 365 days.
WEEKLY:               weeks 1 - 52.
ONCE:   No modifiers.
ONSTART: No modifiers.
ONLOGON: No modifiers.
ONEVENT:           XPath event query string.
ONIDLE:               No modifiers.
MONTHLY: 1 - 12, or  FIRST, SECOND, THIRD, FOURTH, LAST, LASTDAY.

 

Examples:

==> Creates a scheduled task "doc" on the remote machine "ABC" which runs notepad.exe every hour under user "runasuser".

SCHTASKS /Create /S ABC /U user /P password /RU runasuser  /RP runaspassword /SC HOURLY /TN doc /TR notepad

 

==> Creates a scheduled task "accountant" on the remote machine  "ABC" to run calc.exe every five minutes from the specified start time to end time between the start date and end date.

SCHTASKS /Create /S ABC /U domain\user /P password /SC MINUTE  /MO 5 /TN accountant /TR calc.exe /ST 12:00 /ET 14:00  /SD 06/06/2006 /ED 06/06/2006 /RU runasuser /RP userpassword

 

==> Creates a scheduled task "gametime" to run freecell on the  first Sunday of every month.

SCHTASKS /Create /SC MONTHLY /MO first /D SUN /TN gametime   /TR c:\windows\system32\freecell

 

==> Creates a scheduled task "report" on remote machine "ABC" to run notepad.exe every week.

SCHTASKS /Create /S ABC /U user /P password /RU runasuser  /RP runaspassword /SC WEEKLY /TN report /TR notepad.exe

 

==> Creates a scheduled task "logtracker" on remote machine "ABC" to run notepad.exe every five minutes starting from the specified start time with no end time. The /RP password will be prompted for.

SCHTASKS /Create /S ABC /U domain\user /P password /SC MINUTE  /MO 5 /TN logtracker   /TR c:\windows\system32\notepad.exe /ST 18:30  /RU runasuser /RP

 

==> Creates a scheduled task "gaming" to run freecell.exe starting at 12:00 and automatically terminating at 14:00 hours every day

SCHTASKS /Create /SC DAILY /TN gaming /TR c:\freecell /ST 12:00  /ET 14:00 /K

 

==> Creates a scheduled task "EventLog" to run wevtvwr.msc starting whenever event 101 is published in the System channel

SCHTASKS /Create /TN EventLog /TR wevtvwr.msc /SC ONEVENT  /EC System /MO *[System/EventID=101]

 

==> Spaces in file paths can be used by using two sets of quotes, one set for CMD.EXE and one for SchTasks.exe. The outer quotes for CMD need to be double quotes; the inner quotes can be single quotes or escaped double quotes:

SCHTASKS /Create   /tr "'c:\program files\internet explorer\iexplorer.exe'   \"c:\log data\today.xml\"" ...

Powershell Function - Get Occurance of Days of the Week

If you are like me, you keep running into people asking you to set their maintenance windows to the 3rd Saturday of the month or to the 2nd & 4th Friday of each month.  To help make it a little easier I've created this function that will return what the 3rd Saturday or the 4th Friday is.  Use this to help automate creation of those Maintenance Windows that don't easily fall into SCCM's normal parameters from the console.  Enjoy!

<#
.Synopsis
    Get-OccuranceOfDayOfWeek returns a specific occurance of a day of the week such as 3rd Saturday

.DESCRIPTION

   Get-OccuranceOfDayOfWeek returns a specific occurance of a day of the week
   such as the 3rd Saturday or the 1st Friday.  Useful for dealing with
   maintenance windows that occur on specific occurances of days of the week.
   The function only returns occurances within the current month, you will
   need to modify it if you need to project further into the future.

   It is possible that the 4th or 5th occurance may return a date in the
   following month.  This is not uncommon with the 5th occurance.

.EXAMPLE
   Get-OccuranceOfDayOfWeek -DayOfWeek Tuesday -Occurance 4
   Returns: Tuesday, February 28, 2017 11:28:54 PM

.EXAMPLE
   Get-OccuranceOfDayOfWeek -DayOfWeek Saturday -Occurance 2
   Returns: Saturday, February 11, 2017 11:39:37 PM

.INPUTS
   String  - Full name of a day of the week (Monday, Tuesday, etc)
   Integer - Which occurance to return (1-4)

.OUTPUTS
   DateTime - The date of the specified occurance within the current month

.NOTES
    # Script by Mark Randol
    # randoltech.blogspot.com
#>
function Get-OccuranceOfDayOfWeek{
    [CmdletBinding(DefaultParameterSetName='OccuranceOfDayOfWeek',
                  SupportsShouldProcess=$true,
                  PositionalBinding=$false)]
    [OutputType([DateTime])]
    Param(
        # Day of the Week
        [Parameter(Mandatory=$true,
                   ValueFromPipeline=$true,
                   ValueFromPipelineByPropertyName=$true,
                   ValueFromRemainingArguments=$false,
                   Position=0,
                   ParameterSetName='OccuranceOfDayOfWeek')]
        [ValidateNotNull()]
        [ValidateNotNullOrEmpty()]
        [ValidateLength(0,15)]
        [ValidateSet("Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday")]
        [Alias("day","dayname","dow")]
        [String]
        $DayOfWeek,

        # Occurance
        [Parameter(Mandatory=$true,
                   ValueFromPipeline=$true,
                   ValueFromPipelineByPropertyName=$true,
                   ValueFromRemainingArguments=$false,
                   Position=1,
                   ParameterSetName='OccuranceOfDayOfWeek')]
        [ValidateNotNull()]
        [ValidateNotNullOrEmpty()]
        [ValidateSet(1,2,3,4)]
        [Alias("occ")]
        [Int]
        $Occurance
    )
    Begin{
    }
    Process{
        [Int]$TestDayNum = 0
        [Arr]$OccuranceDates = @()
        do
        {
            $TestDayNum = $TestDayNum + 1
            $TestDayName = (Get-Date -Day $TestDayNum).DayOfWeek
        }
        until ($TestDayName -eq $DayOfWeek)
        $OccuranceDate = $TestDayNum
        do{
            $OccuranceDates += @($OccuranceDate)
            $OccuranceDate = $OccuranceDate + 7
        }
        while ($OccuranceDate -lt 32)
    }
    End{
        [Int]$OutputInt = $Occurance - 1
        [DateTime]$MyOutput = (Get-Date -Year (Get-Date).Year -Month (Get-Date).Month -Day $OccuranceDates[$OutputInt]).Date
        Return $MyOutput
    }
}

[DateTime]$MyDate = (Get-OccuranceOfDayOfWeek -DayOfWeek Saturday -Occurance 2)
Write-Output $MyDate


Powershell - Remove all included collections from a given collection ID

# Remove all included collections from a given collection ID
# Code Segment by Mark Randol - randoltech.blogspot.com
$ArrIncludeRules = Get-CMCollectionIncludeMembershipRule -CollectionId $DeploymentCollectionID
[Int]$LoopCounter = -1
foreach ($IncludeRule in $ArrIncludeRules)
{
    $LoopCounter++
    $IncCollID = $ArrIncludeRules.IncludeCollectionID[$LoopCounter]
    Write-Output "Removing $IncCollID"
    Remove-CMDeviceCollectionIncludeMembershipRule -CollectionId $DeploymentCollectionID -IncludeCollectionId $IncCollID -Force
}