mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Fix "find/replace" accident
windows-1...overview.md https://microsoft-ce-csi.acrolinx.cloud/api/v1/checking/scorecards/67bf32c7-d246-49a1-9603-531cf8904857#CORRECTNESS Line 140: Group Policy requires that the you have AD DS and that the Windows 10/11 Enterprise devices (delete "the" between "that" and "you") Line 140: are joined to the your AD DS domain. (delete "the" between "to" and "your") Line 146: The primary App-V components that the you must have are as follows: (delete "the" between "that" and "you") Line 161: client-side components that you you’ll need to download, activate, and install. (delete "you" between "that" and "you'll)
This commit is contained in:
parent
3e7e357962
commit
f51a53dc07
@ -137,13 +137,13 @@ For more information about implementing Device Guard, see:
|
||||
|
||||
### AppLocker management
|
||||
|
||||
You can manage AppLocker in Windows 10 Enterprise by using Group Policy. Group Policy requires that the you have AD DS and that the Windows 10/11 Enterprise devices are joined to the your AD DS domain. You can create AppLocker rules by using Group Policy, and then target those rules to the appropriate devices.
|
||||
You can manage AppLocker in Windows 10 Enterprise by using Group Policy. Group Policy requires that you have AD DS and that the Windows 10/11 Enterprise devices are joined to your AD DS domain. You can create AppLocker rules by using Group Policy, and then target those rules to the appropriate devices.
|
||||
|
||||
For more information about AppLocker management by using Group Policy, see [AppLocker deployment guide](/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-policies-deployment-guide).
|
||||
|
||||
### App-V
|
||||
|
||||
App-V requires an App-V server infrastructure to support App-V clients. The primary App-V components that the you must have are as follows:
|
||||
App-V requires an App-V server infrastructure to support App-V clients. The primary App-V components that you must have are as follows:
|
||||
|
||||
- **App-V server**. The App-V server provides App-V management, virtualized app publishing, app streaming, and reporting services. Each of these services can be run on one server or can be run individually on multiple servers. For example, you could have multiple streaming servers. App-V clients contact App-V servers to determine which apps are published to the user or device, and then run the virtualized app from the server.
|
||||
|
||||
@ -158,7 +158,7 @@ For more information about implementing the App-V server, App-V sequencer, and A
|
||||
- [Deploying the App-V Sequencer and Configuring the Client](/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client)
|
||||
|
||||
### UE-V
|
||||
UE-V requires server- and client-side components that you you’ll need to download, activate, and install. These components include:
|
||||
UE-V requires server- and client-side components that you’ll need to download, activate, and install. These components include:
|
||||
|
||||
- **UE-V service**. The UE-V service (when enabled on devices) monitors registered applications and Windows for any settings changes, then synchronizes those settings between devices.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user