Office365 actions - disable protected view on trusted locations - does not function with gpo network drives

ZhuJode 76 Reputation points
2022-01-28T15:59:53.713+00:00

How are you?

We have a Windows Server 2016 Standard (let us call it serverx) server that acts as the local Active Directory and File Server.
We used to map the network drive to drive A for our clients using GPO.
The issue is that I am unable to disable the protected view on Office documents stored on this server.
The server is listed in the Trust Center's Trustworthy Locations, and the Allow trusted locations on my network (not recommended) checkbox is selected, however this has no effect.

I also added an entry for serverx to the hosts file to avoid any naming conflicts. There is no impact.

Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,379 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 39,786 Reputation points
    2022-01-31T09:22:13.067+00:00

    Hi there,

    You can disable Protected View via Registry Editor.

    1. Open Registry Editor.
    2. Navigate to the following location if you want to disable Protected View for Word/Excel/PowerPoint.

    HKCU\Software\Microsoft\Office\14.0\Word\Security\ProtectedView
    HKCU\Software\Microsoft\Office\14.0\Excel\Security\ProtectedView
    HKCU\Software\Microsoft\Office\14.0\PowerPoint\Security\ProtectedView

    Now in the right panel of the registry editor, you can see three values.

    DisableAttachementsInPV
    DisableInternetFilesInPV
    DisableUnsafeLocationsInPV

    By setting each value to 1, you will disable Protected View for that file location.


    --If the reply is helpful, please Upvote and Accept it as an answer--

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.