Massively Updating to Mac OS X?
Zerocool3001 asks: "I work for a school in California that uses all Macintoshes. All of the machines have Mac OS 9 on them. We would like to upgrade to Ma OS X 10.2 and we have a net install server with disk images ready to install. However, it appears as though net installations of disk images is not possible in Mac OS 9. If you have any way to install a disk image over a large network to about 500-700 computers, we could definitely use the suggestions."
When I was at school our Macs were cloned from a master server every shutdown. The software they used was assimilator. I don't really know if the master image has to be OS 9, or if anything will work. You can download assimilator's PDF manual on the page I linked to. Maybe this will help. You would definitely have to get the assimilator executable into the startup or shutdown items folder of the target machine though. But I suppose that would be a lot faster than actually installing OS X.
Hank! White!
Instead of asking people here on Slashdot...
I'm sure that for these kinds of numbers, in a high-profile installation... -someone- over at Apple would be interested in making things go smoothly for you.
I'd imagine that you could get help directly from Apple - and probably better than anything you'll find here.
Wouldn't it be cheaper and worth the effort to do a netboot setup? THen you jsut go around to all the OS 9 machines and set the startup disk to be netboot (or whatever they call it I forget) and reboot :-).
Of course you might want to invest in gigabit ethernet and some switches at the same time. Other than that, you'd have to around to each machine individually with the OS X CD.
/* oops I accidentally made a comment, sorry */
Based on your description, NetInstall is out of the question, so really all you can do is ASR. It's a bit trickey to get working correctly the first time, but when it works, it'll do a very fast setup of the machines in question. You'll have to do some digging though, as there several different ways to go about it on both Classic and X machines. Apple.com is probably your first best friend here.
Aside from that, from what I remember, you can do some openfirmware stuff where openfirmware will allow you to remotely boot off of a disk. This way, you could automate most of your install. The problem with all of this of course is the hardware you're using - automating this all means lots of scripting to figure out which drive, save, etc.
Regardless of any of the above, contacting Apple for a more direct contract on the install might be your best bet. Course, if you're cheap, you can always hire some students (i.e. get 3 hours of semester credit or whatever) to help do updates.
A couple of years ago CFEngine seemed like a good way to go to maintain large LANs, including not only OS but application updates. It became a GNU project. I haven't kept up, so I don't know present status. It did require initial installation of a small monitor tool on each machine. But that might be accomplished remotely by adding it to each machine's startup folder.
Staying with pure Apple methods, you might be able to add a network drive to each computer's environment, than remotely modify/replace the StartupDisk Control Panel to boot from the network drive, which would then run a script to wipe the main disk and install the new OS.
It's easier to be a result of the past, but more fun to be a cause of the future! http://www.spacefinancegroup.com/
But this might be of use to you. Google is your friend. http://www.macos.utah.edu/Documentation/MacOSX_Dep loyment/Specifics_ToolsUsedDeploy.html
The NetInstall process doesn't have anything to do with the OS the machine is running. It's just a netboot that happens to run an installer instead of a complete OS.
The hardware you are running on makes a difference, though. It's best if you've got a B&W G3 or slot-loading imac (or better). These machines support "dynamic" netbooting... they also added the nice feature of just booting the machine by holding the "N" key.
If you have older machines, then you have to be proviging IP Addresses (via DHCP) from the server that's doing the Netboot/Netinstalling.
Firewalls can also come into play here. You have to have the appropriate port for NFS, TFTP, and Bootp open in order to Netboot/Netinstall OS X.
I hope this helped...
NetBoot is possible from OS 9. I run an Xserve (with 10.2 server) and have been able to do it since I got the server. If you read through the NetBoot portion of the OS X Server Admin Guide (found here: http://www.info.apple.com/kbnum/n120174). You should see that you need a specific (newer) version of the Startup Disk control panel. I believe they say that it comes on the server software CDs, but I got it from the latest OS 9 system software of a G4 tower. I would guess that you need to be running OS 9.2.2, but I'm not positive. Most of my troubleshooting CDs are still booting OS 9 and I needed to be able to reboot from them to a server image. It's worked well for me, so far.
1. Do not taunt Happy Fun Ball. 2. Do not eat iPod shuffle.
I have set this up on our small office network (30 Macs; 100Mb switched; xServe) and it works great. I'm a part-time tech person; no terminal.
e store.html
Go here and get NetRestore:
http://www.bombich.com/software/netr
Go here and download the video, NetRestore in Depth:
http://macosxlabs.org/webcasts/index.html
The only thing I can add is that your clients need to be ugraded to OS 9.2.2 to netboot.
With Netboot and NetInstall, coupled with Network Home Directories, I figure I can cut my time spent doing tech work in half. (I'm being optimistic, but still...)
From their site:
I personally use ASR to deploy systems. Setup a base image and roll 'em. More info at http://www.bombich.com/mactips/index.htmlApple has K-12 account reps who would LOVE to get in on helping a school update that many machines.
Try calling the Educational Support # at 1-800-800-2775 (APPL). Usually there are individual K-12 reps for each area or school. See if the folks at Educational Support can get you in contact with that person. Honestly, with this kind of volume, they could probably make it much easier for you, both logistically and financially, if you get what I mean.
Also, might I suggest as a resource:
http://www.apple.com/education/k12/
1) make sure netboot is working properly on your server (you can use the default OS 9 image that gets installed with netboot to test) 2)build your image on your most recent machine 3) Use Mike Bombich's Carbon Copy Cloner to make an ASR image (it's in the preferences) and save it to another drive. Then load it onto a sharepoint on your server. 4) Install Mike Bombich's NetRestore onto the server. Use netrestore helper to make an Netboot image that boots to ASR. (configure the settings to use your asr image) 5) Netboot the machines to your netboot image 6) Run ASR (you can automate this) Easy as pie (Although I can't bake :))
This article is about the Menlo School, and was posted by a friend of mine. Menlo has more like 100 or 200 computers, so the task isn't really quite as gigantic as it seems by the article. Still...
TANSTAAFI: There Ain't No Such Thing As A Free iPod.
Have you looked at Apple Remote Desktop? It supposedly supports remote software updates and installs.
Here's hoping you see this message in time, the morning of Tuesday May 20th Apple is hosting an interactive webcast on using Apple Software Restore.
You could have the kids do it as part of a class - great learning experience!
Of course, there are soooo many things that could go wrong....
=)
than you can say pron!
We would like to upgrade to Ma OS X 10.2 and we have a net install server with disk images ready to install.
Man, I wish I could've upgraded my Ma. She was stuck in the 60's.
Sound waves should be free!
1. open a terminal and type
:) ) keep it close for reference.
/Volumes/MacDrive -erase
/Volumes/MacDrive -erase
man -t asr
(this will print the man page to your default printer)
2. read this manpage (then read it again
3. setup a system in the way you want it to be cast, OS9, OSX and all your applications then make a disk image of it. (see the man page)
4. boot to OSX via, NetBoot, or an external firewire drive.
5. Cast this image either via http or local file system.
#local filesystem method, pretty fast over firewire
asr -source Library.dmg -target
(watch out for the trailing slash on the target drive)
#Network over a webserver
asr -source http://10.5.5.1/images/foo_science_lab.dmg -target
As much as i loathe OS 9, i've found that most boxes form the OS9 day run kinda slow w/ OSX installed. And more so, they take forever to boot. it's my opinion that it's more than woth the trade off to work woth OSX(mmm...), but make sure that everyone who will be using these agrees. if they're alwaysd on, though i'd say go for it.
You should be use a few FireWire hard drives, with 10.2.6 installed on them. Boot the machine, and either use a program like NetRestore to erase/restore a disk image of a Master 10.2 install onto the drive or roll your own shell script to do the same. The advantage to FireWire is that it is really fast, copying about 1 GB per minute from a 4200 rpm drive. Also, when you are doing 10 or 15 machines at the same time, you don't have to worry about the network bogging down (or your server!). The man page has some excellent information on this, simply "man asr" in the terminal.
Also, if you are putting OS X 10.2 on older machines you probably have to upgrade the firmware first. Someone already has to walk to the location to reboot the machine and probably make sure that a teacher didn't copy their grades to the Hard Drive (that you will be erasing in a minute). Also, once you get the image restored onto the machine, there are a few preferences that are set on a "ByHost" basis - tied to the MAC address of the machine. Things like energy saver settings, and Remore Desktop being enabled. The latter is important if you want to be able to manage your machines later on without walking across the campus.
You should contact Apple and connect with a System Engineer who can work with you to make your deployment a whole lot smoother. Moving over several hundred machines to a new OS is no small task, but a little automation can go a long ways toward making it a manageable process.
If you want to keep it really simple, set up a machine with Mac OS with a single partition of size smaller than any of your disks (say, 5G) and do an install on that. The startup script would do something like:This copies the partition table, the boot stuff, the 5G partition, and then some extra blocks that don't matter.
Afterwards, your script should create an additional partition so that people can use the remaining disk space on their machines.
Alternatively, you can create the partitions dynamically in a script and then copy the file system contentsThat's a lot more work to set up and debug, however.
I used to work at a large University. When we upgraded from 8 - 9 we planned a whole bunch of ideas such as directory logins, samba servers home drives etc.
Apple came and helped us out with planning. Yes we were buying about 100 new macs but they stills helped us out over several days for free. Talk to your apple rep. Apple corp employ many education specialists just for this sort of thing.
Use NetRestore and NetBoot on your OS X server for rollout, then maintain them with Radmind. NetRestore is much like Apple Software Restore, but better, and Radmind is a replacement for RevRDist or Assimilator, but again, much improved. I've used them all and managing OS X this way is so easy is ridiculous.
http://www.jamfsoftware.com works natively in 9 or X. easy, automated package creation & a modular install process where you can select/deselect packages.
Poor baby, Did the good Father make you angry? That's too bad. I know you are probably used to biting a pillow, but maybe this time you should just go cry into it.
I smell like beans.
This is all really clearly detailed at Apple Software Restore. The idea is to create a bootable disk image with all the software (apps, fonts, etc.) you want to deploy, put it on a file server, and then boot into the target machine with a FireWire disk or CD with Mac OS X on it. This is so you can go into Terminal and use the command-line tool to run 'asr' to install the disk image.