Hi.
We are trying to evaluate which update solution to use.
We package the apps with CCP, and the users should never get prompted about updates and they are not able to download/upgrade by them self, and they are not admins on their computers. So far we haven´t implemented any update solution.
First of all, when i try remoteupdatemanager.exe in an elevated cmd i get the following message:
RemoteUpdateManager exiting with Return Code (1)
And the remoteupdatemanager.log tells me this:
6/19/13 08:47:15:738 [INFO] AAMEE Utilities RemoteUpdateManager
06/19/13 08:47:15:738 [INFO] AAMEE Utilities RemoteUpdateManager ##################################################
06/19/13 08:47:15:738 [INFO] AAMEE Utilities RemoteUpdateManager ##################################################
06/19/13 08:47:15:738 [INFO] AAMEE Utilities RemoteUpdateManager Launching the RemoteUpdateManager...
06/19/13 08:47:15:738 [INFO] AAMEE Utilities RemoteUpdateManager RemoteUpdateManager version is : 3.1.105.0 (BuildVersion: 3.1; BuildDate: Tue Sep 04 2012 13:58:18 )
06/19/13 08:47:15:738 [INFO] AAMEE Utilities RemoteUpdateManager **************************************************
06/19/13 08:47:15:738 [INFO] AAMEE Utilities RemoteUpdateManager Initializing UpdaterCore Library...
06/19/13 08:47:15:925 [INFO] AAMEE Utilities RemoteUpdateManager UpdaterCore library initialized successfully.
06/19/13 08:47:15:925 [INFO] AAMEE Utilities RemoteUpdateManager **************************************************
06/19/13 08:47:15:925 [INFO] AAMEE Utilities RemoteUpdateManager Starting UpdaterCore CheckForUpdate...
06/19/13 08:47:17:844 [ERROR] AAMEE Utilities RemoteUpdateManager UpdaterCore failed for CFU errorCode(212) curRefId((null)) errorCodeString(U41M1C212)
06/19/13 08:47:17:844 [INFO] AAMEE Utilities RemoteUpdateManager **************************************************
06/19/13 08:47:17:922 [INFO] AAMEE Utilities RemoteUpdateManager ##################################################
06/19/13 08:47:17:922 [INFO] AAMEE Utilities RemoteUpdateManager Ending the RemoteUpdateManager Return Code (1)
06/19/13 08:47:17:922 [INFO] AAMEE Utilities RemoteUpdateManager ##################################################
06/19/13 08:47:17:922 [INFO] AAMEE Utilities RemoteUpdateManager ##################################################
06/19/13 08:47:17:922 [INFO] AAMEE Utilities RemoteUpdateManager
Anyone have any idea about this error?
And then to other update quistions. when i read the documentation about how to update i dont really get it.
1: is one possible solution to package the updates in CCP and then use SCCM to deploy them? i tried to create packages yesterday but the CCP didn´t work so i dont know in what format the updates come in, .exe or .msi and so on.
2: If we go with the solution of having an Adobe update server on our network, do i then need to repackage all our existing apps which have the config "AUM is disabled" and configure the "use internal update server" or can i push out a config for this?
3: If we start to use internal update server, if i choose "enable adobe update manager" will then user be able to update themself? We want to handle all of it for the users, is that what "disable adobe update manager" is? i find this very confusing.
4: Today with our non CC packages (acrobat standard and flash) we are using System Center Updates Publisher to publish acrobat and flash updates to SC Configuration Manager to deploy these updates to the clients the same way we deploy MS updates. Can we use this method for all the CC packages?