How to enable WMI from te server

Theo
Theo used Ask the Experts™
on
When trying to obtaion an inventory of my network I see that some workstations report only partial information because WMI is not enabled. I can do that with the help of this KB article: http://support.microsoft.com/kb/875605 . However, I do not want to do this everytime I connect another computer, and this solution is meant for XP, have no idea yet about Vista/7. My question can I change something on my SBS2003 server so that every new computer takes over the right settings?

Thanks
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
Are all the workstations members of the domain? In this case I would use Group Policy to propagate an enabling of WMI.
Top Expert 2013

Commented:
Except for the permissions issue, you can configure the client machine's firewall by making changes to the related Group Policy on the server. This will then be applied to all workstations. Most often just the "Allow remote administration exception" change will resolve the issue.
In the group Policy Management console go to the "Small Business Server Firewall" policy - Edit | Computer Configuration | Administrative Templates | Network | Network Connections | Windows Firewall | Domain Profile | enable the appropriate exceptions
The policy changes will take up to 90 minutes to be applied to the workstations and do require a reboot. You can force this with  gpupdate /force, but the reboot is still required for firewall changes.

Author

Commented:
Gentlemen thank you both.
When I go to the Group Policy management console ( "Small Business Server Firewall" policy - Edit | Computer Configuration | Administrative Templates | Network | Network Connections | Windows Firewall | Domain Profile ), everything is already enabled. There are 4 keys to switch, but the one tha comes closest is 'Allow remote desktop exception'. There is no .... administration exception.

Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

Top Expert 2013

Commented:
It should be there. Is your server fully up to date with SP2

Author

Commented:
Yes SP2 is definitely there. This is the path I use:

Group Policy Managemet
Forest Richel2.local
Domains
Richel2.local
Small Busiess Server Windows Firewall
/Network/ Network Connections Windows Firewall/Domain profile
(here are the following 4 settings):

Windows Firewall allow file and printer sharing (Enabled)
Windows Firewall allow local port exceptions (Enabled)
Windows Firewall Allow local program exceptions (Enabled)
Windows Firewall Allow remote desktop exception (Enabled)

Author

Commented:
Sorry I omitted a fifth setting: Windows Firewall: Protect all Network connections (Enabled).
Top Expert 2013

Commented:
Interesting. There should be 14 policies one of which is the "allow remote administration exception"
Can you create a new policy and see if it is there?

Author

Commented:
I think I have found it.

In the path: Group Policy Managemet
Forest Richel2.local
Domains
Richel2.local
Small Busiess Server Windows Firewall

I clicked on the latter and proceeded in the right side box. One can however edit nothing here. What I should have done was: Click right on 'Small Busiess Server Windows Firewall'and then select 'edit'. Then opens a new window with the 14 options and editable. I have changed the necessary switch and will get back here when I know it works, but that is going to be tomorrow.
Top Expert 2013

Commented:
Sounds good. Let us know how you make out.

Author

Commented:
Well it works partially: XP computer are accessible, a Vista ws is not accessible and returns:

Event 10006 Source Dcom

DCOM got error "The RPC server is unavailable. " from the computer 192.168.16.11 when attempting to activate the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

(Of course we have rebooted)

Top Expert 2013
Commented:
That may not be an easy one to fix.
First thing I would do is manualy make the DCOM changes outlined in your Microsoft article on one machine to see if that is the actual problem. If so we can look into whether that change can be made using the registry. From there we can make the registry changes, assuming there is one, using group policy.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial