cache both mavericks and yosemite at the same time for self service ??

[tcandela]

to give users a choice to install either Mavericks or Yosemite.
can I have both Mavericks and Yosemite self service upgrade policies at the same time?

I currently have about 20 computers with Mavericks already cached, if I add this same computer group to now get Yosemite cached, will they interfere with each other?

If I remove Mavericks from Self Service, and add Yosemite, what happens to the computers that already got the cache of Mavericks? Will it interfere with Yosemite caching and installing?

[davidacland · Accepted solution]

The installer names are different and you can go from 10.8 to 10.9 or straight to 10.10 so I can't see a problem.

The cached version will just sit there unused. I'm not sure if it clears out automatically after any period of time.

Personally I would only offer them one choice of 10.10. Assuming you've tested it with your apps, settings and peripherals, offering both will only make your life harder.

[tcandela]

so the ones that currently have Mavericks cached will not effect Yosemite cache if i turn off the self service for Mavericks.

Yep, just 10.10 I'll advertise in self service

some already ran mavericks via self service (which is fine) while some have not. So I think Yosemite is safe now since 10.10.3

i have 10.7 10.8 10.9 systems, so the upgrade to Yosemite from 10.7 is allowed

[jhalvorson]

By offering both in Self Service, you run the risk of someone click on each upgrade, thinking they need to install 10.9 to get to 10.10. Self Service does allow you select multiple items that will run in the order of being selected. Of course if you set the computer to restart immediately after the OS install, that would probably prevent a second OS install from happening within the same Self Service session.

[donmontalvo]

Can cache both installers, then make the 10.10 installer available only after user upgrades to 10.9.

[jhalvorson]

@donmontalvo is right because the cached file in the Waiting Room won't delete the 10.10 installer until you issue a command or the 10.10 installer is launched.

You could use Self Service as a way for people to vote/request OS they want cached. Create a policy that if they select 10.9 that it would place a dummy receipt that you could use to create a smart group to then offer 10.9 upgrades within Self Service. You would crate another policy to let them request 10.10. Still could be an issue if someone selects both as they would get a dummy receipt for both.

Ah, choices...

[bentoms]

@tcandela Yosemite will update from 10.6.8, see this Apple article.

So just cache 10.10 & remove 10.9 from the equation.

[tcandela]

I ended up removing Mavericks from self service and added Yosemite .