You change the deployment package source for a software updates deployment package, in System Center 2012 Configuration Manager, by obtaining an instance of the SMS_SoftwareUpdatesPackage class and by using the ValidateNewPackageSource method.
Note |
---|
The package source for most other types of packages can be changed in the console. However, this option is not available for software updates packages. |
To change the deployment package source
-
Set up a connection to the SMS Provider.
-
Obtain an existing package object by using the SMS_SoftwareUpdatesPackage class.
-
Verify the package source by using the ValidateNewPackageSource method.
-
Change the package source for an existing software updates deployment package by changing the PkgSourcePath property of the package.
Example
The following example method shows how to change the deployment package source for a software updates deployment package by using the SMS_SoftwareUpdatesPackage class and the ValidateNewPackageSource method.
Note |
---|
All of the updates available in the old package source must be available in the new package source (the content source path, passed in as the newPackageSourceLocation variable in the below scripts). |
For information about calling the sample code, see Calling Configuration Manager Code Snippets.
Example of the subroutine call in Visual Basic:
Copy Code | |
---|---|
' PREWORK FOR ChangeDeploymentPackageSource ' Define the new package location to validate (package location must be UNC). newPackageSourceLocation = "\\SMSSERVER\source1" Call ChangeDeploymentPackageSource(swbemServices, _ "ABC00003", _ newPackageSourceLocation) |
Example of the method call in C#:
Copy Code | |
---|---|
//PREWORK FOR ChangeDeploymentPackageSource. // Define the new package location to validate (package location must be UNC). string newPackageSourceLocation = "\\\\SMSSERVER\\source1"; // Load the validateNewPackageSource parameters into an object to pass to the method. Dictionary<string, object> validateNewPackageSourceParameters = new Dictionary<string, object>(); validateNewPackageSourceParameters.Add("PackageSource", newPackageSourceLocation); //The method call. SUMSnippets.ChangeDeploymentPackageSource(WMIConnection, "ABC00003", validateNewPackageSourceParameters, newPackageSourceLocation); |
Visual Basic Script | Copy Code |
---|---|
Sub ChangeDeploymentPackageSource(connection, _ existingSUMPackageID, _ newDeploymentPackageLocation) On Error Resume Next ' Get an existing SUM Deployment Package to change. Set existingSUMDeploymentPackage = connection.Get("SMS_SoftwareUpdatesPackage.PackageID='" & existingSUMPackageID & "'") ' Check the package source for the existing SUM Deployment Package using the ValidateNewPackageSource method. existingSUMDeploymentPackage.ValidateNewPackageSource(newDeploymentPackageLocation) ' Check the error information from the SWBemLasError object to determine success or failure of the ValidateNewPackageSource method. If Err.Number = 0 Then ' Output a success message if the new package location is valid. Wscript.Echo "The new location of the SUM deployment package validated. " Wscript.Echo "Updating the SUM deployment package with the new package location. " ' Update the StoredPkgPath property of the existing deployment package ' with the new source location if the package location is valid. existingSUMDeploymentPackage.PkgSourcePath = newDeploymentPackageLocation ' Save the updated package deployment package. existingSUMDeploymentPackage.Put_ Else ' Output a failure message if the new deployment package location is not valid. Wscript.Echo "The new location of the SUM deployment package failed to validate. " End If End Sub |
C# | Copy Code |
---|---|
public void ChangeDeploymentPackageSource(WqlConnectionManager connection, string existingSUMPackageId, Dictionary<string, object> validateNewPackageSourceParameters, string newPackageSource) { try { // Get the specific SUM Deployment Package to change. IResultObject existingSUMDeploymentPackage = connection.GetInstance(@"SMS_SoftwareUpdatesPackage.PackageId='" + existingSUMPackageId + "'"); // Validate the existing SUM Deployment Package content using the ValidateContent method. // Note: The method will throw an exception, if the package source does not validate. existingSUMDeploymentPackage.ExecuteMethod("ValidateNewPackageSource", validateNewPackageSourceParameters); // Output a success message if the new package location is valid. Console.WriteLine("The new location of the SUM deployment package validated. "); // Update the PkgSourcePath property of the existing deployment package with the new source location. existingSUMDeploymentPackage["PkgSourcePath"].StringValue = newPackageSource; // Save the package properties. existingSUMDeploymentPackage.Put(); // Output a success message that the package location was updated. Console.WriteLine("Updated the SUM deployment package with the new package location. "); } catch (SmsException ex) { Console.WriteLine("Failed to validate the new package source."); Console.WriteLine("Failed to update the SUM deployment package."); Console.WriteLine("Error: " + ex.Message); throw; } } |
The example method has the following parameters:
Parameter |
Type |
Description |
connection |
|
A valid connection to the SMS Provider. |
existingSUMPackageID |
|
The package ID for an existing software updates deployment package. |
validateNewPackageSource |
|
The validateNewPackageSource is a dictionary object containing the parameters that the ValidateNewPackageSource method requires. PackageSource |
newPackageSourceLocation |
|
The new deployment package source location. The source path must be a Universal Naming Convention (UNC) path. All of the updates available in the old package source must be available in the new package source. |
Compiling the Code
This C# example requires:
Namespaces
System
System.Collections.Generic
System.Text
Microsoft.ConfigurationManagement.ManagementProvider
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine
Assembly
adminui.wqlqueryengine
microsoft.configurationmanagement.managementprovider
Robust Programming
For more information about error handling, see About Configuration Manager Errors.
Security
For more information about securing Configuration Manager applications, see Securing Configuration Manager Applications.