deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

clean up

Browse Source
This commit is contained in:
Justin Hall 2019-04-05 10:43:39 -07:00
parent 8e751df01a
commit 8af8f1077a
1 changed files with 0 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/security/information-protection/windows-information-protection/limitations-with-wip.md
View File

@ -137,11 +137,3 @@ This table provides info about the most common problems you might encounter whil
>[!NOTE] >[!NOTE]
>Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Contributing to our content](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md). >Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Contributing to our content](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md).
Anywhere under c:windows\* is a design. We don’t want you to shoot yourself in the foot. We don’t want that encrypted to a specific user because it’s used y all windows users. If you are logged in as one admin user and another user signs in as a diff admin user, they have no way to elevate to get the encrypted data.
If it’s in windir, they will not encrypt if it was already there. If there is a file in the dir and you try to encrypt it, it will fail. But if you drag and drop to there, it will retain encryption. That honors the intent of the owner. So if you redirect OneDrive to C:windows\temp, the files will not get encrypted. They won’t change it.
Put in the limitations section, add a section that says this is by design
Workaround,