Add Imported Computer to user defined Collection

1 Why and how it works

This can be helpful if your OSD collection has a limiting collection other than the All Systems collection. The computer is added to the collection chosen on the Import Computer form, immediately after the import.

1. Create a Drop-down machine variable, for example Category, with one item for each collection.
2. Move the variable to the top of the Import Computer form.
3. Write a PowerShell script that reads the variable and calls SoftwareCentral to add the computer to the collection.
4. Enable the Import Computer custom action and point it at the script.
5. Import a computer and choose a collection in the variable.

2 Create the Category variable

Create the variable in the Machine Variables interface (see Machine Variables). Click Add new variable, then fill in the window.

Add one item for each collection with Add, and save the variable with Save. Cancel closes the window without a change.

3 Show the variable on the form

Drag the Category row to the top of the Machine Variables list. Each row has a grip at its right end; the tooltip reads Drag to change the order of the variables.

Open the Import Computer form. The variable appears under Optional computer settings. If a computer template makes the variable mandatory, the heading changes to Computer settings.

You can add the new Machine Variable to Computer Templates and make it mandatory. This example does not cover that.

4 The script

Create a new PowerShell script and copy the code below into it. Change the address of the web service to your own SoftwareCentral address.

# Import Computer - Add to Collection after import
#
# This script adds a newly imported computer to a collection, defined by a Machine Variable.
# See how to configure this script in the manual.
#
# Load parameters:
Param
(
[int]$ResourceID,
[string]$Hostname,
[string]$MacAddress,
[string]$SMBIOSGUID,
[string]$SiteCode
)
# Write to the SoftwareCentral log, that the script has started:
Write-Host "Launching PowerShell Script after Computer Import for computer: '" $Hostname "'."
# Define the MachineVariable Name we want the Value from:
[String]$strVariableName = "Category"
# The object that will make the call to the Web Service
# Change the address to your own SoftwareCentral site address
$proxy = New-WebServiceProxy -Uri "http://softwarecentral/Api/WS_Devices.asmx" -Class "Proxy" -UseDefaultCredential
# Call the Web Service and get the Machine Variable Value
$strVariableValue = $proxy.GetMachineVariable($Hostname,$SiteCode,$strVariableName)
if (![string]::IsNullOrEmpty($strVariableValue))
{
    # If the Machine Variable Value is not null or empty, add the computer to the collection
    Write-Host $proxy.AddToCollection($Hostname,$strVariableValue,$SiteCode)
}

Save your PowerShell script on the server where SoftwareCentral is installed or on a share that SoftwareCentral can read from. Note that you should not add this script to the folder where SoftwareCentral is installed.

The script receives these values from the custom action. The names are the same as in the Variables list of the custom action.

Note that this script uses the SoftwareCentral API methods "Devices - Get Machine Variable" and "Devices - Add to collection".

To simplify the setup, you should add the SoftwareCentral application pool user to the SoftwareCentral Administrators Group. If you do not do this, you must grant access to each web service for the application pool user.

See Web Service Security for more information on how to allow access for users who are not members of the SoftwareCentral Administrators Group.

5 Enable the custom action

Go to Settings in SoftwareCentral, open the SoftwareCentral group on the left and select Custom Actions.

Click Save Settings to save the tab.

6 Test the setup

Go to Import Computer, choose a collection in Category, and import a computer.

After the computer is imported, the SoftwareCentral log shows that the script ran and that the computer was added to the collection:

The lines to look for are:

7 Best practice

• Use collection IDs in Item value, not collection names. SoftwareCentral checks the ID with the ConfigMgr site; a wrong ID stops the add with the message Collection does not exist.
• Give the importing roles access to the collections they can choose. A role that is not an administrator can only add computers to collections assigned to it. Other collections fail with This role is not allowed to operate on this collection.
• Use the application pool user for Run as when you can. It needs no password. Another user works only while the password stored in the Password Manager is correct.
• Keep the script where only administrators can change it. The script runs on the server with the rights of the account set in Run as.
• Test with one computer first. Check the log after the import before you use the setup for everyone.

8 Troubleshooting