mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Fix smart quotes in code samples
This commit is contained in:
Michaël Hompus
parent
b11be10946
commit
fc717a791f
@ -78,7 +78,7 @@ After your operating system is installed on the target computer, you need to cop
|
||||
|
||||
4. Rename the newly created item to *Copy Files* and move it up to the top of the **Postinstall** folder.
|
||||
|
||||
5. In the **Command Line** box enter the following text, `xcopy “%DEPLOYROOT%\$OEM$\$1” “%OSDisk%\” /yqe`.
|
||||
5. In the **Command Line** box enter the following text, `xcopy "%DEPLOYROOT%\$OEM$\$1" "%OSDisk%\" /yqe`.
|
||||
|
||||
6. Click the **Apply** button to save your changes.
|
||||
|
||||
|
||||
@ -99,7 +99,7 @@ If you have a single-forest on-premises deployment with Microsoft Exchange 2013
|
||||
8. OPTIONAL: You can also allow your Surface Hub to make and receive public switched telephone network (PSTN) phone calls by enabling Enterprise Voice for your account. Enterprise Voice isn't a requirement for Surface Hub, but if you want PSTN dialing functionality for the Surface Hub client, here's how to enable it:
|
||||
|
||||
```PowerShell
|
||||
Set-CsMeetingRoom -Identity HUB01 -DomainController DC-ND-001.contoso.com -LineURI “tel:+14255550555;ext=50555" -EnterpriseVoiceEnabled $true
|
||||
Set-CsMeetingRoom -Identity HUB01 -DomainController DC-ND-001.contoso.com -LineURI "tel:+14255550555;ext=50555" -EnterpriseVoiceEnabled $true
|
||||
```
|
||||
|
||||
Again, you need to replace the provided domain controller and phone number examples with your own information. The parameter value `$true` stays the same.
|
||||
|
||||
@ -65,7 +65,7 @@ If you deployed Skype for Business Cloud PBX with one of the hybrid voice option
|
||||
If you haven’t created a compatible policy yet, use the following cmdlet (this one creates a policy called "Surface Hubs"). After it’s created, you can apply the same policy to other device accounts.
|
||||
|
||||
```
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name "SurfaceHubs" -PasswordEnabled $false
|
||||
```
|
||||
|
||||
After you have a compatible policy, then you will need to apply the policy to the device account. However, policies can only be applied to user accounts and not resource mailboxes. Run the following cmdlets to convert the mailbox into a user type, apply the policy, and then convert it back into a mailbox (you may need to re-enable the account and set the password again).
|
||||
|
||||
@ -50,7 +50,7 @@ Deployment of Microsoft Surface UEFI Manager is a typical application deployment
|
||||
|
||||
The command to install Microsoft Surface UEFI Manager is:
|
||||
|
||||
`msiexec /i “SurfaceUEFIManagerSetup.msi” /q`
|
||||
`msiexec /i "SurfaceUEFIManagerSetup.msi" /q`
|
||||
|
||||
The command to uninstall Microsoft Surface UEFI Manager is:
|
||||
|
||||
@ -334,11 +334,11 @@ After your scripts are prepared to configure and enable SEMM on the client devic
|
||||
|
||||
The SEMM Configuration Manager scripts will be added to Configuration Manager as a script application. The command to install SEMM with ConfigureSEMM.ps1 is:
|
||||
|
||||
`Powershell.exe -file “.\ConfigureSEMM.ps1”`
|
||||
`Powershell.exe -file ".\ConfigureSEMM.ps1"`
|
||||
|
||||
The command to uninstall SEMM with ResetSEMM.ps1 is:
|
||||
|
||||
`Powershell.exe -file “.\ResetSEMM.ps1”`
|
||||
`Powershell.exe -file ".\ResetSEMM.ps1"`
|
||||
|
||||
To add the SEMM Configuration Manager scripts to Configuration Manager as an application, use the following process:
|
||||
|
||||
|
||||
@ -48,14 +48,14 @@ process](https://docs.microsoft.com/windows/deployment/windows-10-deployment-sce
|
||||
|
||||
Copy
|
||||
```
|
||||
<settings pass=”offlineServicing”>
|
||||
<component name=”Microsoft-Windows-CodeIntegrity”
|
||||
processorArchitecture=”amd64”
|
||||
publicKeyToken=”31bf3856ad364e35”
|
||||
language=”neutral”
|
||||
versionScope=”nonSxS”
|
||||
xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State”
|
||||
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
|
||||
<settings pass="offlineServicing">
|
||||
<component name="Microsoft-Windows-CodeIntegrity"
|
||||
processorArchitecture="amd64"
|
||||
publicKeyToken="31bf3856ad364e35"
|
||||
language="neutral"
|
||||
versionScope="nonSxS"
|
||||
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
|
||||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
|
||||
<SkuPolicyRequired>1</SkuPolicyRequired>
|
||||
</component>
|
||||
</settings>
|
||||
@ -94,14 +94,14 @@ Education customers who wish to avoid the additional overhead associated with Wi
|
||||
|
||||
Copy
|
||||
```
|
||||
<settings pass=”offlineServicing”>
|
||||
<component name=”Microsoft-Windows-CodeIntegrity”
|
||||
processorArchitecture=”amd64”
|
||||
publicKeyToken=”31bf3856ad364e35”
|
||||
language=”neutral”
|
||||
versionScope=”nonSxS”
|
||||
xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State”
|
||||
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
|
||||
<settings pass="offlineServicing">
|
||||
<component name="Microsoft-Windows-CodeIntegrity"
|
||||
processorArchitecture="amd64"
|
||||
publicKeyToken="31bf3856ad364e35"
|
||||
language="neutral"
|
||||
versionScope="nonSxS"
|
||||
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
|
||||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
|
||||
<SkuPolicyRequired>1</SkuPolicyRequired>
|
||||
</component>
|
||||
</settings>
|
||||
|
||||
@ -190,7 +190,7 @@ Set-AssignedAccess -AppUserModelId Microsoft.Windows.SecureAssessmentBrowser_cw5
|
||||
12. Create a new **Action**.
|
||||
13. Configure the action to **Start a program**.
|
||||
14. In the **Program/script** field, enter **powershell**.
|
||||
15. In the **Add arguments** field, enter **-file “<path to powershell script>”**.
|
||||
15. In the **Add arguments** field, enter **-file "<path to powershell script>"**.
|
||||
16. Click **OK**.
|
||||
17. Navigate to the **Triggers** tab and create a new trigger.
|
||||
18. Specify the trigger to be **On a schedule**.
|
||||
|
||||
@ -24,7 +24,7 @@ When you deploy Application Virtualization by using an electronic software distr
|
||||
|
||||
3. Run the following command on the computer:
|
||||
|
||||
`Msiexec.exe /I “packagename.msi” /q`
|
||||
`Msiexec.exe /I "packagename.msi" /q`
|
||||
|
||||
**To publish a package using Windows Installer and the package manifest**
|
||||
|
||||
@ -32,7 +32,7 @@ When you deploy Application Virtualization by using an electronic software distr
|
||||
|
||||
2. Run the following command on each user’s computer:
|
||||
|
||||
`Msiexec.exe /I “\\pathtomsi\packagename.msi” MODE=STREAMING OVERRIDEURL=”\\\\server\\share\\package.sft” LOAD=TRUE /q`
|
||||
`Msiexec.exe /I "\\pathtomsi\packagename.msi" MODE=STREAMING OVERRIDEURL="\\\\server\\share\\package.sft" LOAD=TRUE /q`
|
||||
|
||||
**Important**
|
||||
For OVERRIDEURL all backslash characters must be escaped using a preceding backslash, or the OVERRIDEURL path will not be parsed correctly. Also, properties and values must be entered as uppercase except where the value is a path to a file.
|
||||
|
||||
@ -31,7 +31,7 @@ Use the following procedure to create a virtual application by using the command
|
||||
|
||||
3. At the command prompt, type the following command, replacing the text in quotation marks with your values:
|
||||
|
||||
`SFTSequencer /INSTALLPACKAGE:“pathtoMSI” /INSTALLPATH:“pathtopackageroot” /OUTPUTFILE:“pathtodestinationSPRJ”`
|
||||
`SFTSequencer /INSTALLPACKAGE:"pathtoMSI" /INSTALLPATH:"pathtopackageroot" /OUTPUTFILE:"pathtodestinationSPRJ"`
|
||||
|
||||
**Note**
|
||||
You can specify additional parameters by using the command line, depending on the complexity of the application you are sequencing. For a complete list of parameters that are available for use with the App-V Sequencer, see [Sequencer Command-Line Parameters](sequencer-command-line-parameters.md).
|
||||
|
||||
@ -31,7 +31,7 @@ Use the following procedure to create a virtual application by using the command
|
||||
|
||||
3. At the command prompt, type the following command, replacing the text in quotation marks with your values:
|
||||
|
||||
`SFTSequencer /INSTALLPACKAGE:“pathtoMSI” /INSTALLPATH:“pathtopackageroot” /OUTPUTFILE:“pathtodestinationSPRJ”`
|
||||
`SFTSequencer /INSTALLPACKAGE:"pathtoMSI" /INSTALLPATH:"pathtopackageroot" /OUTPUTFILE:"pathtodestinationSPRJ"`
|
||||
|
||||
**Note**
|
||||
You can specify additional parameters by using the command line, depending on the complexity of the application you are sequencing. For a complete list of parameters that are available for use with the App-V Sequencer, see [Application Virtualization Sequencer Command Line](application-virtualization-sequencer-command-line.md).
|
||||
|
||||
@ -24,7 +24,7 @@ Use the following procedure to upgrade a virtual application by using a command
|
||||
|
||||
3. At the command prompt, type the following command, replacing the text in quotation marks with your values:
|
||||
|
||||
`SFTSequencer /UPGRADE:“pathtosourceSPRJ” /INSTALLPACKAGE:“pathtoUpgradeInstaller” /DECODEPATH:”pathtodecodefolder” /OUTPUTFILE:“pathtodestinationSPRJ”`
|
||||
`SFTSequencer /UPGRADE:"pathtosourceSPRJ" /INSTALLPACKAGE:"pathtoUpgradeInstaller" /DECODEPATH:"pathtodecodefolder" /OUTPUTFILE:"pathtodestinationSPRJ"`
|
||||
|
||||
**Note**
|
||||
You can specify additional parameters by using the command line, depending on the complexity of the application you are upgrading. For a complete list of parameters that are available for use with the App-V Sequencer, see [Command-Line Parameters](command-line-parameters.md).
|
||||
|
||||
@ -24,7 +24,7 @@ Use the following procedure to upgrade a virtual application by using a command
|
||||
|
||||
3. At the command prompt, type the following command, replacing the text in quotation marks with your values:
|
||||
|
||||
`SFTSequencer /UPGRADE:“pathtosourceSPRJ” /INSTALLPACKAGE:“pathtoUpgradeInstaller” /DECODEPATH:”pathtodecodefolder” /OUTPUTFILE:“pathtodestinationSPRJ”`
|
||||
`SFTSequencer /UPGRADE:"pathtosourceSPRJ" /INSTALLPACKAGE:"pathtoUpgradeInstaller" /DECODEPATH:"pathtodecodefolder" /OUTPUTFILE:"pathtodestinationSPRJ"`
|
||||
|
||||
**Note**
|
||||
You can specify additional parameters by using the command line, depending on the complexity of the application you are upgrading. For a complete list of parameters that are available for use with the App-V Sequencer, see [Sequencer Command-Line Parameters](sequencer-command-line-parameters.md).
|
||||
|
||||
@ -145,13 +145,13 @@ Use Windows Explorer to move the **MBAM Compliance Status Database Data.bak** fi
|
||||
To automate this procedure, you can use Windows PowerShell to run a command that is similar to the following:
|
||||
|
||||
```powershell
|
||||
Copy-Item “Z:\MBAM Recovery Database Data.bak”
|
||||
Copy-Item "Z:\MBAM Recovery Database Data.bak"
|
||||
\\$SERVERNAME$\$DESTINATIONSHARE$
|
||||
|
||||
Copy-Item “Z:\SQLServerInstanceCertificateFile”
|
||||
Copy-Item "Z:\SQLServerInstanceCertificateFile"
|
||||
\\$SERVERNAME$\$DESTINATIONSHARE$
|
||||
|
||||
Copy-Item “Z:\SQLServerInstanceCertificateFilePrivateKey”
|
||||
Copy-Item "Z:\SQLServerInstanceCertificateFilePrivateKey"
|
||||
\\$SERVERNAME$\$DESTINATIONSHARE$
|
||||
|
||||
```
|
||||
@ -253,16 +253,16 @@ Use the information in the following table to replace the values in the code exa
|
||||
Set-WebConfigurationProperty
|
||||
'connectionStrings/add[@name="KeyRecoveryConnectionString"]' -PSPath
|
||||
"IIS:\sites\Microsoft Bitlocker Administration and
|
||||
Monitoring\MBAMAdministrationService" -Name "connectionString" -Value “Data
|
||||
Monitoring\MBAMAdministrationService" -Name "connectionString" -Value "Data
|
||||
Source=$SERVERNAME$\$SQLINSTANCENAME$;Initial Catalog=MBAM Recovery and
|
||||
Hardware;Integrated Security=SSPI;”
|
||||
Hardware;Integrated Security=SSPI;"
|
||||
|
||||
Set-WebConfigurationProperty
|
||||
'connectionStrings/add[\@name="Microsoft.Mbam.RecoveryAndHardwareDataStore.ConnectionString"]'
|
||||
-PSPath "IIS:\sites\Microsoft Bitlocker Administration and
|
||||
Monitoring\MBAMRecoveryAndHardwareService" -Name "connectionString" -Value
|
||||
"Data Source=$SERVERNAME$\$SQLINSTANCENAME$;Initial Catalog=MBAM Recovery
|
||||
and Hardware;Integrated Security=SSPI;”
|
||||
and Hardware;Integrated Security=SSPI;"
|
||||
```
|
||||
|
||||
>[!Note]
|
||||
|
||||
@ -72,7 +72,7 @@ To run the example Windows PowerShell scripts in this topic, you must update the
|
||||
7. To automate this procedure, you can use Windows PowerShell to run a command on the Administration and Monitoring Server that is similar to the following code example.
|
||||
|
||||
``` syntax
|
||||
PS C:\> Set-WebConfigurationProperty '/appSettings/add[@key="Microsoft.Mbam.Reports.Url"]' -PSPath "IIS:\\sites\Microsoft Bitlocker Administration and Monitoring\HelpDesk" -Name "Value" -Value “http://$SERVERNAME$/ReportServer[_$SRSINSTANCENAME$]/Pages/ReportViewer.aspx?/Microsoft+BitLocker+Administration+and+Monitoring/”
|
||||
PS C:\> Set-WebConfigurationProperty '/appSettings/add[@key="Microsoft.Mbam.Reports.Url"]' -PSPath "IIS:\\sites\Microsoft Bitlocker Administration and Monitoring\HelpDesk" -Name "Value" -Value "http://$SERVERNAME$/ReportServer[_$SRSINSTANCENAME$]/Pages/ReportViewer.aspx?/Microsoft+BitLocker+Administration+and+Monitoring/"
|
||||
```
|
||||
|
||||
Using the descriptions in the following table, replace the values in the code example with values that match your environment.
|
||||
|
||||
@ -158,7 +158,7 @@ It might be necessary to change the PowerShell execution policy to allow these s
|
||||
3. Run this command on a machine running the ConfigMgr Admin Console:
|
||||
|
||||
``` syntax
|
||||
C:\Program Files (x86)\Microsoft User Experience Virtualization\ConfigPack\UevAgentPolicyGenerator.exe –Site ABC –CabFilePath “C:\MyCabFiles\UevPolicyItem.cab” –ConfigurationFile “c:\AgentConfiguration.xml”
|
||||
C:\Program Files (x86)\Microsoft User Experience Virtualization\ConfigPack\UevAgentPolicyGenerator.exe –Site ABC –CabFilePath "C:\MyCabFiles\UevPolicyItem.cab" –ConfigurationFile "c:\AgentConfiguration.xml"
|
||||
```
|
||||
|
||||
4. Import the CAB file using ConfigMgr console or PowerShell Import-CMConfigurationItem
|
||||
@ -201,7 +201,7 @@ The result is a baseline CAB file that is ready for import into Configuration Ma
|
||||
3. Add the command and parameters to the .bat file that will generate the baseline. The following example creates a baseline that distributes Notepad and Calculator:
|
||||
|
||||
``` syntax
|
||||
C:\Program Files (x86)\Microsoft User Experience Virtualization\ConfigPack\UevTemplateBaselineGenerator.exe –Site “ABC” –TemplateFolder “C:\ProductionUevTemplates” –Register “MicrosoftNotepad.xml, MicrosoftCalculator.xml” –CabFilePath “C:\MyCabFiles\UevTemplateBaseline.cab”
|
||||
C:\Program Files (x86)\Microsoft User Experience Virtualization\ConfigPack\UevTemplateBaselineGenerator.exe –Site "ABC" –TemplateFolder "C:\ProductionUevTemplates" –Register "MicrosoftNotepad.xml, MicrosoftCalculator.xml" –CabFilePath "C:\MyCabFiles\UevTemplateBaseline.cab"
|
||||
```
|
||||
|
||||
4. Run the .bat file to create UevTemplateBaseline.cab ready for import into Configuration Manager.
|
||||
|
||||
@ -21,7 +21,7 @@ Enter the **Get-AppvClientPackage** cmdlet to return a list of packages entitled
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Get-AppvClientPackage –Name “ContosoApplication” -Version 2
|
||||
Get-AppvClientPackage –Name "ContosoApplication" -Version 2
|
||||
```
|
||||
|
||||
## Add a package
|
||||
@ -44,13 +44,13 @@ Use the **Publish-AppvClientPackage** cmdlet to publish a package that has been
|
||||
Enter the cmdlet with the application name to publish it to the user.
|
||||
|
||||
```PowerShell
|
||||
Publish-AppvClientPackage “ContosoApplication”
|
||||
Publish-AppvClientPackage "ContosoApplication"
|
||||
```
|
||||
|
||||
To publish the application globally, just add the *-Global* parameter.
|
||||
|
||||
```Powershell
|
||||
Publish-AppvClientPackage “ContosoApplication” -Global
|
||||
Publish-AppvClientPackage "ContosoApplication" -Global
|
||||
```
|
||||
|
||||
## Publish a package to a specific user
|
||||
@ -70,7 +70,7 @@ To use this parameter:
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Publish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
Publish-AppvClientPackage "ContosoApplication" -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
```
|
||||
|
||||
## Add and publish a package
|
||||
@ -90,7 +90,7 @@ Use the **Unpublish-AppvClientPackage** cmdlet to unpublish a package which has
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Unpublish-AppvClientPackage “ContosoApplication”
|
||||
Unpublish-AppvClientPackage "ContosoApplication"
|
||||
```
|
||||
|
||||
## Unpublish a package for a specific user
|
||||
@ -110,7 +110,7 @@ To use this parameter:
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Unpublish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
Unpublish-AppvClientPackage "ContosoApplication" -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
```
|
||||
|
||||
## Remove an existing package
|
||||
@ -120,7 +120,7 @@ Use the **Remove-AppvClientPackage** cmdlet to remove a package from the compute
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Remove-AppvClientPackage “ContosoApplication”
|
||||
Remove-AppvClientPackage "ContosoApplication"
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
|
||||
@ -45,7 +45,7 @@ This topic explains the following procedures:
|
||||
|
||||
2. Enable the connection group by typing the following command:
|
||||
|
||||
Enable-AppvClientConnectionGroup –name “Financial Applications”
|
||||
Enable-AppvClientConnectionGroup –name "Financial Applications"
|
||||
|
||||
When any virtual applications that are in the member packages are run on the target computer, they will run inside the connection group’s virtual environment and will be available to all the virtual applications in the other packages in the connection group.
|
||||
|
||||
@ -81,11 +81,11 @@ This topic explains the following procedures:
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Enable-AppVClientConnectionGroup</p></td>
|
||||
<td align="left"><p>Enable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
<td align="left"><p>Enable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Disable-AppVClientConnectionGroup</p></td>
|
||||
<td align="left"><p>Disable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
<td align="left"><p>Disable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -25,7 +25,7 @@ Use the following procedure to configure the App-V client configuration.
|
||||
|
||||
`Set-AppVClientConfiguration $config`
|
||||
|
||||
`Set-AppVClientConfiguration –Name1 MyConfig –Name2 “xyz”`
|
||||
`Set-AppVClientConfiguration –Name1 MyConfig –Name2 "xyz"`
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
@ -693,8 +693,8 @@ PATCH https://graph.windows.net/contoso.com/devices/db7ab579-3759-4492-a03f-655c
|
||||
Authorization: Bearer eyJ0eXAiO………
|
||||
Accept: application/json
|
||||
Content-Type: application/json
|
||||
{ “isManaged”:true,
|
||||
“isCompliant”:true
|
||||
{ "isManaged":true,
|
||||
"isCompliant":true
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
@ -71,8 +71,8 @@ The following sample shows an OMA DM first package that contains a generic alert
|
||||
<Data>1226</Data> <!-- generic alert -->
|
||||
<Item>
|
||||
<Meta>
|
||||
<Type xmlns=”syncml:metinfo”> com.microsoft:mdm.unenrollment.userrequest</Type>
|
||||
<Format xmlns= “syncml:metinfo”>int</Format>
|
||||
<Type xmlns="syncml:metinfo"> com.microsoft:mdm.unenrollment.userrequest</Type>
|
||||
<Format xmlns= "syncml:metinfo">int</Format>
|
||||
</Meta>
|
||||
<Data>1</Data>
|
||||
</Item>
|
||||
|
||||
@ -88,8 +88,8 @@ The following Windows PowerShell commands demonstrate how you can call the listA
|
||||
listAumids
|
||||
|
||||
# Get a list of AUMIDs for an account named “CustomerAccount”:
|
||||
listAumids(“CustomerAccount”)
|
||||
listAumids("CustomerAccount")
|
||||
|
||||
# Get a list of AUMIDs for all accounts on the device:
|
||||
listAumids(“allusers”)
|
||||
listAumids("allusers")
|
||||
```
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user