Deprecated methods

Functions

Semantics:

Adds a new policy to the PMAD. The version (instance) ID of the policy is a GUID. If another policy is added to PMAD with the same version (instance) ID, an error is returned if the name, policy (logical) ID, version, or stream content is different from that of the existing policy. If everything is the same, the interface pointer to the existing policy is returned.

The new policy that is created by this method requires this version of the policy type. This means the minimal required package version of this policy type version must be installed on the node before the new policy version is deployed.

Parameters:

	sName	- Visible name of the policy. The maximal length is 64 characters.
	sVersion	- Version string of the new policy version.
	sLogicalId	- Policy (logical) ID (GUID without brackets). It is the same for all versions of the policy. When it is used in the API, it often refers to the latest version of the package.
	sInstanceId	- Package version (instance) ID (GUID without brackets). It uniquely identifies a package version.
	sUser	- Name of the user who created the policy. The name can be any kind of string. The maximal length is 64 characters.
	sDescription	- Description of the policy version. The maximal length is 256 characters.
	sCategory	- Category of the policy version. The maximal length is 32 characters.
	dCreationDate	- Creation date as a COleDateTime value.
	pPolContents	- Data content of the policy.
	bForce	- Not used yet.
	ppPolicy	- IOvPmdLogicalPolicy interface pointer to the new policy. It is NULL, if the operation has failed.

Possible errors:

Database communication errors
Not enough disk space to save the policy
Policy with the same instance id but different attributes already exists
Name may not contain '*'

Since:

7.0

Deprecated since:

8.00

Instead of this method, you should use the IOvPmdLogicalPolicyType80::AddLogicalPolicy3(...) method. It still exists for backward-compatibility. It is possible that this method will be made obsolete in future releases.

Semantic:

Schedules a job that uninstalls all installed policies and packages.

This is an asynchronous operation. The method does not perform validation before job execution. The method simply adds the job to the queue and returns immediately. The deployment job itself may fail during execution. An error description is available for the failed deployment job (see IOvPmdJobEntry::GetErrorDescription(...) ).

Possible errors:

Network communication errors
Database communication errors

Since:

6.x

Deprecated since:

8.00

Instead of this method, you should use IOvPmdNode80::Uninstall(...).

Semantics:

Deploys the specified instrumentation categories to the node.

This is an asynchronous operation. The method does not perform validation before job execution. The method simply adds the job to the queue and returns immediately. The deployment job itself may fail during execution. An error description is available for the failed deployment job (see IOvPmdJobEntry::GetErrorDescription(...) ).

Parameters:

vInstrumDirArray

- This parameter is a variant that contains a SAFEARRAY. Each element of the array is again a variant that contains a BSTR. This string represents an instrumentation category (subdirectory) that you should deploy to the node. The method looks for the specified sub-directories and, if they are found, it deploys all files that are stored in these sub-directories. If the parameter "varInstrumDirArray" is empty or the containing SAFEARRAY is empty, the method deploys all subdirectories that are available for the managed node's platform.

Parameters:

bFirstRemoveInstr

- If bFirstRemoveInstr is set to VARIANT_TRUE, all instrumentation files that are currently installed on the managed node are removed before the new instrumentation files are deployed.

Possible errors:

Database communication errors

Since:

7.0

Deprecated since:

8.00

This operation has the same semantic as method IOvPmdNode80::DeployInstrumentation3(...) called with the flag PMAD_DEPL_REMOVE_FIRST_OPT. It exists only for backward-compatibility. Because this method is marked as deprecated, you should call IOvPmdNode80::DeployInstrumentation3(...) in your application.

Semantics:

This method schedules the installation of this policy version on all nodes that are members of the specified node group. If the package version that implements the required policy type version of this policy version is not yet installed on the nodes of specified group, it is automatically installed by PMAD before the policy is deployed. An package upgrade is performed on the nodes if the policy requires an newer version of the package than the one that is currently installed.

For every node in the node group, a separate deployment job is created by this method. The method simply adds all the jobs to the queue, and then returns to the caller. Note that there is no dedicated deployment job type to deploy a policy to a node group.

Parameters:

	sNodeGroup	- ID of the node group where this policy version should be installed.
	bCheckVersion	- If TRUE, this policy version is installed only if no version or an older version of the same policy is currently installed on the node.
	bEnable	- Boolean that defines whether the policies should be enabled or disabled after installation.

