Tomster/Microsoft-Edge-Policies
1
0
Fork 0
mirror of https://github.com/TommyTran732/Microsoft-Edge-Policies synced 2024-11-04 10:11:33 -05:00
Code

Typo fix

Browse Source 
Signed-off-by: Tommy <contact@tommytran.io>
This commit is contained in:
Tommy 2024-01-17 00:47:04 -07:00
parent 30430dbffe
commit aa5984789a
Signed by: Tomster
GPG Key ID: 555C902A34EC968F
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -52,14 +52,14 @@ Next, create `/Library/LaunchDaemons/io.tommytran.prefs.plist`:
<plist version="1.0"> <plist version="1.0">
<dict> <dict>
<key>Label</key> <key>Label</key>
<string>dev.privsec.prefs</string> <string>io.tommytran.prefs</string>
<key>RunAtLoad</key> <key>RunAtLoad</key>
<true/> <true/>
<key>LaunchOnlyOnce</key> <key>LaunchOnlyOnce</key>
<true/> <true/>
<key>ProgramArguments</key> <key>ProgramArguments</key>
<array> <array>
<string>/Library/PrivSec Corporation/scripts/apply_prefs.sh</string> <string>/Library/Tomster Corporation/scripts/apply_prefs.sh</string>
</array> </array>
</dict> </dict>
</plist> </plist>
@ -68,7 +68,7 @@ Next, create `/Library/LaunchDaemons/io.tommytran.prefs.plist`:
Finally, load in the service: Finally, load in the service:
``` ```
sudo launchctl load /Library/LaunchDaemons/dev.privsec.prefs.plist sudo launchctl load /Library/LaunchDaemons/io.tommytran.prefs.plist
``` ```
I have also noticed that Microsoft Edge does not seem to reload Managed Preferences probably until the computer reboots. Note that this may not work after a macOS update, and you will need to reboot the computer again for the policies to apply. I am not sure if this is a macOS behavior or if it is caused because my machine is not enrolled in an MDM. I have also noticed that Microsoft Edge does not seem to reload Managed Preferences probably until the computer reboots. Note that this may not work after a macOS update, and you will need to reboot the computer again for the policies to apply. I am not sure if this is a macOS behavior or if it is caused because my machine is not enrolled in an MDM.