/build/static/layout/Breadcrumb_cap_w.png

Help with netbooting late 2012 iMac (thin model)

Hey guys, I'm in very tight situation with trying to get these new iMacs to netboot. Our other iMacs netboot fine ( but only after running the sudo bless command first) and I just captured an image from one so I know it's working. I have been using the older iMac as my test machine and have had no problems netbooting, deploying, or capturing images with the K2000 and the older imac. Now, with the new model it will not netboot no matter what I try. I have tried the same commands that I run on the other older model which are 

sudo bless --netboot --server bsdp://1.1.1.1 --nextonly

sudo bless --netboot --server bsdp://1.1.1.1 --nextonly reboot

Has anyone else deployed the new iMacs yet and had any luck with this? I have the image ready to deploy I just can't get these things to netboot! It's very frustrating.

 

Any help will be appreciated,

Jeremy


0 Comments   [ + ] Show comments

Answers (2)

Posted by: SMal.tmcc 11 years ago
Red Belt
1

there is an efi problem with certain models that they cannot netboot across subnets anymore to any pxe server.  may be your problem

http://jamfnation.jamfsoftware.com/discussion.html?id=5716

http://jamfnation.jamfsoftware.com/discussion.html?id=5835

https://discussions.apple.com/thread/3337689?start=0&tstart=0


Comments:
  • Thanks for the links. It's appreciated. I tried those with no luck. Looks like the efi firmware is really screwing us. I have 23 to get installed and I only have until tomorrow afternoon to do it. I'll keep trying everything I can. - Memphis University School 11 years ago
    • you can put them on the same subnet as your k2000 or create a RSA on that subnet. - SMal.tmcc 11 years ago
      • Now that actually works, but it gets hung up on the apple logo and just hangs. I tried an older macbook and imac and they boot up flawlessly. - Memphis University School 11 years ago
  • The hanging could be caused by the mac boot env you have uploaded does not play well with that model. try uploading a new mac boot env from one of the new machines and make it the default, do not delete the old one so you can switch back to when needed. If this is 10.8 I think you have to wait till k2000 version 3.5 - SMal.tmcc 11 years ago
  • I captured the netboot environment from the mountain lion installesd.dmg Would that make a difference which computer I used media manager on to capture that? Yes, it is 10.8 - Memphis University School 11 years ago
  • I don't believe it will matter what version of OS X you are uploading media from but I have run into issues where the version I am trying to boot into is higher than the media. - Timi 11 years ago
  • have run into problems of drivers missing when uploading boot from a different model then the one PXE booting - SMal.tmcc 11 years ago
  • Thanks guys. I'm going to try that today. - Memphis University School 11 years ago
Posted by: Memphis University School 11 years ago
Yellow Belt
0

Well 10.8 is not supported by media manager so we are waiting to see if we can get into the 3.5 beta to resolve this issue. Kinda stuck right now.

 

Thanks for all the help.


Comments:
  • I'm having the same issue. I'm using Dell K2000 appliance to Netboot. Older Mac's work well. So far everything but the new Thin IMacs. I can see the proper netboot option and it just goes to a no symbol and boots to itself. The IMac is on the same subnet as the K2 and I did create a new OSX 10.8.2 Netboot environment from it. No luck. I'm running V3.5 of the K2. Any update on this post? - Chadg001 10 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