How are you taking the image?
I could do with a little help here...... The situation is:
We have a Mac Mini OSX 10.8 running server 2.2, it is a very basic setup with Open Directory and File Sharing enabled, we are also using workgroup manager to manage preferences.
The problem starts with the clients. They are running OSX 10.6 and we are trying to create a standard image to deploy across the rest and then bind them to OD. When the image is deployed only one client will bind, they other with the same image state that there is already a computer with that name and do we want to overwrite.
I have changed the hostname on the other clients but it still throws up the error. What are we doing wrong? Is there anyway to essentially 'Sysprep' like you do with Windows?
Any help/advice would be greatly appreciated.
How are you taking the image?
1. Why are you deploying 10.6 for clients? Is there a particular compatibility issue you're concerned with?
2. Are you taking an image of a computer that has already been bound to OD?
The best way to use DeployStudio is to build a computer exactly as you want it configured, but don't bind it and name it something generic (e.g. z_10.68_MediaLab). Then use the computer naming and binding script features in DeployStudio at post install time in your workflow. That's all you need to do.
Jwzg (9th February 2014)
We are deploying 10.6 because we only have licencing for this version. The macs we have are not compatable with the Free OSX upgrade, typical apple!.
No the computer had not already been bound to OD it was a clean build.
We used Disk utility in OSX to take the image.
Are there any tips for using/setting up Deploy Studio?
I wouldn't recommend using disk utility. I haven't tried that in so long I don't know if it would still work (maybe it does with 10.6).
Just follow the documentation on the Wiki pretty much to the letter and you will be fine - http://www.deploystudio.com/Doc/Doc.html
DeployStudio is very easy to get up and running. Just get your head around workflows and you will be able to automate a great deal. Besides monolithic images you can push out packages as well and make them available to end users in a self service fashion. If you dual-boot it can handle that as well, but I would recommend also setting up a FOG server and sysprepping the Windows image using the fog client to name and bind the windows partition after the DeployStudio image completes.
primarytechy (10th February 2014)
Thanks for that!
So using this tool will remove any issues binding to the OD?
You want to make sure the base image isn't bound to OD/AD before being re-deployed. Otherwise it is quite rightly going to have an issue when it realised a machine already contains the name and hissy fits when looking for the OD.
Deploy Studio is great. You can add any OD/AD binding tasks to the workflow. And at the same time, if you need too, create a bind only workflow, for it you need to re-name or re-join a machine further down the line.
primarytechy (12th February 2014)
Cheers everyone for your help, its saved me a lot of time!!!!
There are currently 1 users browsing this thread. (0 members and 1 guests)