Fix; Export from CC fails to see mapped Network drive from Windows 10

When Windows 10 rolled out Microsoft changed the structure of Permission authentications and parent child policies with reference to Network Drives…

This may have been necessary because of an exploit that can propagate itself across networks when a drive is mapped to an infected or hacked machine.

Windows blocked the policies giving software the ability to access network drives… even those mapped to the client PC. My software Coder says it is a huge rewrite to give access to the Control Center, but he found a temporary work around… Which I have tested and operates exactly as you need…

Please give this to your Client Network IT Tech, as this requires a Registry Edit addition, and we must decline from performing this on client PCs 😊 (for obvious reasons) This will need to edited on each machine that is running the Control Center Terminal software.

• The following steps requires making a registry key and multiple D word 32 entry at the location:
  • “Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System”
  • and adding the D Word Key value “EnableLinkedConnections” with a value data:1

• No need to restart the PC… but made sure my new key was still in the registry…
• restart the CC and the network links appears
• You will be was able to export an event directly to a Mapped Network Drive windows 10 PC across your network with absolutely no issue at all!