|
| | | Junior Member
 
Group: Forum Members
Last Login: 1/13/2010 7:46:11 AM
Posts: 23, Visits: 108 |
| | I think it would be fairly easy and valuable to add the ability to check for a share name on a client and make a user-defined config group out of it. |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| | Yes, it is easy in fact! Try creating a user-defined configuration group with the following ruleset (this looks for a share called "downloads": EXISTS <Registry Value> "HKLM\System\CurrentControlSet\Services\Lanmanserver\Shares\\downloads"
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Junior Member
Group: Forum Members
Last Login: 1/13/2010 7:46:11 AM
Posts: 23, Visits: 108 |
| | I wish it were that simple, the problem is I want to look for admin shares such as C$,ADMIN$, etc.. Any ideas? |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| | Administrative (hidden) shares should exist unless the computer has been configured to not create/recreate them at startup. Here's a link to Microsoft KB article discussing issues that can occur if administrative shares are disabled: http://support.microsoft.com/kb/842715/en-us. You can create a configuration group to find out which workstation computers have administrative shares enabled: NOT EXISTS <Registry Value> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\\AutoShareWks" OR <Registry Value> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\\AutoShareWks" = "1" Here's the same rule, only for servers: NOT EXISTS <Registry Value> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\\AutoShareServer" OR <Registry Value> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\\AutoShareServer" = "1" Hopefully this gives you the information you need.
New Boundary Technologies Support
support@newboundary.com |
| |
|
|