Accomplishing an install of migration of the Symantec Endpoint Protection Manager (SEPM) or the Symantec Endpoint Protection (SEP) client results in a failed install or migration. Additionally, file corruption may be noted if the install is successful or not.
Accomplishing the same task locally is successfully. The most likely cause is an improperly configured remote session.
Installation or migration failures while using a misconfigured remote session or remote session software.
1. Improper configuration of a remote session or remote session software.
2. Failed authentication of system.
3. Failed authentication of user.
4. Domain or local policy restrictions.
This scenario is seen on a very small percentage of installations or migrations. Connecting to or configuring a SEPM in a remote session is fully supported by Symantec. An installation or migration of the SEPM or unmanaged SEP client in a properly configured remote session software is fully supported by Symantec.
In a situation where a misconfigured remote session is suspected, installing or migrating the SEPM or unmanaged SEP client in a local session (physically at the system), using the Local Administrator account will resolve the issue. The successful local install is a clear indicator that the remote session is misconfigured and requires further investigation.
Note: Beginning in version 6.1 and above of Microsoft's RDP Client (mstsc.exe), the /console switch has been replaced with /admin. Version 6.1 is included in Server 2008, Vista SP1 and XP SP3.
3rd-party Remote Session Software:
Helpful Microsoft Documentation: