It will work fine on 1-4 machines, but anything more would freeze the image install process. Again powering off a machine > OPTION + Power on, selecting the Netrestore Image from the startup disks. Again, this older process was freezing up when only using the Netrestore feature within Server. Which was wiping out a machine's current HD, and installing my image of a fresh os x install. I am trying to find a great/consistent alternative to using the NetRestore Image process. Does DeployStudio need to be installed on every single machine I plan on re-imaging? That would create a lot of unwanted time for my process. Used the 'Restore' function, set the HFS folder, and selected my master dmg I created in the above step. this went fine, it put itself in the HFS directory within the DeployStudio folderĢ.) I then made a custom work flow. Thanks to all who read this, and thanks in advance for any input and thoughts.ġ.) I made a master, source was my clean os x install machine 'Blueprint' booted into Target Disk Mode These machines will never be hooked up to my switch again.
I want to come back in the room, all machines are at the log in screen, ready to be used for the first time, I power down the machines, grab 23 more and do it again, and again and again. I want to plug in a fleet of 23, power them on holding Option, select the NetRestore Image to install on the 23’s internal harddrives, go through just the necessary prompts, which should be 1.) Choose English as default language, 2.) Confirm the hard drive listed is the install directory for the Netrestore Image. I need a method that won’t freeze up the 23 machines. So I can unplug it from the network, and there won't be any previous personal data on there, and it will be a fresh install of the os x, ala the 'Blueprint' machine.
Versus what I need it to do, which is to INSTALL the ‘Blueprint’s Image’. Then I realized this is a boot method to RUN the ‘Blueprint’s image it captured through the network. People had been recommending Deploy Studio, so I installed it, set up a DeployStudio Server, even “Created a DeployStudio NetBoot set”. Ideally, I want to have the 'Admin' machine plugged into Port #1, and Ports 2-24 will get a new machines as fast as I can clean wipe/os x install/ Install works fine on about 3-5 machines, but any more than say 5 machines, the install processes ALL FREEZE. Process completed fine, had 23 machines ported into the switch, using the option at startup method to boot from hosted netrestore image(s). So I formatted the drives, and then created my own Library/NetBoot/NetBootSP1 folder, and used this folder as the save to directory. Because I decided to host this image on a SSD 4 bay OWC Thunderbolt 1 drive. I saved the creation to a different location than the default (library/NetBoot/NetBootSP0). The source was the mounted drive which was the ‘Blueprint’ machine, I chose to customize the creation, added user account (so all would be default username and password). I then ran System Image Utility, created a ‘Netrestore Image’. I ran the Disk Utility to ‘Repair Permissions’ on the mounted drive which is the ‘blueprint’ machine. >Plug in a thunderbolt cable into the ‘blueprint’ machine, into ‘admin machine’> So this machine has restarted in Target Disk Mode. I don’t think our end customers would want the ‘Server’ app. It doesn’t have Apple’s ‘Server’ application installed on it, unlike the other machine, ‘admin’. Essentially, this machine is the machine I’m capturing my image from. So I went into the System Preferences > Startup Disk > Target Disk Mode.
#Deploystudio server not visible mac os#
The ‘blueprint’ machine is a fresh 10.10.5 mac OS X. I have 2 Macbook Pro’s acting as the ‘blueprint’ and ‘admin’ machines. Also went out and bought myself a 24 port switch. So I downloaded and installed the latest version of Apple’s ‘Server’ application. But as I needed to reformat/fresh install OS X’s at a larger volume per week, I looked into better methods.
Needless to say, this method worked fine. My job is to take usb thumb drives with the OS X install > wipe the current HD, and write a fresh OS X to the laptop, and then set it in the “ready to be sold” pile. So long story short, I work for a company that purchases hundreds of Macbook Pro’s at a time.
0 kommentar(er)
