Hi All - I've noticed that after upgrading to Mavericks, I am having to reinstall Java 6 in order for SEP LiveUpdate to work properly. I know that Mavericks disables Java 6, but is there an easier way to re-enable Java 6 rather than reinstalling the client?
Solved
Mavericks, Java, and SEP
+6Best answer by nessts
how are you creating your SEP install package that you are deploying? when you get the package from the SEPM you should check the menus there is an option to create a mass deployment package, sorry i forget the exact terminology, but that package should be what you use to deploy not the .app they give you right?
I have deployed 12.1.4 to several machines and all talk to the SEPM find, get updates etc.
Of course i refuse to allow upgrades from 10.8 to 10.9 so they are all clean installs.
+35Not from what I've seen.
Depending on how you upgrade, you can have Casper force an install of Java 6 on your 10.9. Macs.
I have a script that was originally written to force Java to be reinstalled to fix this issue:
It should also work to force an install of the latest Java 6 on your 10.9 Mac:
#!/bin/bash
# Original version of this script posted by
# Michael Kuron <michael-lists@PHYSCIP.UNI-STUTTGART.DE>
# Posted to the MacEnterprise list on June 22, 2013:
# http://tinyurl.com/m8fp4ou
#
# This script works on Mac OS X 10.7.0 and higher
#
# Determine OS version
osvers=$(sw_vers -productVersion | awk -F. '{print $2}')
if [[ ${osvers} -ge 7 ]]; then
# Set the JAVA_INSTALL_ON_DEMAND
# environment variable. This variable
# overrides the install check and forces
# the softwareupdate tool to install Apple's
# latest Java 6 update
export JAVA_INSTALL_ON_DEMAND=1
# Uses the softwareupdate tool to check
# for and get the name of the latest Apple
# Java update for 10.7.x and 10.8.x
pkgname=$(softwareupdate --list | grep '*' | grep -i java | awk '{print $2}')
# Installs the latest available Apple
# Java update for 10.7.x and 10.8.x
softwareupdate --install $pkgname
else
echo "Not supported on this version of Mac OS X"
fi
+18Are you still running an older version of SEP? We're using 12.1.4 and the Java requirement seems to be gone.
Since we are also switching to a VPN solution that does not require Java, we are not installing it at all on our 10.9 systems.
+26Will confirm that 12.1.4 DOES NOT require Java for the LiveUpdate mechanism but is officially required for Mavericks from Symantec. They seem to have the deployment issues ironed out a bit...I am going to be working on testing that after Thanksgiving.
+6I have confirmed that 12.1.4 does not require Java for Live Update functions. That said, after packaging the client and deploying it to a couple of test machines, i noticed that the antivirus is disabled, and i am unable to enable it. I've tried the update on a clean machine (no SEP client) and a machine which already had an older 12.1 version... same results. The vendor package I'm using is a 'managed client' which should report to our SEPM console, but i also see a license expired message and no communication with the server.... perhaps there is some sort of unique GUID assigned to each machine which needs to be removed prior to finalizing the package? My search continues...
+18how are you creating your SEP install package that you are deploying? when you get the package from the SEPM you should check the menus there is an option to create a mass deployment package, sorry i forget the exact terminology, but that package should be what you use to deploy not the .app they give you right?
I have deployed 12.1.4 to several machines and all talk to the SEPM find, get updates etc.
Of course i refuse to allow upgrades from 10.8 to 10.9 so they are all clean installs.
+26okay...so that sounds somewhat weird.
Uh...here's what I've done with it...I haven't used SEPM just yet to build a new package. For one, I'm guessing you will have to update SEPM as well as the client...that is why I am still in play mode with this...we have a scheduled update of SEPM coming over Winter break for a multitude of reasons. In the meantime, I am able to get into the .app installer and pull out the package and install over the top of an existing install seemingly fine. I do note that sometimes it takes up to a day for Mac machines to phone home to the SEPM server to get updated policies and what not...quite annoying but have been assured that it is supposedly normal behavior. I'll keep you posted on my trials and tribulations with it once we get our SEPM server updated here over winter break.
+18definitely get the SEPM updated before. and get the installer app generated from the SEPM life should be good.
+6The package i have was exported from the SEPM. It comes in a .app format. Reading through the Symantec message boards, i found this:
SEP 12.1.4 has a new package format for the Mac client. When you export the package out of SEPM it will be in .app format. Then when you run the .app file on a Mac system it has an option to export into a single .pkg file. You can use the .pkg file to deploy the package from virtually any Mac remote deployment software, such as Apple Remote Desktop or Casper.
When i execute the .app, i do not see an option to export into a single .pkg file... has anyone had luck with this?
+6Found it! when you open the .app installer, there is a Tools menu in the top menu bar where you can create a remote deployment package.
Cheers!
+18Ha, I will have to try that, I pulled the files out of the .app and repackaged them in Iceberg with a postflight script (works just fine though).
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.