"Error connecting to the remote registry" when pushing remote agent for Backup Exec


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 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,
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Naga Bhanu Kiran KotaCloud Architecture ManagerCommented:

i think there might some restrictions for the user a/c you are using to deploy the software. Check this microsoft article


Check if this user has the log on locally, act as part of OS and long interactively permissions on these two servers.

davidrobertbristowAuthor Commented:
Thanks.  I'll try your solution over the next hour and let you know how it works out.
davidrobertbristowAuthor Commented:
Okay, regarding http://support.microsoft.com/kb/314837 mydomain\administrators have full control to the winreg key.  I am comparing two servers, sames OS win2003, one of which allowed me to write to the registry (let's call it "success") and the other which didn't (let's call it "failed").  The difference that I see is that "failed" has a key "AllowedExactPaths" while "success" does not.  Would this make a difference?

Regarding additional comments,
1.  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 updates).
2.  For both servers no users or groups are defined for "deny log on locally"
3.  I couldn't find the "logon interactively" policy.
4.  I am able to log on through TS as an Administrator on failed.

Thanks for your help,

Get Blueprints for Increased Customer Retention

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

davidrobertbristowAuthor Commented:
Sorry, "act as part of the Operating System" user rights assignment is also the same for both success and failed (lists my Administrator account).

Thanks again,
davidrobertbristowAuthor Commented:
Also, windows firewall is turned off on "failed".  No other firewall program is running.  Thanks.
davidrobertbristowAuthor Commented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.