mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into vs-8826977
This commit is contained in:
26
mdop/TOC.md
26
mdop/TOC.md
@ -1,21 +1,21 @@
|
|||||||
# [Microsoft Desktop Optimization Pack](index.md)
|
# [Microsoft Desktop Optimization Pack](index.md)
|
||||||
## [Advanced Group Policy Management](agpm/)
|
## [Advanced Group Policy Management](agpm/index.md)
|
||||||
## [Application Virtualization]()
|
## [Application Virtualization]()
|
||||||
### [Application Virtualization 5](appv-v5/)
|
### [Application Virtualization 5](appv-v5/index.md)
|
||||||
### [Application Virtualization 4](appv-v4/)
|
### [Application Virtualization 4](appv-v4/index.md)
|
||||||
### [SoftGrid Application Virtualization](softgrid-application-virtualization.md)
|
### [SoftGrid Application Virtualization](softgrid-application-virtualization.md)
|
||||||
## [Diagnostics and Recovery Toolset]()
|
## [Diagnostics and Recovery Toolset]()
|
||||||
### [Diagnostics and Recovery Toolset 10](dart-v10/)
|
### [Diagnostics and Recovery Toolset 10](dart-v10/index.md)
|
||||||
### [Diagnostics and Recovery Toolset 8](dart-v8/)
|
### [Diagnostics and Recovery Toolset 8](dart-v8/index.md)
|
||||||
### [Diagnostics and Recovery Toolset 7](dart-v7/)
|
### [Diagnostics and Recovery Toolset 7](dart-v7/index.md)
|
||||||
### [Diagnostics and Recovery Toolset 6.5](dart-v65.md)
|
### [Diagnostics and Recovery Toolset 6.5](dart-v65.md)
|
||||||
## [Microsoft Bitlocker Administration and Monitoring]()
|
## [Microsoft Bitlocker Administration and Monitoring]()
|
||||||
### [Microsoft Bitlocker Administration and Monitoring 2.5](mbam-v25/)
|
### [Microsoft Bitlocker Administration and Monitoring 2.5](mbam-v25/index.md)
|
||||||
### [Microsoft Bitlocker Administration and Monitoring 2](mbam-v2/)
|
### [Microsoft Bitlocker Administration and Monitoring 2](mbam-v2/index.md)
|
||||||
### [Microsoft Bitlocker Administration and Monitoring 1](mbam-v1/)
|
### [Microsoft Bitlocker Administration and Monitoring 1](mbam-v1/index.md)
|
||||||
## [Microsoft Enterprise Desktop Virtualization]()
|
## [Microsoft Enterprise Desktop Virtualization]()
|
||||||
### [Microsoft Enterprise Desktop Virtualization 2](medv-v2/)
|
### [Microsoft Enterprise Desktop Virtualization 2](medv-v2/index.md)
|
||||||
## [User Experience Virtualization]()
|
## [User Experience Virtualization]()
|
||||||
### [User Experience Virtualization 2](uev-v2/)
|
### [User Experience Virtualization 2](uev-v2/index.md)
|
||||||
### [User Experience Virtualization 1](uev-v1/)
|
### [User Experience Virtualization 1](uev-v1/index.md)
|
||||||
## [MDOP Solutions and Scenarios](solutions/)
|
## [MDOP Solutions and Scenarios](solutions/index.md)
|
@ -1,6 +1,6 @@
|
|||||||
# [Windows 10 and Windows 10 Mobile](index.md)
|
# [Windows 10 and Windows 10 Mobile](index.md)
|
||||||
## [What's new in Windows 10](whats-new/)
|
## [What's new in Windows 10](whats-new/index.md)
|
||||||
## [Plan for Windows 10 deployment](plan/)
|
## [Plan for Windows 10 deployment](plan/index.md)
|
||||||
## [Deploy Windows 10](deploy/)
|
## [Deploy Windows 10](deploy/index.md)
|
||||||
## [Keep Windows 10 secure](keep-secure/)
|
## [Keep Windows 10 secure](keep-secure/index.md)
|
||||||
## [Manage and update Windows 10](manage/)
|
## [Manage and update Windows 10](manage/index.md)
|
@ -48,7 +48,7 @@ To help address this security insufficiency, company’s developed data loss pre
|
|||||||
Unfortunately, data loss prevention systems have their own problems. For example, the more detailed the rule set, the more false positives are created, leading employees to believe that the rules slow down their work and need to be bypassed in order to remain productive, potentially leading to data being incorrectly blocked or improperly released. Another major problem is that data loss prevention systems must be widely implemented to be effective. For example, if your company uses a data loss prevention system for email, but not for file shares or document storage, you might find that your data leaks through the unprotected channels. But perhaps the biggest problem with data loss preventions systems is that it provides a jarring experience that interrupts the employees’ natural workflow by blocking some operations (such as sending a message with an attachment that the system tags as sensitive) while allowing others, often according to subtle rules that the employee doesn’t see and can’t understand.
|
Unfortunately, data loss prevention systems have their own problems. For example, the more detailed the rule set, the more false positives are created, leading employees to believe that the rules slow down their work and need to be bypassed in order to remain productive, potentially leading to data being incorrectly blocked or improperly released. Another major problem is that data loss prevention systems must be widely implemented to be effective. For example, if your company uses a data loss prevention system for email, but not for file shares or document storage, you might find that your data leaks through the unprotected channels. But perhaps the biggest problem with data loss preventions systems is that it provides a jarring experience that interrupts the employees’ natural workflow by blocking some operations (such as sending a message with an attachment that the system tags as sensitive) while allowing others, often according to subtle rules that the employee doesn’t see and can’t understand.
|
||||||
|
|
||||||
### Using information rights management systems
|
### Using information rights management systems
|
||||||
To help address the potential data loss prevention system problems, company’s developed information rights management (also known as IRM) systems. Information rights management systems embed protection directly into documents, so that when an employee creates a document, he or she determines what kind of protection to apply. For example, an employee can choose to stop the document from being forwarded, printed, shared outside of the organization, and so on.
|
To help address the potential data loss prevention system problems, companies developed information rights management (also known as IRM) systems. Information rights management systems embed protection directly into documents, so that when an employee creates a document, he or she determines what kind of protection to apply. For example, an employee can choose to stop the document from being forwarded, printed, shared outside of the organization, and so on.
|
||||||
|
|
||||||
After the type of protection is set, the creating app encrypts the document so that only authorized people can open it, and even then, only in compatible apps. After an employee opens the document, the app becomes responsible for enforcing the specified protections. Because protection travels with the document, if an authorized person sends it to an unauthorized person, the unauthorized person won’t be able to read or change it. However, for this to work effectively information rights management systems require you to deploy and set up both a server and client environment. And, because only compatible clients can work with protected documents, an employees’ work might be unexpectedly interrupted if he or she attempts to use a non-compatible app.
|
After the type of protection is set, the creating app encrypts the document so that only authorized people can open it, and even then, only in compatible apps. After an employee opens the document, the app becomes responsible for enforcing the specified protections. Because protection travels with the document, if an authorized person sends it to an unauthorized person, the unauthorized person won’t be able to read or change it. However, for this to work effectively information rights management systems require you to deploy and set up both a server and client environment. And, because only compatible clients can work with protected documents, an employees’ work might be unexpectedly interrupted if he or she attempts to use a non-compatible app.
|
||||||
|
|
||||||
|
@ -270,6 +270,8 @@ Fonts that are included in Windows but that are not stored on the local device c
|
|||||||
|
|
||||||
To turn off font streaming, create a REG\_DWORD registry setting called **DisableFontProviders** in **HKEY\_LOCAL\_MACHINE\\System\\CurrentControlSet\\Services\\FontCache\\Parameters**, with a value of 1.
|
To turn off font streaming, create a REG\_DWORD registry setting called **DisableFontProviders** in **HKEY\_LOCAL\_MACHINE\\System\\CurrentControlSet\\Services\\FontCache\\Parameters**, with a value of 1.
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> After you apply this registry setting, you must restart the device for it to take effect.
|
||||||
|
|
||||||
### <a href="" id="bkmk-previewbuilds"></a>6. Insider Preview builds
|
### <a href="" id="bkmk-previewbuilds"></a>6. Insider Preview builds
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user