|
|
Agent issue w/ DPM 2010 on Windows Server 2008 R2 w/ Hyper-V
I've installed the DPM 64-bit client on a Win 2008 R2 server w/ Hyper-V
(using manual installation) that is not a DC, and is in the same domain as
the DPM server. When I try to use SetDPMServer, using 3 formats for server
name: NetBIOS name alone, FQDN style, and domain-qualified, I get failures
each time. In the domain-qualified case it's an "RPC server is unavailable",
in the other cases it's an 0x80004005 "Unspecified error". I've disabled the
firewall internally (I can ping the DPM server), and I've confirmed that the
DPM server is in the necessary local security groups. I've also installed
(and rebooted after) the recommended hotfixes KB975354 and KB975921 that are
apparently needed for protecting VMs on R2. Where should I go from here?
I've heard about DCOM and port issues in some cases, but again, the firewall
is disabled. Suggestions?
|
|
0
|
|
|
|
Reply
|
Utf
|
2/26/2010 3:16:01 PM |
|
This can happen if you have a firewall policy applied and due to which the
well known rules for WMI got removed from the firewall.
Please verify the below:
1. open firewall.cpl and click "Allow programs to communicate though
firewall"
2. scroll to the end and see if you can find "Windows management
instrumentation"
If you could not find the rule. This was the root cause for the agent
install failure.
Resolution:
Please rollback your security policies if any applied and try the agent
install.
If you have to apply any security policy make sure you select "Remote Wmi"
as a remote administration role.
Please let us know if the problem is resolved
--
This posting is provided “AS IS” with no warranties, and confers no rights
"cseaman" <cseaman@discussions.microsoft.com> wrote in message
news:A913C1D6-EB97-4F85-8D4D-812794779B5D@microsoft.com...
> I've installed the DPM 64-bit client on a Win 2008 R2 server w/ Hyper-V
> (using manual installation) that is not a DC, and is in the same domain as
> the DPM server. When I try to use SetDPMServer, using 3 formats for
> server
> name: NetBIOS name alone, FQDN style, and domain-qualified, I get failures
> each time. In the domain-qualified case it's an "RPC server is
> unavailable",
> in the other cases it's an 0x80004005 "Unspecified error". I've disabled
> the
> firewall internally (I can ping the DPM server), and I've confirmed that
> the
> DPM server is in the necessary local security groups. I've also installed
> (and rebooted after) the recommended hotfixes KB975354 and KB975921 that
> are
> apparently needed for protecting VMs on R2. Where should I go from here?
> I've heard about DCOM and port issues in some cases, but again, the
> firewall
> is disabled. Suggestions?
|
|
0
|
|
|
|
Reply
|
Chandraneel
|
3/3/2010 8:04:46 AM
|
|
|
1 Replies
1625 Views
(page loaded in 0.015 seconds)
|
|
|
|
|
|
|
|
|