BUG-000141239 for Portal for ArcGIS

Bug ID Number	BUG-000141239
Submitted	July 6, 2021
Last Modified	February 10, 2025
Applies to	Portal for ArcGIS
Version found	10.8.1
Operating System	Windows OS
Operating System Version	N/A
Status	Known Limit

Additional Information

Due to the large size of the Portal for ArcGIS install, updates require significant computer resources. Even if only a few files are being updated, the installer software loads the entire setup, and uses up the memory and CPU utilization. In addition, setups are extremely disk intensive. As a result, the setup times out when it is run under less than optimal conditions. This also occurs when installing in-house. This is directly related to system resources on the target machine, and network latency. The fact that it appears during Remote Control sessions underscores the second point; by definition a remote session is at least one step removed from the target machine. If the Managed Service Provider (MSP) is on a remote server, that is another hop. If another Virtual Machine (VM) is layered on top of that, it is even farther removed. This is not even considering firewalls or anti-virus software that is scanning each file being opened or installed, the disk input/output limitations, other processes that may be running. Esri recommends the following: - If possible, copy and run the MSP locally to avoid issues with network latency. - Change the User Account Control (UAC) settings to the lowest setting on the target machine. Under normal settings, UAC generates a pop-up box to confirm the install; if no answer is given it cancels the install. This pop-up can disappear very quickly and leaves no trace of what has occurred. - Run the installation by command line instead with the /qn option to not display the user interface: msiexec /p patchfile.msp REINSTALL=ALL REINSTALLMODE=omus /qn - It may be necessary to upgrade the target machine on both the CPU and memory, and copy the setup locally to that machine, eliminating unnecessary network hops. A system is only as fast as the slowest component. Even under the best conditions, the Portal for ArcGIS update can take an hour or more.

Workaround

This behavior occurs when the Remote Desktop window connection to the portal virtual machine is minimized. Run the patch and leave Remote Desktop window in full screen mode, and the patch runs successfully.