Installing Windows Agent on Windows Server 2008 x64

[Shirash]

Hi,

I am trying to install the Windows Agent on a Windows Server 2008 x64 Server, running Microsoft Exchange 2007. I had already installed the agent some months ago. Yesterday I ran through an update for the agents on all servers. Everything worked except for this one. So I uninstalled the agent on this server and tried it again using the Symantec Backup Exec 2010 R2. The installation failed with this message:

"Failed to connect to the remote computer. Make sure that the computer is available, WMI is enabled and not blocked by a firewall. 14" (not original message, translated from german)

I disabled the windows firewall temporarily. There is no other firewall running.
Copying the agent from the backupexec 2010 server to the exchange server and installing it manualy war working, the backups are working also.

But I hope there is a better solution fixing this issue.

It's much better for updating the agents using Backup Exec with the server list for remote installations.

[CraigV]

Hi Shirash,

I've had this too. Normally installing the agent manually worked, but you can also check and make sure that DNS isn't an issue, both on this server, and on your media server. Try resolving name and IP from both servers.

If that doesn't solve the issue, check the TN below and see if you can fix the problem...

http://www.symantec.com/business/support/index?page=content&id=TECH128062

Thanks!

[Shirash]

Hi Craig,

thanks for your feedback!
DNS ist working on both servers correctly.

The IP and hostname resolving correctly using nslookup.

The TN doesn't help me really.
There is no directory:

c:\ProgramData\Symantec\Backup Exec\PushLogs

and the eventlog doesn't show me any errors with DCOM.

[CraigV]

...and have you stopped and disabled your AV if you have 1 installed?

[Shirash]

Yes, there is no running AV at the moment...

[CraigV]

...that's weird. Try a reboot of the server before updating the RAWS agent again!

[Shirash]

Have the same problem at a Sharepoint 2010 Server.

I think there musst be a issue with the IIS.

Any known issues with this?

[Shirash · Accepted solution]

Solved the problem:

Started "remote registry service" on the remote machines.

:)