You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PARAM(
[parameter()][string]$CheckProcess,
[parameter()][int]$CheckProcessId,
[parameter(Mandatory=$True)][string]$ActivityText,
[parameter()][int]$MaximumExecutionMinutes,
[parameter()][switch]$TerminateRunawayProcess
)
Write-BISFFunctionName2Log -FunctionName ($MyInvocation.MyCommand | % {$_.Name}) #must be added at the begin to each function
$a=0
if ($MaximumExecutionMinutes) {
$MaximumExecutionTime = (Get-Date).AddMinutes($MaximumExecutionMinutes)
Write-BISFLog "Maximum execution time will internal override with the value of $MaximumExecutionTime minutes"
} ELSE {
IF ($LIC_BISF_CLI_METCfg -eq "YES") {$MaximumExecutionMinutes = $LIC_BISF_CLI_MET}
IF ($LIC_BISF_CLI_METCfg -eq "NO") {$MaximumExecutionMinutes = 1440}
IF ($LIC_BISF_CLI_METCfg -eq "") {$MaximumExecutionMinutes = 60}
$MaximumExecutionTime = (Get-Date).AddMinutes($MaximumExecutionMinutes)
Write-BISFLog "Maximum execution time used the GPO value with $MaximumExecutionMinutes minutes"
}
From @matthias-schimm on March 12, 2018 20:21
For some customers is possible to configure the $MaximumExecutionMinutes = 60 through ADMX
Copied from original issue: #11
The text was updated successfully, but these errors were encountered: