Jump to content

r042wal

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About r042wal

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Dyllon, problem solved and thanks for your patience and perseverance. The DCOM WMI article was informative and shed new light on the subject. As you know, the administrator account is disabled by default on a domain controller and we are encouraged to create a user account with domain admin rights. That's the way this network has been since 2006. Administrator account had been disabled and the Domain Admin crated was named sbsadmin since it is a Small Business Server 2011 network. As soon as I tried to push an install to the problematic Win 10 computer using the built-in administrator acc
  2. No luck. Made explicit inbound rules on the endpoint for both ports
  3. OK thanks. I'm uploading a capture. The computer I'm pushing in the capture is 192.168.0.43 amanda3.zip
  4. I already had the WMI rules. I had a GPO for that but I also added it manually to the Win 10 computer as well ass the File and Printer Sharing inbound rules. It still didn't work: 192.168.0.43 Installation failed. Access is denied. Failed to create remote service. 8/30/2017 2:38:21 PM 192.168.0.43 Installation failed. The RPC server is unavailable. Please allow WMI through Windows Firewall. 8/30/2017 2:38:21 PM I made an install package. I'm not too impressed that all this worked had to be put into a computer just because it is Win 10. I'm su
  5. No that's not the case. I have 26 Windows 7 clients and 4 servers and they all worked fine pushing. I have not done anything out of the ordinary. As I said this appears to be something specific to Windows 10 and if I can't manage them through the policy on the server, why bother. Maybe if you can't figure it out I will go back to my sales rep and have them escalate it. I can't afford to have problems with Win 10 computers right out of the box going forward.
  6. I can telnet from the client to port 18457 on the server
  7. Sorry, the error is "The RPC server is unavailable. Please allow WMI through Windows Firewall"
  8. I applied the rules (see below) and still receive both errors depending on whether I check WMI off or not: Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\Windows\system32>netsh firewall set service RemoteAdmin enable IMPORTANT: Command executed successfully. However, "netsh firewall" is deprecated; use "netsh advfirewall firewall" instead. For more information on using "netsh advfirewall firewall" commands instead of "netsh firewall", see KB article 947709 at https://go.microsoft.com/fwlink/?linkid=121488 .
  9. I have some new Win 10 computers on my network, out of the box, no 3rd-party antivirus/firewall products. I get two different errors depending on whether WMI is checked or not: Installation failed. Access is denied. Failed to create remote service. (winthout WMI) Installation failed. The RPC server is unavailable (enable WMI) I confirmed the .NET 3.5 role is enabled. WMI service is running on the computer. All my Win 7 clients pushed out without issue. The new Win 10 computers are on a Small Business Server 2011 network. Group Policy prevents the firewall from being disable
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.