Possible errors:

Node group with specified name is not defined in WMI
Database communication errors

Since:

6.x

Deprecated since:

8.00

This operation has the same semantic as the method IOvPmdLogicalPolicy80::DeployOnNodeGroup2(...). It exists only for backward-compatibility. Because this method is marked as deprecated, you should call IOvPmdPolicyGroup80::DeployOnNodes2(...) in your application.

Semantics:

Schedules the installation of all policies that are part of this policy group and its child groups on all nodes that are part of the specified the node group.
For every policy and node, a separate deployment job is created by this method. The method simply adds all the jobs to the queue, and then returns to the caller. Note that there is no dedicated deployment job type to deploy a policy group to the node.

Parameters:

	sNodeGroup	- Name (ID) of the node group in WMI.
	bCheckVersion	- If true, a policy version is installed only if no version or an older version of the same policy is currently installed on the node. Otherwise, it is always deployed.
	bEnable	- Boolean to define whether the policy versions should be enabled or disabled after installation.

Possible errors:

Node group not found in WMI
Database communication errors

Since:

6.x

Deprecated since:

8.00

This operation has the same semantic as the method IOvPmdPolicyGroup80::DeployOnNodeGroup2(...). It exists only for backward-compatibility. Because this method is marked as deprecated, you should call IOvPmdPolicyGroup80::DeployOnNodeGroup2(...) in your application.

Semantics:

This method schedules the installation of this policy version on all nodes specified in the list of node IDs (parameter "vNodeIDs"). If the package version that implements the required policy type version of this policy version is not yet installed on the specified nodes, it is automatically installed by PMAD before the policy is deployed. An package upgrade is performed on the node if the policy requires an newer version of the package than the one that is currently installed.

This is an asynchronous operation. The method does not perform validation before job execution. The method simply adds the job to the queue and returns immediately. The deployment job itself may fail during execution. An error description is available for the failed deployment job (see IOvPmdJobEntry::GetErrorDescription(...) ).

Parameters:

	vNodeIDs	- VARIANT of SAFEARRAY containing the IDs of the nodes where the policy should be installed.
	bCheckVersion	- If TRUE, this policy version is installed only if no version or an older version of the same policy is currently installed on the node.
	bEnable	- Boolean that defines whether the policies should be enabled or disabled after installation.

Possible errors:

Invalid variant structure of parameter 'vNodeIDs'
Database communication errors

Since:

6.x

Deprecated since:

8.00

This operation has the same semantic as the method IOvPmdLogicalPolicy80::DeployOnNodes2(...) called with the flags PMAD_DEPL_IGNORE_VERSION_OPT and PMAD_DEPL_DISABLE_OPT. It exists only for backward-compatibility. Because this method is marked as deprecated, you should call IOvPmdPolicyGroup80::DeployOnNodes2(...) in your application.

Semantics:

Schedules the installation of all policies that are part of this group and its child groups on the specified nodes.
For every policy and node, a separate deployment job is created by this method. The method simply adds all the jobs to the queue, and then returns to the caller. Note that there is no dedicated deployment job type to deploy a policy group to the node.

Parameters:

	vNodeIDs	- VARIANT that contains a SAFEARRAY with the ID of the nodes, where the policies should be installed, as elements.
	bCheckVersion	- If true, a policy version is installed only if no version or an older version of the same policy is currently installed on the node. Otherwise, it is always deployed.
	bEnable	- Boolean to define whether the policy versions should be enabled or disabled after installation.

Possible errors:

Invalid variant structure of parameter 'vNodeIDs'
Database communication errors

Since:

6.x

Deprecated since:

8.00

This operation has the same semantic as the method IOvPmdPolicyGroup80::DeployOnNodes2(...). It exists only for backward-compatibility. Because this method is marked as deprecated, you should call IOvPmdPolicyGroup80::DeployOnNodes2(...) in your application.

Semantics:

Return the specified version of the object.

Parameters:

	sVersion	- The version string of the object to be returned (for example, "3.4" or "0003.0004").
	ppInstance	- The IDispatch interface pointer of the specified object version. It is NULL if the specified version does not exist.

Possible errors:

Database communication errors

Since:

6.x

Deprecated since:

