Whether we run RemoteUpdateManager (RUM) or build new packages with CCP that include updates, we're finding that it can take up to twelve hours for the update process to complete for a full install of all the Windows applications. (The install/update process will often not report that it has done, but the collection of log files and testing makes it seem that is has.) My test bench system for this (a Dell 7010) and gets a fresh Windows image and Adobe install before the test. Windows Resource Monitor shows extended periods of inactivity (network, CPU, disk) after the initial installs and while the updates are running. According to the Adobe install logs, some updates take 1 - 2 hours to run. In the Task Manager, a Wait Chain analysis shows that RUM processes are in "deadlock", something I don't quite now how to interpret.
It appears that whether I run RUM or build packages to include updates, the updates are always pulled from Adobe. CCP doesn't seem to cache them the way it does with the applications. We're not in a position to set up our own update server (we're a large, multi-campus college and a request like this isn't very high priority for our server people).
I'd like to know if anybody else has been experiencing this. We had a support ticket open on this, but it was closed without being resolved. (With each test run taking us 12+ hours, I don't think Adobe Enterprise Support is set up to handle issues like this with multiple follow-ups).
Thanks!
