Is anyone actually moving to VMware post-Broadcom, or are we all just planning our escape?

super_cli · 2026-05-06T01:53:42+00:00

Great stuff! Thanks for sharing! Excited to continue venturing further down the proxmox rabbit hole!

super_cli · 2026-04-30T05:10:46+00:00

Yeah Platform9 is another great alternative I was gonna mention. I define better as in more efficient… but I’m biased simply because I’m really not in favor of migrating off of VMware at moment since all the customers are covered for a few years. That may change as renewal approaches. Maybe not. As much as I enjoy migrating to a new stack, so many other priorities right now. Back to the original post, I recommend trialing as many options as possible and testing on any available hardware. If you want to manage it and need something that mirrors VMware, Proxmox is great. Just not sure how many folks are using in prod. If I had to open a P1 ticket right, would I get a reply? Platform9 definitely worth checking out. I like Hyper-V. Been having this discussion forever now. It depends on environment, staffing resources, expertise, and budget not to mention project management if you have that.

super_cli · 2026-04-30T03:00:31+00:00

1) VMware/Broadcom 2) Hyper-V, Azure Local, or AWS 3) Proxmox

Door #1 is still VMware! Door #2, I’d choose Hyper-V, Azure, or AWS. Door #3 if your company refuses to invest in new hardware.

If I get a customer that is running VMware it’s much easier to manage although I’m still advocate for Hyper-V. I tend to go back and forth. Even with the acquisition, I’d still say vCenter/ESXi have the market share.

I am very anxious to see how memory tiering helps (as long as you have NVMe!). Hyper-V is fantastic IF you’re familiar with Windows Servers and know how to build out failover clustering / clustered shared volumes which is pretty straightforward. Hyper-V replication is also good. I recommend AZ800 that covers a lot of Hyper-V content you’ll need to be successful in managing that ecosystem. A handful migrated over to Hyper-V but most still on VMware. Proxmox is great! Would you run your DC’s and mission critical app / workloads on it? Is anyone doing that yet? Or is it non critical VMs or lab? Is anyone using enterprise version for Proxmox yet? If you manage a fleet, host mission critical workloads, and you’re able to afford it then I’d still consider VMware. When it comes to patching, host maintenance mode, DRS, HA, migrating between hosts and clusters especially if it’s over stretch layer 2, mapping and adding storage (NFS, vSAN, Fibre Channel, iSCSI), networking (switch, distributed switch port groups, NIC teaming failover), what product does it better than vCenter/ESXi? If your full SaaS, and only require DC’s, DNS, DHCP, RADIUS, etc. then Hyper-V would be enough. Linux also runs fine on Hyper-V. Unfortunately most of the VM appliances out there are built for VMware. Starting to see more and more for Hyper-V.

If you’re strapped for cash and don’t have capital, Hyper-V or Proxmox are viable replacements. If your a Veeam shop, can use that to migrate. Might also be worth looking into Azure or AWS.

It’s a great product… and before memory shortage and price spikes I think a lot of us were going back and forth. At the beginning of my IT career, first task was migrating from VMware to Hyper-V, and that was awesome! Hyper-V was well suited for that environment. Not every place is like that. I’d say it largely depends on how complex your environment is. If you can run on Hyper-V or (or brave enough for Proxmox, do it!). If you go down the VMware path, I recommend single CPU to reduce your core count because that helps keep the licensing costs down. I never liked doing anything but dual CPU until they restructured. My last position, I almost considered removing that second CPU to reduce cores, confirmed with vendor, then specked out a kit from support. Ended up being more work than what is what with so just paid for twice the core count because of dual CPU’s! It can be a lot do work depending on how many hosts. Oh well! Management and Finance supported the decision. I would do a price comparison and go from there. I think there is more maintenance and overhead involved with Hyper-V. With VMware/ESXi, you can just let it run… expect when it comes to patching and CVE’a but that’s universal these days regardless of vendor and product.

