Slashdot Mirror
Large-Scale Mac Deployment?
UncleRage writes "I've been asked to research and ultimately recommend a deployment procedure for Macs across a rather large network. I'm not a stranger to OS X; however, the last time I worked on deployment NetRestore was still king of the mountain. Considering the current options, what methodologies do admins adhere to? Given the current selection of tools available, what would you recommend when planning, prototyping, and rolling out a robust, modular deployment scenario? For the record, I'm not asking for a spoon-fed solution; I'm more interested in a discussion concerning the current tools and what may (or may not) have worked for you. There are a lot of options available for modular system deployment... what are your opinions?"
Yeah right, like anyone will buy a network operating system for a server based on shiny pictures and huge features like "mail server" and "calendar server".
It's like they think their regular starry-eyed customers are their target audience with that cute little website they're showing off.
Considering the current options, what methodologies do admins adhere to? Given the current selection of tools available, what would you recommend when planning, prototyping, and rolling out a robust, modular deployment scenario?
Just ask the random basement dwelling momma's boys at Slashdot, reformat their expert advice (using Open Office, of course), and start planning how to spend your pay raise!
Seriously, is this the place "professionals" seek such advice? Scarry.
If you want news from today, you have to come back tomorrow.
1. All deployers should don turtle necks
2. Deployers must act smug while promising the world
3. Now lock down everything...and I mean EVERYTHING that you don't explicitly approve or might not approve or might conceivably hamper possible earnings
4. Delay all deployments and roll out machines in a slow trickle
5. Did I mention that you should act smug
6. If problems are reported, deny, deny, deny them and blame it on misuse by the users
7. ????
8. Profit!!!
Think different.
These posts express my own personal views, not those of my employer
Lets try this again you retarded troll.. Macintoshes are not and have never been more expensive than PCs.
If you actually buy quality equipment it costs more but you don't have to replace PSUs every week. Its amazing that PC bigots think its perfectly expectable that a 300 computer installation has 2-3 computers per week die with PSU and motherboard failures.
I was at a Mac installation of the same size(in a very tough school) and over 5 years about 80 computer needed repair 78 instances of kids ripping the CD trays right out of the computer (if anyone was wondering why macs went to slot loads) one blown USB port and one blown ethernet port. For the same size install of Dells in a public library see above...note i'm not kidding here the Dell tech was in every week replacing Motherboards/PSUs.
Its not funny, unless you consider insulting gay men funny.
There's no word play, no second meaning, nothing clever at all. Like most American comedy.
That's exactly what he said. 0-40 MPH is very easy -- even a MCSE admin could set it up to do that. But once you get to a complicated AD environment you will have a very hard time.
Except the more accurate analogy would be 0-150. Ie: perfectly fine out of the box for the vast majority of environments.
But it can be easily summed up for all MS "technologies": microsoft doesn't scale.
Amazing then, isn't it, that so many huge companies manage to run their infrastructure on them (exhibit A: Microsoft itself).