System Image Utility User Guide
Sep 26, 2018. Seamless control of servers running Mac OS X Server. Admin Tools uses a GUI for ease of configuration. The 10.6.4 version can administer servers running both 10.5 and 10.6 versions of the Apple.
A NetRestore network image allows you start up a Mac and quickly replace the entire contents of the internal startup volume. This type of network image can be based on a Mac that’s already configured with preferences, settings, and apps, and is ready to use, or one that starts up into macOS Setup Assistant.
Workflows that create custom NetRestore network images can use a bootable volume, a disk image (of a bootable volume), or a macOS install app as their source. For example, if you create a NetRestore network image of a Mac and at some point the internal storage device on the Mac fails, you can use the image you created to restore the volume on a new internal storage device.
Create a NetRestore image from a mounted volume or disk image
- In the System Image Utility app on your Mac, click the Source pop-up menu, choose a configured Mac volume, then click Next.
- Select NetRestore Image, then click Next.
- Read the macOS License Agreement. If you agree, click Agree to continue.
- (Optional) Click the Add button to add configuration profiles, packages, or scripts to your NetInstall image, then click Next.The living bible free download. Click the Remove button to remove any items.
- (Optional) Specify system configuration options, then click Next.To learn more about computer naming and ByHost preferences, see System Configuration settings.
- (Optional) Click the Add button to bind the recipients of this image to a directory server, then click Next.To learn more about binding to a directory server using System Image Utility, see Bind to a directory service.
- (Optional) Choose to automatically install on a specific volume and whether to erase the volume, and set the system language.To learn more about automating installations, see Configure automation settings.
- Enter a network disk name and description, select how the image number is to be assigned, then click Next.Page mac dmg. To learn more about defining image settings, see Define image settings.
- (Optional) Select the computer models that can start up using this image, then click Next.To learn more about restricting computer models, see Manage supported computer models.
- (Optional) Click the Add button or click Import to add MAC addresses to an allow or deny list, then click Next.
- In the Save As dialog, choose where to save the image (you can move it later), then click Save.If NetInstall service is configured on an Ethernet network port and the Server app is set to serve images from a volume, the NetInstall service share point folder NetBootSPn appears in the pop-up menu.
Important: Do not attempt to edit content in the image destination folder while the image is being created.
Create a NetRestore image from a macOS install app
- In the System Image Utility app on your Mac, click the Source pop-up menu, choose a macOS install app, then click Next.
- Select NetRestore Image, then click Next.
- Read the macOS License Agreement. If you agree, click Agree to continue.
- Create an administrator or user account, select the language and whether to log the user in automatically, then click Next.https://igclever407.weebly.com/eclipse-mac-download-17.html. To learn more about user account creation, see Create a user account.
- (Optional) Click the Add button to add configuration profiles, packages, or scripts to your NetInstall image, then click Next.Click the Remove button to remove any items.
- (Optional) Specify system configuration options, then click Next.To learn more about computer naming and ByHost preferences, see System Configuration settings.
- (Optional) Click the Add button to bind the recipients of this image to a directory server, then click Next.To learn more about binding to a directory server using System Image Utility, see Bind to a directory service.
- (Optional) Choose to automatically install on a specific volume and whether to erase the volume, and set the system language.To learn more about automating installations, see Configure automation settings.
- https://newzing148.weebly.com/download-ygopro-2-for-mac.html. Enter a network disk name and description, select how the image number is to be assigned, determine whether a macOS Recovery partition is applied, enter the volume name, then click Next.To learn more about defining image settings, see Define image settings. Monogram font download mac free.
- (Optional) Select the computer models that can start up using this image, then click Next.To learn more about restricting computer models, see Manage supported computer models.
- (Optional) Click the Add button or click Import to add MAC addresses to an allow or deny list, then click Next.
- In the Save As dialog, choose where to save the image (you can move it later), then click Save.If NetInstall service is configured on an Ethernet network port and the Server app is set to serve images from a volume, the NetInstall service share point folder NetBootSPn appears in the pop-up menu.
Important: Do not attempt to edit content in the image destination folder while the image is being created.
Create a NetRestore image from a defined NetRestore source
- In the System Image Utility app on your Mac, click the Source pop-up menu, choose Define NetRestore Source(s), then click Next.
- Read the macOS License Agreement. If you agree, click Agree to continue.
- Click the Add button to define your NetRestore sources, select any NetRestore options, then click Next.For more information on NetRestore source information and options, see Set NetRestore source information.
- (Optional) Click the Add button to add configuration profiles, packages, or scripts to your NetInstall image, then click Next.Click the Remove button to remove any items.
- (Optional) Specify system configuration options, then click Next.To learn more about computer naming and ByHost preferences, see System Configuration settings.
- (Optional) Click the Add button to bind the recipients of this image to a directory server, then click Next.To learn more about binding to a directory server using System Image Utility, see Bind to a directory service.
- (Optional) Choose to automatically install on a specific volume and whether to erase the volume, and set the system language.To learn more about automating installations, see Configure automation settings.
- Enter a network disk name and description, select how the image number is to be assigned, determine whether a macOS Recovery partition is applied, enter the volume name, then click Next.To learn more about defining image settings, see Define image settings.
- (Optional) Select the computer models that can start up using this image, then click Next.To learn more about restricting computer models, see Manage supported computer models.
- (Optional) Click the Add button or click Import to add MAC addresses to an allow or deny list, then click Next.
- In the Save As dialog, choose where to save the image (you can move it later), then click Save. Note app for windows like mac.If NetInstall service is configured on an Ethernet network port and the Server app is set to serve images from a volume, the NetInstall service share point folder NetBootSPn appears in the pop-up menu.
Important: Do not attempt to edit content in the image destination folder while the image is being created.
See alsoAbout System Image Utility on MacTypes of images in System Image Utility on MacCreate and deploy network disk images in System Image Utility on MacApple Support article: How to create a bootable installer for macOS
A basic how-to for using System Image Utility | 14 comments | Create New Account
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.
Not sure if this should be labeled as a hint (even though your article title does say how-to).
It's a good write-up, but maybe it should go in macosxhowtos ?
-J-
---
-J-
It's a good write-up, but maybe it should go in macosxhowtos ?
-J-
---
-J-
Mobile market download for mac. Never heard of it. And google doesn't seem to know about such a place, either. Mind providing a link for us?
What a beautifully written hint, one that (in its third step) shows how the late 2008 Macbooks are not as appropriate for wide deployment in an enterprise/institutional environment as the earlier Macbooks.
3A. Remove your battery.
3B. Remove screws (3-4?) and 2.5' SATA Hard Drive.
3C. Place Macbook HD in an external USB / SATA bridge enclosure.
.
5A. Once Disk Utility opens, you will see in the list of drives an external USB drive.
Check to make sure this is the disk you are wanting to use to create a netinstall
image, as it may take some time to create depending on the size of your client machine's drive.
Really, it's not that much harder, is it?
Yes, I'd prefer eSATA and FireWire to USB for data transfer as well, but removing the FireWire
from the MacBooks (and Airs, and probably revised Minis) is hardly a dealbreaker
these days with the proliferation of (inexpensive!) USB2 devices.
3B. Remove screws (3-4?) and 2.5' SATA Hard Drive.
3C. Place Macbook HD in an external USB / SATA bridge enclosure.
.
5A. Once Disk Utility opens, you will see in the list of drives an external USB drive.
Check to make sure this is the disk you are wanting to use to create a netinstall
image, as it may take some time to create depending on the size of your client machine's drive.
Really, it's not that much harder, is it?
Yes, I'd prefer eSATA and FireWire to USB for data transfer as well, but removing the FireWire
from the MacBooks (and Airs, and probably revised Minis) is hardly a dealbreaker
these days with the proliferation of (inexpensive!) USB2 devices.
Another, possibly better option is to look at InstaDMG (found on AFP548.com). Using InstaDMG you can create a 'modular' image, which is based on putting packages together vs cloning a system. When cloning a system, you leave yourself open for also cloning system settings, such as ByHost files and the local Kerberos database.
Instadmg is totally the way to go. It can be a bit of a hassle in the beginning to get all your changes into packages rather than manually tweaking the golden machine, but once you have that, getting an image for new hardware is a snap.
Well, a snap that takes around two hours to run, but your involvement is about 30 seconds at the beginning. QA is a lot easier, since you only have to QA your packages once, not every single time you make a new image.
Well, a snap that takes around two hours to run, but your involvement is about 30 seconds at the beginning. QA is a lot easier, since you only have to QA your packages once, not every single time you make a new image.
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?
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?
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).
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).
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:
/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
/Library/Preferences/SystemConfiguration/com.apple.network.identification.plist
/Library/Preferences/SystemConfiguration/preferences.plist
also, be sure to to delete machine specific network configuration files from your image:
/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
/Library/Preferences/SystemConfiguration/com.apple.network.identification.plist
/Library/Preferences/SystemConfiguration/preferences.plist
If you were just going to create a NetBoot / NetInstall set, you can leave out the steps 4-10 (where the .dmg is created) and just select the mounted Mac-HD in the System Image Utility. This will save you about 1-2 hours or so.
On a sidenote, I strongly recommend to read the book 'Mac OS X 10.5 Deployment v10.5' from Peachpit, as it covers the whole Deployment-through-NetBoot setup in good detail. After reading this, I was able to set up our server to push the image on ~ 8 Macs per hour.
I suggest DeployStudio, you can also make images through the network, so no Firewire is needed. Furthermore it is really built for large multiple image deployments: http://www.deploystudio.com/Home.htmlOn a sidenote, I strongly recommend to read the book 'Mac OS X 10.5 Deployment v10.5' from Peachpit, as it covers the whole Deployment-through-NetBoot setup in good detail. After reading this, I was able to set up our server to push the image on ~ 8 Macs per hour.
This is THE tool for managing images both for Mac and PC. If you spend time to learn how it works, it saves you LOTS of time afterwards.
---
The box said, Windows 95 or better, so I bought OS X.
The box said, Windows 95 or better, so I bought OS X.
Nice write-up, however, I'd like to mention a few things. Like Asmus mentions above, you can skip the steps of creating the .dmg if you are just creating a NetInstall set. Secondly, and more importantly, in my experience, its unnecessary to have your actual server create the Netinstall set in the first place. As long as you have an admin Mac somewhere that you install the Server Admin tools on. No, you do not need to be running OS X Server on this Mac, just the correct version of OS X (Leopard) to use those tools, including SIU. Just connect the target Mac you want to create your image from to the said admin Mac in target mode, run SIU, and follow the latter steps of choosing the system to create the image from.
This will save you the trouble of putting any unnecessary load on your server. The only extra step is you will need to copy the resulting NBI image file once its done to the appropriate location on your server. In most cases, this is in /Library/NetBoot/NetBootSP0, although in could theoretically be on any attached disk system if you set the location in Server Admin
I've been using SIU now for several years to push to my campus macs (> 150 total, including iBooks and MacBooks) and the software just keeps getting better. Several things to be aware of, though, before you delve right into SIU:This will save you the trouble of putting any unnecessary load on your server. The only extra step is you will need to copy the resulting NBI image file once its done to the appropriate location on your server. In most cases, this is in /Library/NetBoot/NetBootSP0, although in could theoretically be on any attached disk system if you set the location in Server Admin
• Update to server 10.5.6, which fixes some major problems with binding machines to OD after pushing the NetInstall image. See: http://support.apple.com/kb/TS1245 for more info. I have yet to need 10.5.6 for NetImaging myself, but I wish Apple had caught this before I spent 3 days pulling my hair out last September before I figured out was was happening.
• In terminal, use the scutil --set commands before you image to make sure that you blank out the three 'name' locations: LocalHostName, HostName & ComputerName:
scutil --set LocalHostName '
scutil --set HostName '
scutil --set ComputerName '
• If the source machine has been under construction for a while, system logfiles and other crufty logs build up. It helps for future troubleshooting to see log data gleaned during the use of a particular machine itself, and not all which came before NetImaging. In terminal, type sudo periodic daily weekly monthly to clean things up. Once the source is mounted in FW Target mode visit /var/log
Mac Disk Utility
and /Library/Logs and delete all the *.gz and *.bzg compressed files. It won't hurt to delete all the logfiles you find, either. And don't forget to empty the Trash and user Downloads folders, too!• Although the disk image creation step can be eliminated and the NetInstall image created directly from the target machine, I like to create the disk image and make a copy read/write so I can make changes to various files without having to boot the source should the need arise.
• Once the source machine is booted into FW target mode, always run the Repair Permissions and Repair Disk actions in DiskUtility.
As for SIU itself, the 10.5.4 version had some errors & omissions which also caused some grief:
• The 'Apply Computer Name and Local Hostname settings from a file' module is broken.
Archive Utility Mac Download
Mac Utility Download
• Make sure to disable Spotlight indexing for the FW Target drive once it is mounted on the server.+- IconDaemon -+
---
Patriotism is the last refuge of scoundrels! - Samuel Butler
Patriotism is the last refuge of scoundrels! - Samuel Butler
Mac Os Utility
Can I ask if anyone has done this recently using Mountain Lion and ML Server. What I am finding is that if I create the image, that part works fine but if I then mount it and try to use SIU to install from it, it only gives me the option to use a NetBoot image and no Netinstall or Netrestore. Anyone else seen this?