Home > Backup Exec > Backup Exec 2010 R3 Error Connecting To Remote Registry

Backup Exec 2010 R3 Error Connecting To Remote Registry

Contents

I'm beginning to think going into IT was a mistake Water Cooler I earned my CompTIA A+ certification in 2013, and began going to school for Computer Science in 2014. Or do you use the same login for the BE Server as for the Agent update too? By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. Even specifying the domain admin credentials through the wizard for the RAWS installation account I was receiving the remote registry error. http://sovidi.com/backup-exec/backup-exec-2010-remote-agent-install-error-connecting-remote-registry.php

For both servers no users or groups are defined for "deny log on locally" 3. I used it on my 2008 but I had to do it from a server with Extra drives as the 2008 ntbackup doesn't work unless you have extra drives. To install the necessary roles, go to Server Manager, and select Add Roles and Featu… Windows Server 2012 Storage Software Storage Advertise Here 846 members asked questions and received personalized solutions Privacy Policy Site Map Support Terms of Use About Us Our Team Vendor Partners Careers Locations Upcoming Events Technology Solutions VoIP & Video Conferencing Networking & Security Application Delivery & Mobility

Backup Exec 2010 R3 Remote Agent Install Error 1603

Error connecting to remote registry on \\SERVER. Good to know about Acronis, though thanks. Only when I logged into the media server and ran the console as a domain admin was i able to successfully push the agent. I have no doubts error 2 is the real issue.

Hopefully I will get the same result! 0 Kudos Reply Thanks again! Suggested Solutions Title # Comments Views Activity Migrate VMs from one Datastore to another on ESX 4.1 5 56 60d Elevating Domain functional level 9 82 29d Windows Server 2003 getting I had actually considered them at one point. Backup Exec 2010 R3 Admin Guide In system log is nothing.

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 Backup Exec Error Connecting To The Remote Computer C. In most organizations, VMs contain many duplicate copies of data, such as VMs deployed from the same template, VMs with the same OS, or VMs that h… VMware Storage Software Virtualization Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use.

SonicWall renewal - review implementation SonicWall licensing is up for renewal. Upgrade Backup Exec 2010 R3 To 2012 If that isn't the problem then make sure that pot 10,000 is open on those machines. All we want is a backup that works, we can rely on and doesn't take too much time to babysit. 0 Cayenne OP James590 Mar 26, 2010 at WTH?

Backup Exec Error Connecting To The Remote Computer

Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Online 2010 Other Versions Library Forums Gallery We’re sorry. Machine Creation Services (MCS) 3 Questions to Ask When Evaluating Managed Print Services companies Error fix: Microsoft SCCM 2012 Error Code Ox87D00668 (.NET Patching Issue) Controlling Printing Costs with Print Governance Backup Exec 2010 R3 Remote Agent Install Error 1603 MS System Center Data Protection Manager 2007 I'm using it and really like it. 0 Thai Pepper OP Trivious Mar 29, 2010 at 6:02 UTC  Interesting Limey. Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available 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

features. http://sovidi.com/backup-exec/backup-exec-remote-agent-error-connecting-to-the-remote-registry.php The difference that I see is that "failed" has a key "AllowedExactPaths" while "success" does not. 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 It returns 2 errors.  1: SQL1 -- The job failed with the following error: The resource could not be backed up because an error occurred while connecting to the Backup Exec for Backup Exec 2010 R3 Sp2

After this phase when you start the installation then it uses the specified credentials. The Backup Exec Install requires admin level privledges on the remote systems in order to successfully install or update agents. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]   Topic Last Modified: 2007-01-23 Microsoft® Exchange Server 2007 setup cannot continue because the have a peek here As you finish projects in Quip, the work remains, easily accessible to all team members, new and old. - Increase transparency - Onboard new hires faster - Access from mobile/offline Try

Covered by US Patent. Backup Exec 2010 R3 Deduplication Go to the Agent directory under the BE installation directory and then copy either the RAWS32/RAWS64 directory over to the remote machine and then do the agent installation from the copied I was told that after Exchange 2007 service pack 2 it would, but NOPE.

Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." It seems like this is the likely problem, mentioned in the below Symantec technote: http://www.symantec.com/business/support/index?page=content&id=TECH128062

Initially I was using my user account which does not have local admin rights on the remote hosts, to log onto the media server and launch the BE console topush the Manage Your Profile | Site Feedback Site Feedback x Tell us about your experience... Solved "Error connecting to the 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: Symantec Backup Exec 2010 R3 Server Suite Join our community for more solutions or to ask questions.

During the install, we will attempt to read/write to the remote systems registry. My new house... The content you requested has been removed. Check This Out All rights reserved.

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 And it didn't solve the problem. "Microsoft Exchange 2010 database backup fails with v-79-57344-913 database was not found" 0 Kudos Reply « Previous 1 2 Next » Contact Privacy Policy Terms It sucks though that they run from 4pm until about 1pm the next day. RAWS does not need a service account, as it runs as local system.

When you are performing a push install, you are being prompted for credentials to the remote machine. You'd use the same credentials to install/update the RAWS agent as you would to install the application... I can start and stop the service, reinstall the agent, reboot backup exec server, nothing works. 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.

if not, it'll try to do a standard backup using a standard agent and probably fail backup exec will also let you push a "standard" agent to a sql box and Office locations in Denver, Boulder, Colorado Springs, Fort Collins, Glenwood Springs, Pueblo, Silverthorne, Albuquerque, Santa Fe and Cheyenne. 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