Skip to content

Latest commit

 

History

History
245 lines (135 loc) · 6.41 KB

win32-tsapplicationfileextensions.md

File metadata and controls

245 lines (135 loc) · 6.41 KB
title description ms.assetid ms.tgt_platform keywords topic_type api_name api_location api_type ms.topic ms.date
Win32_TSApplicationFileExtensions class
The file name extensions that are handled by an application on a Remote Desktop Session Host (RD Session Host) server.
beefc266-5ad6-49ee-b761-98764e2905d6
multiple
Win32_TSApplicationFileExtensions class Remote Desktop Services
Win32_TSApplicationFileExtensions class Remote Desktop Services , described
apiref
Win32_TSApplicationFileExtensions
Win32_TSApplicationFileExtensions.Caption
Win32_TSApplicationFileExtensions.Description
Win32_TSApplicationFileExtensions.InstallDate
Win32_TSApplicationFileExtensions.Name
Win32_TSApplicationFileExtensions.Status
TsPubWmi.dll
DllExport
reference
05/31/2018

Win32_TSApplicationFileExtensions class

Describes the file name extensions that are handled by an application on a Remote Desktop Session Host (RD Session Host) server.

Syntax

class Win32_TSApplicationFileExtensions : CIM_LogicalElement
{
  string   Caption;
  string   Description;
  datetime InstallDate;
  string   Name;
  string   Status;
};

Members

The Win32_TSApplicationFileExtensions class has these types of members:

Methods

The Win32_TSApplicationFileExtensions class has these methods.

Method Description
FileAssociations Scans the registry to get the current file associations for an application.
FileExtensions Provides a list of the file name extensions that are handled by an application.

Properties

The Win32_TSApplicationFileExtensions class has these properties.

Caption

Data type: string

Access type: Read-only

Qualifiers: MaxLen (64)

Short description (one-line string) of the object.

This property is inherited from CIM_ManagedSystemElement.

Description

Data type: string

Access type: Read-only

Description of the object.

This property is inherited from CIM_ManagedSystemElement.

InstallDate

Data type: datetime

Access type: Read-only

Qualifiers: Mappingstrings ("MIF.DMTF|ComponentID|001.5")

The date the object was installed. A lack of a value does not indicate that the object is not installed.

This property is inherited from CIM_ManagedSystemElement.

Name

Data type: string

Access type: Read-only

The name of the object.

This property is inherited from CIM_ManagedSystemElement.

Status

Data type: string

Access type: Read-only

Qualifiers: MaxLen (10)

Current status of the object. Various operational and nonoperational statuses can be defined. Operational statuses include: "OK", "Degraded", and "Pred Fail" (an element, such as a SMART-enabled hard disk drive, may be functioning properly but predicting a failure in the near future). Nonoperational statuses include: "Error", "Starting", "Stopping", and "Service". The latter, "Service", could apply during mirror-resilvering of a disk, reload of a user permissions list, or other administrative work. Not all such work is on-line, yet the managed element is neither "OK" nor in one of the other states.

This property is inherited from CIM_ManagedSystemElement.

("OK")

("Error")

("Degraded")

("Unknown")

("Pred Fail")

("Starting")

("Stopping")

("Service")

Remarks

To connect to the \root\CIMV2\TerminalServices namespace, the authentication level must include packet privacy. For C/C++ calls, this is an authentication level of RPC_C_AUTHN_LEVEL_PKT_PRIVACY, which can be set by using the CoSetProxyBlanket COM function. For Visual Basic and scripting calls, this is 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 Microsoft Windows Software Development Kit (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

Requirement Value
Minimum supported client
Windows Vista
Minimum supported server
Windows Server 2008
Namespace
Root\CIMv2\TerminalServices
MOF
Tsallow.mof
DLL
TsPubWmi.dll