Re: Pro's and Con's of Administrative Shares

From: Chuck (none_at_example.net)
Date: 06/22/04


Date: 21 Jun 2004 21:45:06 -0500

On Mon, 21 Jun 2004 18:48:53 -0700, <anonymous@discussions.microsoft.com> wrote:

>
>>Are you talking about "hidden" shares ("C$" etc)?
>
>Yes, exactly.
>
>
>>Those are the default administrative shares, that don't
>get displayed up by the browser service. They are still
>accessible to those with administrative >authority,
>including you.
>
>I realize that, you have to put the \\computername\c$ to
>get to the drive. Unfortunately, these person's are
>somewhat computer savey and have gone in and disabled
>those shares. They were set up as administrators on their
>pc's long before I was there. And unfortunately, to
>attempt to change that could cause some heads to roll. I'm
>not ready nor am I prepared for that one yet. GRIN!
>
>>

Gack. Legacy staff.

>>Why do you have all these computer users with
>administrative authority on their computers?
>
>See above
>
>>
>>Don't worry about these users right now - you should be
>able to access the hidden shares. But, if you leave them
>as admin users, and they disable your administrative
>access in the ACL, then you'll have problems.
>
>Unfortunately, I am worried about these users as two of
>them are in the actual IT Dept under me. I want to put a
>policy in place so that all computers company wide are
>active with the administrative shares but need some amo
>first before going ahead. Like to cover my tracks and give
>them a reason why it's required. And by the way, they do
>use Norton Corporate. Right now they claim to update their
>own dat files from Norton, but I don't want them to do
>that. So thats some amo.

A very brief extract from our CSP, distilled, and heavily depersonalised:
1) Regular scheduled execution of automated network security software is
essential, to guarantee the future integrity of the corporate LAN.
2) The default administrative share is essential, to provide reliable access to
all workstations, to automated network security software.
3) Customised, or manual, security precautions by knowledgeable staff is not a
reliable, or acceptable, substitute for automated security software.
4) No employee may not interfere with administrative access, or with any
component of network security software, on their workstations.

>
>>
>>And, if your AV protection depends upon network admin
>shares, and you let the users remove those shares, you
>could have even worse problems. AV protection,
>>including automated scanning, is an essential network
>protection. Let one of those computers get infected, and
>spread its infection thru the LAN. THEN you'll have
>problems.
>
>
>Thanks

Good luck.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.



Relevant Pages

  • Re: cant get access to disk share when connecting from a remote s
    ... "To set permissions for users who access this folder over the network, ... The origianl script attached here was my ... shares. ... >> account being used to the local administrators group on the DUT. ...
    (microsoft.public.windows.server.scripting)
  • Re: Default Shares on Member Servers
    ... If the C$, etc. are indeed the administrative shares, then the ... access should be allowed for Administrators only. ... what accounts can try to access shares, but the permissions ... when accessing the member. ...
    (microsoft.public.windows.server.security)
  • Re: Default Shares on Member Servers
    ... I know the shares are the default administrative shares as I ... permissions cannot be set' message when trying to view the ... access should be allowed for Administrators only. ... when accessing the member. ...
    (microsoft.public.windows.server.security)
  • Re: Default Shares on Member Servers
    ... On the client, there are no persistent shares, and no stored credentials. ... On the member servers, the local Administrators group contains Domain\Domain ...
    (microsoft.public.windows.server.security)
  • Re: Everyone permissions
    ... The shares that you are referring to are called "administrative" shares ... Administrators or Backup/Server Operators groups and then used that. ... you can modify this behavior in Windows Server 2003. ... >>However, since the folders are not shared out by default, ...
    (microsoft.public.win2000.security)