In this post we’ll look at Advertisements in SCCM 2007. First we’ll retrieve an existing advertisement using PowerShell.

PS > $pkgAdobe = Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Package WHERE Name = 'Adobe Reader'"

In the example above we use the SMS_Package Class to retrieve a specific Package, next we use the SPS_Advertisement and retrieve an Advertisement where the PackageID equals the one stored in $pkgAdobe.

PS > $advAdobe = Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Advertisement WHERE PackageID = '$($pkgAdobe.PackageID)'"

Let’s check out some of the Advertisements Properties.

PS > $advAdobe | Select-Object AdvertFlags, DeviceFlags, RemoteClientFlags, SourceSite, TimeFlags

AdvertFlags       : 34603040
DeviceFlags       : 0
RemoteClientFlags : 8240
SourceSite        : LAB
TimeFlags         : 8193

In the example above we display the AdverFlags which indicates how the advertisement should be announced to the user, the DeviceFlags that describes the device (default value is 0), the RemoteClientFlags that specify how the program should run, the SourceSite and the TimeFlags which are reserved for internal use.

Now let’s see how we can create a new Advertisement. First we need to gather some information such as CollectionID, PackageID and ProgramName.

PS > $collectionID = (Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Collection WHERE Name = 'All Windows XP Systems'").CollectionID
PS > $packageID = (Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select PackageID from SMS_Package WHERE Name = 'Windows PowerShell'").PackageID
PS > $prg = Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Program WHERE PackageID = '$packageID'"

Next we store the arguments in a HashTable. Since many of the values (AdvertFlags, DeviceFlags, RemoteClientFlags and TimeFlags) can be a little hard to figure out we’ll use the “Adobe Reader” Advertisement as reference. (for more information on possible values check out this link).

PS > $arguments =
>> @{AdvertFlags = $advAdobe.AdvertFlags;
>> AdvertisementName = "PowerShell";
>> CollectionID = $collectionID;
>> PackageID = $packageID;
>> DeviceFlags = $advAdobe.DeviceFlags;
>> ProgramName = $prg.ProgramName;
>> RemoteClientFlags = $advAdobe.RemoteClientFlags;
>> SourceSite = $advAdobe.SourceSite;
>> TimeFlags = $advAdobe.TimeFlags
>> }

With the arguments prepared and ready we can go ahead and create a new Advertisement using the Set-WmiInstance Cmdlet and the SMS_Advertisement class.

PS > Set-WmiInstance -class SMS_Advertisement -arguments $arguments -namespace "root\SMS\Site_LAB"


__GENUS                 : 2
__CLASS                 : SMS_Advertisement
__SUPERCLASS            : SMS_BaseClass
__DYNASTY               : SMS_BaseClass
__RELPATH               : SMS_Advertisement.AdvertisementID="LAB20002"
__PROPERTY_COUNT        : 28
__DERIVATION            : {SMS_BaseClass}
__SERVER                : SCCM
__NAMESPACE             : root\SMS\Site_LAB
__PATH                  : \\SCCM\root\SMS\Site_LAB:SMS_Advertisement.AdvertisementID="LAB20002"
ActionInProgress        : 1
AdvertFlags             : 34603040
AdvertisementID         : LAB20002
AdvertisementName       : PowerShell
AssignedSchedule        : {}
AssignedScheduleEnabled : False
AssignedScheduleIsGMT   : False
AssignmentID            : 0
CollectionID            : SMS000ES
Comment                 :
DeviceFlags             : 0
ExpirationTime          : 19900101000000.000000+***
ExpirationTimeEnabled   : False
ExpirationTimeIsGMT     : False
HierarchyPath           :
IncludeSubCollection    : True
ISVData                 :
ISVDataSize             : 0
MandatoryCountdown      : 0
PackageID               : LAB00024
PresentTime             : 19900101000000.000000+***
PresentTimeEnabled      : True
PresentTimeIsGMT        : False
Priority                : 2
ProgramName             : PowerShell - Install
RemoteClientFlags       : 8240
SourceSite              : LAB
TimeFlags               : 24577

When we create a new advertisment using Windows PowerShell it’s placed in the default container. We can move the advertisement to a specific folder using the SMS_ObjectContainerItem class.

First we retrieve the Container Node using the SMS_ObjectContainerNode. Notice how we point out the Name and ObjectType in the WQL statement. ObjectType 3 equals SMS_Advertisement.

PS > $containerNode = Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_ObjectContainerNode WHERE Name = 'Applications' AND ObjectType = '3'"

We also need the Advertisements ID so we’ll go ahead and store it in a variable.

$advID = (Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select AdvertisementID from SMS_Advertisement WHERE AdvertisementName = 'PowerShell'").AdvertisementID

Next we store the arguments in a HashTable as shown below.

PS > $arguments = @{
InstanceKey = $advID;
ObjectType = 2;
ContainerNodeID = $containerNode.ContainerNodeID
}

Finally we use the SMS_ObjectContainerItem Class to move the Advertisement to a folder.

PS > Set-WmiInstance -Class SMS_ObjectContainerItem -arguments $arguments -namespace "root\SMS\Site_LAB"

__GENUS          : 2
__CLASS          : SMS_ObjectContainerItem
__SUPERCLASS     : SMS_BaseClass
__DYNASTY        : SMS_BaseClass
__RELPATH        : SMS_ObjectContainerItem.MemberID=138
__PROPERTY_COUNT : 6
__DERIVATION     : {SMS_BaseClass}
__SERVER         : SCCM
__NAMESPACE      : root\SMS\Site_LAB
__PATH           : \\SCCM\root\SMS\Site_LAB:SMS_ObjectContainerItem.MemberID=138
ContainerNodeID  : 12
InstanceKey      : LAB20002
MemberGuid       : 53D8BAD4-09D9-4304-9C24-65723453F6CD
MemberID         : 138
ObjectType       : 3
SourceSite       : LAB

If we take a look in the Configuration Manager Console now we’ll see that our Advertisement is created and in the correct folder

In the Next post we’ll take a look at how we can manage the SMS Client.

We can use the SPS_DistributionPoint class to retrieve information about all or a specific distribution point in SCCM 2007 using Windows PowerShell. In the example below we first retrieve a Package and then use the PackageID to retrieve the Distribution Point associated with the Package.

PS > $pkgAdobe = Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Package WHERE Name = 'Adobe Reader'"
PS > $distAdobe = Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_DistributionPoint WHERE PackageID = '$($pkgAdobe.PackageID)'"

Now we can use the variable to Display all or specific properties. In the example below we use the Select-Object cmdlet to display the ServerNALPath, SiteCode, SiteName and ResourceType. Each role (DP, PXE, SUP, MP etc) has a NAL Path. The NAL Path contains a netbiosName, SiteCode and a Path if its a Distribution Point. The ResourceType property displays the resource type of the distribution point.

PS > $distAdobe | Select ServerNALPath, SiteCode, SourceSite, SiteName, ResourceType

ServerNALPath : ["Display=\\SCCM\"]MSWNET:["SMS_SITE=LAB"]\\SCCM\
SiteCode      : LAB
SourceSite    : LAB
SiteName      : Lab Site
ResourceType  : Windows NT Server

Now let’s see how we can create a new Distribution Point. First we retrieve a specific PackageID which we will use when creating a new Distribution Point.

PS > $packageID = (Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select PackageID from SMS_Package WHERE Name = 'Windows PowerShell'").PackageID

PS > $arguments = @{
>> PackageID = $packageID;
>> ServerNALPath = '["Display=\\SCCM\"]MSWNET:["SMS_SITE=LAB"]\\SCCM\';
>> SiteCode = "LAB";
>> SiteName = "LAB Site";
>> SourceSite = "LAB";
>> ResourceType = "Windows NT Server"
>> }

Finally we use the Set-WmiInstance cmdlet to create a new Distribution Point as shown below.

PS > Set-WmiInstance -class SMS_DistributionPoint -arguments $arguments -namespace "root\SMS\Site_LAB"

__GENUS          : 2
__CLASS          : SMS_DistributionPoint
__SUPERCLASS     : SMS_BaseClass
__DYNASTY        : SMS_BaseClass
__RELPATH        : SMS_DistributionPoint.PackageID="LAB00024",ServerNALPath="[\"Display=\\\\SCCM\\\"]M
                   =LAB\"]\\\\SCCM\\",SiteCode="LAB"
__PROPERTY_COUNT : 15
__DERIVATION     : {SMS_BaseClass}
__SERVER         : SCCM
__NAMESPACE      : root\SMS\Site_LAB
__PATH           : \\SCCM\root\SMS\Site_LAB:SMS_DistributionPoint.PackageID="LAB00024",ServerNALPath="
                   CM\\\"]MSWNET:[\"SMS_SITE=LAB\"]\\\\SCCM\\",SiteCode="LAB"
BitsEnabled      : False
IsFileStreaming  : False
IsPeerDP         : False
IsProtected      : False
ISVData          :
ISVDataSize      : 0
LastRefreshTime  : 19900101000000.000000+***
PackageID        : LAB00024
RefreshNow       : False
ResourceType     : Windows NT Server
ServerNALPath    : ["Display=\\SCCM\"]MSWNET:["SMS_SITE=LAB"]\\SCCM\
SiteCode         : LAB
SiteName         : LAB Site
SourceSite       : LAB
Status           : 2

If we take a look in the Configuration Manager console we see that a Distribution Point is added to our Package.

In the next post we’ll take a look at advertisements.

In this post we’ll see examples on retrieving, modifying and creatint Programs in SCCM 2007. First let’s see how to retrieve a specific Program using Windows PowerShell.

PS > $pkgAdobe = Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Package WHERE Name = 'Adobe Reader'"
PS > $prgAdobe = Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Program WHERE PackageID = '$($pkgAdobe.PackageID)'"

In the example above we first use the SMS_Package class to retrieve a package where the Name is equal to “Adobe Reader”, next we use the SMS_Program class and in the WQL statement we specify that the PackageID should be equal to $pkgAdobe.PackageID.

We can use the Select-Object cmdlet to display specific properties – notice how the “Comment” property is empty in the example below.

PS > $prgAdobe | Select ProgramName, PackageID, Comment

ProgramName                 PackageID    Comment
-----------                 ---------    -------
Adobe Reader - Install      LAB00016

If we want to set the Comment we can simply type.

PS > $prgAdobe.Comment = "Adobe Reader"
PS > $prgAdobe.Put()

Path          : \\localhost\root\SMS\Site_LAB:SMS_Program.PackageID="LAB00016",ProgramName="Adobe Reader - Install"
RelativePath  : SMS_Program.PackageID="LAB00016",ProgramName="Adobe Reader - Install"
Server        : localhost
NamespacePath : root\SMS\Site_LAB
ClassName     : SMS_Program
IsClass       : False
IsInstance    : True
IsSingleton   : False

In the example above we use the Put() method to commit the changes. If we Select the Comment Property we’ll see that the Comment property contains a value.

PS > $prgAdobe | Select-Object Comment

Comment
-------
Adobe Reader

Now let’s see how to create a new Program. in a previous post we created a new Package Named “Windows PowerShell”. Let’s go ahead and add a Program to the package. First we retrieve the PackageID using the SMS_Package class.

PS > $packageID = (Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select PackageID from SMS_Package WHERE Name = 'Windows PowerShell'").PackageID

Next we build up a HashTable containing the Properties and Values that we want to use when creating our new package.

PS > $arguments = @{
>> PackageID = $packageID;
>> ProgramFlags = $prgAdobe.ProgramFlags;
>> ProgramName = "PowerShell - Install";
>> CommandLine = "Install.bat"
>> }

In the example above we set the PackageID, ProgramFlags, ProgramName and CommandLine.

The ProgramFlags identify the installation characteristics of the program. In this example we copy the characteristics from the “Adobe Reader – Install” program. You can also set up specific ProgramFlags. You can check out this link for more information on ProgramFlags.

The CommandLine shows the command that runs when the program is started. In this example we use a bat file. Here’s the code placed in the install.bat file.

If we type $arguments the Name and Values stored in the HashTable are displayed.

PS > $arguments

Name                           Value
----                           -----
PackageID                      LAB00024
CommandLine                    Install.bat
ProgramFlags                   135307264
ProgramName                    PowerShell - Install

Finally we can create a new Program using Set-WmiInstance and the SMS_Program Class as shown below.

PS > Set-WmiInstance -class SMS_Program -arguments $arguments -namespace "root\SMS\Site_LAB"

If we take a look in the Configuration Manager Console we’ll see that the Program is added to the “Windows PowerShell” package.

The image below demonstrates the Program Properties in the Configuration Manager Console.

In the next post we’ll take a look at Distribution Points.

There are a couple of WMI classes that handle Site Collections. We can display them by using the Get-WmiObject cmdlet as shown below.

PS > Get-WmiObject -Namespace "root\SMS\Site_LAB" -List | 
>> Where-Object { $_.Name -match "Collection" } | 
>> Select-Object -Property Name

Name
----
SMS_Collection
SMS_FullCollectionMembership
SMS_CollectionSettings
SMS_CollectionMember
SMS_CollectionMember_a
SMS_CollectionToPkgAdvert_a
SMS_CollectionRule
SMS_CollectionRuleDirect
SMS_CollectionRuleQuery
SMS_CollectionVariable

Let’s take a closer look at the SMS_Collection class. If we want to get a specific Collection we can use the Get-WmiObject cmdlet. In the example below we use the -Query parameter and specify WMI Query Language (WQL) statement to run.

PS > Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Collection WHERE CollectionID = 'SMS000ES'"

__GENUS                  : 2
__CLASS                  : SMS_Collection
__SUPERCLASS             : SMS_BaseClass
__DYNASTY                : SMS_BaseClass
__RELPATH                : SMS_Collection.CollectionID="SMS000ES"
__PROPERTY_COUNT         : 16
__DERIVATION             : {SMS_BaseClass}
__SERVER                 : SCCM
__NAMESPACE              : root\SMS\Site_LAB
__PATH                   : \\SCCM\root\SMS\Site_LAB:SMS_Collection.CollectionID="SMS000ES"
CollectionID             : SMS000ES
CollectionRules          :
CollectionVariablesCount : 0
Comment                  : All Windows XP Systems
CurrentStatus            : 1
LastChangeTime           : 20100924123504.383000+***
LastMemberChangeTime     : 20100926162237.750000+***
LastRefreshTime          : 20101006172345.000000+***
MemberClassName          : SMS_CM_RES_COLL_SMS000ES
Name                     : All Windows XP Systems
OwnedByThisSite          : True
PowerConfigsCount        : 0
RefreshSchedule          :
RefreshType              : 1
ReplicateToSubSites      : False
ServiceWindowsCount      : 0

The command above retrieves an instance of the SMS_Collection class. Notice how we specify the CollectionID in the WQL statement. If we don’t know the collections ID we can change the query to check for the collections name instead as demonstrated below.

PS > Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Collection WHERE Name = 'All Windows XP Systems'"

If we want to list all available collections we can change the query to “Select * from SMS_Collection” instead. Note that if you have alot of Collections in your test environment this command may use alot of memory.

PS > Get-WmiObject -Namespace "root\SMS\Site_LAB" -Query "Select * from SMS_Collection"

It’s also possible to use additional PowerShell Cmdlets with Get-WmiObject. If we only want to display the Name and CollectionID properties we can pipe the objects to the Select-Object cmdlet as shown below.

PS > Get-WmiObject -Namespace "root\SMS\Site_LAB" `
>> -Query "Select * from SMS_Collection" | 
>> Select-Object Name, CollectionID

Name                                                        CollectionID
----                                                        ------------
Root Collection                                             COLLROOT
All Systems                                                 SMS00001
All Users                                                   SMS00002
All User Groups                                             SMS00003
All Windows Workstation or Professional Systems             SMS00004
All Active Directory Security Groups                        SMS00005
All Windows Server Systems                                  SMS000DS
All Windows 2000 Professional Systems                       SMS000GS
All Windows 2000 Server Systems                             SMS000HS
All Windows XP Systems                                      SMS000ES
All Windows Server 2003 Systems                             SMS000FS
All Windows Mobile Devices                                  SMSDM001
All Desktops and Servers                                    SMSDM003
All Windows Mobile Pocket PC 2003 Devices                   SMSDM002
All Windows Mobile Pocket PC 5.0 Devices                    SMSDM005
All Windows Mobile Smartphone 2003 Devices                  SMSDM006
All Windows Mobile Smartphone 5.0 Devices                   SMSDM007
OSD                                                         LAB00012
Demo                                                        LAB00013

Finally, if we want to create a csv file based on our collections we can use the Export-Csv cmdlet.

PS > Get-WmiObject -Namespace "root\SMS\Site_LAB" -Query "Select * from SMS_Collection" | 
>> Select-Object -Property Name, CollectionID | 
>> Export-Csv C:\Temp\Collections.csv -NoTypeInformation

In the example above we use Get-WmiObject to retrieve all Collections and pipe the objects to the Select-Object where we select the Name and CollectionID properties. Finally we send the objects down the pipe and use the Export-Csv cmdlet to create a csv file.

In the next post we’ll see examples on how to Display, Update and Create Packages in SCCM using Windows PowerShell.