8.00

Instead of this method, you should use the 'GetOtherVersion2' methods that are defined in IOvPmdPackage80, IOvPmdLogicalPolicy80, and IOvPmdLogicalPolicyType80.

Semantics:

Returns a list of all policy groups to which this policy version is assigned.

Parameters:

ppGroups

- Safearray of IDispatch interface pointers to the policy groups. Use the method "IOvPmdPolicyManager::CVar(...)" to access the elements of the array within a VB script.

Possible errors:

Database communication errors

Since:

6.x

Deprecated since:

8.00

Instead of this method, use the method IOvPmdLogicalPolicy80::GetPolicyGroupList2(...). It still exists for backward-compatibility. It is possible that this method will be made obsolete in future releases.

Semantics:

This method asks the managed node which packages are currently installed, and then updates the DB node inventory on the server accordingly. It does not perform a policy synchronization but only a package synchronization.

In addition, the synchronization method has the following limitations:

1. Packages that are not known (registered) on the PMAD-Server are not automatically registered during the synchronization process. The operation fails with an error if such a package is installed on the node.
2. If the version of the package that is installed on the node does not exist in the PMAD DB, but another version of the same package is already known, the operation first registers this package version and then adds it to the inventory of the node in the server DB.

This is an asynchronous operation. The method does not perform validation before job execution. The method simply adds the job to the queue and returns immediately. The deployment job itself may fail during execution. An error description is available for the failed deployment job (see IOvPmdJobEntry::GetErrorDescription(...) ).

Possible errors:

see method IOvPmdNode80::Synchronize(...)

Since:

7.0

Deprecated since:

8.00

This operation has the same semantic as method IOvPmdNode80::Synchronize(...) called with the flag 'PMAD_DEPL_SKIP_POLICIES_OPT'. It exists only for backward-compatibility. Because this method is marked as deprecated, you should call IOvPmdNode80::Synchronize(...) in your application.

Semantics:

This method schedules a complete reinstallation of the node. It does not uninstall the policies and packages before installing them again. Instead, they are replaced on the node. First, the method reads the policy and package inventory from the DB on the server. Second, it installs the package versions that are on the node again. Afterwards, all policy versions are redeployed. The instrumentation categories that are required by these policy versions are also redeployed.

This is an asynchronous operation. The method does not perform validation before job execution. The method simply adds the job to the queue and returns immediately. The deployment job itself may fail during execution. An error description is available for the failed deployment job (see IOvPmdJobEntry::GetErrorDescription(...) ).

Possible errors:

Network communication errors
Database communication errors

Since:

6.x

Deprecated since:

8.00

Instead of this method, you should use IOvPmdNode80::Redeploy(...).

Semantics:

The semantic of this method is the same as IOvPmdLogicalPolicy80::RemoveFromAllNodes3(...).

The deployment job fails with an error message if another server owns this policy version on the managed node (see IOvPmdLogicalPolicy80::RemoveFromAllNodes3(...) ).

This is an asynchronous operation. The method does not perform validation before job execution. The method simply adds the job to the queue and returns immediately. The deployment job itself may fail during execution. An error description is available for the failed deployment job (see IOvPmdJobEntry::GetErrorDescription(...) ).

Parameters:

bForce

- VARIANT_BOOL flag to force policy removal from the node inventory on the management server, even if policy removal from the nodes failed.

Possible errors:

Database communication errors

Since:

7.50

Deprecated since:

8.00

Instead of this method, use the method IOvPmdLogicalPolicy80::RemoveFromAllNodes3(...). It still exists for backward-compatibility. It is possible that this method will be made obsolete in future releases.

Semantics:

This method schedules the uninstallation of all versions of this policy on all nodes on which it had been deployed. Packages that have been installed during installation of the policy are not uninstalled. This must be performed with IOvPmdPackage::RemoveFromNodes(...).

If dependent policies are still on the node, the job fails with an error message (see IOvPmdLogicalPolicy80::RemoveFromAllNodesForAllVersions2(...)).

The deployment job fails with an error message if another server owns this policy version on the managed node (see IOvPmdLogicalPolicy80::RemoveFromAllNodesForAllVersions2(...)).

