Both incorrect, unfortunately.
What makes you think you aren't the one who is incorrect?
Both incorrect, unfortunately.
What makes you think you aren't the one who is incorrect?
The worst part is the people making all the decisions see the iOS devices and shiny things like the Air and think they are cool. Then they come to the technical people and tell us to make it work with our existing infrastructure, but they have no idea how difficult it is.
This is why the "technical people" have a job. The users do not exist to make your life pleasant. You exist to make the "next thing" work. Deal with that or find another profession.
This is why the "technical people" have a job. The users do not exist to make your life pleasant. You exist to make the "next thing" work. Deal with that or find another profession.
This is why the "technical people" have a job. The users do not exist to make your life pleasant. You exist to make the "next thing" work. Deal with that or find another profession.
Unless it's the boss telling you what to do, what users "want" can be ignored. It's not the IT department's job to accede to the receptionist who wants to use their iPhone.
For the price difference between a PC and an MBA you make an employee feel enormously valued, and that alone will benefit the business. Having an employee who feels the company cares about employees vs. an employee who thinks they don't give a **** will make a difference in productivity and quality of the work.
I've done a lot of IT procurement over the years. If either myself when purchasing, or someone coming to me for approval, stated a benefit for buying a Mac over a PC was that it would make the employee more valued, they'd get laughed out of the door. I'd ask them to justify the extra initial cost, plus the cost of running non-standard hardware in a corporate environment, against the already known cost of issuing standard hardware.
Over the years I can only recall a handful of times when an employee has requested a Mac, and with one exception they have never been able to justify it. The one exception was for a CFO who held the purse strings anyway.
I've done a lot of IT procurement over the years. If either myself when purchasing, or someone coming to me for approval, stated a benefit for buying a Mac over a PC was that it would make the employee more valued, they'd get laughed out of the door. I'd ask them to justify the extra initial cost, plus the cost of running non-standard hardware in a corporate environment, against the already known cost of issuing standard hardware.
Over the years I can only recall a handful of times when an employee has requested a Mac, and with one exception they have never been able to justify it. The one exception was for a CFO who held the purse strings anyway.
As a small-time IT Manager (the company whose infrastructure I manage does ~$100MM revenues worldwide) I can tell you that this blog post is misleading at best.
Apple does everything you can think of to discourage its' products from entering the enterprise. I have 17 macs, running 10.5, 6, and 7, and they are a farce from a management perspective.
Oh, wait, also from a functionality perspective. And, most importantly, from the perspective of available applications.
To paraphrase your god Steve, with whom I once had a personal email exchange, software is the most important thing. Software is what matters.
And macs just don't have software.
ERP? Not really
CAD? Not really
Office? Pain and suffering
Joining a domain and accessing services? Like a trip to the dentist for my users every single morning.
Management? They are harder to manage than a 1990's Windows domain.
The servers are beyond a farce. The servers are well into the absurd, and I'm glad they finally stopped referring to them as servers. They truly are just a set of cheesy services overlaid on an overpriced desktop.
This blog post took away most of the remainder of my respect for MacRumors. It's clearly owned by someone who owns a lot of Apple stock and has an agenda. Don't believe the hype.
PS I was a die-HARD mac fanatic until I had to manage them in the enterprise. I took this job specifically because I got to manage mac clients and XServes, which I thought was a dream. Holy crap was I wrong.
Unless apple can get to my office locations in < 4 hours to do any onsite maintenance repair work, Apple will never be my vendor of choice in the Corporate environment.
If either myself when purchasing, or someone coming to me for approval, stated a benefit for buying a Mac over a PC was that it would make the employee more valued, they'd get laughed out of the door.
I would think that would be pretty easy.
"I'm slightly more productive when using tools which with I am more familiar. I make $30,000 (or $40,000 or $50,000 or whatever) per year. Even a marginal increase in my productivity would be far more valuable to this company than the costs of purchasing and maintaing the hardware. Get your head out of that box, IT monkey."
First - there's more to someones existence.
Second - in defense of IT people - The users don't exist to make life UNpleasant either.
And at the end of the day - there are situations which simply cannot be solved or can't be solved in a practical matter. Sometimes the work arounds are more complicated than doing without.
Your "deal with that or find another profession" is pretty obnoxious. I get your point. And your message might be valid - your delivery was rather harsh.
Why do you assume a user should have to justify a Mac over a PC. Why shouldn't IT justify why they insist on giving users PCs over Macs?
Unless it's the boss telling you what to do, what users "want" can be ignored. It's not the IT department's job to accede to the receptionist who wants to use their iPhone.
I work in IT. If I hire you to make what the boss wants "go", then you make it go. Reality is harsh. I never said the users exist to make life unpleasant, I said IT personnel are hired for a reason. Far too many IT personnel are more than happy to push their idea of a solution out to users, but not accept the business direction because they disagree. Disagreements are fine with a sound reason, but in the end, the business makes the decision, not the IT employee.
I sincerely doubt these users are switching to Apple devices without approval by the boss. Do you?
Why do you assume a user should have to justify a Mac over a PC. Why shouldn't IT justify why they insist on giving users PCs over Macs? And you can't use the argument that "all our software runs on PCs" - I'm talking about reasons why an entire PC ecosystem is better than a Mac-based operation.
It's give or take in IT. Sometimes, it's not even a matter of technical "can-do", but corporate policies in place for information privacy, secrecy and security. Some devices/software just cannot be made to comply with the policies sometimes and users need to understand that's out of IT's hands.
----------
Even if it's "the boss", if it's not "the top boss", then HR has the final word on acceptable corporate policy and Acquisitions will say if budget can be alloted to the project or not and "his boss" will tell you whether the production gains for "the boss" are worth the spending that will be required to implement the solution.
IT installs what was acquired after a bidding process with strict requirements based on a customer needs analysis. If your IT works any other way, it's flawed.
Customer comes in with a problem to solve. Requirements are drafted for the solution. Bids are opened up for software/hardware acquisitions based on these requirements (and are quite vendor agnostic).
If the "requirement" is "Mac", then by god, that will be on the requirement sheet. But at the end of the day, "Mac" is hardly a requirement, it's not a "need", it's a "want".
I'm the first one that "wants" a Mac as my corporate desktop. I'm also the first to realise that it's hardly a "need".
----------
I do. I bring in my Mac clandestinely.
As I said originally, if the business decides to move towards Apple, and IT is tasked with making it "go", IT will make it go. There are solutions to better integrate these devices into the environment. IT can make a case against the move, but it is a business decision to pay the price for the switch.
If it's "my boss" I'm going to start implementing and integrating what I am assigned. I'll tell him the pros and cons, but once he's made that decision, my only recourse is to either go over his head or do what I'm told. You make this sound as if some rogue employees are trying to force this on the company. While it does happen, we usually deal with those cases fairly swiftly. Your manager telling you the company decided to move in a new direction and you need to implement a solution is not the same thing.
How is that different from what I said? Also, you don't determine the need, the business determines the need.
Good for you. If you bring your Mac clandestinely on my network, you won't stay connected for very long.
What did you do prior to LCDs ?
What makes you think IT makes a case against moves ? We certainly don't. Again, bidding process, requirements from customer need analysis, etc.. etc..
If we're at the "implementation and planning" phase, it's quite too late to make a case against it. That is to be done during the bidding process, and all the requirement justifications to displace a bid need to be based on requirements the bid fails to meet.
No, if my boss comes up to me and asks me to do something that's outside of corporate policy, I'll tell him it is and that it's probably not going to be possible.
If he insists, I'll go through change control with all the documentation on the change he wants me to implement, as is the proper procedure for a deployment and I'll have them tell him no instead. If he still doesn't get it, then I can tell him I tried and that it's out of my hands and needs to go higher up himself to get his change approved.
All I've wasted in about 60 minutes of my time documenting the change and submitting it for approval.