I had been trying to create a boot environment of OS 10.10 and it always ends up with an error "Expected 10.9* not 10.10" 
We have the latest K2000 version (3.7.113224) installed as well the and we are using the K2000 Media Manager 3.7.112213 ver.

We also try and ran the Media manager in a 10.9 and 10.10 system with the same results. 

Is anyone experienced this problem or there is any work around? We are getting some of the newer macs and the boot environment must be updated to be able to netboot them.

Thank you.
Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment


10.10 Yosemite is not supported in 3.7sp1, there will be an upcoming hotfix to SP1 that will include Yosemite support for creating a 10.10 netboot environment.

*update: The hotfix has been released to support Yosemite.  You can find it here: https://support.software.dell.com/download-install-detail/6036347?prodjid=1-D3BJ5S
You must have a support login to download the patch.
The patch will not restart the K2.  Once the patch is applied, the new Mac Media Manager will need to be downloaded and used to create the 10.10 netboot environment.  We also recommend using this version of Media Manager to recreate any 10.9 netboot environments.

Product Support Principal Engineer, K2000
Answered 04/10/2015 by: cserrins
Red Belt

  • Thank you! We'll be waiting on that hotfix.
  • I, too, am attempting to create a Yosemite netboot. Please keep me updated!
  • I've applied the hotfix, downloaded the Media Manager, and am still getting an error. I read an old article stating that the machine used to build the netboot environment needs to be on the same subnet as the K2000 - is this still the case?
    • Yes, and you should build on the same OS version as the netboot version you are trying to create.
      • Our system administrator applied that fix and I tried using the K2000 Media Manager on a 10.10 laptop, using a 10.10 InstallESD.dmg mounted to Volumes/OS X Install ESD / and I still get the "Expected source media version 10.9 doesn't match actual 10.10 version!" after the hotfix applied.

        Any suggestions?
      • ajsein, In the new version, you are to point to the "Install OS X Yosemite.app" file, not the installesd.dmg file.
      • Sorry, can't go deeper in the thread structure. I tried uploading by just navigating to "Install OS X Yosemite.app" bundle with the K2000 Media Manager before and it failed looking for a file in a relative path, from memory: "Packages/OSInstall.mpkg" and I cannot remember the full error text. I looked into it and this seemed to match a mounted InstallESD.dmg according to my more Mac-experienced co-worker. Turned out to be true.

        Is there a newer version of K2000 manager after the hotfix?
      • Make sure you are using MM 3.7.116605. Make sure you are running the same OS as the media. Make sure you have 25Gb free space at a minimum and try it a second/third time (sometimes we see a failure the first couple of times and then it works).
  • I've managed to create a working NetBoot Environment for Yosemite. I created it using a MacBook Pro 11,4 (mid 2015). Unfortunately it only works with our older Macs - I had to build it using Yosemite downloaded for an older model MacBook (already running Yosemite - continued past the warning to download it anyway).

    When I attempt to download a new copy of Yosemite on the new MacBook, I get an error: "We could not complete your purchase. OS X Yosemite is already installed on this Mac." I'm guessing the difference is that the newer MacBook shipped with Yosemite installed.

    Anyone know a way around this so I can create a Yosemite NetBoot Environment I can actually boot new machines to? Or should this be a new question entirely?
    • Try downloading it while in the recovery partition.
      • working on that now...
      • I ran out of time with the device I was working on.

        From the recovery partition, I was able to get the installer to download, but when I tried creating my boot environment, the Media Manager was stalling at something it couldn't unmount and ultimately skipped, and I didn't take good enough notes on it at the time. The process thought it was completing successfully and created/uploaded a boot environment, but it was a a 17.5 MB file instead of an 8-ish GB one.

        The contents of the Install OS X Install folder downloaded on the new MacBook Pro was very different from the contents of the OS X Install folders downloaded using the same process on both an external hard drive and an older MacBook.

        I will try it again on the next new MacBook Pro that comes in to be set up.
Please log in to comment
Answer this question or Comment on this question for clarity