There is not a single state in the USA where using the right lane to pass slower traffic in the left/center lanes is illegal. It is allowed everywhere.
But in that case, Microsoft still has to support and maintain the Windows OS running within the Azure Virtual Desktop. If they're doing that, why not support it on the end user compute as well, and get that sweet sweet recurring Windows license revenue from businesses?
We tried this, but we just got more defects, because the Devs lost what little Ops knowledge they had. Where previously Ops would have to involve Devs, now that Production Support has some Dev knowledge, suddenly they get the blame for everything. Devs no longer have interest in things like "reading log files"; they just ship any problems over to Production Support.
Any day, I (as a manager) would prefer to have an experienced Developer do a Production Support role, rather than a cheaply obtained non-engineering campus graduate hired as "Tech Ops" resource to do Production Support on complex, mission-critical systems.
It is a bad idea for a company to give shoddy after-sales support to customers, because they would then lose the customer's trust and relationship in the long run. No customer wants to see their production systems have frequent incidents caused hours or days of outages.
Vendor companies ignoring investment and support for Production Support on their Products/Services, do so at their own peril.
In fact, canny companies have realised the real money is not in upfront cost, but in volume billing (billing/invoicing, based on monthly transactions counts, number of users/licenses and tiered rate card), so they need to have adequate Production Support teams
This is why companies are trying their level best to move existing customers to subscription services (e.g., Office 365 by Micro$oft).
You can find examples that go both ways for both endeavors, anecdata...
The problem in your case is not the dev vs ops split, it's a company culture thing which I'm sure you see play out in more places than this current focus
How does remote RDP/VNC kill AD and Group Policy? You still need AD to provide centralized authentication/authorization. And you still need Group Policy to configure the VMs according to the corporate standards - disk images may work for the initial rollout but not for applying future changes.
That's a KVM role. The idea in the 21th century it's to spawn a personal VM per user. Network boundaries would be defined in hypervisor devel, (VLANs, network share accesses and so on), you would need nearly no GPO's but different WMI setups with options prebaked.
The old NT based ACL's/GPO's and such are obsolete as I said when a cheap Linux KVM server can do tons of stuff by itself and firewalls (even professional ones) are dirt cheap. The old world died long ago.
You shouldn't be backing up profiles, accounts or settings from an AD domain. We should already have instant VM booting (from the network) with everything snapshotted to a working state since long ago.
Network boundaries are insufficient. A file share might need to be read-write for some users and read-only for others. Database access is even more granular.
Different users will have licenses to different software. Maintaining individualized VM images isn't sustainable.
Nah. EVs can often charge ~80% in 20-30 mins. Pumping gas takes me at least 5 mins. You win pretty quickly on this metric unless you do a lot of 200+ mile trips.
"Has been set," not "will be set". We've been operating under the new scheme for months. Despite Powell's protestations, there was no evidence for cutting rates, and lots of evidence for doing the opposite. Unfortunately he gave in to Trump... but that obviously wasn't enough.
reply