travelsoreo.blogg.se - Untouched mac os x mavericks installer

#UNTOUCHED MAC OS X MAVERICKS INSTALLER INSTALL#
#UNTOUCHED MAC OS X MAVERICKS INSTALLER UPGRADE#

Installer:PHASE:Waiting for other installations to complete… Installer:PHASE:Preparing for installation… The installer reported: installer: Package name is OS X Mounting afp:///CasperShare to /Volumes/CasperShare.Ĭopying InstallOSX_10.8.4_12E55_custom.pkg. Verifying /Library/Preferences/.Įxecuting Policy at 11:24 AM | jwojda | 1 Computer. I found another post talking about to use Current Startup Disk (no bless) and when I set that, I get the following. I was having trouble with installing it, it would always say complete, but the OS was untouched. change /Users/helpdeskard UniqueID 505 498 change /Users/admin UniqueID 504 499ĭscl. Users/Shared/Install OS X Mountain Lion.app/Contents/MacOS/Install OS X Mountain Lion&ĭscl. change /Users/helpdeskard UniqueID 498 505 change /Users/admin UniqueID 499 504ĭscl.

#UNTOUCHED MAC OS X MAVERICKS INSTALLER INSTALL#

UID elevation/10.8 install kickoff script:ĭscl. This is based on a Smart Group with the following criteria: OS is not 10.8, Packages Installed by Casper has "Install OS X Mountain Lion.dmg".

#UNTOUCHED MAC OS X MAVERICKS INSTALLER UPGRADE#

I have an additional policy which will routinely bug users who have no initiated the upgrade via a pop-up.

This is based on a smart group with the following criteria: OS is 10.8, Packages Installed by Casper has "Install OS X Mountain Lion.dmg".

Once the machine recons in as being upgraded to 10.8, a script runs to correct the elevated UIDs for our hidden admin accounts.

Have a Self Service initiated policy that elevates the UID of our two hidden admin accounts to above 500, and kicks off the 10.8 install, which the users walk through to complete.

Cache the 10.8 installer package with a pop-up directing users to Self Service when the package is successfully cached targeted to the static upgrade group.

Create a static group of machines to upgrade.

Note: I used the info at as reference, using Scenario 2. If I then run the QuickAdd package locally, everything is fixed - however, I would prefer this be a smooth process that doesn't involve running anything after the upgrade to Mtn Lion.Īny ideas on what I'm doing wrong or what might resolve this issue? Thanks! It also appears that our hidden admin user does not exist/work on the machine. When I reboot I no longer get the "checking for updates" message either. Also, I cannot then force install a package onto a machine, which also makes me think the connection is broken. Previously any user could launch an item in Self Service without an admin UN/PW. I've got the script and Mtn Lion package working to the point where it works to upgrade to Mtn Lion just fine except once it's up and running I find that the machine has lost its JAMF/Self Service connection - it now requires an admin username/password to install something from Self Service. We are attempting to create a package in Self Service to allow a user to upgrade to Mountain Lion (from Lion).