Something to keep in mind is NGFW. Ubiquiti and Meraki, for example, are NGFW.
It looks like much of the market is already starting to cool on the UTM crazy and NGFW is taking off as the "next stage" of popular approaches. Basically a reversal of direction or marketing at least, even from the big players in the UTM space like Palo Alto, Fortinet, Cisco, etc.
The whole crux of my ask was - the desire to buy as few Windows Server CALs as possible.
This is unrelated to the question asked, though.
you know i have noticed you and dash really communicate differently. not good or bad, just different. then you both have trouble understanding the other. from the many threads i have read with you two, that is the common theme i have seen.
I'd assume part of it is that I am highly literal. That tends to be a root of many communications issues for me in general.
yeah i think your right you are literal. i had to adjust my communication with you. that was my fault though, i am used to having to be so unliteral with my users because i would lose them that i got into that bad habit lol. i know for me, i was not explaining my thoughts in a well laid out way and that made me harder to understand and threw you off. did i do better that time?
Thanks to those of you that offered a suggestion. I built a second RDS server and applied my group policy and browsing was fine. I then started to think about what I needed to do to move it in to production and replace the one that had the browsing issue. Then it hit me.... I have load balancing on my SonicWall. RDS is mapped through the firewall on https. Therefore requests that went out over https could go out over either interface, but always came back on one. This is why it would sometimes work. This is also why most other sites would work, but https (in this case Office 365 which always goes over https) would only work once in a while. Adding a route to force all traffic from the RDS server out over the interface that traffic will come in on fixed the problem.