• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1493
  • Last Modified:

Share Permissions

I have a major issue with end-users being able to see other users home drives. This is what I have. Win2003 servers with Active Directory. I have a folder called Home Drives and the share permissions are Administrator, Everyone group and system. The NTFS permissions are Administrator, Creator Owner and system. What might I have setup wrong. If I remove the everyone group from the share, then no one can see their home drive. Is there a best practice for share and NTFS permissions when setting up home drive shares?

Thank you for your input.
0
sjacobi
Asked:
sjacobi
1 Solution
 
from_expCommented:
most common solution for home folders is to create them hidden (with $ sign at the end)
also microsoft recommended solution it to configure share permissions everyone full control and limit access permissions to folders only by ntfs permissions
0
 
2PiFLCommented:

Remove Everyone from the Share permissions and Add Authenticated Used with Read / Write to the Share Permissions.

On the Security Tab of the top level Home folder Add Administrator and System with Full Control and Authenticated Users with Read / Write.  Then Click the Advanced button, Select Authenticated Users, Click Edit and in the "On To" box select "This folder only".  Click Ok until your out.

Then on each individual Home folder give Read / Write to the individual User on the Security tab.

You can also apply the Access Based Enumeration MSI so that users only see the folders that they have rights to.                  
0
 
Kevin HaysIT AnalystCommented:
Most people will remove everything out of the share permissions and add in "everyone" will full control.  THen remove all security groups from the NTFS tab and start adding in what they want from there to control access since the administration and troubleshooting is easier at this point.

If you are not comfortable using the everyone on the share tab with full control then do as 2PiFL suggested and use the "authenticated users", but I would give them full control on the share so you can explicitly control the NTFS.

Remember the least restrictive permissions will always apply when comparing share v/s ntfs.  That's the reason most people give either everyone/authenticated users full control on the share and share only.

0
 
DoradoITTeamCommented:
I created an scripts that does it, and i have worked great, im sharing only the root part of the folder
Ex.
Home Folders - Share Name = \\fileserver\homeusers$ permission to everyone

Inside that folder i created an structure for departments and then user name Ex.
\\fileserver\homeusers$\accounting\user1, then assigned NTFS permission to User1 folder

Attached there is a VBscript that automatically creates the user drive when the user log on for the first time, dcserver1 is my domain controller where i put all files that maybe needed for any computer like cacls, takeown files, the fileserver1 is my home users drive fileserver and prnserver1 is my print server, hope this helps

Dim WshShell
Set WshShell = CreateObject("wscript.Shell")
Const RSettings_RegFile = "\\dcserver1\System_Files$\GPO_Files\RS_Spanish.reg"
 'Retrieve System Folder
		strComputer = "."
		Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2")
		Set colOSItems = objWMIService.ExecQuery("SELECT * FROM Win32_OperatingSystem")
			For Each objOSItem In colOSItems
  				strSystemFolder = objOSItem.SystemDirectory
			Next
'Verify if Logo App exists
  'Verify Takeown exists
	Set objFSO = CreateObject("Scripting.FileSystemObject")
		If objFSO.FileExists( strSystemFolder  & "\Logon_Logo.exe") Then
    	  ' Do nothing
		Else
    	  ' Copy the file from specific location
		Const OverwriteExisting = False
		Set objFSO = CreateObject("Scripting.FileSystemObject")
		objFSO.CopyFile "\\dcserver1\System_Files$\Logon_logo.exe" , strSystemFolder & "\", OverwriteExisting    	   
		End If	
 
 WshShell.Run strSystemFolder  & "\Logon_Logo.exe"
 
'***************************************************
'********** Retrieve Current Logon User ************
'***************************************************
 
	Set wshNetwork = CreateObject("WScript.Network")
	strUser = wshNetwork.UserName
	'strGroup = "DL-SEC-IT-Staff"
	strAdminGroup = "SFNET/Administrator"
	
	'WScript.Echo "Current User: " & strUser
'***************************************************
'******* Verify if Folder Directory Exists *********
''**************************************************
 
	Set objFSO = CreateObject("Scripting.FileSystemObject")
	strHomePath = "\\fileserver1\privado$\Informatica\" & strUser
 
	If objFSO.FolderExists(strHomePath) Then
	    Set objFolder = objFSO.GetFolder(strHomePath)
	Else
		'Create it if doesn't exist    
		Set objFSO = CreateObject("Scripting.FileSystemObject")
		Set objFolder = objFSO.CreateFolder(strHomePath)	    
		'Assign folder permisions	
		WshShell.run "cacls " & strHomePath & " /t /e /g " & strUser & ":F",  7, False	
		WshShell.run "cacls " & strHomePath & " /t /e /g " & strAdminGroup & ":F",  7, False	
'		WshShell.run "cacls " & strHomePath & " /t /e /g " & strGroup & ":R",  7, False	
		'Reset Default Permisions
        WshShell.run "cacls " & strHomePath & " /e /r " & "BUILTIN\Administrators",  7, False	
		WshShell.run "cacls " & strHomePath & " /e /r " & """BUILTIN\Users""",  7, False	        
		WshShell.run "cacls " & strHomePath & " /e /r " & """NT AUTHORITY\SYSTEM""",  7, False	
		WshShell.run "cacls " & strHomePath & " /e /r " & """CREATOR OWNER""",  7, False	
		
 
		'Verify Takeown exists
		Set objFSO = CreateObject("Scripting.FileSystemObject")
		
		If objFSO.FileExists( strSystemFolder  & "\takeown.exe") Then
    	  ' Do nothing
		Else
    	  ' Copy the file from specific location
 
		Set objFSO = CreateObject("Scripting.FileSystemObject")
		objFSO.CopyFile "\\dcserver1\System_Files$\takeown.exe" , strSystemFolder & "\", OverwriteExisting    	   
		End If	
		'Take Ownership of Folder
		WshShell.run "takeown /f " & strHomePath,  7, True
	End If
 
'************************************************************
'******************** MAP USER DRIVE ************************
'************************************************************
	
	WshShell.Run "net use x: " & strHomePath,7,False
'************************************************************
'******************* MAP DEPTO DRIVE ************************
'************************************************************
	WshShell.Run "net use y: " & "\\fileserver1\ITPublic$" ,7,False	
 
'************************************************************
'******************* MAP PUBLIC DRIVE ***********************
'************************************************************
	WshShell.Run "net use z: " & "\\fileserver1\Public$" ,7,False	
 
'************************************************************
'******************* MAPPING PRINTERS ***********************
'************************************************************
'	wshNetwork.AddWindowsPrinterConnection "\\printserver1\nps_it_3"
'	wshNetwork.SetDefaultPrinter "\\printserver1\nps_it_3"
	
'************************************************************
'**************** CHANGE REGIONAL SETTINS *******************
'************************************************************
    WshShell.Run "regedit /s " & RSettings_RegFile
'************************************************************
'****************** CLOSE DESKTOP LOGO **********************
'************************************************************
	Set objWMIService = GetObject("winmgmts:" _
    	& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
 
	Set colProcessList = objWMIService.ExecQuery _
    	("Select * from Win32_Process Where Name = 'Logon_Logo.exe'")
 
	For Each objProcess in colProcessList
    	objProcess.Terminate()
	Next	

Open in new window

0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now