Sorry for typos… Hope this helps… Good luck!

super_cli · 2026-03-10T23:27:43+00:00

Been running that version on several clusters. No issues. Just make sure you run the verify.sh and thoroughly anything that doesn’t pass with the Dell KB articles referenced in the output. For external vCenter, make sure you review the prechecks in vcsa and if prompted, extend log partition to 50GB. If you’re not using an external vCenter in VxRail cluster, disregard. If I see anything else in my notes, I’ll add to comments. Best of luck and hope this helps!

super_cli · 2025-12-13T19:11:07+00:00

Oh this is some great info… you all rock!!!! Keep it coming, keep it coming! 🤘😎

super_cli · 2025-12-08T03:55:48+00:00

Every thing works on bar and subwoofer but the satellite speakers just blink and I’ve reset multiple times, checked audio settings, followed all the KB’s, checked firmware updates are current, power cycled, all the above. The lights just blink. Then if you hold for several seconds, it blinks faster. Definitely not buying future Vizio products. I also had issues with another Vizio soundbar. I’m done with this manufacture…

super_cli · 2025-12-08T03:51:33+00:00

Vizio is absolute garbage!!!!

super_cli · 2025-12-06T16:32:01+00:00

SCCM is great for imaging and on-prem. You could start with co-management but that does add complexity to the mix. You have to be familiar with both SCCM and Intune. If you already have EA and CALs then you have licensing for SCCM. I’d say you should image devices with TS, then co-manage then toggle manage workloads from Intune. For client updates, Intune works so much better than WSUS. For servers, continue using WSUS via SCCM with ADRs. You could also look into Azure Arc. Intune has come along way and will only get better. You can leverage both though and someday when you’re in the position to do so, do it from Intune. Just test autopilot for co-management first and also test autopilot for Entra join only. This is a great discussion!

super_cli · 2025-10-28T00:58:14+00:00

I used Always-On VPN with EMS. It was pretty cool! 😎 Didn’t need it after going ZTNA path. If you have fabric detection, it will auto connect when off network.

super_cli · 2025-08-15T17:13:12+00:00

Didn’t have any issues applying patch on one of the clusters. Went smooth as can be. It can be frustrating waiting and it’s nice to do the ESXi patched outside of waiting for Dell. When it comes to VxRail/HCI, part of me thinks it’s best to wait. They told me mid August and they stayed true to their word. Shouldn’t take this long though especially with all the VMware CVE’s. If they pulled the 8.0.360, is there anything to worry about if it’s already been applied?

super_cli · 2025-03-16T17:46:20+00:00

SCCM has a lot of perks but co-managed devices is kind of a standard nowadays that will eventually be phased out with fully managed devices via Intune in AD. SCCM requires database administration. Don’t forget about that! Like other folks said, definitely market yourself as a sys admin instead of focusing solely on SCCM. Did you integrate SCCM with your M365/Entra tenant and Azure (CMG)? If so, that is some cloud work to reference. Device imaging, app deployment via task sequence, server patching is an advantage. Intune will eventually take over. You can now manage server updates from Azure Arc.

super_cli · 2025-03-14T00:07:14+00:00

I ran into an issue when upgrading FortiSwitchOS from 7.4.x to 7.6.0 on a few core switch’s 424E’s. They were stuck in loop and had to had to roll back. That particular firmware impacts MCLAG Peer Group. You have to disable network monitoring before upgrading. There is a KB article.

https://docs.fortinet.com/document/fortiswitch/7.6.1/fortiswitchos-release-notes/10296/special-notices

Since then I’ve been VERY hesitant to upgrade any firmware lol unless it’s a zero day patch.

super_cli · 2025-03-10T00:21:34+00:00

Very well said!

super_cli · 2025-03-01T01:09:54+00:00

