Error Connecting To Remote Registry Backup Exec
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
Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67
Sign In CommunityCategoryBoardResourcesUsers backup exec cannot connect to the remote computer turn on suggestions Auto-suggest 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 : Agent Update: Error connecting to the remote regis... VOX : Backup and Recovery : Backup Exec : Agent Update: Error connecting to the remote regis... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Agent Update: Error connecting to the remote registry of Server St3phan Level 3 05-24-2011 02:42 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I have a problem with the Agent Update of Backup Exec from 2010 R2 to R3. During theupdateof theagents(includingtheinstallationof agents), Inoticedthe following: I logged ontheBackupExecmediaserver with my personal accountthatisno member of thedomainadminsandalso has no access to someservers. Onthe mediaservers this account has local admin priviledges and is also listed as user in Backup Exec If Iwantto updatetheagentson theservers, I getthe error:Errorconnectingtotheremoteregistryofservers.Ensurethatthecurrentloggedinaccountisnotblockedfromaccessingtheremoteregistryandthattheremoteregistryisavailablebeforetryingagain. Thiswouldalsoseemlogicalas far aswhenI will not have awindowto set theusercredentialsfortheremote computer. I entered the correct remote computer credentials in this window: Theaccount thatIuseisdefinitelya localadminonallservers.Withthis account,theBackupExecservices run, too. Interestingly,itispossibleto updatetheagentswhenI logintotheBackupExecmediaserverwith this accountthat islocaladminonallserversandrunningthe services. 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? Did anybody knows this behavoir and could tell me how I can fix this? 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 Mod
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 A push install of the remote agent fails with: "Error connecting https://vox.veritas.com/t5/Backup-Exec/Agent-Update-Error-connecting-to-the-remote-registry-of-Server/td-p/396173 to the remote computer. Ensure that the computer is available, has WMI enabled and is not blocked by a firewall" Article:000015581 Publish: Article URL:http://www.veritas.com/docs/000015581 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your https://www.veritas.com/support/en_US/article.TECH177317 Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Push install of the Backup Exec Remote Agent to a Remote Windows Server fails with error: "Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled and is not blocked by a firewall" Error Message Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. Solution Solution 1: Manually install the remote agent Copy the RAWS32/RAWS64 (from X:\Program Files\Symantec\Backup Exec\Agents) and the MSXML folders on the particular remote server where you want to install Remote Agent.On the remote server, run setup.exe from the RAWS32/RAWS64 folder and complete the install.Make sure to enable "Publishing" on
October (10) September (7) August (10) July (1) June (2) May (2) April (3) March (3) February (3) January (4) December (3) November (4) October (4) September (19) August (3) July (14) June http://dbastas.blogspot.com/2012/03/symantec-backup-exec-remote-agent.html (8) May (5) April (6) March (13) February (18) January (7) December (3) November http://www.lewan.com/blog/2010/09/28/backup-exec-2010-r2-remote-agent-install-error-code-1603 (15) October (9) September (1) August (6) July (21) June (21) May (82) Labels ADSL (1) Antispam (2) Antivirus (1) asterisk (1) Avaya (2) Boot Disks (2) Cisco (13) Core (7) Dell (1) Excel (1) Exchange Server (34) Firefox (1) Hyper-V (19) Hyper-V R2 (22) IIS (1) IPv6 (1) ISA Server (3) Linux (22) Microsoft Office (3) mysql backup exec (1) Networking (20) ntfrs (2) OpenVPN (1) Oracle (3) Outlook (6) PFSense (2) Powershell (7) Procurve (5) Remote Control (1) Routers (2) SharePoint Server (1) SmoothWall (1) SQL Server (6) squid (1) Symantec BackupExec (1) Synology (1) Teamviewer (1) Terminal Services (1) Thecus (1) TMG 2010 (1) UPS (1) VBA (1) VMware (92) VMware View (3) VMware Workstation (1) WDS (1) wget (1) Windows 2000 (6) Windows 7 (41) Windows 8 (3) Windows error connecting to Live Mesh (1) Windows Server 2003 (50) Windows Server 2008 (49) Windows Server 2008 R2 (49) Windows Server 2012 (5) Windows Vista (32) Windows XP (17) Zyxel (2) Followers About Me Dimitris Bastas A boy and his dog View my complete profile Visitors Sunday, March 18, 2012 Symantec Backup Exec remote agent installation error When you try to install Symantec Backup Exec Agent to a remote computer you receive the following error: "Error connecting to the remote server. Ensure that the server is available, has WMI enabled, and is not blocked by a firewall.24" To fix this problem try the following on the remote computer: Run Group Policy Editor or the local group policy editor (gpedit.msc) and from the Local Computer Policy/Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignments allow Administrators, Local Service, and Network Service accounts to "Adjust Memory Quotas for Process Properties" and Local Service, and Network Service to "Replace a process level token". Remote user must also be a member of Local Administrators group and Remote Registry service must be running. Reboot the remote server to apply changes. Try to install Backup Exec agent again after rebooting the remote server. 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)
Managed IT Services Managed Infrastructure Managed Cloud Hosting Managed Print Managed Data Protection Managed Network Security Managed Technology Spend Blog Contact Us Customer Support Lewan Technology Blog The latest insights, industry news, tips and topics from our team of experts. 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 trying to remotely push a Backup Exec 2010 R2 remote agent, we were getting a lot of the "error code 1603" messages, which stated: "Error connecting to the remote server. 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 Our workaround was to just install the client manually on each server that wouldn't connect, instead of going through all the steps mentioned in the above technote. Written by Lewan Solutions View & Submit Comments [fa icon="envelope"] Subscribe to Email Updates Search Blog Posts in Google [fa icon="comments-o"] Follow us Get even more great content, photos, event info and industry news. [fa icon="tags"] Posts by Topic VMware (175) Citrix (130) Microsoft (115) Microsoft Windows (79) Citrix XenDesktop (69) Citrix XenApp (65) How To Guide (57) Virtualization (55) VMware vSphere (48) Managed Services (36) Cisco (33) Data Storage (31) Apple (25) Lewan Awards & Certifications (22) Lewan News & PR (18) Microsoft Exchange (18) Data Backup & Recovery (17) Microsoft Hyper-V (15) Cloud Computing (14) NetApp (13) Paper (12) Paperless Solutions (12) Data Security (10) Dell (10) Disk Performance (10) IT Solutions (10) Managed Infrastructure & Helpdesk (10) Citrix XenServer (9) Lewan Events (9) Printers & Copiers (9) Xerox (9) AppSense (8) HP (8) Networking (8) Sales Technique (8) Linux (7) Microsoft Office (7) PowerShell (6) Citrix Storefront (5) Unified Communication & Collaboration (5) VMware vCenter (5) Citrix XenMobile (4) Email Security (4) infographic (4) CommVault (3) CRN (3) Fortrust (3) Google (3) Microsoft Outlook (3) Nimble Storage (3) Unidesk (3) Barracuda (