The Win32_TSRemoteControlSetting WMI class defines the remote control
configuration settings for the Win32_Terminal
class.
The following syntax is simplified from MOF code and includes all defined and inherited properties, in alphabetical order. For reference
information on methods, see the table of methods later in this topic.
Syntax
[dynamic, provider("Win32_WIN32_TSREMOTECONTROLSETTING_Prov")]class Win32_TSRemoteControlSetting : Win32_TerminalSetting
{
string Caption;
string Description;
uint32 LevelOfControl;
uint32 PolicySourceLevelOfControl;
uint32 RemoteControlPolicy;
string SettingID;
string TerminalName;
};
Methods
The Win32_TSRemoteControlSetting class defines the following method.
| Method | Description |
RemoteControl |
Sets the LevelOfControl property of this class.
|
Properties
The Win32_TSRemoteControlSetting class defines the following properties.
- Caption
-
- Data type: string
- Access type: Read-only
- Qualifiers: MaxLen(64)
Short textual description (one-line string) of the
CIM_Setting object. This property is inherited from
CIM_Setting.
- Description
-
- Data type: string
- Access type: Read-only
Description of the CIM_Setting object. This property
is inherited from CIM_Setting.
- LevelOfControl
-
- Data type: uint32
- Access type: Read-only
Level of control for the session, which specifies whether the session will only be viewed by the remote user,
or viewed and controlled through a keyboard and mouse. For more information, see the Remarks section of the
RemoteControl method.
The following values are supported.
| Value | Meaning |
- Disable
- 0 (0x0)
| Remote control is disabled.
|
- EnableInputNotify
- 1 (0x1)
| The user of remote control has full control of the user's session, with the user's permission.
|
- EnableInputNoNotify
- 2 (0x2)
| The user of remote control has full control of the user's session; the user's permission is not
required.
|
- EnableNoInputNotify
- 3 (0x3)
| The user of remote control can view the session remotely, with the user's permission; the remote user
cannot actively control the session.
|
- EnableNoInputNoNotify
- 4 (0x4)
| The user of remote control can view the session remotely, but not actively control the session; the
user's permission is not required.
|
- PolicySourceLevelOfControl
-
- Data type: uint32
- Access type: Read-only
Indicates whether the LevelOfControl property is configured by the server,
group policy, or by default.
Windows Server 2003 and Windows XP: This property is not available.
| Value | Meaning |
- 0 (0x0)
| Server
|
- 1 (0x1)
| Group policy
|
- 2 (0x2)
| Default
|
- RemoteControlPolicy
-
- Data type: uint32
- Access type: Read/write
The policy the server uses to retrieve the remote control settings.
| Value | Meaning |
- Per User
- 1
| The user's remote control settings are in effect.
|
- Server Override
- 0
| The user's remote control settings are overridden by the server.
|
- SettingID
-
- Data type: string
- Access type: Read-only
- Qualifiers: MaxLen(256)
Identifier by which the CIM_Setting object is known.
This property is inherited from CIM_Setting.
- TerminalName
-
- Data type: string
- Access type: Read-only
- Qualifiers: Key
The name of the terminal.
Remarks
To connect to the \root\CIMV2\TerminalServices namespace, the authentication level must include packet
privacy. For C/C++ calls, this would be an authentication level of
RPC_C_AUTHN_LEVEL_PKT_PRIVACY. For Visual Basic and scripting calls, this would be an
authentication level of WbemAuthenticationLevelPktPrivacy or "pktPrivacy", with a value
of 6. The following Visual Basic Scripting Edition (VBScript) example shows how to connect to a remote computer
with packet privacy.
strComputer = "RemoteServer1"
Set objServices = GetObject( _
"winmgmts:{authenticationLevel=pktPrivacy}!Root/CIMv2/TerminalServices")
Managed Object Format (MOF) files contain the definitions for Windows Management Instrumentation (WMI) classes. MOF files are not installed as part of the Windows SDK. They are installed on the server when you add the associated role by using the Server Manager. For more information about MOF files, see Managed Object Format (MOF).
Requirements
| Minimum supported client | Windows XP |
| Minimum supported server | Windows Server 2003 |
| MOF | Tscfgwmi.mof |
| DLL | Tscfgwmi.dll |
| Namespace | \root\CIMV2\TerminalServices on Windows Vista and Windows Server 2008\root\CIMV2 on Windows XP and Windows Server 2003 |
See Also
- Win32_Terminal
- Win32_TerminalSetting
Send comments about this topic to Microsoft
Build date: 10/19/2009