ipmo pscx $priv=get-privilege $priv.Enable("SeRestorePrivilege") $priv.Enable("SeBackupPrivilege") $priv.Enable("SeSecurityPrivilege") $priv.Enable("SeTakeOwnershipPrivilege") set-privilege $priv; $report=$null $Report=@() $InputFile = "C:\temp\Folders.txt" $OutputFile = "C:\temp\FolderPermissions.csv" $FolderList = Get-Content $InputFile ForEach ($Folder in $FolderList) { # Get access list items of the folder $Permissions = (Get-Acl -Path $Folder).Access | # Add the path property and assign its value, -PassThru so the object is assigned to $Permissions forEach-Object { $_ | Add-Member -MemberType NoteProperty -Name Path -Value $Folder -PassThru } $Report += $Permissions } $Report | Select-Object path,IdentityReference,FileSystemRights,IsInherited | Export-CSV $OutputFile -NoTypeInformationthanks to whoever's code source I used... so much internet so little time.
Wednesday, December 10, 2014
Elevate'd Privilege - ACLs of Folders - Backup operator
Using PSCX powershell module to give backup operator rights (also might need to do a file server level)
Labels:
backup operators,
elevate,
ninja,
powershell,
pscx,
security
Saturday, December 6, 2014
802.1x vs Symantec Endpoint
Recently I have been on a BYOD/ Enterprise mobility project.
As part of this project we are deploying CISCO ISE.
at first network engineer could not work out why the authentication box was missing need to start the wire, so my problem
Could not get the SOE\MOE device to authenticate against the switch. Basically the prompt for auth would never happen. Stock devices were okay.
Pretty sure it was Symantec EndPoint
Symantec couldn't understand the different between Symantec NAC and CISCO ISE. Sigh. I repeated myself about 20 times.
All I got was articles about Symantec NAC.
When Symantec looked at the policies they didnt check what policy was being used on the device. (I am not AV Engineer)
The default firewall policies has a bunch of exceptions at a very low level to allow the 802.1x requests. Once I added these into the policy.. everything worked. :)
As part of this project we are deploying CISCO ISE.
at first network engineer could not work out why the authentication box was missing need to start the wire, so my problem
Could not get the SOE\MOE device to authenticate against the switch. Basically the prompt for auth would never happen. Stock devices were okay.
Pretty sure it was Symantec EndPoint
Symantec couldn't understand the different between Symantec NAC and CISCO ISE. Sigh. I repeated myself about 20 times.
All I got was articles about Symantec NAC.
When Symantec looked at the policies they didnt check what policy was being used on the device. (I am not AV Engineer)
The default firewall policies has a bunch of exceptions at a very low level to allow the 802.1x requests. Once I added these into the policy.. everything worked. :)
clumsy, an utility for simulating broken network for Windows Vista / Windows 7 and above
http://jagt.github.io/clumsy/index.html
Leveraging the awesome WinDivert library, clumsy stops living network packets and capture them, lag/drop/tamper/.. the packets on demand, then send them away. Whether you want to track down weird bugs related to broken network, or evaluate your application on poor connections, clumsy will come in handy
from :http://trentent.blogspot.com.au/2014/11/best-windows-network-bandwidth.html
Leveraging the awesome WinDivert library, clumsy stops living network packets and capture them, lag/drop/tamper/.. the packets on demand, then send them away. Whether you want to track down weird bugs related to broken network, or evaluate your application on poor connections, clumsy will come in handy
from :http://trentent.blogspot.com.au/2014/11/best-windows-network-bandwidth.html
Labels:
clumsy,
network tools,
performance,
trentent,
utilities
Subscribe to:
Posts (Atom)