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?"
that is a whole lot of gay to be rolling out
Man, I'd update your resume because they won't need you anymore. Or, insist that some MS products are still around because of ... of...email ...no...um...well, that's your problem.
It's NOT me! It's the meds! I'm on 1000mg of Fukitol.
....fucking Apple Cinema Display
Damn! Is there a video? I tried googling "apple cinema display fucking" and "apple cinema display porn" and nothing.
So, what was it fucking? The DVD drive? or the USB port?
It's NOT me! It's the meds! I'm on 1000mg of Fukitol.
Isn't this what the genius bar is for? Ask them. I'm sure they do this all the time.
400 dollars an hour?! What are you using? Lawyers? How does that work?
1) Monitor breaks
2) Sue Apple
3) Free monitor?
For justice, we must go to Don Corleone
Agreed. It's the only OS for seriously large botnets.
Just hire yourself a bunch of guys in black turtleneck sweaters and the computers will basically install and configure themselves.
If libertarians are so opposed to effective government, why don't they all move to Somalia?
This is a Big Mac deployment? Sounds like a job for my tummy!
Oh, the fail.
Among my experiences (mostly historic): ... get coffee as much of the btree is traversed
-Some shims/extensions installed to compensate for hardware issues were unconditionally loaded, even on hardware that didn't need/couldn't boot with them. That made reusing disk images on slightly different hardware revisions... fun.
-Wake on LAN should do... stuff. Consistently.
-I've autodiscovered a shared printer which I'll share with everybody. I've autodiscovered a shared printer which I'll share with everybody. I've autodiscovered a shared printer which I'll share with everybody...
-What's that? The mounted ASIP resource disappeared for a few seconds and now everyone's trying to reconnect? At once? And their workstations are beachballed until the share comes back, even though they have no open resources on it?
-Restoring resource forks from backup always works!
-What do you mean by "the QuickTime update broke the AppleScript methods for a completely unrelated subsystem"?
-I've autodiscovered the same printer share which I'll share with everybody...
-ls -lr on a folder with a few hundred files in subfolders
-I've connected to this resource before, so I'll make a new alias for it with a subtilely different name
-What do you mean you've deleted stuff to the network trash and now it's locked?
-I've autodiscovered the same printer share which I'll share with everybody...
There are 1.1... kinds of people.
To continue your analogy, when your driver has a heart attack (or you get sick of him and get rid of him), Linux will crash into the next brick wall since you can't find anyone who knows your custom system, while it's very easy to find someone to keep your Windows running at 60mph.