gsadmin/GPOZaurr
1
0
Fork 0
mirror of https://github.com/EvotecIT/GPOZaurr.git synced 2026-09-04 14:45:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixed typo "Unfortunetly" -> "Unfortunately"

Browse Source
This commit is contained in:
David M Williams
2024-08-21 12:32:12 +10:00
committed by GitHub
parent 029225a65c
commit 9ec8f5128b
4 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Private/Invoke.GPOZaurrBlockedInheritance.ps1
+1 -1
View File
@@ -80,7 +80,7 @@
"As GPOs can be inherited by default, they can also be blocked, if required using the Block Inheritance. "
"If the Block Inheritance setting is enabled, the inheritance of group policy setting is blocked. "
"This setting is mostly used when the OU contains users or computers that require different settings than what is applied to the domain level. "
"Unfortunetly blocking inheritance can have serious security consequences. "
"Unfortunately blocking inheritance can have serious security consequences. "
)
New-HTMLText -Text @(
'As it stands currently there are ',
Private/Invoke.GPOZaurrConsistency.ps1
+1 -1
View File
@@ -145,7 +145,7 @@
}
New-HTMLWizardStep -Name 'Fix inconsistent downlevel permissions' {
New-HTMLText -Text @(
"Unfortunetly this step is manual until automation is developed. "
"Unfortunately this step is manual until automation is developed. "
"If there are inconsistent permissions found inside GPO one has to fix them manually by going into SYSVOL and making sure inheritance is enabled, and that permissions are consistent across all files."
"Please keep in mind that it's possible inconsistent downlevel permissions fix will not be required once the top level fix is applied. "
"Rerun report to find out if you've just fixed top-level permissions. "
Private/Invoke.GPOZaurrPermissionsAnalysis.ps1
+2 -2
View File
@@ -185,7 +185,7 @@
} -FontSize 10pt
New-HTMLText -FontSize 10pt -Text @(
"Unfortunetly it's not as simple as it sounds. While checking for permissions mostly works fine, it's possible a Group Policy has totally removed account permissions from being able to asses any of it. ",
"Unfortunately it's not as simple as it sounds. While checking for permissions mostly works fine, it's possible a Group Policy has totally removed account permissions from being able to asses any of it. ",
"The account we're using "
"$($Env:USERDOMAIN)\$($Env:USERNAME.ToUpper())",
" may simply not have enough permisions to properly asses permissions for a GPO. "
@@ -265,7 +265,7 @@
New-HTMLText -Text "Fourth problem relates to UNKNOWN SID" -FontSize 10pt -FontWeight bold -TextDecoration underline -Alignment center
New-HTMLText -FontSize 10pt -TextBlock {
"Sometimes groups or users are deleted in Active Directory and unfortunetly their permissions are not cleaned automatically. "
"Sometimes groups or users are deleted in Active Directory and Unfortunately their permissions are not cleaned automatically. "
"Those are left in-place and stay there forever until removed. "
} -LineBreak