Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'A basic how-to for using System Image Utility' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A basic how-to for using System Image Utility
Authored by: kendals on Dec 24, '08 10:42:58AM

I used SIU on my systems at home..this is my setup:

Server hosting SIU image: Mac Mini G4 with 1Gb RAM
client macs: Intel C2D iMac, C2D Macbook, 2 G4 Mac minis

This works perfectly for me, BUT I do have one problem..

I tried to take my image (again, which works perfectly on PPC or Intel macs) to my parents house and put in on their server... the client Macs never boot, they always get the System Restart gray screen. The only difference between their setup and mine is that they have a Intel CoreDuo Mac mini..

Do I have to create a separate SIU install just for their environment?

[ Reply to This | # ]
A basic how-to for using System Image Utility
Authored by: leamanc on Dec 24, '08 11:28:11AM

Short answer: Yes.

Long answer: No, but you would need to modify your image to include components for a Core Duo system. I imagine you imaged off of a Core 2 Duo system. Unfortunately, the transparency of PPC Mac OS across different systems is long gone. For best results, maintain an image of each different iteration of the Intel architecture (CPU and video cards).

[ Reply to This | # ]
A basic how-to for using System Image Utility
Authored by: BiL Castine on Dec 25, '08 06:26:08AM

i image a lot of disparate systems: G4 PowerBooks, G4 PowerMacs, G5 PowerMacs, Mac Pros, and MacBook Pros from a single 10.5.x image. they key is to build your image on the latest available hardware to insure you have all of the platform specific tweaks. once the next system update comes out you can update your image and it will support the latest hardware. for example, my 10.5.5 image wouldn't support the new unibody MacBook Pro until the 10.5.6 update came out, now it supports all machines again. it's likely that if you are using 10.5.x you just need to update to the latest system release.

also, be sure to to delete machine specific network configuration files from your image:

[ Reply to This | # ]