@scottalanmiller Yep, I just wanted to share the configuration I use as my daily driver because it makes working in the terminal that much more efficient. The OP mentioned wanting something that was a bit slicker and more powerful, and I think in addition to your choice of terminal, your choice of shell and other tools contributes to having a better experience. I prefer FISH for my shell, and tmux is my terminal multiplexor of choice. ZSH is another great alternative shell as well.
A simple restart command doesn't perform the update step, just the restart, so the update doesn't get applied.
This has been an issue for a very long time with windows. I am surprised it hasn't been fixed yet. It's really annoying
Well, at least with Win 7, a standard reboot applies updates. At least, I think it does. The main difference between Win 7 and 10, is that they have switched to the osoclient.exe to manage the updates.
I'm pretty sure server 2008 and onward had the issue. I don't remember dealing with it on workstations
I still have a 2008 R2 box and can test it on the next go 'round. I won't have it much longer, as I am dumping it prior to EOS.
LOL - Didn't make this cutoff. Next week, hopefully.
@JaredBusch fair enough, I haven't used the product itself as of yet and wasn't aware it had whitelisting inside the product, if this was specific to just fail2ban then that method would be suitable, but in this case I agree with you, my mistake.
It is likely obvious, but as I know that some people are searching for this information, creating administrative users in this way can be done very easily from remote command lines such as ScreenConnect, ConnectWise, MeshCentral, and so forth.
No doubt. Currently working on getting Server 2019 DC, DHCP, and RDS working in a lab. A few challenges so far. Was going to try using PS to do many tasks I normally do in GUI (force myself to learn as I go) but decided to put it on the back burner due to frustration. I will get there with PS but it has to wait.
Unfortunately, no matter how much we want to complain about PS and how Windows has no production-level roadmap at this point and is getting worse by the day, if you are going to run Windows today, PS is how it is done. Issues with PS have only one valid purpose to discuss - to use to explain to management why Windows shouldn't be getting deployed in production workloads, or why risks with it need to be accepted. It's like the licensing issues with Windows, these things all add up to cost and risk and risk is really just cost. It's part of the "decision numbers." Beyond that, it is what it is. If the business actually knows how costly it is and still chooses it, then PS is how you manage it.
If you deploy and start without using PS, it'll be that much harder to switch later. I know the learning curve is absurd and the whole thing is so much harder than it has any purpose being, but I would bite the bullet if at all possible and learn it now. It'll just be harder later.