05-19-2011 01:01 AM
Hi,
I get the following error when I push install agents to Win7 x64 computers.
-Error E0D3EBC0: Cannot deploy the Agent to NAME.
--OS008, Exception occurred: Attempt to access the remote Service Manager failed.
The requested control is not valid for this service.
(UMI:V-281-211-60352)
Any help would be greatly appreciated!
05-19-2011 01:36 AM
06-09-2011 02:37 AM
Have you tried the link ?
06-09-2011 08:08 AM
Yes, I checked all the settings mentioned on your link. I have deployed agents to WinXP computers but I'm still not able to deploy agents to Win7 x64 computers.
I would like to deploy the agent manually, but there is not even an KB article on how to do this.
EDIT: funny, I can't even reproduce the error message anymore. Nothing happens when I click on "Deploy Agent"
06-09-2011 08:37 AM
I set up a lab and installed BESR 2010 onto a 2003 R2 computer. I was able to deploy agents to Win7 x64 from the lab.
I'm quite upset to be honest.....
EDIT: Even though the agent deployed, I cannot connect to it from the lab nor from the production environment.
I'm close to beat the *****....... I spend so much time on this. What is an NFR license good for if you don't get any support.....
06-09-2011 08:43 AM
Because of the way COM is designed in latter operrating systems, you cannot deploy the Backup Exec System Recovery 2010 agent to Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2. Instead, you must manually install the agent to computers that run Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2. After you have manually installed the agent, you can then use Backup Exec System Recovery 2010 to remotely manage the Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 computer.
To install the agent remotely, visit the machine directly and install, or create a remote session and install the agent using a network share back to the install files, or copy the install file to that local machine.
06-09-2011 08:44 AM
The firewall built into Windows 7 computers will prevent remote management. Try disabling that.
06-10-2011 02:13 AM
I really appreciate your help Andy,
EDIT: KB article on how to manually install BESR agent, applies to 2011: http://www.symantec.com/business/support/index?page=content&id=HOWTO48582
Besides, I already tried to manually install the agent but I wasn't able to manage the agent. So I'm going to try it again.
Also, I believe it would be from great benefit for your customers if there was an KB article on error:
-Error E0D3EBC0: Cannot deploy the Agent to NAME.
--NAME, Exception occurred: Attempt to access the remote Service Manager failed.
The requested control is not valid for this service.
06-10-2011 04:40 AM
I just ran a port query on a Win7 x64 remote computer I installed BESR agent manually on. Andy, why is your agent installer not creating firewall exceptions on Win7 x64 computers?
I'm really upset! I spend at least 5 hours on this. I just couldn't believe it is so simple...
BESR 2010 agent installer does not create firewall exceptions on Win7 x64, therefore you cannot manage Win7 x64 computers unless you create those exceptions manually. How could something like this pass Symantec Quality Assurance?
06-10-2011 03:30 PM
1:1 management through the BESR console utilizes DCOM, which is why the agent isn't dynamically reconfiguring your firewall. This is why, as a test, we recommend disabling the firewall altogether to determine if this is the issue. DCOMs range of ports is sometimes tricky when it comes to reconfiguring firewalls.
07-13-2011 08:06 AM
I have tried installing the agent manually using the link above, but I still cannot connect to or manage this remote agent without turning off the firewall.
I am installing SSR 2011 on both Server 2008 & 2008 R2 with the same problem.
07-13-2011 09:02 AM
Are you using the Windows Firewall? If so, search the Microsoft website for details on how to make exceptions for DCOM traffic. There are several articles, depending on the OS you are using.