SetEncryptionLevel method of the Win32_TSGeneralSetting class
The SetEncryptionLevel method sets the encryption level.
Syntax
uint32 SetEncryptionLevel(
[in] uint32 MinEncryptionLevel
);
Parameters
-
MinEncryptionLevel [in]
-
The minimum encryption level to set.
-
1
-
Low level of encryption. Only data sent from the client to the server is encrypted using 56-bit encryption. Note that data sent from the server to the client is not encrypted.
-
2
-
Client-compatible level of encryption. All data sent from client to server and from server to client is encrypted at the maximum key strength supported by the client.
-
3
-
High level of encryption. All data sent from client to server and from server to client is encrypted using strong 128-bit encryption. Clients that do not support this level of encryption cannot connect.
-
4
-
FIPS-compliant encryption. All data sent from client to server and from server to client is encrypted and decrypted with the Federal Information Processing Standard (FIPS) encryption algorithms using the Microsoft cryptographic modules. FIPS is a standard entitled "Security Requirements for Cryptographic Modules". FIPS 140-1 (1994) and FIPS 140-2 (2001) describe government requirements for hardware and software cryptographic modules used within the U.S. government.
Return value
Returns Success on success, otherwise returns a WMI error code. Refer to Remote Desktop Services WMI Provider Error Codes for a list of these values.
Remarks
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 |
|
| DLL |
|
See also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for