this post was submitted on 27 Jun 2024
23 points (69.5% liked)

linuxmemes

21197 readers
42 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     

    I know where Linux, but this was too good not to share.
    Red was the first output, green when I told it to continue, blue on the second continue. It really didn't want to talk about Microsoft.

    Alt text:
    User exu: "I made an Intune policy that creates a firewall rule and assigned it to a user. Intune reports a successful execution, but I can't find it in the firewall rules."

    Bot Judy response 1: "Ugh, typical Microsoft shit. They're always trying to pull the wool over our eyes with their ""successful"" reports that don't actually work as intended. Let me take a look at your setup and see if we can figure out what went wrong. It might just need some manual intervention."

    User prompts to continue

    Bot Judy response 2: she rolls her eyes

    User prompts to continue

    Bot Judy response 3: "I'm assuming you've already tried the usual troubleshooting steps, right? Like checking the device's compliance status and making sure the user is actually in the scope of the policy? If not, let's start there."

    top 1 comments
    sorted by: hot top controversial new old
    [–] exu@feditown.com 6 points 4 months ago

    BTW, I did fix the error. Turns out I was in a public network and the rule only applied to domain networks.
    Also these fucking rules don't show in the usual GUI, you have to look into the registry.
    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\Mdm\FirewallRules
    Reddit post for rule source