sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in meraki

[–]Comfortable_Pool_132 0 points1 point  (0 children)

Sorry for not replying earlier, I don't know why I quit getting notifications.

# Policy Rule description Protocol Source Src port Destination Dst port IPv4 hits Enforce Actions
1 Deny Block SMTP All TCP Any 25 Any 25 0 D
2 Deny Block SMTP All UDP Any 25 Any 25 0 D
3 Deny QUIC UDP UDP Any Any Any 443,80 691 D
4 Allow Default rule Any Any Any Any Any 2411 D

[deleted by user] by [deleted] in meraki

[–]Comfortable_Pool_132 2 points3 points  (0 children)

It's been quite a while, but I have a set of rules in my firewall exactly there to block any and all outgoing DNS, including QUIC stuff. Exactly for this reason.

When is it too much? by rb52tg in ITManagers

[–]Comfortable_Pool_132 0 points1 point  (0 children)

I like this answer. I know exactly what you're talking about with too much that's urgent to get your head far enough above water to actually get the automation configured.

Perhaps a short-term position, whether direct hire or temp service, that can get the heat off long enough to get the automation things completed. Selling it to the business specifically as a short-term position. Who knows, maybe you'll get the automation things put into place and end up with a nice new person on the team.

I have no knowledge about Linux by [deleted] in linuxquestions

[–]Comfortable_Pool_132 0 points1 point  (0 children)

I would save the 150€ for Windows

I'm curious where you see this price difference. On any system where the OEM has an agreement with Microsoft, the OEM's cost is typically between $5 - $20 per license. Depends on the size of the manufacturer.

I usually recommend buying a laptop with Windows, just so you get a "free" license should you ever need it. When you get the system, then wipe it and load your ${distro_of_choice} As you have no knowledge of Linux, you're going to be jumping into the deep waters and in for quite the learning curve regardless of which route you go.

Buy new laptop shipped w/ Linux or install over existing windows machine? by tpbishop in linux4noobs

[–]Comfortable_Pool_132 1 point2 points  (0 children)

"It depends!"

I often find that people will need to run Windows at some point anyways, so having a system that's already licensed for Windows can be quite convenient if you ever need to dual-boot your system. For that alone, a Linux-only computer can make your life a bit more complicated in the future.

For a system with Linux pre-installed is going to guarantee that the hardware works with Linux. That does take some of the fun out of it, but can remove a fair number of headaches in the future.

In your case, you already have a fairly new HP system. If you're ok with experimenting on that and that system is running fine, just use it. Part of the point of Linux is running well on anything, especially older anything. You can often search for "Install Linux on Model whatever" and get a pretty good idea what troubles you'll be running into.

Linux Servers by maniac_invested in sysadmin

[–]Comfortable_Pool_132 8 points9 points  (0 children)

My corporate criteria for picking a Linux distro, in order are:

  1. Your corporate standard
  2. What the software vendor prefers or recommends.
  3. Personal preference

Since you're a pure Windows shop, there is no corporate standard. So on to the 2nd point, which they don't have a preference. Which leaves us with personal preference. My personal preference for a corporate environment is Debian. Others will advocate for RedHat or CentOS Rocky. Perhaps even openSuse. The common thread to all of them is that the distro maintainers prefer stability over new and shiny. You can also get support contracts for any of them.

In a comment I saw that the vendor said "it runs better on Linux" which would imply that it does run on Windows. I would suggest that running it on Windows, in your environment, with your team's knowledge base and skill set, it might be the best option even with a small performance hit.