Unable to deploy the Symantec System Recovery 2013 agent through the standalone console to remote computers running Windows Vista, 7, 8, Server 2008, Server 2008 R2, or Server 2012

Article:TECH207036  |  Created: 2013-06-07  |  Updated: 2013-10-01  |  Article URL http://www.symantec.com/docs/TECH207036
Article Type
Technical Solution


Issue



Unable to deploy the Symantec System Recovery (SSR) 2013 agent through the standalone console to remote computers running Windows Vista, 7, 8, Server 2008, Server 2008 R2, or Server 2012

 

 


Error



Error E0D3EBC0: Cannot deploy the Agent to <COMPUTER_NAME>.

--<COMPUTER_NAME>, Exception occurred: Attempt to push package to remote machine failed due to an invalid environment

The file download was aborted abnormally. The file is incomplete.

 


Environment



 Standalone SSR 2013 installation not utilizing Symantec System Recovery 2013 Management Solution

 


Cause



SSR 2013 currently does not support agent deployment from the "Computers" menu of the SSR 2013 standalone console to remote computers running Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012.

 

Note:  This issue only applies to the standalone console for SSR 2013.  The Symantec System Recovery 2013 Management Solution supports deployment of SSR to all computers running Windows XP, Vista, Windows 7, Windows 8, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012.

 


Solution



Symantec System Recovery 2013 should be installed locally on any computer running Windows Vista, Windows 7, Windows 8, Windows Server 2008, or Windows Server 2008 R2, or Windows Server 2012.  After SSR is installed locally on the computer and it is rebooted, attempt to connect again from the "Computers" menu of the SSR 2013 standalone console. 
 
If unable to connect to the remote computer, this is most likely due to DCOM permissions or a firewall which is blocking DCOM communications.  Please see "Related Articles" for instructions on correcting those issues. 
 
 




Article URL http://www.symantec.com/docs/TECH207036


Terms of use for this information are found in Legal Notices