I'v been working with JAMF on this issue and got the same work around- using the InstallESD.dmg. However using that gave me the same results as before.

does anyone know if changing the name of the downloaded installer app from "Install OS X Yosemite.app" to "My dept OS X Yosemite.app" PRIOR to dragging it into Casper Admin have a negagtive effect on its conversion to "Install OS X Yosemite.InstallESD.dmg" ?

Update on this:
I upgraded to JSS 9.6.4
Re-downloaded the Yosemite Installer from App Store on a Mavericks computer
Dragged the full installer into Casper Admin, checked box for apple OSX installer, set priority 1
Updated my Self Service policies: first one caches this package and then sends custom trigger to 2nd policy
Second policy installs the cached package, set policy to restart to the installer and restart immediately (both)

Worked! (previous attempt using full installer went through ALL steps including booting to installer but never installed 10.10. Workaround using the install.esd resulted in the weird errors above as though it were a 10.6 computer)

Wrinkles: I downloaded the Yosemite installer on the actual model that I then ran the self service policy on
I am not 100% sure I deleted the original installer from the computer after putting it up to Casper Admin edit:
Same computer, re-imaged back to 10.9.5, then ran Self Service policy, now no worky and getting the weird must be at 10.7 error. Wondering if that installer was still in the apps folder, and the second policy somehow called the actual original installer.... hmmmm... back to the drawing board

Chiming in with the same results as @Sandy][/url. 9.64 did not resolve the error, we continue to have the 10.7 issue.

Yeah, I'm having the same problem as well. I tried both the InstallESD workaround as well as the direct copy from the App store.
I did some fooling around and got it to work, but I tried so many things, including removing the framework, that I have no idea how it worked.
But 9.64 didn't seem to be the fix.

Check that the computer to be upgradedn registers as MDM capable.

I just today experienced this, using JSS 9.63
This Mac was upgraded from 10.6 to 10.9.5 using Self Service.
I tried to use Self Service to upgrade to Yosemite, same method.
Then I encountered the "OS X Installer is for 10.10. Must be 10.7 or later to deploy it as an upgrade" message in the policy log.
Weird, since I have used this ESD in a policy successfully on other Macs.
I took a look at the Machine stats and noticed it wasn't MDM capable.
I re-enrolled it, then reconned it, and it came up as MDM capable, and then the installer worked. I did not remove the framework first.

JSS 9.63, uploaded latest Yosemite installer.

Created Smart Group (Is Like 10.9).

Policy to cache Yosemite installer (disabled Restart Options since we are only caching) to above Smart Group.

Smart Group created (Is Like 10.9 and Has Yoyo Installer cached)

Self Service policy scoped to above Smart Group (set Restart Options to boot into installer)

Confirmed update completes without issue, hidden accounts okee dokee.

EDIT 2015-04-30: If you don't have a visible account on the Mac, you'll be prompted to create an account; keep this in mind if you're hiding your JAMF management account.

@donmontalvo - I followed those steps. But, I am required to interact with the installer and setup a new account during the installation.

Once I go through it, all of my previous data, accounts and settings are still there.

But, I don't like the fact that the users will have to go through the installer as if it were a new machine.

Is there a way to upgrade the OS without having to go through the setup?

BTW, I am going from 10.9.5 to 10.10.3.

Thanks!

@mmunoz2 We're using this to upgrade existing 10.9 users to 10.10.

If you're doing new Macs, why not drop a non-booted Yoyo image onto it (AutoDMG, JSS, etc.)?

PS, say hi to Nestor Menar (NYC) for me. :)

Don

@donmontalvo Hey Don. What you are doing is exactly what I am attempting to replicate. However, after the machine boots into the cached Install OS X Yosemite.InstallESD.dmg, it treats it as a new machine rather than an upgrade and I am forced to interact with it. I must be missing a step. For all new machines, I simply image them with Casper Imaging and a dmg created with AutoDMG. Thanks.

@mmunoz2 if the Mac has already been booted, and has the jamf management account, it shouldn't prompt you to create a new user. Our testing shows user just needs to OK the installer, once its done there's one prompt for iCloud, then they get to the Desktop.

@donmontalvo That's the baffling part. The machine has been booted into in order to launch Self Service and kick off the upgrade policy. It is managed so the management account does exist. Yet, it prompts to create a new user every time. Bizarre.

@mmunoz2 if the management account is the only account on the Mac, and it is hidden, I'm not surprised that you are being prompted to create an account. ;)

It works successfully for me. I followed createosxinstallpkg by Greg and it seems working ok. I deploy as a pkg.

@donmontalvo I knew i was missing something. I was testing with a hidden admin account (different from our management account. But, hidden either way). After creating a standard AD mobile account. Everything worked just as expected. Thanks for taking the time to help.

@donmontalvo is there any reason why this won't work with FV2 machines? It seems to work fine on our unencrypted machines, but when I try to apply it to a FV2 machine, it reboots into kernel panic, requiring upgrade/reinstall from a usb flash drive. Has anyone else run it this and/or have an alternate solution for upgrading FV2 machines to Yosemite via Casper?