mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
Merged PR 9792: BitLocker CSP - added one new node
This commit is contained in:
Maricia Alforque
@ -6,11 +6,13 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: MariciaAlforque
|
||||
ms.date: 01/04/2018
|
||||
ms.date: 06/29/2018
|
||||
---
|
||||
|
||||
# BitLocker CSP
|
||||
|
||||
> [!WARNING]
|
||||
> Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
The BitLocker configuration service provider (CSP) is used by the enterprise to manage encryption of PCs and devices. This CSP was added in Windows 10, version 1703.
|
||||
|
||||
@ -842,6 +844,34 @@ The following diagram shows the BitLocker configuration service provider in tree
|
||||
</Replace>
|
||||
```
|
||||
|
||||
<a href="" id="allowstandarduserencryption"></a>**AllowStandardUserEncryption**
|
||||
Allows Admin to enforce "RequireDeviceEncryption" policy for scenarios where policy is pushed while current logged on user is non-admin/standard user.
|
||||
|
||||
"AllowStandardUserEncryption" policy is tied to "AllowWarningForOtherDiskEncryption" policy being set to "0", i.e, silent encryption is enforced.
|
||||
|
||||
If "AllowWarningForOtherDiskEncryption" is not set, or is set to "1", "RequireDeviceEncryption" policy will not try to encrypt drive(s) if a standard user is the current logged on user in the system.
|
||||
|
||||
The expected values for this policy are:
|
||||
|
||||
- 1 = "RequireDeviceEncryption" policy will try to enable encryption on all fixed drives even if a current logged in user is standard user.
|
||||
- 0 = This is the default, when the policy is not set. If current logged on user is a standard user, "RequireDeviceEncryption" policy will not try to enable encryption on any drive.
|
||||
|
||||
If you want to disable this policy use the following SyncML:
|
||||
|
||||
``` syntax
|
||||
<Replace>
|
||||
<CmdID>111</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/AllowStandardUserEncryption</LocURI>
|
||||
</Target>
|
||||
<Meta>
|
||||
<Format xmlns="syncml:metinf">int</Format>
|
||||
</Meta>
|
||||
<Data>0</Data>
|
||||
</Item>
|
||||
</Replace>
|
||||
```
|
||||
### SyncML example
|
||||
|
||||
The following example is provided to show proper format and should not be taken as a recommendation.
|
||||
|
||||
@ -6,16 +6,19 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: MariciaAlforque
|
||||
ms.date: 12/05/2017
|
||||
ms.date: 06/29/2018
|
||||
---
|
||||
|
||||
# BitLocker DDF file
|
||||
|
||||
> [!WARNING]
|
||||
> Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
This topic shows the OMA DM device description framework (DDF) for the **BitLocker** configuration service provider.
|
||||
|
||||
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
|
||||
|
||||
The XML below is the current version for this CSP.
|
||||
The XML below is the current version Windows 10, next major version.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
@ -41,7 +44,7 @@ The XML below is the current version for this CSP.
|
||||
<Permanent />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>com.microsoft/1.0/MDM/BitLocker</MIME>
|
||||
<MIME>com.microsoft/3.0/MDM/BitLocker</MIME>
|
||||
<DDFName></DDFName>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
@ -63,7 +66,7 @@ The XML below is the current version for this CSP.
|
||||
Disabling the policy will not turn off the encryption on the storage card. But will stop prompting the user to turn it on.
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>100</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/RequireStorageCardEncryption</LocURI>
|
||||
@ -87,6 +90,10 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:SupportedValues low="0" high="1">
|
||||
<MSFT:SupportedValue value="0" description="Default when policy is not set."/>
|
||||
<MSFT:SupportedValue value="1" description="Allows the admin to require storage card encryption."/>
|
||||
</MSFT:SupportedValues>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
@ -106,7 +113,7 @@ The XML below is the current version for this CSP.
|
||||
Disabling the policy will not turn off the encryption on the system drive. But will stop prompting the user to turn it on.
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>101</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/RequireDeviceEncryption</LocURI>
|
||||
@ -130,6 +137,10 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:SupportedValues low="0" high="1">
|
||||
<MSFT:SupportedValue value="0" description="Default when policy is not set."/>
|
||||
<MSFT:SupportedValue value="1" description="Allows the admin to require encryption."/>
|
||||
</MSFT:SupportedValues>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
@ -160,7 +171,7 @@ The XML below is the current version for this CSP.
|
||||
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>102</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/EncryptionMethodByDriveType</LocURI>
|
||||
@ -186,6 +197,9 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:ADMXBacked>VolumeEncryption.admx</MSFT:ADMXBacked>
|
||||
<MSFT:ADMXCategory>VolumeEncryption~AT~WindowsComponents~FVECategory</MSFT:ADMXCategory>
|
||||
<MSFT:ADMXPolicyName>EncryptionMethodWithXts_Name</MSFT:ADMXPolicyName>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
@ -200,7 +214,7 @@ The XML below is the current version for this CSP.
|
||||
<Description>This policy setting allows you to configure whether BitLocker requires additional authentication each time the computer starts and whether you are using BitLocker with or without a Trusted Platform Module (TPM). This policy setting is applied when you turn on BitLocker.
|
||||
Note: Only one of the additional authentication options can be required at startup, otherwise a policy error occurs.
|
||||
If you want to use BitLocker on a computer without a TPM, set the "ConfigureNonTPMStartupKeyUsage_Name" data. In this mode either a password or a USB drive is required for start-up. When using a startup key, the key information used to encrypt the drive is stored on the USB drive, creating a USB key. When the USB key is inserted the access to the drive is authenticated and the drive is accessible. If the USB key is lost or unavailable or if you have forgotten the password then you will need to use one of the BitLocker recovery options to access the drive.
|
||||
On a computer with a compatible TPM, four types of authentication methods can be used at startup to provide added protection for encrypted data. When the computer starts, it can use only the TPM for authentication, or it can also require insertion of a USB flash drive containing a startup key, the entry of a 6-digit to 20-digit personal identification number (PIN), or both.
|
||||
On a computer with a compatible TPM, four types of authentication methods can be used at startup to provide added protection for encrypted data. When the computer starts, it can use only the TPM for authentication, or it can also require insertion of a USB flash drive containing a startup key, the entry of a 4-digit to 20-digit personal identification number (PIN), or both.
|
||||
If you enable this policy setting, users can configure advanced startup options in the BitLocker setup wizard.
|
||||
If you disable or do not configure this policy setting, users can configure only basic options on computers with a TPM.
|
||||
Note: If you want to require the use of a startup PIN and a USB flash drive, you must configure BitLocker settings using the command-line tool manage-bde instead of the BitLocker Drive Encryption setup wizard.
|
||||
@ -227,7 +241,7 @@ The XML below is the current version for this CSP.
|
||||
Disabling the policy will let the system choose the default behaviors.
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>103</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/SystemDrivesRequireStartupAuthentication</LocURI>
|
||||
@ -253,6 +267,9 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:ADMXBacked>VolumeEncryption.admx</MSFT:ADMXBacked>
|
||||
<MSFT:ADMXCategory>VolumeEncryption~AT~WindowsComponents~FVECategory~FVEOSCategory</MSFT:ADMXCategory>
|
||||
<MSFT:ADMXPolicyName>ConfigureAdvancedStartup_Name</MSFT:ADMXPolicyName>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
@ -264,9 +281,10 @@ The XML below is the current version for this CSP.
|
||||
<Get />
|
||||
<Replace />
|
||||
</AccessType>
|
||||
<Description>This policy setting allows you to configure a minimum length for a Trusted Platform Module (TPM) startup PIN. This policy setting is applied when you turn on BitLocker. The startup PIN must have a minimum length of 6 digits and can have a maximum length of 20 digits.
|
||||
<Description>This policy setting allows you to configure a minimum length for a Trusted Platform Module (TPM) startup PIN. This policy setting is applied when you turn on BitLocker. The startup PIN must have a minimum length of 4 digits and can have a maximum length of 20 digits.
|
||||
If you enable this policy setting, you can require a minimum number of digits to be used when setting the startup PIN.
|
||||
If you disable or do not configure this policy setting, users can configure a startup PIN of any length between 6 and 20 digits.
|
||||
NOTE: If minimum PIN length is set below 6 digits, Windows will attempt to update the TPM 2.0 lockout period to be greater than the default when a PIN is changed. If successful, Windows will only reset the TPM lockout period back to default if the TPM is reset.
|
||||
The format is string.
|
||||
Sample value for this node to enable this policy is:
|
||||
<enabled/><data id="MinPINLength" value="xx"/>
|
||||
@ -274,7 +292,7 @@ The XML below is the current version for this CSP.
|
||||
Disabling the policy will let the system choose the default behaviors.
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>104</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/SystemDrivesMinimumPINLength</LocURI>
|
||||
@ -300,6 +318,9 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:ADMXBacked>VolumeEncryption.admx</MSFT:ADMXBacked>
|
||||
<MSFT:ADMXCategory>VolumeEncryption~AT~WindowsComponents~FVECategory~FVEOSCategory</MSFT:ADMXCategory>
|
||||
<MSFT:ADMXPolicyName>MinimumPINLength_Name</MSFT:ADMXPolicyName>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
@ -331,7 +352,7 @@ The XML below is the current version for this CSP.
|
||||
Disabling the policy will let the system choose the default behaviors.
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>105</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/SystemDrivesRecoveryMessage</LocURI>
|
||||
@ -357,6 +378,9 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:ADMXBacked>VolumeEncryption.admx</MSFT:ADMXBacked>
|
||||
<MSFT:ADMXCategory>VolumeEncryption~AT~WindowsComponents~FVECategory~FVEOSCategory</MSFT:ADMXCategory>
|
||||
<MSFT:ADMXPolicyName>PrebootRecoveryInfo_Name</MSFT:ADMXPolicyName>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
@ -397,7 +421,7 @@ The XML below is the current version for this CSP.
|
||||
Disabling the policy will let the system choose the default behaviors.
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>106</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/SystemDrivesRecoveryOptions</LocURI>
|
||||
@ -423,6 +447,9 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:ADMXBacked>VolumeEncryption.admx</MSFT:ADMXBacked>
|
||||
<MSFT:ADMXCategory>VolumeEncryption~AT~WindowsComponents~FVECategory~FVEOSCategory</MSFT:ADMXCategory>
|
||||
<MSFT:ADMXPolicyName>OSRecoveryUsage_Name</MSFT:ADMXPolicyName>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
@ -463,7 +490,7 @@ The XML below is the current version for this CSP.
|
||||
Disabling the policy will let the system choose the default behaviors.
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>107</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/FixedDrivesRecoveryOptions</LocURI>
|
||||
@ -489,6 +516,9 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:ADMXBacked>VolumeEncryption.admx</MSFT:ADMXBacked>
|
||||
<MSFT:ADMXCategory>VolumeEncryption~AT~WindowsComponents~FVECategory~FVEFDVCategory</MSFT:ADMXCategory>
|
||||
<MSFT:ADMXPolicyName>FDVRecoveryUsage_Name</MSFT:ADMXPolicyName>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
@ -510,7 +540,7 @@ The XML below is the current version for this CSP.
|
||||
Disabling the policy will let the system choose the default behaviors.
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>108</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/FixedDrivesRequireEncryption</LocURI>
|
||||
@ -536,6 +566,9 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:ADMXBacked>VolumeEncryption.admx</MSFT:ADMXBacked>
|
||||
<MSFT:ADMXCategory>VolumeEncryption~AT~WindowsComponents~FVECategory~FVEFDVCategory</MSFT:ADMXCategory>
|
||||
<MSFT:ADMXPolicyName>FDVDenyWriteAccess_Name</MSFT:ADMXPolicyName>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
@ -563,7 +596,7 @@ The XML below is the current version for this CSP.
|
||||
Disabling the policy will let the system choose the default behaviors.
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<CmdID>109</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/RemovableDrivesRequireEncryption</LocURI>
|
||||
@ -589,6 +622,116 @@ The XML below is the current version for this CSP.
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:ADMXBacked>VolumeEncryption.admx</MSFT:ADMXBacked>
|
||||
<MSFT:ADMXCategory>VolumeEncryption~AT~WindowsComponents~FVECategory~FVERDVCategory</MSFT:ADMXCategory>
|
||||
<MSFT:ADMXPolicyName>RDVDenyWriteAccess_Name</MSFT:ADMXPolicyName>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
<NodeName>AllowWarningForOtherDiskEncryption</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Add />
|
||||
<Delete />
|
||||
<Get />
|
||||
<Replace />
|
||||
</AccessType>
|
||||
<Description>Allows Admin to disable all UI (notification for encryption and warning prompt for other disk encryption)
|
||||
and turn on encryption on the user machines silently.
|
||||
Warning: When you enable BitLocker on a device with third party encryption, it may render the device unusable and will
|
||||
require reinstallation of Windows.
|
||||
Note: This policy takes effect only if "RequireDeviceEncryption" policy is set to 1.
|
||||
The format is integer.
|
||||
The expected values for this policy are:
|
||||
|
||||
1 = This is the default, when the policy is not set. Warning prompt and encryption notification is allowed.
|
||||
0 = Disables the warning prompt and encryption notification. Starting in Windows 10, next major update,
|
||||
the value 0 only takes affect on Azure Active Directory joined devices.
|
||||
Windows will attempt to silently enable BitLocker for value 0.
|
||||
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>110</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/AllowWarningForOtherDiskEncryption</LocURI>
|
||||
</Target>
|
||||
<Meta>
|
||||
<Format xmlns="syncml:metinf">int</Format>
|
||||
</Meta>
|
||||
<Data>0</Data>
|
||||
</Item>
|
||||
</Replace>
|
||||
</Description>
|
||||
<DFFormat>
|
||||
<int />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<ZeroOrOne />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Dynamic />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:SupportedValues AllowedValues="0,1">
|
||||
<MSFT:SupportedValue value="0" description="Disables the warning prompt. Starting in Windows 10, next major update, the value 0 only takes affect on Azure Active Directory joined devices. Windows will attempt to silently enable BitLocker for value 0."/>
|
||||
<MSFT:SupportedValue value="1" description="Default when policy is not set."/>
|
||||
</MSFT:SupportedValues>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
<NodeName>AllowStandardUserEncryption</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Add />
|
||||
<Delete />
|
||||
<Get />
|
||||
<Replace />
|
||||
</AccessType>
|
||||
<Description>Allows Admin to enforce "RequireDeviceEncryption" policy for scenarios where policy is pushed while current logged on user is non-admin/standard user.
|
||||
"AllowStandardUserEncryption" policy is tied to "AllowWarningForOtherDiskEncryption" policy being set to "0", i.e, Silent encryption is enforced.
|
||||
If "AllowWarningForOtherDiskEncryption" is not set, or is set to "1", "RequireDeviceEncryption" policy will not try to encrypt drive(s) if a standard user
|
||||
is the current logged on user in the system.
|
||||
|
||||
The expected values for this policy are:
|
||||
|
||||
1 = "RequireDeviceEncryption" policy will try to enable encryption on all fixed drives even if a current logged in user is standard user.
|
||||
0 = This is the default, when the policy is not set. If current logged on user is a standard user, "RequireDeviceEncryption" policy
|
||||
will not try to enable encryption on any drive.
|
||||
|
||||
If you want to disable this policy use the following SyncML:
|
||||
<Replace>
|
||||
<CmdID>111</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/AllowStandardUserEncryption</LocURI>
|
||||
</Target>
|
||||
<Meta>
|
||||
<Format xmlns="syncml:metinf">int</Format>
|
||||
</Meta>
|
||||
<Data>0</Data>
|
||||
</Item>
|
||||
</Replace>
|
||||
</Description>
|
||||
<DFFormat>
|
||||
<int />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<ZeroOrOne />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Dynamic />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
<MSFT:SupportedValues AllowedValues="0,1">
|
||||
<MSFT:SupportedValue value="0" description="This is the default when the policy is not set. If current logged on user is a standard user, RequireDeviceEncryption policy
|
||||
will not try to enable encryption on any drive."/>
|
||||
<MSFT:SupportedValue value="1" description="RequireDeviceEncryption policy will try to enable encryption on all fixed drives even if a current logged in user is standard user."/>
|
||||
</MSFT:SupportedValues>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
</Node>
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 21 KiB |
@ -1677,6 +1677,10 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
</ul>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Bitlocker CSP](bitlocker-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new node AllowStandardUserEncryption.</p>
|
||||
</td></tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">[Policy CSP](policy-configuration-service-provider.md)</td>
|
||||
<td style="vertical-align:top"><p>Recent changes:</p>
|
||||
<ul>
|
||||
|
||||
Reference in New Issue
Block a user