This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 26%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
Hi!
Tested on Windows Server 2019 Standard.
The example is taken from here https://video2.skills-academy.com/en-us/powershell/module/fileserverresourcemanager/new-fsrmquota?view=windowsserver2022-ps only the folder for which the quota is created has been replaced.
PS C:\Windows\system32> $Action = New-FsrmAction -Type Command -Command "c:\windows\system32\cmd.exe" -CommandParameters "echo [source file path] >> c:\log.txt" - ShouldLogError
$Threshold = New-FsrmQuotaThreshold -Percentage 90 -Action $action
New-FsrmQuota -Path "D:\Test" -Size 128MB -Threshold $Threshold -SoftLimit
New-FsrmQuota : 0x80070057, Parameter specified incorrectly.
string:3 character:1
The D:\Test folder exists. If you create from graph. interface, everything is perfectly created. From Powershell works if there are no threshold properties. Can you tell me what needs to be fixed to make it work?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 91%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWK%3C/text%3E%3C/svg%3E)
Konstantin, did you ever figure this out? I get the same error when I try to create a FSRM template using a threshold that includes a Command action. Like you, I can set it up in the GUI fine.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 4%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Here's the code you provided:
$Action = New-FsrmAction -Type Command -Command "c:\windows\system32\cmd.exe" -CommandParameters "echo [source file path] >> c:\log.txt" -ShouldLogError
$Threshold = New-FsrmQuotaThreshold -Percentage 90 -Action $action
New-FsrmQuota -Path "D:\Test" -Size 128MB -Threshold $Threshold -SoftLimit
From the code and error message, it seems like the issue might be related to the usage of the -Size parameter in combination with the -Threshold parameter. The -Size parameter specifies the quota size, and the -Threshold parameter specifies the threshold actions to be triggered when the quota reaches a certain level. It's possible that there's a conflict or incorrect combination of these parameters.
The error could be due to the fact that you're providing both a -Size parameter and a -Threshold parameter. When using threshold actions, you typically wouldn't specify a size at the same time. The threshold actions will be triggered based on the quota's usage percentage, and the -Size parameter might not be compatible in this context.
To resolve the issue, try creating the quota without the -Size parameter and only use the threshold parameters. Here's an adjusted version of your code:
$Action = New-FsrmAction -Type Command -Command "c:\windows\system32\cmd.exe" -CommandParameters "echo [source file path] >> c:\log.txt" -ShouldLogError
$Threshold = New-FsrmQuotaThreshold -Percentage 90 -Action $action
New-FsrmQuota -Path "D:\Test" -Threshold $Threshold -SoftLimit
This version of the code removes the -Size parameter, focusing only on the threshold and action settings. Make sure to adjust the path, action, and other settings as needed for your scenario.
If you need to set both a size limit and threshold actions, you might need to split this into two separate operations: first, create the quota without thresholds and then set the threshold actions afterward.
I figured it out! Here was my process: Since I could create the Action/Threshold via the GUI but not via PowerShell, I had the bright idea to use PS to compare the working Action I created via the GUI vs. the failed Action I created via PS. When I did that, I noticed the following differences:
KillTimeOut, SecurityLevel, and RunLimitInterval. It turns out the PS defaults for SecurityLevel and KillTimeout don't work. So you need to add " -SecurityLevel LocalService -KillTimeout 0" or similar to the New-FsrmAction to get it to work.
Here's the good Action:
Body :
Command : c:\windows\system32\windowspowershell\v1.0\powershell.exe
CommandParameters : .\Send-FSRMEmail.ps1 -QuotaSystemPath '[Quota System Path]' -SourceFileRemotePaths '[Source File Remote
Paths]'
EventType : None
KillTimeOut : 0
MailBCC :
MailCC :
MailTo :
ReportTypes :
RunLimitInterval : 60
SecurityLevel : LocalService
ShouldLogError : True
Subject :
Type : Command
WorkingDirectory : D:\Scripts
PSComputerName :