+ Post New Thread
Results 1 to 13 of 13
Mac Thread, Mac Deployment in Technical; Hi all, I could do with a little help here...... The situation is: We have a Mac Mini OSX 10.8 ...
  1. #1

    Join Date
    Feb 2012
    Location
    South Yorkshire
    Posts
    7
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Mac Deployment

    Hi all,

    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.

  2. #2

    Join Date
    Nov 2012
    Posts
    41
    Thank Post
    3
    Thanked 2 Times in 2 Posts
    Rep Power
    3
    How are you taking the image?

  3. #3

    Join Date
    Oct 2012
    Posts
    53
    Thank Post
    15
    Thanked 5 Times in 4 Posts
    Rep Power
    10
    DeployStudio is your friend.

    Quote Originally Posted by primarytechy View Post
    Hi all,

    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.

  4. #4

    seawolf's Avatar
    Join Date
    Jan 2010
    Location
    Melbourne
    Posts
    726
    Thank Post
    7
    Thanked 219 Times in 171 Posts
    Rep Power
    150
    Quote Originally Posted by primarytechy View Post
    Hi all,

    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.
    As suggested by Jwzg, DeployStudio is a good solution for you. It is easy to deploy and configure using the instructions from the Wiki. It is also very reliable and fast for deploying monolithic images. A couple of questions though:

    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.

  5. Thanks to seawolf from:

    Jwzg (9th February 2014)

  6. #5

    Join Date
    Feb 2012
    Location
    South Yorkshire
    Posts
    7
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by seawolf View Post
    As suggested by Jwzg, DeployStudio is a good solution for you. It is easy to deploy and configure using the instructions from the Wiki. It is also very reliable and fast for deploying monolithic images. A couple of questions though:

    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.
    Hi,
    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?

  7. #6

    seawolf's Avatar
    Join Date
    Jan 2010
    Location
    Melbourne
    Posts
    726
    Thank Post
    7
    Thanked 219 Times in 171 Posts
    Rep Power
    150

    Mac Deployment

    Quote Originally Posted by primarytechy View Post
    Hi,
    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?
    So, you are running some pretty old Macs (pre-2008) it sounds like? If so, then yes you are a bit limited there.

    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.

  8. Thanks to seawolf from:

    primarytechy (10th February 2014)

  9. #7

    Join Date
    Feb 2012
    Location
    South Yorkshire
    Posts
    7
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Thanks for that!

    So using this tool will remove any issues binding to the OD?

  10. #8

    Join Date
    Oct 2008
    Posts
    14
    Thank Post
    0
    Thanked 3 Times in 1 Post
    Rep Power
    12
    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.

  11. #9

    seawolf's Avatar
    Join Date
    Jan 2010
    Location
    Melbourne
    Posts
    726
    Thank Post
    7
    Thanked 219 Times in 171 Posts
    Rep Power
    150
    Quote Originally Posted by primarytechy View Post
    Thanks for that!

    So using this tool will remove any issues binding to the OD?
    If you still have a problem when using this, then the problem lies with the OD setup most likely.

  12. #10

    seawolf's Avatar
    Join Date
    Jan 2010
    Location
    Melbourne
    Posts
    726
    Thank Post
    7
    Thanked 219 Times in 171 Posts
    Rep Power
    150
    Quote Originally Posted by primarytechy View Post
    Thanks for that!

    So using this tool will remove any issues binding to the OD?
    So, how is the Mac deployment going with DeployStudio?

  13. Thanks to seawolf from:

    primarytechy (12th February 2014)

  14. #11

    Join Date
    Feb 2012
    Location
    South Yorkshire
    Posts
    7
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by seawolf View Post
    So, how is the Mac deployment going with DeployStudio?
    All done! Thanks.

  15. #12

    seawolf's Avatar
    Join Date
    Jan 2010
    Location
    Melbourne
    Posts
    726
    Thank Post
    7
    Thanked 219 Times in 171 Posts
    Rep Power
    150
    Awesome!

  16. #13

    Join Date
    Feb 2012
    Location
    South Yorkshire
    Posts
    7
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Cheers everyone for your help, its saved me a lot of time!!!!

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 1
    Last Post: 31st January 2012, 06:01 AM
  2. Replies: 0
    Last Post: 16th May 2011, 05:51 AM
  3. Replies: 1
    Last Post: 10th May 2011, 06:23 PM
  4. Deploy Dual Boot Macs
    By steventaylor in forum O/S Deployment
    Replies: 2
    Last Post: 2nd February 2010, 11:23 AM
  5. Replies: 1
    Last Post: 25th June 2008, 03:19 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •