Sheridan Posted September 25, 2018 Posted September 25, 2018 (edited) I've found the usual double standard error in Windows 10 - we disable browsing of network mapped folders (used for applications etc) in Explorer, but if you simply press the Start button, or use the Search and type the mapped drive letter (i.e h:) it will open the drive up for browsing! Completely ignoring the group policy settings that prevents explorer from browsing that drive. Obviously permissions are applied to the folders, but its this sort of stuff that makes me think 10 still isn't reliable for GPOs - i.e you set it in one place and W10 simply ignores it somewhere else... Just realised this also applies for UNC paths as well, so they can browse any server share they can find (permissions allowing of course) but whats the point of implementing GPOs when the 'type to search' overrides and ignores all of them! Has anyone tried disabling cortana by renaming the folder in the SystemApps? It seems to kill the start menu (its all greyed out) - I'm sick of all this modern apps crap now as its nothing but problems. Edited September 25, 2018 by Sheridan
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now