Search

Quotas ignored after WMF 3.0 update by Keno M Fischer

Active

2
0
Sign in
to vote
Type: Bug
ID: 775399
Opened: 12/28/2012 11:58:17 AM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
All quotas as described in http://msdn.microsoft.com/en-us/library/windows/desktop/ee309367%28v=vs.85%29.aspx are ignored after the update to WMF 3.0. This used to work in WMF 2.0. See the following example:

Windows PowerShell
Copyright (C) 2012 Microsoft Corporation. All rights reserved.

PS C:\Users\vagrant> winrs -r:http://localhost:5985/wsman -u:vagrant -p:vagrant cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\vagrant>cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd
/C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd
Not enough quota is available to process this command.

C:\Users\vagrant>winrm get winrm/config/winrs
Winrs
    AllowRemoteShellAccess = true
    IdleTimeout = 7200000
    MaxConcurrentUsers = 10
    MaxShellRunTime = 2147483647
    MaxProcessesPerShell = 1024
    MaxMemoryPerShellMB = 1024
    MaxShellsPerUser = 30

The quota should not have been triggered. The same holds true for other quotas as well (see e.g. http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/51810d3b-6236-44f8-99fd-10f004ad8002)
Details (expand)
How often does this happen?
Always Happens

Have you seen this problem before in this product?

No, this is new to the most recent version
Reproduction Steps
1. Set quotas to high value (e.g. winrm set winrm/config/winrs '@{MaxProcessesPerShell="1024"}' )
2. Open winrs to localhost
3. Perform any command that uses more than the default quota, but less than the set quota (e.g. cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd /C cmd)
4. Notice that the quota gets triggered
Expected Results
The set quota should be respected.
File Attachments
0 attachments
Sign in to post a comment.
Sign in to post a workaround.