Error Connecting To Remote Computer Backup Exec 2010
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange backup exec 2010 r2 Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano backup exec error connecting to the remote computer ensure that the computer is available 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Push Install of the Remote Agent fails with an error backup exec cannot connect to remote computer connecting to remote computer Article:000015582 Publish: Article URL:http://www.veritas.com/docs/000015582 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your
The Backup Exec Server Could Not Connect To The Remote Computer
Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Push install of the Backup Exec Remote Agent to a Remote Windows Server fails but other installation methods may work successfully. Error Message Error connecting to the remote computer. backup exec error connecting to the remote registry Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 24 Cause WMI Remote execution requires the following: "Adjust Memory Quotas for Process Properties" "Replace a process level token" Solution WMI Remote execution requires the following: For Local Group / Local Computer Policy Under Administrative Tools / Local Computer Policy / Computer Configuration / Windows Settings / Security Settings / Local Policies / User Rights Assignments.Confirm if the Administrators, Local Service, and Network Service accounts have the right "Adjust Memory Quotas for Process Properties".Local Service, and Network Service have the "Replace a process level token".Go to Run type in "gpupdate /force" and update the policy.After that try the push install of the Remote Agents for Windows server again. If problem persist, install Remote Agent for Windows Servers (RAWS) using manual method following instructions listed here. Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the originalGovernance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In backup exec 2010 remote agent CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest
Backup Exec 2010 Remote Agent Utility
helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search
Backup Exec 2010 Remote Agent Not Detected
instead for Do you mean VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Make sure... VOX : Backup and Recovery : Backup Exec : https://www.veritas.com/support/en_US/article.TECH177320 Error connecting to the remote computer. Make sure... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error connecting to the remote computer. Make sure that the computer is available, WMI is enabled and not blocked Windows Firewall.14 DenisFrolov Level 3 04-29-2013 06:57 AM Options Mark as New https://vox.veritas.com/t5/Backup-Exec/Error-connecting-to-the-remote-computer-Make-sure-that-the/td-p/626777 Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, I can not install the Remote Agent Backup Exec 2010 R3 on Win Server 2008 R2 to backup Exchange 2010. Domain account with full administrator rights. The error is: Error connecting to the remote computer. Make sure that the computer is available, WMI is enabled and not blocked Windows Firewall.14 Firewall is turned off, antivirus is empty, the WMI service is enabled. Network access to server is have. I tried instal with local administrator account and gave all sorts of rights, but to no avail. Agent has been installed very good on the other server. Labels: 10.x and Earlier Agent for Microsoft Exchange Server Agents Backup and Recovery Backup Exec Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 10 Replies Hi, Check out the TN CraigV Moderator Partner Trusted Advisor Accredited 04-29-2013 07:06 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, Check out the TN below: http://www.symantec.com/business/support/index?page=content&id=TECH128062 Thanks! 0 Kudo
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Backup Exec 2014 Agent Installasion Want to Advertise Here? Solved Backup Exec 2014 Agent Installasion Posted on 2014-11-27 Storage Software Windows Server 2003 2 Verified Solutions 5 Comments 2,060 Views Last Modified: 2014-12-29 We have recently Upgraded Our backup media Server for Backup exec 2010 R3 to 2014 SP1. I am trying to re install the backup agent on the clients and facing issue. The Nodes are running 2003 R2 OS With SP2 , When I try to Update these servers from the backup exec console on the media Server it gives me the following Error "Error Connecting to the Remote Computer. Ensure that the computer is Available, has WMI Enabled, and is not blocked by firewall. 2147944122" Screen Print Attached for reference I have checked the Connectivity and I am able to Ping the Client servers from the media Servers, also the WMI Service is restarted on both the nodes, But I Still face the Error. I Also tried uninstalling the previous version of the Agent from the Server and tried a Manual install by transferring the "RAWS32" folder from the media Server, But it Still fails with the following Error (Attached is the Installation Log file for reference) 11-26-2014,19:41:15 : AgentSeqDlgs::AgentInstaller 11-26-2014,19:41:15 : Executing runtime installer package vcredist_x86.exe. 11-26-2014,19:41:15 : C:\VCRedist\V10.0\vcredist_x86.exe /q /norestart /log "C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\V10.0_x86_msruntime_install.log" + 11-26-2014,19:41:15