Hyperv has shit automation support and doesn't provide native apis to work with. You need vmm or some third layer to talk to. That's where the shit starts
The problem is what happens if they pull a VMware. They could just bump up licensing costs so that you end up spending the same as you would to be in the cloud
I usually figure out what it is that my users are trying to accomplish, which is usually something absolutely insane to buy Photoshop for, like resizing or adding text to pictures, and steer them toward some basic app like Paint.NET.
We are an enterprise manufacturing company. We have lots of hosts on process networks not connected to the internet. Seems like the subscription license won’t be compatible, so we plan to seriously look at Proxmox for those in the coming years as we replace hosts.
For our datacenter, we decided to move everything to Azure. This decision was in the works before the license change, but the acquisition by Broadcom and their track record certainly played a part in the conversation.
For our site hosts, we are looking into Azure HCI or possibly Hyper-V, especially since these sites don’t have many VM’s and don’t need features offered by VMware.
If you’re an Azure expert and are looking for a new job, send me a message. We’re hiring.
I have experience with Azure IaaS, but am certainly no expert. Managed like 5 VMs max. Great with PowerShell. Wrote a script for all of our on prem servers backed up to blob storage to recover to Azure in case of natural disaster. Fun project.
I work for Disney and we're in the process of migrating all VMware boxes in our 3 data centers over to azure. We decided not to renew our contract with them. Guess it wasn't just us?
Have your group ask microsoft what the charges for Azure will be for your year 3 year 4 and year 5 commitments.
100% sure the Azure rep will gag on whatever they have in their mouths at that moment and start deflecting. If MS can fuck the US Government in a 10yr Azure contract, odds are pretty high they’ll do the same to Disney.
Source: Our company bought into O365+Azure+ADFS at a good rate for 3yrs, then got burned by MS once the honeymoon was over. They’re not going to make it fun for you all once your contract ends.
We have an entire set of rules for mandatory time off, max hours between rest and sabbaticals between large projects, and it is still a struggle to keep staff healthy. It is just a brutal line of work. It takes a toll on your body too. Shit, I had to get four stents on my heart at 44 and cancer at 49.
Good. I can't stand the insane communities on Reddit. It's full of clickbait and grifters. There's small communities are what the Internet is about. We should be happy.
We need competition plain and simple start finding “good enough” and promoting it because at the end of the day if it’s good enough it’s solved the problem. Like gimp, it doesn’t have the bells and whistles but it’s good enough.
Not knowing who is on here, this is most certainly NOT a safe space. OP should not share if they think it would be detrimental if that information got out.
As soon as everyone signs their zones with DNNSEC, we can implement DANE to use self-signed certificates safely, and all our problems will go away, world peace will be achieved, and food will taste better.
I still don’t understand the resistance to DNSSEC. It’s just the right solution to the problem (or something like it is). Most of the arguments I’ve seen against it are just “the governments and three letter agencies control the TLDs!!” which like… Sure. But even with the usual CA infrastructure all of the trust depends upon the TLDs anyway. Like… If you are a TLD and control the root DNS servers you can obviously redirect any domain to wherever you want and get a LetsEncrypt certificate for any domain under the TLD anyway? Maybe somebody would notice, but it’s probably just as likely that somebody would notice them messing around with DNSSEC (and then there would even be cryptographic proof of foul play?)
Me too. Unfortunately, given that they’ve got decades of work to catch up to, and a much looser (and I assume smaller) team, I don’t think they’ll achieve feature parity in time to be useful.
Actually, it’s already useful for some folks. Sure, if you’re after a 100% feature parity to say XP, that’s not happening any time soon, but there are already folks using ReactOS in niche cases like embedded systems, especially in old systems like CNC machines, scientific instruments, industrial/factory machines and so on.
The main problem with old machines like that isn’t that they were running Windows NT4 or XP, but the fact that the hardware they’re using is breaking down and it’s getting increasingly difficult to replace it whilst maintaining compatibility. ReactOS is basically the only “supported” OS that still is compatible with those old specialised drivers and apps, while still being compatible with somewhat modern hardware.
Sysadmin
Top