mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-21 17:57:22 +00:00
Merged PR 5662: 2/1 PM Publish
This commit is contained in:
Alma Jenks
commit
94e45040c1
@ -228,6 +228,7 @@
|
||||
#### [RemoteManagement](policy-csp-remotemanagement.md)
|
||||
#### [RemoteProcedureCall](policy-csp-remoteprocedurecall.md)
|
||||
#### [RemoteShell](policy-csp-remoteshell.md)
|
||||
#### [RestrictedGroups](policy-csp-restrictedgroups.md)
|
||||
#### [Search](policy-csp-search.md)
|
||||
#### [Security](policy-csp-security.md)
|
||||
#### [Settings](policy-csp-settings.md)
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 14 KiB |
@ -1455,6 +1455,7 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
<li>LocalPoliciesSecurityOptions/SystemObjects_RequireCaseInsensitivityForNonWindowsSubsystems</li>
|
||||
<li>LocalPoliciesSecurityOptions/UserAccountControl_DetectApplicationInstallationsAndPromptForElevation</li>
|
||||
<li>LocalPoliciesSecurityOptions/UserAccountControl_UseAdminApprovalMode</li>
|
||||
<li>RestrictedGroups/ConfigureGroupMembership</li>
|
||||
<li>Search/AllowCortanaInAAD</li>
|
||||
<li>Search/DoNotUseWebResults</li>
|
||||
<li>Security/ConfigureWindowsPasswords</li>
|
||||
@ -1516,6 +1517,16 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
|
||||
<td style="vertical-align:top"><p>Updated the description for AllowWarningForOtherDiskEncryption to describe changes added in Windows 10, next major update.</p>
|
||||
</td></tr>
|
||||
<tr class="odd">
|
||||
<td style="vertical-align:top">[RemoteWipe CSP](remotewipe-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added the following nodes in Windows 10, next major update:</p>
|
||||
<ul>
|
||||
<li>AutomaticRedeployment</li>
|
||||
<li>doAutomaticRedeployment</li>
|
||||
<li>LastError</li>
|
||||
<li>Status</li>
|
||||
</ul>
|
||||
</td></tr>
|
||||
<tr class="odd">
|
||||
<td style="vertical-align:top">[Defender CSP](defender-csp.md)</td>
|
||||
<td style="vertical-align:top"><p>Added new node (OfflineScan) in Windows 10, next major update.</p>
|
||||
</td></tr>
|
||||
|
||||
@ -2487,6 +2487,13 @@ The following diagram shows the Policy configuration service provider in tree fo
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
### RestrictedGroups policies
|
||||
|
||||
<dd>
|
||||
<a href="policy-csp-restrictedgroups.md#restrictedgroups-configuregroupmembership">RestrictedGroups/ConfigureGroupMembership</a>
|
||||
</dd>
|
||||
|
||||
|
||||
### Search policies
|
||||
|
||||
<dl>
|
||||
|
||||
96
windows/client-management/mdm/policy-csp-restrictedgroups.md
Normal file
96
windows/client-management/mdm/policy-csp-restrictedgroups.md
Normal file
@ -0,0 +1,96 @@
|
||||
---
|
||||
title: Policy CSP - RestrictedGroups
|
||||
description: Policy CSP - RestrictedGroups
|
||||
ms.author: maricia
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: nickbrower
|
||||
ms.date: 01/12/2018
|
||||
---
|
||||
|
||||
# Policy CSP - RestrictedGroups
|
||||
|
||||
> [!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.
|
||||
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--StartPolicies-->
|
||||
## RestrictedGroups policies
|
||||
|
||||
<dl>
|
||||
<dd>
|
||||
<a href="policy-csp-restrictedgroups.md#restrictedgroups-configuregroupmembership" id="restrictedgroups-configuregroupmembership">RestrictedGroups/ConfigureGroupMembership</a>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
<hr/>
|
||||
<!--StartPolicy-->
|
||||
<a href="" id="restrictedgroups-configuregroupmembership"></a>**RestrictedGroups/ConfigureGroupMembership**
|
||||
|
||||
<!--StartSKU-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
<th>Mobile Enterprise</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>4</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>4</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>4</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>4</sup></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<!--EndSKU-->
|
||||
<!--StartScope-->
|
||||
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||
|
||||
> [!div class = "checklist"]
|
||||
> * Device
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--EndScope-->
|
||||
<!--StartDescription-->
|
||||
This security setting allows an administrator to define the members of a security-sensitive (restricted) group. When a Restricted Groups Policy is enforced, any current member of a restricted group that is not on the Members list is removed. Any user on the Members list who is not currently a member of the restricted group is added. You can use Restricted Groups policy to control group membership.
|
||||
|
||||
> [!Note]
|
||||
> This policy is only scoped to the Administrators group at this time.
|
||||
|
||||
Using the policy, you can specify what members are part of a group. Any members that are not specified in the policy are removed during configuration or refresh. For example, you can create a Restricted Groups policy to only allow specified users (for example, Alice and John) to be members of the Administrators group. When policy is refreshed, only Alice and John will remain as members of the Administrators group.
|
||||
|
||||
> [!Note]
|
||||
> If a Restricted Groups policy is applied, any current member not on the Restricted Groups policy members list is removed. This can include default members, such as administrators. Restricted Groups should be used primarily to configure membership of local groups on workstation or member servers. An empty Members list means that the restricted group has no members.
|
||||
|
||||
<!--EndDescription-->
|
||||
<!--SupportedValues-->
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--Example-->
|
||||
|
||||
<!--/Example-->
|
||||
<!--Validation-->
|
||||
|
||||
<!--/Validation-->
|
||||
<!--EndPolicy-->
|
||||
<hr/>
|
||||
|
||||
Footnote:
|
||||
|
||||
- 1 - Added in Windows 10, version 1607.
|
||||
- 2 - Added in Windows 10, version 1703.
|
||||
- 3 - Added in Windows 10, version 1709.
|
||||
|
||||
<!--EndPolicies-->
|
||||
|
||||
@ -7,12 +7,15 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: nickbrower
|
||||
ms.date: 11/13/2017
|
||||
ms.date: 01/29/2018
|
||||
---
|
||||
|
||||
# RemoteWipe 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 RemoteWipe configuration service provider can be used by mobile operators DM server or enterprise management server to remotely wipe a device. The RemoteWipe configuration service provider can make the data stored in memory and hard disks difficult to recover if the device is remotely wiped after being lost or stolen.
|
||||
|
||||
The following diagram shows the RemoteWipe configuration service provider management object in tree format as used by both OMA DM and OMA Client Provisioning. Enterprise IT Professionals can update these settings by using the Exchange Server.
|
||||
@ -45,14 +48,27 @@ Supported operation is Exec.
|
||||
<a href="" id="doWipePersistUserData"></a>**doWipePersistUserData**
|
||||
Added in Windows 10, version 1709. Exec on this node will perform a remote reset on the device and persist user accounts and data. The return status code shows whether the device accepted the Exec command.
|
||||
|
||||
## The Remote Wipe Process
|
||||
<a href="" id="automaticredeployment"></a>**AutomaticRedeployment**
|
||||
Added in Windows 10, next major update. Node for the Automatic Redeployment operation.
|
||||
|
||||
<a href="" id="doautomaticredeployment"></a>**AutomaticRedeployment/doAutomaticRedeployment**
|
||||
Added in Windows 10, next major update. Exec on this node triggers Automatic Redeployment operation. This works like PC Reset, similar to other existing nodes in this RemoteWipe CSP, except that it keeps the device enrolled in Azure AD and MDM, keeps Wi-Fi profiles, and a few other settings like region, language, keyboard.
|
||||
|
||||
The remote wipe command is sent as an XML provisioning file to the device. Since the RemoteWipe Configuration Service Provider uses OMA DM and WAP, authentication between client and server and delivery of the XML provisioning file is handled by provisioning.
|
||||
<a href="" id="lasterror"></a>**AutomaticRedeployment/LastError**
|
||||
Added in Windows 10, next major update. Error value, if any, associated with Automatic Redeployment operation (typically an HRESULT).
|
||||
|
||||
In Windows 10 Mobile, the remote wipe command is implemented on the device by using the **ResetPhone** function. On the desktop, the remote wipe triggers the **Reset this PC** functionality with the **Remove everything** option.
|
||||
<a href="" id="status"></a>**AutomaticRedeployment/Status**
|
||||
Added in Windows 10, next major update. Status value indicating current state of an Automatic Redeployment operation.
|
||||
|
||||
> **Note** On the desktop, the remote wipe effectively performs a factory reset and the PC does not retain any information about the command once the wipe completes. Any response from the device about the actual status or result of the command may be inconsistent and unreliable because the MDM information has been removed.
|
||||
Supported values:
|
||||
|
||||
- 0: Never run (not started). The default state.
|
||||
- 1: Complete.
|
||||
- 10: Reset has been scheduled.
|
||||
- 20: Reset is scheduled and waiting for a reboot.
|
||||
- 30: Failed during CSP Execute ("Exec" in SyncML).
|
||||
- 40: Failed: power requirements not met.
|
||||
- 50: Failed: reset internals failed during reset attempt.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: nickbrower
|
||||
ms.date: 12/05/2017
|
||||
ms.date: 01/29/2018
|
||||
---
|
||||
|
||||
# RemoteWipe DDF file
|
||||
@ -17,7 +17,7 @@ This topic shows the OMA DM device description framework (DDF) for the **RemoteW
|
||||
|
||||
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 DDF for Windows 10, version 1709.
|
||||
The XML below is the DDF for Windows 10, next major update.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
@ -43,7 +43,7 @@ The XML below is the DDF for Windows 10, version 1709.
|
||||
<Permanent />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<DDFName></DDFName>
|
||||
<MIME>com.microsoft/1.1/MDM/RemoteWipe</MIME>
|
||||
</DFType>
|
||||
<Description>The root node for remote wipe function.</Description>
|
||||
</DFProperties>
|
||||
@ -131,8 +131,94 @@ The XML below is the DDF for Windows 10, version 1709.
|
||||
<Description>Exec on this node will perform a remote reset on the device and persist user accounts and data. The return status code shows whether the device accepted the Exec command.</Description>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
<NodeName>AutomaticRedeployment</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
</AccessType>
|
||||
<DFFormat>
|
||||
<node />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Permanent />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<DDFName></DDFName>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
<Node>
|
||||
<NodeName>doAutomaticRedeployment</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
<Exec />
|
||||
</AccessType>
|
||||
<DFFormat>
|
||||
<chr />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Permanent />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
<NodeName>LastError</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
</AccessType>
|
||||
<DefaultValue>0</DefaultValue>
|
||||
<Description>Error value, if any, associated with Automatic Redeployment operation (typically an HRESULT).</Description>
|
||||
<DFFormat>
|
||||
<int />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Permanent />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
<Node>
|
||||
<NodeName>Status</NodeName>
|
||||
<DFProperties>
|
||||
<AccessType>
|
||||
<Get />
|
||||
</AccessType>
|
||||
<DefaultValue>0</DefaultValue>
|
||||
<Description>Status value indicating current state of an Automatic Redeployment operation. 0: Never run (not started). The default state. 1: Complete. 10: Reset has been scheduled. 20: Reset is scheduled and waiting for a reboot. 30: Failed during CSP Execute ("Exec" in SyncML). 40: Failed: power requirements not met. 50: Failed: reset internals failed during reset attempt.</Description>
|
||||
<DFFormat>
|
||||
<int />
|
||||
</DFFormat>
|
||||
<Occurrence>
|
||||
<One />
|
||||
</Occurrence>
|
||||
<Scope>
|
||||
<Permanent />
|
||||
</Scope>
|
||||
<DFType>
|
||||
<MIME>text/plain</MIME>
|
||||
</DFType>
|
||||
</DFProperties>
|
||||
</Node>
|
||||
</Node>
|
||||
</Node>
|
||||
</MgmtTree>
|
||||
|
||||
```
|
||||
|
||||
## Related topics
|
||||
|
||||
@ -47,9 +47,7 @@ You must start this app from the **Settings** panel.
|
||||
|
||||
2. Under **Diagnostic data**, select the **Diagnostic Data Viewer** button.
|
||||
|
||||
|
||||
|
||||
f -OR-
|
||||
<br><br>-OR-<br><br>
|
||||
|
||||
Go to **Start** and search for _Diagnostic Data Viewer_.
|
||||
|
||||
@ -98,11 +96,8 @@ When you're done reviewing your diagnostic data, you should turn of data viewing
|
||||
You can review additional Windows Error Reporting diagnostic data in the **View problem reports** tool. This tool provides you with a summary of various crash reports that are sent to Microsoft as part of Windows Error Reporting. We use this data to find and fix specific issues that are hard to replicate and to improve the Windows operating system.
|
||||
|
||||
**To view your Windows Error Reporting diagnostic data**
|
||||
1. Go to **Start**, select **Control Panel** > **All Control Panel Items** > **Security and Maintenance** > **Problem Reports**.
|
||||
|
||||
- OR -
|
||||
|
||||
Go to **Start** and search for _Problem Reports_.
|
||||
1. Go to **Start**, select **Control Panel** > **All Control Panel Items** > **Security and Maintenance** > **Problem Reports**.<br><br>-OR-<br><br>
|
||||
Go to **Start** and search for _Problem Reports_.
|
||||
|
||||
The **Review problem reports** tool opens, showing you your Windows Error Reporting reports, along with a status about whether it was sent to Microsoft.
|
||||
|
||||
|
||||
BIN
windows/deployment/images/event.PNG
Normal file
BIN
windows/deployment/images/event.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 66 KiB After Width: | Height: | Size: 77 KiB |
@ -59,7 +59,8 @@ These phases are explained in greater detail [below](#the-windows-10-upgrade-pro
|
||||
If the computer successfully boots into Windows PE, but you are not able to browse the system drive on the computer, it is possible that non-Microsoft disk encryption software is blocking your ability to perform a Windows 10 upgrade. Update or temporarily remove the disk encryption.
|
||||
|
||||
3. **First boot phase**: Boot failures in this phase are relatively rare, and almost exclusively caused by device drivers. Disconnect all peripheral devices except for the mouse, keyboard, and display. Obtain and install updated device drivers, then retry the upgrade.
|
||||
4. **Second boot phase**: In this phase, the system is running under the target OS with new drivers. Boot failures are most commonly due to anti-virus software or filter drivers. Disconnect all peripheral devices except for the mouse, keyboard, and display. Obtain and install updated device drivers, then retry the upgrade.
|
||||
|
||||
4. **Second boot phase**: In this phase, the system is running under the target OS with new drivers. Boot failures are most commonly due to anti-virus software or filter drivers. Disconnect all peripheral devices except for the mouse, keyboard, and display. Obtain and install updated device drivers, temporarily uninstall anti-virus software, then retry the upgrade.
|
||||
|
||||
If the general troubleshooting techniques described above or the [quick fixes](#quick-fixes) detailed below do not resolve your issue, you can attempt to analyze [log files](#log-files) and interpret [upgrade error codes](#upgrade-error-codes). You can also [Submit Windows 10 upgrade errors using Feedback Hub](submit-errors.md) so that Microsoft can diagnose your issue.
|
||||
|
||||
@ -67,9 +68,7 @@ If the general troubleshooting techniques described above or the [quick fixes](#
|
||||
|
||||
The **Windows Setup** application is used to upgrade a computer to Windows 10, or to perform a clean installation. Windows Setup starts and restarts the computer, gathers information, copies files, and creates or adjusts configuration settings.
|
||||
|
||||
When performing an operating system upgrade, Windows Setup uses the following phases. A reboot occurs between each of the phases.
|
||||
|
||||
The user interface will be the same during the Safe OS phase, the first boot phase, and the beginning of the second boot phase. Percent progress is displayed and will advance as you move through each phase, reaching 100% at the end of the second boot phase.
|
||||
When performing an operating system upgrade, Windows Setup uses phases described below. A reboot occurs between each of the phases. After the first reboot, the user interface will remain the same until the upgrade is completed. Percent progress is displayed and will advance as you move through each phase, reaching 100% at the end of the second boot phase.
|
||||
|
||||
1. **Downlevel phase**: The downlevel phase is run within the previous operating system. Windows files are copied and installation components are gathered.
|
||||
|
||||
@ -176,7 +175,7 @@ Some result codes are self-explanatory, whereas others are more generic and requ
|
||||
|
||||
### Extend codes
|
||||
|
||||
>Important: Extend codes reflect the current Windows 10 upgrade process, and might change in future releases of Windows 10. The codes discussed in this section apply to Windows 10 version 1607, also known as the Anniversary Update.
|
||||
>**Important**: Extend codes reflect the current Windows 10 upgrade process, and might change in future releases of Windows 10. The codes discussed in this section apply to Windows 10 version 1607, also known as the Anniversary Update.
|
||||
|
||||
Extend codes can be matched to the phase and operation when an error occurred. To match an extend code to the phase and operation:
|
||||
|
||||
@ -270,7 +269,7 @@ To use Event Viewer:
|
||||
Note: For legacy operating systems, the Event Name was WinSetupDiag01.
|
||||
|
||||
Ten parameters are listed in the event:
|
||||
|
||||
<br>
|
||||
<table border="0">
|
||||
<tr><td>P1: The Setup Scenario (1=Media,5=WindowsUpdate,7=Media Creation Tool)</td></tr>
|
||||
<tr><td>P2: Setup Mode (x=default,1=Downlevel,5=Rollback)</td></tr>
|
||||
@ -284,8 +283,9 @@ Ten parameters are listed in the event:
|
||||
<tr><td>P10: New OS branch (Ex: rs3_release}</td></tr>
|
||||
</table>
|
||||
|
||||
The event will also contain links to log files that can be used to perform a detailed diagnosis of the error.
|
||||
The event will also contain links to log files that can be used to perform a detailed diagnosis of the error. An example of this event from a successful upgrade is shown below.
|
||||
|
||||
|
||||
|
||||
## Log files
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ The Feedback Hub will open.
|
||||
|
||||
- Under **Tell us about it**, and then under **Summarize your issue**, type **Upgrade failing**.
|
||||
- Under **Give us more detail**, provide additional information about the failed upgrade, such as:
|
||||
- When did the failures occurs?
|
||||
- When did the failure occur?
|
||||
- Were there any reboots?
|
||||
- How many times did the system reboot?
|
||||
- How did the upgrade fail?
|
||||
|
||||
@ -182,8 +182,9 @@ Table 1: Cross compatibility for Windows 10, Windows 8.1, Windows 8, and Window
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
### Encrypting volumes using the manage-bde command line interface
|
||||
|
||||
|
||||
## <a href="" id="bkmk-dep3"></a>Encrypting volumes using the manage-bde command line interface
|
||||
|
||||
Manage-bde is a command-line utility that can be used for scripting BitLocker operations. Manage-bde offers additional options not displayed in the BitLocker control panel. For a complete list of the options, see [Manage-bde](http://technet.microsoft.com/library/ff829849.aspx).
|
||||
Manage-bde offers a multitude of wider options for configuring BitLocker. This means that using the command syntax may require care and possibly later customization by the user. For example, using just the `manage-bde -on` command on a data volume will fully encrypt the volume without any authenticating protectors. A volume encrypted in this manner still requires user interaction to turn on BitLocker protection, even though the command successfully completed because an authentication method needs to be added to the volume for it to be fully protected.
|
||||
@ -240,9 +241,8 @@ A common protector for a data volume is the password protector. In the example b
|
||||
manage-bde -protectors -add -pw C:
|
||||
manage-bde -on C:
|
||||
```
|
||||
## <a href="" id="bkmk-dep3"></a>Using manage-bde to encrypt volumes with BitLocker
|
||||
|
||||
### Encrypting volumes using the BitLocker Windows PowerShell cmdlets
|
||||
## <a href="" id="bkmk-dep4"></a>Encrypting volumes using the BitLocker Windows PowerShell cmdlets
|
||||
|
||||
Windows PowerShell cmdlets provide an alternative way to work with BitLocker. Using Windows PowerShell's scripting capabilities, administrators can integrate BitLocker options into existing scripts with ease. The list below displays the available BitLocker cmdlets.
|
||||
<table>
|
||||
@ -442,9 +442,7 @@ Add-BitLockerKeyProtector C: -ADAccountOrGroupProtector -ADAccountOrGroup "<SID>
|
||||
```
|
||||
> **Note:** Active Directory-based protectors are normally used to unlock Failover Cluster enabled volumes.
|
||||
|
||||
## <a href="" id="bkmk-dep4"></a>Using PowerShell to encrypt volumes with BitLocker
|
||||
|
||||
### Checking BitLocker status
|
||||
## <a href="" id="bkmk-dep5"></a> Checking BitLocker status
|
||||
|
||||
To check the BitLocker status of a particular volume, administrators can look at the status of the drive in the BitLocker control panel applet, Windows Explorer, manage-bde command line tool, or Windows PowerShell cmdlets. Each option offers different levels of detail and ease of use. We will look at each of the available methods in the following section.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user