Re: WMI32_PRODUCT not listed
- From: Gerry Hickman <gerry666uk@xxxxxxxxxxx>
- Date: Sun, 02 Jul 2006 15:09:16 +0100
Hi James,
I think DCOM can be really good in an enterprise environment; the problem with Anti-Virus software and software Firewalls tends to be related to the way "Windows NT" has now become "Windows XP" and is the "norm" for home users. In the old days, you had NT for the enterprise and Win98 for home.
There's a massive difference between running RPC on a properly configured network with hardware firewalls, user-only rights, and a team of Network Admins, vs having it sitting there on a stand-alone home computer where Microsoft have dictated they will all log in as Administrators.
This has led to a slew of tools such as Windows Defender, Malicious software removal tool, WindowsUpdate, OfficeUpdate, XP firewall and numerous "home user" Anti-SpyWare and Anti-Virus packages that should never be allowed anywhere near a real LAN.
My main gripe (in the context of Microsoft and WMI) is that they are not consistent - there's no overall strategy, it's just fads and fashions.
James Crosswell wrote:
Gerry Hickman wrote:James Crosswell wrote:
Try http://www.microforge.net/kb/147
The situation with Win2003 is a mess; Microsoft should decide if these facilities are going to be used or not. Making Win2003 inconsistent with other o/s in relation to this is bad. What next, let's have some parts of WMI working in Vista, but not others??
I have to wonder why they removed this provider in Windows 2003 by default - it's certainly in a PITA though.
This is not to mention the numerous problems that users have configuring security on DCOM in order to get WMI to work (if it's not the Windows firewall it's some other antivirus product getting it's paws in the way - because they all know that DCOM is used for so many things that it presents a wide attack surface). I don't think WMI should be using DCOM in the first place - why don't they just use HTTP on the standard ports like all the other WBEM architectures? Then WMI wouldn't suffer just because DCOM is hijacked for a bunch of other fairly unscrupulous uses.
Ah well - I guess they have their reasons... it sure doesn't make it easy though.
Best Regards,
James Crosswell
Microforge.net LLC
http://www.microforge.net
--
Gerry Hickman (London UK)
.
- Prev by Date: list running applications
- Next by Date: Re: Script change of WMI permissions
- Previous by thread: list running applications
- Next by thread: Re: WMI32_PRODUCT not listed
- Index(es):
Relevant Pages
|
Loading