Hi Eric,

Sorry I should have responded earlier and said all complete.

Group Policy solution was the easiest.

Thanks


On 8 August 2013 13:23, Eric Wittersheim <[email protected]> wrote:

> Barrie,
>
> If you are running AD you can do this easily with Group Policy. Or you can
> make your registry changes via login script.  I like the Group Policy
> Preferences option when I need to make a registry change.
>
> Eric
>
>
>
>
> On Wed, Aug 7, 2013 at 4:01 PM, Barrie Russell 
> <[email protected]>wrote:
>
>> Hi,
>>
>> Unfortunately, while it did get rid of the context menus, it  did not get
>> rid of the items command bar.
>>
>> However after reading the link you attached, I fired up procmon and found
>>
>>
>> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\CommandStore\shell\Windows.Share
>> If I take ownership and rename that key, the menu item disappears.
>>
>> Now just need to work out how to automate this over all machines.
>>
>> Thanks
>>
>> On 7 August 2013 21:25, Aakash Shah <[email protected]> wrote:
>>
>>>  If you want to just remove the ability for people to see/access “Share
>>> With” from the UI, it appears that you can delete the following registry
>>> keys:****
>>>
>>> ** **
>>>
>>> ; Share with****
>>>
>>> [-HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\Sharing]****
>>>
>>>
>>> [-HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers\Sharing]
>>> ****
>>>
>>> [-HKEY_CLASSES_ROOT\Directory\shellex\ContextMenuHandlers\Sharing]****
>>>
>>> [-HKEY_CLASSES_ROOT\Drive\shellex\ContextMenuHandlers\Sharing]****
>>>
>>>
>>> [-HKEY_CLASSES_ROOT\LibraryFolder\background\shellex\ContextMenuHandlers\Sharing]
>>> ****
>>>
>>>
>>> [-HKEY_CLASSES_ROOT\UserLibraryFolder\shellex\ContextMenuHandlers\Sharing]
>>> ****
>>>
>>> ** **
>>>
>>> Source:
>>> http://www.sevenforums.com/customization/16714-context-menu-cleanup-time.html#post178160
>>> ****
>>>
>>> ** **
>>>
>>> I did not test all of them, but I did test deleting *
>>> HKCR\Directory\shellex\ContextMenuHandlers\Sharing* and it did
>>> successfully remove the Share With context menu item from folders.****
>>>
>>> ** **
>>>
>>> However, I don’t know if this has any other adverse side effects (I’ve
>>> not implemented this in a production environment).****
>>>
>>> ** **
>>>
>>> Note that there may be other areas where they can browse the domain, so
>>> setting the AD results to show 0 results as you’ve already done may be a
>>> good item to keep for you.  However, I believe that this affects the
>>> ability for a user to browse for printers too in case you need that ability.
>>> ****
>>>
>>> ** **
>>>
>>> -Aakash Shah****
>>>
>>> ** **
>>>
>>> *From:* [email protected] [mailto:
>>> [email protected]] *On Behalf Of *Barrie Russell
>>> *Sent:* Wednesday, August 7, 2013 1:04 PM
>>> *To:* [email protected]
>>> *Subject:* [NTSysADM] Remove Windows explorer command bar****
>>>
>>> ** **
>>>
>>> Hi Guys,****
>>>
>>>  ****
>>>
>>> Just going through a Pen Test at the moment and got pinned on this
>>> little gem.****
>>>
>>>  ****
>>>
>>> I can't seem to find a way to remove the "Share With" button that
>>> appears when you click on a folder.****
>>>
>>>  ****
>>>
>>> As a restricted user you can't actually share anything, it does however
>>> pop up an AD search box which then allows you to browse all through the
>>> directory structure. That is where I got hurt.****
>>>
>>>  ****
>>>
>>> Google has produced some results on manually modifying the contents of
>>> some DLL's, but that is not really practical and may get over ridden at
>>> anytime by patch/hotfix or service pack.****
>>>
>>>  ****
>>>
>>> As a mitigation I have used group policy to reduce the amount of AD
>>> search results to 0, but if anyone has any out of the box ideas that can
>>> help it would be greatly appreciated.****
>>>
>>>  ****
>>>
>>> Apart from this little gem, things have gone pretty well, just would
>>> like to fix this one prior to the report being written so it shows as
>>> resolved and not outstanding.****
>>>
>>>  ****
>>>
>>> Thanks****
>>>
>>> Barrie****
>>>
>>>  ****
>>>
>>>  ****
>>>
>>
>>
>

Reply via email to