Share via


DCOMSec-wmi.vbs

By The Scripting Guys, Microsoft Corporation

This script exempts applications from the DCOM activation security check by editing the registry, using the WMI System Registry provider. It can run against a local or remote computer.

You can get the GUID of the application to be exempted from the Component Services MMC snap-in (comexp.msc).

DCOMSec-wmi.vbs corresponds to DCOMSec.vbs, one of the scripts that ships with Application Compatibility Testing and Mitigation Guide for Windows XP Service Pack 2 and which are documented in the Appendix. You can download a Windows Installer (.msi) file that installs the Guide and its associated scripts from:

https://www.microsoft.com/downloads/details.aspx?FamilyId=9300BECF-2DEE-4772-ADD9-AD0EAF89C4A7&displaylang=en

To use the script, copy the code, paste it into Notepad, and then save the script as DCOMSec-wmi.vbs. To run the script, open a command prompt window to the directory of the script and type:

cscript dcomsec-wmi.vbs

If the default script host on the computer is Cscript.exe, the initial "cscript" may be omitted.

Script Code

'******************************************************************************
'DCOMSec-wmi.vbs
'Author: Peter Costantini, the Microsoft Scripting Guys
'Date: 8/25/04
'Revision 1.0
'This script can be run against a local or remote computer to
'exempt applications from the DCOM activation security check.
'******************************************************************************

On Error Resume Next

'Global variables
strComputer = "." ' Can be changed to name of remote computer.

'Connect with WMI service and StdRegProv class.
Set objReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _
 strComputer & "\root\default:StdRegProv")
If Err = 0 Then
  SetValue
Else
  WScript.Echo "Unable to connect to WMI StdRegProv on " & strComputer & "."
  WScript.Echo "  Error Number:" & Err.Number
  WScript.Echo "  Source:" & Err.Source
  WScript.Echo "  Description:" & Err.Description
End If
Err.Clear

'******************************************************************************

Sub SetValue

'Local constants and variables
Const HKEY_LOCAL_MACHINE = &H80000002
strKeyPath = "SOFTWARE\Microsoft\Ole\AppCompat" & _
 "\ActivationSecurityCheckExemptionList"
'Get GUID of application from Component Services MMC snap-in (comexp.msc).
strEntryName = "{00020812-0000-0000-C000-000000000046}"
'Microsoft Excel Application (example)
strValue = 1

intReturn = objReg.CreateKey(HKEY_LOCAL_MACHINE, strKeyPath)
If intReturn = 0 Then
  WScript.Echo "Created registry subkey: " & strKeyPath & VbCrLf & _
   "If it previously existed, did not overwrite existing values."
  intReturn = objReg.SetStringValue(HKEY_LOCAL_MACHINE, strKeyPath, _
   strEntryName, strValue)
  If intReturn = 0 Then
    WScript.Echo "Added registry entry: " & strEntryName & VbCrLf & _
     "Value: " & strValue
  Else
    WScript.Echo "ERROR: Unable to add registry entry " & strEntryName
  End If
Else
  WScript.Echo "ERROR: Unable to create registry path " & _
   strKeyPath
End If

End Sub

For online peer support, join The Official Scripting Guys Forum! To provide feedback or report bugs in sample scripts, please start a new discussion on the Discussions tab for this script.

Disclaimer

This sample script is not supported under any Microsoft standard support program or service. The sample script is provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.