Home > Backup Exec > Backup Exec Remote Agent Error Connecting To The Remote Registry

Backup Exec Remote Agent Error Connecting To The Remote Registry


Both success and failed have the same "act as part of the OS" settings in "domain controller security settings" (which lists the administrator account that I am authenticating when pushing the About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up Networking I've moved recently. I have been working as an IT Consultant through various contracting consultancy organizations for the past two and a half years, but lately things have been a little off. have a peek here

I am able to log on through TS as an Administrator on failed. Windows is reporting that the specified credentials cannot make a connection to the remote server. With the Acronis stuff it is quirky and not laid out well. 0 Thai Pepper OP Trivious Mar 26, 2010 at 9:58 UTC Hehe, back when it was i have had issue with it too.

Backup Exec Remote Agent Error 1603

Or do you use the same login for the BE Server as for the Agent update too? Labels: 2010 Agents Backup and Recovery Backup Exec Best Practice Configuring Installing Tip-How to Upgrade 0 Kudos Reply 8 Replies Hi St3phan, Might have CraigV Moderator Partner Trusted Advisor Accredited They might have a different security set up inherited from SQL or Exchange. 0 Thai Pepper OP Trivious Mar 26, 2010 at 9:53 UTC I had also enabled "Single

Select Storage from the tabs along the ribbon bar as the top: Ensure the proper storage devi… Storage Software Windows Server 2008 Advertise Here 846 members asked questions and received personalized See more RELATED PROJECTS Active Directory Audit Active Directory - Network Security Audit Enterprise Sandbox The creation of an Enterprise grade sandbox environment, and migration from an existing sanbox. Even specifying the domain admin credentials through the wizard for the RAWS installation account I was receiving the remote registry error. Symantec Backup Exec Remote Agent Join the community of 500,000 technology professionals and ask your questions.

If that isn't the problem then make sure that pot 10,000 is open on those machines. Backup Exec Remote Agent Install Failed With Error Code 1603 Snap! To establish a trust relationship, add the remote agent to the Favorite Resources in the backup selections tree" I'm sure that the agent I install is compatiblewith this version of BE Thank you for your feedback!

Its a shame Microsoft hasn't put out a decent independent backup solution (NTBackup will not backup Exchange hehe) that works well, it may be something to look at. Backup Exec 12.5 Remote Agent Also, If you have passthrough authentication (same localacct names and password on both machines), that could be causing you issues as well, depending on the acctpermissions on the remote system. #2 Thanks. 0 Message Accepted Solution by:davidrobertbristow2008-06-02 I have decided to do a local install of the remote agent and it worked great on my 2 problem servers. We will investigate and you should see it resolved for a future release.

  1. I'll have to take a look at that.
  2. I suspect there is a bug when the remote hosts are verifying the installation to check if you haves RAWS installed and what version you are running.
  3. HTML-Code ist aus.
  4. Try to install Backup Exec agent again after rebooting the remote server.
  5. Best regards Stephan 0 Kudos Reply Isthereanyoneelsewhohas St3phan Level 3 ‎05-25-2011 11:33 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate
  6. It sucks though that they run from 4pm until about 1pm the next day.
  7. Join Now  I am testing the new Backup Exec 2010 (12.5 I believe).
  8. I had the problem with the R2, too.

Backup Exec Remote Agent Install Failed With Error Code 1603

Posted by Dimitris Bastas at 10:23 AM Labels: Symantec BackupExec No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Home | Site Map | I have 2 RD1000 drives, and 4 servers being backed up to them (2 at a time. 1 to each). Backup Exec Remote Agent Error 1603 Add the remote server under user-defined selections, right-click on the server & choose Establish Trust Relationship. 0 Kudos Reply Accepted Solution! Backup Exec 12 Remote Agent Office locations in Denver, Boulder, Colorado Springs, Fort Collins, Glenwood Springs, Pueblo, Silverthorne, Albuquerque, Santa Fe and Cheyenne.

Good to know about Acronis, though thanks. 0 Datil OP Kimberlin Mar 26, 2010 at 10:00 UTC i think backup companies are trying to hard to get the navigate here CONTINUE READING Suggested Solutions Title # Comments Views Activity Issue with Appassure Recovery Point- File or Directory unreadable 2 43 78d Import data to Office 365 - SharePoint 6 50 37d No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities Backup Exec 2010 R2 - Remote Agent Install Error Code 1603 [fa icon="long-arrow-left"] Back to all posts [fa icon="pencil'] Posted by Lewan Solutions [fa icon="calendar"] September 28, 2010 Tweet While onsite Backup Exec 11d Remote Agent

Thanks again for your responses. I read this TechNote: http://www.symantec.com/docs/HOWTO22459, but why could I enter a valid Logon Account in this upper window that we no used? I couldn't find the "logon interactively" policy. 4. http://waspsoft.com/backup-exec/backup-exec-2012-agent-error-connecting-to-the-remote-registry.html All due to a catastroph… Concerto Cloud Services Backup Exec 2014 – Overview and Differences from 2012 Video by: Rodney This tutorial will give a short introduction and overview of Backup

I do have the agent installed and I will try EX1 next. Backup Exec Linux Remote Agent Sorry, we couldn't post your feedback right now, please try again later. To be honest, I haven't had an issue updating my agents (on the servers I have migrated to R3 so far), but have seen the option to trust them (I haven't...haven't

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

When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple. No UNC or mapped drive support kind of sucks. 55 Gigs now =D 0 Serrano OP Helpful Post mark1882 Mar 26, 2010 at 12:23 UTC To backup Exchange Thank You! Backup Exec Exchange Remote Agent Backup Exec requires administrative credentials to the remote machine to do the push.

Interestingly, it is possible to update the agents when I login to the Backup Exec mediaserver with this account that is local admin on all servers and running the services. or you can go to the pkh Moderator Trusted Advisor Certified ‎04-15-2013 08:23 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report i have had issue with it too. this contact form I have to give them this however, computer equipment and software have also become far more complex which could warrant much of the new bloat.  0 Thai Pepper

I read this TechNote:http://www.symantec.com/docs/HOWTO22459, but why could I enter a valid Logon Account in this upper window that we no used? Join & Ask a Question Need Help in Real-Time? Es ist jetzt 00:46 Uhr. 2009 - 2014 treMKa it systems \\ training \\ consulting Thanks for the quick replies guys. 0 Cayenne OP James590 Mar 26, 2010 at 9:55 UTC funny how easily jobs get corrupted in backup exec.

Lewan Technology is a business technology and managed service provider serving Colorado, Wyoming, New Mexico and beyond. As with Backup Exec 2012, the Backup Exec button in the upper left corner. You'd use the same credentials to install/update the RAWS agent as you would to install the application... Foren-Regeln -- treMKa grn/wei -- Standard Mobile Style Kontakt Archiv Datenschutzerklrung Nach oben Alle Zeitangaben in WEZ +2.

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 Startseite Forum Aktionen Alle Foren als gelesen markieren Kontakt Support Impressum Erweiterte Suche Forum Symantec Aktuelle Themen aus dem Symantec Connect Forum Agent Update: Error connecting to the remote registry of I had actually considered them at one point. 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!

What I made was modify X:\WINDOWS\SYSTEM32\DRIVERS\ETC\services and add this value ndmp 10000/tcp #BE10 I'll try repair BE10 for the moment Thanks a lot! bhanu 0 Message Author Comment by:davidrobertbristow2008-06-02 Thanks. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. I believe this was due to using Advanced Open File Option and VSS Snapshot.

I left defaults this time and it is working (so it would seem). For both servers no users or groups are defined for "deny log on locally" 3.