Backup Exec 2010 Remote Agent Install Error Connecting Remote Registry
Contents |
Governance 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 ensure that the computer is available has wmi enabled and is not blocked by a firewall 67 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest
Backup Exec Cannot Connect To The Remote Computer
helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Problem installing Remote Agent for Windows Server... VOX : Backup and Recovery : Backup Exec : Problem installing Remote Agent for Windows Server... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Problem installing Remote Agent for Windows Server on Backup Exec 2010 seguridadallus Level 2 04-11-2013 12:41 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi I have a problem with Backup Exec 2010 attempting install Remote Agent on a Windows Server 2008 Enterprise with Microsoft Exchange. The issue appears when I try to install through Backup Server the agent on the other server, and say: "Error connecting to the remote registry of server. Ensure that the current logged in account is not blocked from accessing the remote registry and that the remote registry is available before try again." So the account is not blocked, password is OK and got administrator privileges, but the error keep appearing and is not allowing install Remote Agent. How I solve this issue? Thanks in advance. Lucas. Solved! Go to Solution. Labels: 2010 Agents Backup and Recovery Backup Exec Configuring Error messages Installing Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! Yep, I finally get solve the seguridadallus Level 2 04-16-2013 07:30 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Yep, I finally get
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 Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Push install of the Backup Exec 2010 Remote Agent and/or Desktop Laptop https://vox.veritas.com/t5/Backup-Exec/Problem-installing-Remote-Agent-for-Windows-Server-on-Backup/td-p/583798 Agent (DLO) to a remote Windows server fails with "Error connecting to the remote server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603" Article:000006395 Publish: Article URL:http://www.veritas.com/docs/000006395 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? https://www.veritas.com/support/en_US/article.TECH128062 Create a Veritas Account now! Welcome First Last Your 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 Backup Exec (BE) 2010 push install of the Backup Exec Remote Agent and/or Desktop Laptop Agent (DLO) to a Remote Windows Server fails with error: "Error connecting to the remote server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." Error Message Error connecting to the remote server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603 Windows System Event log on the remote Windows Workstation or Server shows below:Fig 1 Remote Agent push log
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 https://www.experts-exchange.com/questions/23448709/Error-connecting-to-the-remote-registry-when-pushing-remote-agent-for-Backup-Exec.html 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 > "Error connecting to the remote registry" when pushing remote agent for Backup Exec Want to Advertise Here? Solved "Error connecting to the backup exec remote registry" when pushing remote agent for Backup Exec Posted on 2008-06-01 Storage Software Windows Server 2003 1 Verified Solution 6 Comments 8,432 Views Last Modified: 2013-12-01 Question: I have Backup Exec installed on a Win2003 server. I am pushing remote agents to my other servers. 6 servers have installed the remote agent successfully. However, 2 of them give backup exec 2010 the message "Error connecting to the remote registry". I have verified that the remote registry service is running. I have also checked that mydomain\administrators have full permissions to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ SecurePipeServers\winreg as outlined in the Veritas article http://seer.entsupport.symantec.com/docs/240179.htm Thanks in advance, 0 Question by:davidrobertbristow Facebook Twitter LinkedIn Google Best Solution bydavidrobertbristow I have decided to do a local install of the remote agent and it worked great on my 2 problem servers. Thanks again for your responses. Go to Solution 6 Comments LVL 23 Overall: Level 23 Storage Software 12 Windows Server 2003 8 Message Expert Comment by:bhanukir72008-06-01 Hi i think there might some restrictions for the user a/c you are using to deploy the software. Check this microsoft article http://support.microsoft.com/kb/314837 additionally Check if this user has the log on locally, act as part of OS and long interactively permissions on these two servers. bhanu 0 Message Author Comment by:davidrobertbristow2008-06-02 Thanks. I'll try your solution over the next hour and let you know how it works out. 0 Message Author