Topic: Linux Distributions
Topic: Linux Distributions
In the first place, was there POINTING OF FINGERS or blaming for problems ? It should be alright for people to try to define problems and identify how and why they arise -- in order to shed some light over problems in need of attention. Keeping silent about views cannot lead to any improvement at all.
If the solution is to tell people to find another company to work with, then that will discourage the other people from expressing their views freely in order to improve the company. I would rather collate all views, check the accuracy of allegations, communicate whatever should be known about the problem, and thank all contributors for expressing their views about the problems. But it will be also wise to inform everybody about the findings after investigating details about the problems being experienced and analyzed by different members of the industry.
The answer to fault finding is not another finger pointing back. It is diligence. Then follow up with shedding more light after careful review and investigation of various comments.
Wonder how much this schill for Microsoft is getting paid? Of course MS should get the blame. They build their software and force everyone to comply doing it their way, so ultimately every problem ends up pointing at them, as it should. Engulf n' Devour is their tactic, if they would be nice about it and not play dirty games in the play-yard, we wouldn't have to put up with blame-game stories. Customers pay enough for the software, why should they have to pay in addition for service too? Service should come with the software and MS should respect the customer.
Agree if Microsoft or any vendor is causing the problem that needs to be identified and corrected but first the problem itself needs to be defined.
Any vendor can be replaced but I've found that often that is like tossing the baby out with the bathwater and that the easier path is to actually focus on solving the problem together first.
In my own case, we had a joint project with Microsoft and our team was constantly saying that the Microsoft folks and technolgy was worthless. When I personally looked into it the real problem seemed to be we couldn't keep a spec constant for more than a week and we were using people who didn't like or know how to use Microsoft tools. It didn't help that the Microsoft team wasn't forcing us to lock down a spec so they weren't blameless but we were most of the problem.
We had a similar problem with Notes, couldn't get it to work, turned out the company we hired to implement Notes for us was learning how to implement Notes on our nickle. No wonder it wasn't working.
Diagnose the problem first and then propose a solution rather than blame the provider first and let them defend their position. I think the former is simply the better path.
You "suspect" but I don't see proof. Obviously both company A and company B have incentive to blame the other when something that should work is not working, but how can we know who's right? As you mention, badmouthing company A does no good. Sympathy towards company B is not helping either.
I don't know if they did, but if SanDisk were to publish their specs then Open Source guys could work at it, if they are too lazy or if they don't have the resources to make it work themselves. Once an implementation is working on Linux (FreeBSD, BeOS, or you name it) then it is a software issue and there is no excuse left for Microsoft.
The comment you make about this less than honest consultant seems to imply that Linux in the corporate world is some kind of a scam. It may be the case, but I know for sure it is not always the case.
Again, the answer is in the proof.
Actually anything can be a scam depending on how it is done. I can recall AT&T saying that Windows 95 would save $1,000 per year in desktop support. The average annual cost of desktop support (using Netware as a base) at the company I was working at when they said this was around $500. We wondered if they were planning on writing us a check or if money was going to start flying out of PCs butts.
The example was not intended to diss Linux, it was just the best one I had to prove the point.
So hey, MS is not always to blame... what about the vast number of times it is? Unreproacheable, intentionally bureaucratic in interfacing help, but mostly walled-off from dissent and hidden from the often justified rage of people with business/money/time lost, MS nevertheless greedily sucks up for free all the expertise advice of the thousands of skilled administrators who endlessly and tirelessly come up with fix after fix after fix and post it to their beleaugered colleagues on forums. Make money off other people who are fixing your screw-ups. THAT'S how to get rich... oh, they did... IT people fix stuff. And don't have time to cstalogue the 1000's hours they do free making MS run as advertised.
Rob...... lol! That is why I'm a loyal subscriber! I'm debating if it would be a good idea to send this to my boss, who consults on our infrastructure security and other issues with this guy who worships LINUX. Not only that, he is one of those IT nutbaskets stuck in the 90's who blames Microsoft for everything. Great article!
Topic: Microsoft
Microsoft has cornered software market with its Windows product line and associated apps
Blog: Is Integration Key to Microsoft's Success in the Cloud?
Article: Microsoft's PowerPivot Puts BI Users More in Control
News: Microsoft Helps Discover Flaw in Google Plug-In for IE
Related Topics
Linux Distributions
Lowering Your IT Costs with Oracle Database 11g Release 2This white paper identifies the key capabilities a database management solution needs to successfully deliver more information with higher quality of service, make more efficient use of IT budgets, and reduce the risk of change in data centers.
Software Forum: Information On Demand Virtual ExperienceThis interactive virtual forum presents leading IT experts providing the insights you need to turn your information into a strategic driver for innovation, business optimization and competitive differentiation.

The technology tips and tools to enhance your ability to respond to business change with ease and success.

Best practices to optimize computing ability while minimizing power costs.

Comprehensive power protection solutions.

Products, management tools, and industry insights that enhance the value of virtualization for your business.
Windows 7 Upgrade Project KitMoving to Windows 7? The Windows 7 Upgrade Project Kit is the ideal support tool for managing all phases of an organizational upgrade to Windows 7. The tools and templates in this kit will help you develop a strategy and map out the implementation tactics which link your Windows 7 deployment to your company's bottom line.
The Complete IT Policy KitDownload a comprehensive bundle containing over 40 IT policy templates. Each can be modified to align with your specific business requirements. Complete instructions are included.
" The web contains vast amounts of information, but not everything worth knowing is on the web. An enormous amount of information resides in people's heads: millions of people know useful things and billions more could benefit from that knowledge. Knol will encourage these people to contribute their knowledge online and make it accessible to everyone."
Your blog is KNOL by itself and we are priviliged that you share such wisdom with the rest . and when I read " This provider had low-balled its way into the account and then manipulated the situation to make both Dell and Microsoft look bad so it could do a very expensive migration. This migration entrenched it into the account and vastly increased revenue from that account. It was brilliantly, if not too honestly, done" I have no doubt left in my assumption , what a vast storehouse you are . Please let us learn from your experience and share if you will , as to how this provider actually did what it did . If only we can help us better protect ourselves .
Thanks & Regards