%PDF-1.5 %���� ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµù Õ5sLOšuY Donat Was Here
DonatShell
Server IP : www.kowitt.ac.th  /  Your IP : 216.73.216.118
Web Server : Microsoft-IIS/7.5
System : Windows NT SERVER02 6.1 build 7601 (Windows Server 2008 R2 Standard Edition Service Pack 1) i586
User : IUSR ( 0)
PHP Version : 5.6.31
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : OFF  |  Perl : OFF  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /Windows/PolicyDefinitions/en-US/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ HOME SHELL ]     

Current File : /Windows/PolicyDefinitions/en-US/WindowsRemoteShell.adml
<?xml version="1.0" encoding="utf-8"?>
<!--  (c) 2006 Microsoft Corporation  -->
<policyDefinitionResources xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" revision="1.0" schemaVersion="1.0" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
  <displayName>enter display name here</displayName>
  <description>enter description here</description>
  <resources>
    <stringTable>
      <string id="AllowRemoteShellAccess">Allow Remote Shell Access</string>
      <string id="AllowRemoteShellAccess_Help">Configures access to remote shells.

If you enable this policy setting and set it to False, new remote shell connections will be rejected by the server.

If you disable or do not configure this policy setting, new remote shell connections will be allowed.
</string>
      <string id="IdleTimeout">Specify idle Timeout</string>
      <string id="IdleTimeout_Help">Configures maximum time in milliseconds remote shell will stay open without any user activity until it is automatically deleted.

Any value from 0 to 0x7FFFFFFF can be set. A minimum of 60000 milliseconds (1 minute) is used for smaller values.

If you enable this policy setting the server will wait for the specified amount of time since the last received message from the client before terminating the open shell.

If you do not configure or disable this policy setting the default value of 900000 or 15 min will be used.</string>
      <string id="MaxConcurrentUsers">MaxConcurrentUsers</string>
      <string id="MaxConcurrentUsers_Help">Configures the maximum number of users able to concurrently perform remote shell operations on the system.

The value can be any  number from 1 to 100.

If you enable this policy setting, the new shell connections will be rejected if they exceed the specified limit.

If you disable or do not configure this policy setting, the default number will be 5 users.</string>
      <string id="MaxMemoryPerShellMB">Specify maximum amount of memory in MB per Shell</string>
      <string id="MaxMemoryPerShellMB_Help">Configures maximum total amount of memory in megabytes that can be allocated by any active remote shell and all its child processes.

Any value from 0 to 0x7FFFFFFF can be set, where 0 equals unlimited memory, which means the ability of remote operations to allocate memory is only limited by the available virtual memory.

If you enable this policy setting, the remote operation will be terminated when a new allocation exceeds the specified quota.

If you disable or do not configure this policy setting, the value 150 will used by default.</string>
      <string id="MaxProcessesPerShell">Specify maximum number of processes per Shell</string>
      <string id="MaxProcessesPerShell_Help">Configures the maximum number of processes a remote shell is allowed to launch.

Any number from 0 to 0x7FFFFFFF can be set, where 0 means unlimited number of processes.

If you disable or do not configure this policy setting,  the limit will be 5 processes per shell.</string>
      <string id="ShellTimeOut">Specify Shell Timeout</string>
      <string id="ShellTimeOut_Help">
        This policy setting is deprecated.
      </string>
      <string id="MaxShellsPerUser">Specify maximum number of remote shells per user</string>
      <string id="MaxShellsPerUser_Help">Configures maximum number of concurrent shells any user can remotely open on the same system.

Any number from 0 to 0x7FFFFFFF cand be set, where 0 means unlimited number of shells.

If you enable this policy setting, the user will not be able to open new remote shells if the count exceeds the specified limit.

If you disable or do not configure this policy setting, by default the limit will be set to 2 remote shells per user.
</string>
      <string id="WinRS">Windows Remote Shell</string>
    </stringTable>
    <presentationTable>
      <presentation id="AllowRemoteShellAccess">
        <decimalTextBox refId="AllowRemoteShellAccess" defaultValue="1">AllowRemoteShellAccess</decimalTextBox>
      </presentation>
      <presentation id="IdleTimeout">
        <decimalTextBox refId="IdleTimeout" defaultValue="900000">IdleTimeout</decimalTextBox>
      </presentation>
      <presentation id="MaxConcurrentUsers">
        <decimalTextBox refId="MaxConcurrentUsers" defaultValue="5">MaxConcurrentUsers</decimalTextBox>
      </presentation>
      <presentation id="MaxMemoryPerShellMB">
        <decimalTextBox refId="MaxMemoryPerShellMB" defaultValue="150">MaxMemoryPerShellMB</decimalTextBox>
      </presentation>
      <presentation id="MaxProcessesPerShell">
        <decimalTextBox refId="MaxProcessesPerShell" defaultValue="5">MaxProcessesPerShell</decimalTextBox>
      </presentation>
      <presentation id="ShellTimeOut">
        <decimalTextBox refId="ShellTimeOut" defaultValue="2147483647">ShellTimeOut</decimalTextBox>
      </presentation>
      <presentation id="MaxShellsPerUser">
        <decimalTextBox refId="MaxShellsPerUser" defaultValue="2">MaxShellsPerUser</decimalTextBox>
      </presentation>
    </presentationTable>
  </resources>
</policyDefinitionResources>

Anon7 - 2022
AnonSec Team