a quick update on how I solved the problem because I saw someone voting for this case: I used the Uninstall script from here to automatically remove any old version of AnyConnect before the install and didn't experience the above MSI error once again. I hope it helps someone. :)
are you saying it is a Java issue, or you are saying that you modified a script like the one on that technet page, titled "Uninstalling all previous versions of Java runtime environment using application supersedence in Configuration Manager"
Well, "I used the Uninstall script from here to automatically remove any old version of AnyConnect before the install"...
I modified the script.
Ah yes, we have found work-arounds for this issue as well. The 1303 error seems to be due to the MSI starting the install prior to the uninstall completing, so your work-around, uninstalling it yourself 1st, should take care of that. We also experienced other behaviors with the default upgrade installer from Cisco, where it would hang the windows installer (msiexec), causing the system to be in a state that no MSI would install, as it saw a previous MSI install in progress. This requires manual intervention to identify and then kill the Windows Installer service process as SYSTEM, clean the install registry entries, restart the Windows Installer service, and then start the upgrade over.
I would prefer for Cisco to address the issue with a new installer package.
off the top, what is the command line you are using? Running with administrative rights, wether the user is logged in or not?
msiexec /i anyconnect.msi /quiet /norestart REBOOT=ReallySuppress
I've tried several variations at this point with the same result.
Whether or not the user is logged on, system context as an application and a package with admin rights.
First one I tried was in the Anyconnect deployment document:
msiexec /i anyconnect-win-ver-pre-deploy-k9.msi /norestart /passive /lvx*
Tried the one above:
msiexec /i "anyconnect-win-3.1.06073-pre-deploy-k9.msi" /norestart /passive /L*V
They all seem to timeout with error code 0x87d00213 in sccm. One on a machine with anyconnect, the other does not.
I did have issues with the package timing out, when using the log file command line argument. I would suggest removing that portion, just for a test.
Also, I do not see passive as being an option you would care to use, since when run as system, no-one can see a progress bar., so it may not be quiet. Perhaps just try your command local on the system you are setting at, in a DOS window, and see if there is a popup. I would stick with the /q (quiet) and no restart options.