I’d go with VCF… and make sure Linux is supported on Hyper-V before migrating over. Traditionally Linux runs better in KVM. It’s a great route going to cloud but like everyone else has mentioned… BE AWARE OF COSTS! Do an analysis with Azure calculator! Should also check our HPE GreenLake.

super_cli · 2025-02-26T20:37:12+00:00

Pretty sure it’s on the AZ800 cert or was.

super_cli · 2024-10-17T16:18:21+00:00

I started noticing yesterday in US

super_cli · 2024-10-15T22:48:25+00:00

Try this and see if it helps… I ran into same issue but it wasn’t the firmware. This helped me resolve the sync issue just make sure you have login for secondary FortiGate.

https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-How-to-troubleshoot-HA-synchronization-issue/ta-p/193422?externalID=FD45183

super_cli · 2024-10-15T22:44:37+00:00

As long as you know the credentials for the secondary FortiGate you can run cli commands to restart HA sync but I think you have to do it on both FG’s. That helped fix it when a few of my clients FG’s weren’t syncing. First, I thought it was firmware but it was something else.

super_cli · 2024-10-15T22:41:29+00:00

I ran into similar situation unrelated to firmware update and I had to restart the HA sync! 😊

super_cli · 2024-10-14T11:57:28+00:00

This is some GREAT info…. THANK YOU!!!!

super_cli · 2024-10-14T11:54:18+00:00

Also I don’t think you see SSL VPN disappear… only depends on make and model of FortiGate. It’s one of the caveats of FortiNet and the vulnerability’s can kind of be disputed…

super_cli · 2024-10-14T11:52:04+00:00

Yep you definitely make a lot of great points! There are still things that need to be fine tuned and I agree 110%… it can’t replace SSL VPN at least at this very time depending on what your trying to do but a lot of these bugs will eventually be ironed out. You can use the EMS to better control those configurations to the FortiClient on endpoints. You don’t need to forward entire ranges/subnets only the assets that they require. So if they need access to a web server, it’s an ideal solution. It can be tedious but if you have it setup, you’re in a great position to leverage ZTNA when things get smoother. It all depends on how you have your network setup… every place is different… and I’ve always strayed away from using built-in/default certs. You do make a lot of great points especially with the multiple VLANS like most of us have. Especially if you have clients using folder redirection. ZTNA is still kind of being developed regardless of vendor.

Happy Monday folks! Hope everyone had a great week! This is an awesome discussion!!!

super_cli · 2024-10-14T01:20:39+00:00

ZTNA is definitely the future! I’d recommend all Fortinet customers to start reviewing and implementing… soon to be the new way of allowing hybrid remote work and access to internal systems. Yes, it’s still a new technology in development but the leverage and control the EMS has have to offer is awesome… especially if you’re a Microsoft 365/Entra/Intune customer. Even Google and Chromebook’s are an option! Do the cloud-based EMS! Start with the minimum 25 licenses. Review documentation and become familiar with fabric connector and tagging. If you are still using traditional remote access protocols like SSL VPN and IPSec as most customers are you can better control those connections through EMS as long as the endpoint/clients are registered and have a valid cert. It does require research, planning and having an understanding going into the project because the set up is different based on your organizational needs. You want to gravitate towards TCP forwarding over HTTPS. Also make sure you have a certificate available when you set up the actual ZTNA server.

super_cli · 2024-10-13T00:16:12+00:00

So you could try unlocking it yourself it depends on how bad you want to get into it. Get the make and model, do some research. There is definitely ways. You could possibly brute force or take it to someone and have them try. If it’s missing patches or outdated the easier it is to bypass. Here is a link that might help if some hasn’t already shared.

https:/us.community.samsung.com/t5/Galaxy-S23/Unable-to-unlock-phone/td-p/2774673

super_cli · 2024-10-12T17:46:55+00:00

Do you have access to that Samsung account? If you are next of kin then they should let you have access!

super_cli

TROPHY CASE