Chatee ahora con Soporte
Chat con el soporte

Foglight for Automation Action Packs 5.6.3.8 - Scripting ActionPack User Guide

COM and Automation Objects

The COM and Automation objects are required to perform remote tasks on Windows machines that are not configured for remote activation. Therefore additional configuring of the DLL surrogate is required.

Registry Permissions

Make sure that the Administrator user has Full Control access to the following registry keys:

•
HKEY_LOCAL_MACHINE/Software/Classes/AppID
•
HKEY_LOCAL_MACHINE/Software/Classes/CLSID/{0D43FE01-F093-11CF-8940-00A0C9054228}
•
HKEY_LOCAL_MACHINE/Software/Classes/CLSID/{13709620-C279-11CE-A49E-444553540000}
•
HKEY_LOCAL_MACHINE/Software/Classes/CLSID/{72C24DD5-D70A-438B-8A42-98424B88AFB8}
•
HKEY_LOCAL_MACHINE/Software/Classes/CLSID/{76A64158-CB41-11D1-8B02-00600806D9B6}
Configuration Script

Use the script below to configure DCOM.

1
Create a file named dcom-config.ps1 that contains the script below on the target machine.
2
Run the script on behalf of the Administrator user using the following command:
runas /user:Administrator powershell -File dcom-config.ps1

 

# Copyright 2010 Quest
# ALL RIGHTS RESERVED.
#
# PROPRIETARY/CONFIDENTIAL.
#
# This software is the confidential and proprietary information
# of Quest ("Confidential Information").
#
# You shall not disclose such Confidential Information and shall
# use it only in accordance with the terms of the license agreement
# you entered into with Quest
#
 
Function ConfigureAppID($appId,$appDescription,$systemGlobal) {
Echo "Processing $appId ($appDescription)"
 
if ($systemGlobal) {
$classesKey = "HKLM:\Software\Classes"
}
else {
$classesKey = "HKCU:\Software\Classes"
}
 
$AppIDKey = $classesKey + "\AppID"
 
if (!(Test-Path $AppIDKey)) {
$item=New-Item -Name "AppID" -Path $classesKey -Type directory
}
 
$CLASS_AppIDKey = $AppIDKey + "\{$appId}"
if (!(Test-Path $CLASS_AppIDKey)) {
$item=New-Item -Name "{$appId}" -Path $AppIDKey -Type directory
}
Set-ItemProperty -Path $CLASS_AppIDKey -Name "(default)" -Value "$appDescription"
Set-ItemProperty -Path $CLASS_AppIDKey -Name "DllSurrogate" -Value ""
}
 
Function ConfigureCLSID($clsId,$appId,$systemGlobal) {
Echo "Processing $clsId"
 
$name = (Get-ItemProperty -Path "HKLM:\Software\Classes\CLSID\{$clsId}\ProgID" -Name "(default)")."(default)"
Echo $name
 
if ($systemGlobal) {
$classesKey = "HKLM:\Software\Classes"
}
else {
$classesKey = "HKCU:\Software\Classes"
}
$CLSIDKey = $classesKey + "\CLSID"
$AppIDKey = $classesKey + "\AppID"
 
if (!(Test-Path $CLSIDKey)) {
$item=New-Item -Name "CLSID" -Path $classesKey -Type directory
}
 
$CLASS_CLSIDKey = $CLSIDKey + "\{$clsId}"
if (!(Test-Path $CLASS_CLSIDKey)) {
$item=New-Item -Name "{$clsId}" -Path $CLSIDKey -Type directory
}
Set-ItemProperty -Path $CLASS_CLSIDKey -Name "AppID" -Value "{$appId}"
}
 
Function ConfigureDCOM($appId,$systemGlobal) {
if (!$appId) {
$appId = [System.Guid]::NewGuid()
}
$appDescription = "Default DLL Surrogate"
 
ConfigureAppID -appId $appId -appDescription $appDescription -systemGlobal $systemGlobal
 
$CLSIDS = @(
# Scripting.FileSystemObject
"0D43FE01-F093-11CF-8940-00A0C9054228",
# Shell.Application
"13709620-c279-11ce-a49e-444553540000"
# WScript.Shell
"72C24DD5-D70A-438B-8A42-98424B88AFB8"
# WbemScripting.SWbemLocator
"76A64158-CB41-11D1-8B02-00600806D9B6"
)
 
foreach ($clsId in $CLSIDS) {
ConfigureCLSID -clsId $clsId -systemGlobal $systemGlobal -appId $appId
}
 
}
ConfigureDCOM -systemGlobal $true
 

Actions

This section contains descriptions of the actions included in the ActionPack for Scripting.

Run PowerShell Script

Executes a PowerShell script on the specified remote Windows host.

The Power Shell interpreter and the script file must exist on the remote host. To enable script file execution, run the following command:

powershell -command “&{set-ExecutionPolicy Unrestricted}”

 
Table 2. Run PowerShell Script Input Parameters
Name/Scripting name
Type
Description

Host/host

TopologyObject

[ScriptingHost]. The remote host to execute the command on.

Script/script

String

The full path to the script on the remote host, for example: C:\\test.ps1.

Parameters/params

String

Parameters that will be passed to the command. (Optional)

 
Table 3. Run PowerShell Script Output Parameters
Name/Scripting name
Type
Description

Command/cmd

String

The command that was executed on the remote host.

Output text/stdout

String

System Standard Output Text.

Error text/stderr

String

System Error Output Text. May be empty if no errors occured.

 

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación