231–240 of 402 posts
The licensing costs associated with MS products is stupid high. In analyzing the budget for a county, across all departments the line item for MS was ~$322K for just a 3 month span (o365??). It was the top line item for the quarter, beating out health insurance line related line items.
The licensing costs associated with MS products is stupid high. In analyzing the budget for a county, across all departments the line item for MS was ~$322K for just a 3 month span (o365??). It was the top line item for the quarter, beating out health insurance line related line items.
Earlier quoted context omitted.
The fact that it would even go down and it requires online connection to vacuum up my data is such a bananas level oversight from MS. That company, man, that company.
Does it? I thought local installs still function offline for up to 48 hours, as long as you haven't passed the last synced expiry date? At least, that's how it used to function way back when I used it and had a not-always-online connection.
Earlier quoted context omitted.
The phrase is, "nobody ever got fired for buying Microsoft." It's descended from the same phrase, applied to IBM, when they were the power.
But the impact is deeper nowadays. What was the worst that could happen when you bought IBM back then?
Earlier quoted context omitted.
The fact that it would even go down and it requires online connection to vacuum up my data is such a bananas level oversight from MS. That company, man, that company.
Does it? I thought local installs still function offline for up to 48 hours, as long as you haven't passed the last synced expiry date? At least, that's how it used to function way back when I used it and had a not-always-online connection.
Microsoft is not my favorite company. But the only reason O365 has been down for days is when customer integrations (identity, security stuff, VPN rules, etc) break. That was even true in the early days before 365 branding. Source: I’ve been accountable for 250k+ user O365 environments as a customer director or VP for over a decade.
Earlier quoted context omitted.
The goal is not "superior", the goal is "USA can't kill our infrastructure pressing one button"
The goal is also to have a usable cloud on which you can efficiently develop software. Otherwise we can simply go back to paper.
You don't need a cloud to efficiently develop software. I've worked in companies that were running kubernetes on prem. It was a PITA for kubernetes ops but from a developer perspective it wasn't much different than using the cloud in a large company.
Cloud is very flexible for very small orgs that have little processes but once you get into a certain size with lots of processes, privileges separations and nomenclatures, it becomes so bureaucratic all flexibility of a cloud mostly disappear.
Earlier quoted context omitted.
As someone who split his time 50/50 between AWS and vmware based instances, i cant really think of anything we run in AWS that is not eventually supposed to go back on prem when we have stabilized the specification and lifecycle expectations. And who could not have gone in on prem if we had been willing to spend capex upfront(which would likely had led to lower lifecycle costs). The last time this debate came along m…
> i cant really think of anything we run in AWS that is not eventually supposed to go back on prem Hod do you handle multi-DC, multi-AZ resilience? What are you using instead of IAM policies that cover every resource? (Asking unironically, would just like to know. I worked at cloud-centric companies for last 15 years or so.)
Given that my experience with AWS is to use the same application level cross region resilience techniques im used to on prem(i have worked with high end unix boxen most of my carear) im genuinely baffled when people start talking about cloud resilience as something magical, and nearly all our traffic happens inside of an private network(MPLS/VPN) that stretches across the different sites.
I really haven't seen any magic multi-az resiliiance in aws that dont have an onprem counter part.
None of this is in house whitebox hardware but relatively standard solutions from established vendors(VMware recently started abusing their near monopoly so everyone is looking for/at alternatives like proxmox, xen and nutanix but arent ready to move just yet).
Earlier quoted context omitted.
This is precisely why Microsoft freaked out when Germany last tried this. It led to them inventing this nebulous "TCO" concept wherein they massively overestimated the costs surrounding moving to FOSS in order to try and convince clueless managerial stakeholders to stick with them.
To be fair in certain cases the cost might be very high and considerably higher than whatever the license/subscription fees paid to MS are. e.g. Libre Office doesn’t really have a drop-in replacement for Excel (for non trivial use cases. To be fair it still might be sufficient for the majority of users, but that would mean that some proportion of your workforce has to stay on Excel/Office which kind of beats the whol…
Earlier quoted context omitted.
Yeah last time with Munich they moved back to MS after MS just so happened to move their HQ to that state. Microsoft is clearly keen to avoid this becoming a thing. If governments can shift successfully then so can businesses https://mspoweruser.com/microsoft-germany-moves-into-a-new-h...
I remember that one... In the end the harsh truth for MS is that a guesstimate of 99% of all offices and administration users are using and, most of all, only need 1% of the features Office (including Excel) do offer. The other harsh truth is that those using more advanced features are typically creating spreadsheets full of errors and bugs, which should be better rewritten in dedicated apps. The world is using MS Of…
My experience has been the mirror opposite. I’m doing finance/accounting day to day but can also code. The attempts to replace excel with custom apps were consistently absolute horror shows full of consultants, endless meetings, coders not understanding finance nuances, endless parallel running, budget overruns. And then months and a couple of 100k spent later all to duplicate a spreadsheet someone had originally slapped together in a day or two.
Not wildly attached to excel but now actively steer clear from custom app projects due to career risk of being in proximity of these.
It’s the same as big SAP projects once the “customizations” start. The implementing teams incentives are the precise opposite of the business. Bill as much as possible, extend project timeline, add more features and widgets, make things seem more complicated than they need to be, pull users away from their work to test, cater to the execs with dashboard instead of the team in trenches, endless CYA processes camouflaged as “end user acceptance”, office politics shenanigans to promote the solution etc. I’d much rather debug & streamline a spreadsheet than deal with all that.
I do agree that spreadsheets tend towards chaos as complexity increases though…