This is an asynchronous operation. The method does not perform validation before job execution The method simply adds the job to the queue and returns immediately. The deployment job itself may fail during execution. An error description is available for the failed deployment job (see IOvPmdJobEntry::GetErrorDescription(...) ).

If the 'bForce' parameter is TRUE, the policy is removed from the DB node inventory on the management server, even if the actual policy deinstallation on the managed node failed (for example, because the node was down or reinstalled).

Parameters:

bForce

- VARIANT_BOOL flag to force policy removal from the policy inventory on the management server, even if the policy removal from the node failed.

Possible errors:

Invalid variant structure of the parameter 'vNodeIDs'
Database communication errors

Since:

7.50

Deprecated since:

8.00

Instead of this method, use the method IOvPmdLogicalPolicy80::RemoveFromAllNodesForAllVersions2(...). It still exists for backward-compatibility. It is possible that this method will be made obsolete in future releases.

Semantics:

The semantic of this method is the same as IOvPmdLogicalPolicy80::RemoveFromNodes3(...).

Parameters:

	vNodeIDs	- VARIANT that contains a SAFEARRAY containing the IDs of the nodes where the policy should be uninstalled.
	bForce	- Flag to force policy removal from the policy inventory on the management server, even if policy removal from the node fails.

Possible errors -

Invalid variant structure of the parameter 'vNodeIDs'
Database communication errors

Since:

7.50

Deprecated since:

8.00

Instead of this method, use the method IOvPmdLogicalPolicy80::RemoveFromNodes3(...). It still exists for backward-compatibility. It is possible that this method will be made obsolete in future releases.

Semantics:

This method schedules the uninstallation of all versions of this policy on all nodes specified in the list of node IDs (parameter "vNodeIDs"). Packages that have been installed during installation of the policy are not uninstalled. This must be performed with IOvPmdPackage::RemoveFromNodes(...).

This is an asynchronous operation. The method does not perform validation before job execution. The method simply adds the job to the queue and returns immediately. The deployment job itself may fail during execution. An error description is available for the failed deployment job (see IOvPmdJobEntry::GetErrorDescription(...) ).

If dependent policies are still on the node, the job fails with an error message (see IOvPmdLogicalPolicy80::RemoveFromNodesForAllVersions2(...) ).

The deployment job fails with an error message if another server owns this policy version on the managed node (see IOvPmdLogicalPolicy80::RemoveFromNodesForAllVersions2(...) ).

If the 'bForce' parameter is TRUE, the policy is removed from the DB node inventory on the management server, even if the actual policy deinstallation on the managed node failed (for example, because the node was down or reinstalled).

Parameters:

	vNodeIDs	- VARIANT that contains a SAFEARRAY containing the IDs of the nodes where the policy should be deinstalled.
	bForce	- VARIANT_BOOL flag to force policy removal from the node inventory on the management server, even if the policy removal from the node failed.

Possible errors:

Invalid variant structure of the parameter 'vNodeIDs'
Database communication errors

Since:

7.50

Deprecated since:

8.00

Instead of this method, use the method IOvPmdLogicalPolicy80::RemoveFromNodesForAllVersions2(...). It still exists for backward-compatibility. It is possible that this method will be made obsolete in future releases.

Semantic:

Restarts the deployment job that is specified by its ID. Its state is 'active' after calling this method. All suspended jobs for the same node are moved to state 'pending' by this method.

Parameters:

sJobId

- Unique job identifier.

Possible errors:

Database communication errors

Since:

6.x

Deprecated since:

8.00

This operation has the same semantic as the method IOvPmdJobScheduler80::RestartJob3(...) called with the flag PMAD_DEPL_NONE_OPT. It exists only for backward-compatibility.

Semantic:

Restarts the deployment job that is specified by its ID. Its state is 'active' after calling this method. All suspended jobs for the same node are moved to state 'pending' by this method.

Parameters:

	id	- Unique job identifier.
	vbSkipNodeCheck	- If this flag is TRUE, the restarted job skips the node prerequisite check.

Possible errors:

Database communication errors

Since:

7.50

Deprecated since:

8.00

This operation has the same semantic as the method IOvPmdJobScheduler80::RestartJob3(...) called with the flag PMAD_DEPL_NONE_OPT and PMAD_DEPL_SKIP_NODECHECK_OPT depending on the value of 'vbSkipNodeCheck'. It only exists for backward-compatibility.