Self-Serving Lion?

[#1]

Apologies if this has already been discussed…been away for awhile.

Is anyone self-serving Lion to their users? What do I actually need to include/run from the Lion installer to allow non-admin users to update on their own terms?

We've got our volume purchase codes, I've got the Install Mac OS X Lion.app, and I've made a script to unhide our hidden support accounts. Just need the actual piece that kicks off the installer without requiring a user to be admin.

Thanks,
Bob

[#2]

We seem to have a good foundation in place that has been working well with a few beta users. My only hang up is figuring out a method for the Lion Java install.
Upon reboot in to Lion, since we use Adobe CS, it instantly asks to run the Lion Java install. Not the end of the world cause the client can then just go straight to SS to run our Java install.

So far this is what we are working with;

- copy the Lion upgrade app to /Applications

- point end user to Self Service

Self Service Policy has a simple script with these two lines;

/Applications/Install Mac OS X Lion.app/Contents/MacOS/Install Mac OS X Lion &

killall "Self Service"

We also deploy a plist file to suppress the 802.1x auto connect setting on ethernet, but that may be unique to our environment.

After 5 test deployments, the upgrade has not busted AD or OD bindings and all seems well so far.

The units do put up a yellow light stating that some network accounts are not available, but that instantly goes away after one reboot.

Nick Caro Senior Desktop Support Administrator

[#3]

I tried that workflow already, and the installer pops open after it's downloaded, but it just tells me "Command line installs of Mac OS X are not supported on systems older than 10.7"

Bob

[#4]

Sorry for the double-post. But it looks like killing Self-Service may have
been the key? I was only calling the command line installer before, but
after your email I added the killall Self Service and it appears to be
working now.

Thanks!

Bob

[bentoms]

In terminal typing: java -version will prompt for it to be installed.

The pkg seems to be hosted on sus.. So might be able to grab from there?

Regards,

Ben.

[#6]

Yeah, I should have added more detail on that.
My problem is unique cause our units are bound to OD and pointed to Snow Leopard internal SUS.
I have not been successful at convincing the server admin to add the Lion catalog to it, so it will just continue failing.

If OD was not part of the show, this would be a slam dunk and it amazes me that we can run an OS upgrade via SelfService.

Nick Caro Senior Desktop Support Administrator

[nessts]

I downloaded the package from the download site and just add it to things I install, although I have yet to get my casper imaging working with the factory image, have to poke around on that some more still, but it works from the command line.

--
Todd Ness
Technology Consultant/Non-Windows Services
Americas Regional Delivery Engineering
HP Enterprise Services

[RobertHammen]

What I did (bear in mind we don't use an imaged workflow, but a first-time setup/"thin image"/layer-built image via 26 first-run setup policies).
On Aug 11, 2011, at 12:45 PM, Ben Toms wrote:

I have a run once policy, scoped to all 10.7 machines, that automagically installs Java (downloaded the .dmg from Apple, can't remember if it's a .pkg or .mpkg but copied it into Casper Admin, works like a charm). Bottom line, every new Lion user gets it automagically...

--Robert

[#9]

One thing I ran into was in the settings menu and LDAP Server Connections
the Distinguished Name has to be the full path to the service account in
your ldap server.

IE. CN=YourServiceAcct,OU=ServicesAccounts,OU=Users,DC=Your,DC=Domain,DC=com(ne
t, org,etc)

Alan Hefner

[drewmweiss]

Hey Guys,

I'm trying to get Lion installed via self service. The app copies just fine, but the script won't actually open Lion. When I run the same Policy via a trigger, it copies and opens fine. Any idea what I am doing wrong???

Thanks,

Drew

[#11]

I finally did get it working here, and it sounds like you're going about it the right way.

I set up an initial policy to push the Install Mac OS X Lion.app to the machines (I put it in /var/Applications, so the user wouldn't find it, but that's a personal preference)

Then a second policy, available in Self Service, runs a script Nick mentioned earlier in the thread:

/var/Applications/Install Mac OS X Lion.app/Contents/MacOS/Install Mac OS X Lion & killall "Self Service"

Bob