ValidateNewPackageSource Method in Class SMS_SoftwareUpdatesPackage

Article
05/03/2011

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

The ValidateNewPackageSource Windows Management Instrumentation (WMI) class method, in Configuration Manager, validates a new package source location for a software update. This method might be used when changing the package source location of a software update package due to infrastructure changes or a server failure.

Note

All of the updates available in the old package source must be available in the new package source for validation to succeed.

The following syntax is simplified from Managed Object Format (MOF) code and defines the method.

SInt32 ValidateNewPackageSource(
     String PackageSource
);

Parameters

PackageSource
Data type: String

Qualifiers: [in]

The location of the package content to verify.

Return Values

An SInt32 data type that is 0 to indicate success or non-zero to indicate failure.

For information about handling returned errors, see About Configuration Manager Errors.

Remarks

This method is new in the latest version of Configuration Manager. Note that it is the only way to change the package source for an SMS_SoftwareUpdate Server WMI Class object. Most other types of packages can be changed in the console, but not the software update package. The access to this package from the console is restricted.

To use this method:

Manually copy the package files from the old source location to the new location.
In your application, obtain the SMS_SoftwareUpdatesPackage Server WMI Class object for the software update.
Include a call to ValidateNewPackageSource on the package.
On successful return from the method, have the application change the StoredPkgPath property in the package to indicate the new source location.

Requirements

Runtime Requirements

For more information, see Configuration Manager Server Runtime Requirements.

Development Requirements

For more information, see Configuration Manager Server Development Requirements.