Securing Scripting Clients
Scripts and Visual Basic applications must set DCOM security, especially for remote access, and may also need to enable privileges.
WMI access differs between local and remote computers. For more information, see Connecting to WMI on a Remote Computer.
The following are the default access permissions by account:
Everyone, LocalService, NetworkService
Permission to read or write data and to run provider methods on the local computer. These accounts cannot create new classes or install new providers.
Full control on local computer. When connecting to a remote computer, the account must be a local administrator on the remote computer also.
WMI scripting and Visual Basic applications must set DCOM security levels appropriately for the operating systems they are targeting. For more information, see Setting the Default Process Security Level Using VBScript.
When connecting to a remote computer, you may need to change the service (NTLM or Kerberos) that handles authentication. For more information, see Setting the Authentication Service Using VBScript.
Access to some WMI classes or data may require a privilege that is not enabled. For example, you must include the Security privilege when connecting to the Win32_NTEventlogFile class. For more information, see Executing Privileged Operations Using VBScript.
If you are accessing WMI from an Active Server Page (ASP), then some IIS configuration is required. For more information, see Configuring IIS 5.0 and Later for WMI ASP Scripting.
You may be trying to connect to a namespace which requires an encrypted connection, in other words, one that requires an authentication level of pktPrivacy. For more information, see Setting the Default Process Security Level Using VBScript.