Deploy Windows Live Photo Gallery & Movie Maker via SCCM

Microsoft Windows Live Photo Gallery & Movie Maker are one of the useful image & video management tools even in a professional environment. Having tried multiple ways to silently deploy this tool, I found a blog post of pcloadletter which greatly helped with the command line for the application (wlsetup-all.exe).

I had even tested the deployment script through SCCM on a test machine and it worked like a charm. Hence I thought I could share his post and the finding here.

Though the post says about Installing on Windows 8 OS, I had tested the same command line install on my Windows 7 machine. 

http://pcloadletter.co.uk/2012/08/22/deploying-windows-photo-gallery/

Also sharing here the link to TechNet forums page, in which a fellow SCCM admin had tried the command line for installing Windows Live - Photo Gallery:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/b1cb271e-fbea-461c-a1f5-e3d52e62ce1d/sccm-distribution-of-windows-live-photo-gallery

Using SCCM Queries - step by step document

Here is an Excellent Document I found on the Internet shared by questnet.edu which details on how to use the 'Queries' feature in SCCM Console.

https://www.questnet.edu.au/download/attachments/20873328/Using+MS+SCCM+Queries.pdf

Queries are run against SCCM site's database and retrieve specific data according to the criteria of the query. SMS provides many predefined queries, and if required, we can create additional queries.

Query-based collections are dynamic objects. If a resource no longer meets the collection's query, it is automatically removed from the collection. And if a resource that originally did not meet the collection's query has changed in a way that it now meets the collection's query, it is automatically added to the collection. This behavior greatly reduces and simplifies the administrative work of managing the clients.

Remove Delete Special option from SCCM console

I found this TechNet forum post interesting on which the SCCM team wants to control their engineers from using Delete Special. Though you can set Role based permission to engineers, there are cases where mistake happens by experienced engineers or when people unwittingly delete machines. 

The 'Delete Special' option comes with the SCCM product, and here is how Christjan Schumann explained in the forum post with steps to remove the option from the SCCM console. 

• Make a backup and then edit "SCCM\AdminUI\XmlStorage\ConsoleRoot\adminconsole.xml" file.
• Search for lines containing: DisplayName="DeleteSpecialAction". You will find 3 matches. 
• All of them are parameters of "ActionDescription" tag and 2 of those matches should be removed from XML (from start tag to end tag ).
• To remove "Delete Special" option from context menu of root level collections: delete lines 7787 to 7807.
• To remove "Delete Special" option from context menu of child level collections: delete lines 8529 to 8549.

The above line numbers are valid in original SP2 adminconsole.xml. They might differ if you've customized it before.

Ref. Original Post: http://social.technet.microsoft.com/Forums/systemcenter/en-US/6868c190-1aee-4690-8e23-6e019f8d7472/delete-special

http://social.technet.microsoft.com/Forums/systemcenter/en-US/4b467010-3c55-4fa3-9a61-127c9d846416/sccm-2007-delete-special?forum=configmgradminconsole

Custom SQL query to report MS-Excel and MS-Access

Here is a custom Report to list only MS-Excel (excel.exe) and MS-Access (msaccess.exe) with Office 2003, 2007 and 2010 versions. You can also use to query by editing it to fetch other components of Microsoft Office.

SELECT b.Netbios_Name0,
b.User_Name0,
CASE WHEN a.FileVersion LIKE '11.%' THEN 'Office 2003'
WHEN a.FileVersion LIKE '12.%' THEN 'Office 2007'
WHEN a.FileVersion LIKE '14.%' THEN 'Office 2010'
ELSE 'NULL'
END AS 'Office Version',
a.FileName,
a.FileVersion
FROM v_GS_SoftwareFile a
JOIN v_R_System b ON a.ResourceID = b.ResourceID
WHERE (a.FileName = 'excel.exe' or a.FileName = 'msaccess.exe')
GROUP BY b.Netbios_Name0, b.User_Name0, a.FileName, a.FileVersion
ORDER BY b.Netbios_Name0

Note that you may get repeated machine names if the machine has got multiple updates installed for the MS office versions. 

Ref.: How to bifurcate clients having MS Office 2010/2007/2003 and to put further bifurcate on Office products

WQL Query to add bulk computers to SCCM collection

We use WQL queries to create dynamic SCCM Collections to list machines with a particular software, hardware, etc. But when it comes to adding a random machines from a given list and when we don’t use the SCCM Right-click tools, mostly we go the conventional manual method. Once during a conversation with a Microsoft tech, he helped me with this simple query which made most of my deployments easier. I can say this is faster and lighter than using Right-click tools. Sharing this query here.

We can add any number of Computer list to a Collection, but max 1500 hostnames per query. We can also remove any single machine from this customized collection.  

Select SMS_R_System.ResourceID,SMS_R_System.ResourceType,

SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,

SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client 

from SMS_R_System where SMS_R_System.name in
('Machine1','Machine2','Machine3')

Easy Steps to consolidate the computer list into the query with comma: 
* Add the machines to MS Excel by listing each machine on each row.
* Include a column (A) before machines list with the single code symbol  (').
* On the Columns C and D enter the comma symbol (,) and single code ('). 
* Drag the single code and comma symbols till the last before row of the machine list.
* Add a formula to Column E [=A:A&B:B&C:C&D:D].
* On Column E, Copy - Paste Special with Values.
* Copy the entire column E and paste in the query between brackets ( ). 
* It should look like  ('Machine1',
                               'Machine2',
                               'Machine3',
                               'Machine4')
* Click Ok and close the New collection window and we are done.

SQL Report for TPM (Trusted Platform Module)

A TPM is a microchip designed to provide basic security-related functions, primarily involving encryption keys. The TPM is usually installed on the motherboard of a computer or laptop.

To get an SCCM report on TPM status, we need to extend the hardware inventory to get the TPM chip information included in the inventory. Check this myitforum post for information on extending the inventory.
http://www.myitforum.com/forums/Creating-a-Query-to-determine-TPM-Chip-status-on-Laptops-m209158.aspx

If the above steps are made, then the below given query can be used to get a SQL Report for listing the Laptop names on which on TPM is enabled and/or activated.

Select sys.Name0 as "Machine Name",

sys.AD_Site_Name0 as "Site Name",

TPM.timestamp,

v_GS_COMPUTER_SYSTEM.Manufacturer0 AS Manufacturer,

v_GS_COMPUTER_SYSTEM.Model0 AS Model,

TPM.ManufacturerVersion0 as 'Manufacturer Version',

"TPM_VERSION" = CASE

When TPM.SpecVersion0 in ('1.2, 2, 0', '1.2, 2, 1', '1.2, 2, 2', '1.2, 2, 3')

THEN '1.2'  ELSE 'Null'

END,

"TPM_Activated" = CASE

When TPM.IsActivated_InitialValue0 = 1 THEN 'Yes'

ELSE 'No'

END,

"TPM_Enabled" = CASE

When TPM.IsEnabled_InitialValue0 = 1 THEN 'Yes'

ELSE 'No'

END

from v_GS_TRUSTED_PLATFORM_MODULE TPM

Join v_r_system sys on sys.ResourceID = TPM.ResourceID

inner join v_GS_COMPUTER_SYSTEM on (v_GS_COMPUTER_SYSTEM.ResourceID = tpm.ResourceID)

--where sys.AD_Site_Name0 = @ADSitename

order by "TPM_Activated" asc, "TPM_VERSION" desc, TPM.timestamp 

Ref.:http://social.technet.microsoft.com/Forums/systemcenter/en-US/760c10c5-324a-4e3f-a5e5-5ebdc5b37d3a/create-sccm-report-to-show-tpm-status

SQL Query for MS Office with Hostname details

SCCM Report for all versions of MS Office with Service pack and Hostname details

SELECT  dbo.v_R_System.Name0,

dbo.v_R_System.user_name0,

dbo.v_GS_OPERATING_SYSTEM.Caption0 AS [Operating System],

arp.DisplayName0,

CASE WHEN arp.version0 LIKE '11.0.6361.0' THEN 'SP1'

     WHEN arp.version0 LIKE '11.0.7969.0' THEN 'SP2'

     WHEN arp.version0 LIKE '11.0.8173.0' THEN 'SP3'

     WHEN arp.version0 LIKE '12.0.6215.1000' THEN 'SP1'

     WHEN arp.version0 LIKE '12.0.6425.1000' THEN 'SP2'

     WHEN arp.version0 LIKE '14.0.6029.1000' THEN 'SP1'

ELSE 'NULL' END as 'Service Pack', arp.Version0

FROM dbo.v_Add_Remove_Programs AS arp

INNER JOIN dbo.v_R_System ON arp.ResourceID = dbo.v_R_System.ResourceID

INNER JOIN dbo.v_RA_System_SMSInstalledSites AS ASSG ON dbo.v_R_System.ResourceID = ASSG.ResourceID

INNER JOIN dbo.v_GS_OPERATING_SYSTEM ON dbo.v_R_System.ResourceID = dbo.v_GS_OPERATING_SYSTEM.ResourceID

  --JOIN v_FullCollectionMembership on v_R_System.ResourceID = v_FullCollectionMembership.ResourceID

WHERE 
--v_FullCollectionMembership.CollectionID = ‘@CollectionID’ AND

(arp.DisplayName0 LIKE '%Microsoft Office%edition%' OR

 arp.DisplayName0 LIKE '%Microsoft Office Standard 2007%' OR

 arp.DisplayName0 LIKE '%Microsoft Office Enterprise 2007%' OR

 arp.DisplayName0 LIKE '%Microsoft Office Professional%2007%' OR

 arp.DisplayName0 LIKE '%Microsoft Office Standard 2010%' OR

 arp.DisplayName0 LIKE '%Microsoft Office Enterprise 2010%' OR

 arp.DisplayName0 LIKE '%Microsoft Office Professional%2010%' OR

 arp.DisplayName0 LIKE 'Microsoft Office 2000%' OR

 arp.DisplayName0 LIKE 'Microsoft Office XP%') AND

(arp.DisplayName0 NOT LIKE '%update%') AND

(arp.DisplayName0 NOT LIKE '%Microsoft Office XP Web Components') AND

(dbo.v_R_System.Operating_System_Name_and0 NOT LIKE '%server%') AND

  (arp.InstallDate0 NOT LIKE 'NULL')

ORDER BY arp.Version0, dbo.v_R_System.Name0 

Please note that the above query excludes Windows Server operating system records. You may comment Line-30 to include server OS records on the report.

If you wish to run the query to prompt for a collection, you can remove the comment on Line-16 and Line-18 to achieve it.

SCCM Reporting - HTTP 500 Internal Server Error

On one of our SCCM Primary server, we were unable to run large reports (neither from the SCCM console nor using from web-reports). After much analysis found that the issue was with the 'AspBufferingLimit' value on the Metabase.xml file which is located at “C:\Windows\system32\inetsrv”.

Steps to increase the AspBufferingLimit value in Metabase.xml file as follows:

SCCM Web-Report   -  HTTP 500 Internal Server Error

Open IIS - Right click on Computer Properties - Check the "Enable Direct Metabase Edit" box. This will allow you to edit the Metabase

IIS - Enable Direct Metabase Edit

Open "C:\Windows\system32\inetsrv" - select Metabase.xml - Rightclick and select Edit

Metabase.xml AspBufferingLimit

Update the 'AspBufferingLimit' entry value on Metabase.xml from 4194304 to 8000000 (or as per requirement) - Save and close the file

Updated AspBufferingLimit on Metabase.xml

UnCheck the "Enable Direct Metabase Edit" on IIS after saving Metabase.xml

Uncheck Direct Metabase Edit

 

Start - Run - Services.msc - Choose "IIS Admin Service" - Restart the service

Restart IIS Admin Service

Check running the SCCM console/web report and it should work fine. 

SCCM Report works fine now

Hope this helps.. Thanks!

SCCM Client uninstallation - Manual method

It may occasionally be necessary to remove the System Center Configuration Manager client. We can uninstall an SCCM client on machine by running "ccmsetup.exe /uninstall". 

Some unusual times when the command line doesn’t work, here is a list of things to check and remove to manually clean-up all the traces of the client so as to try a fresh install. 

1. SMS Agent Host Service - (services.msc)
2. CCMSetup service - (services.msc)
3. \windows\ccm directory - (folder path)
4. \windows\ccmsetup directory - (folder path)
5. \windows\ccmcache directory - (folder path)
6. \windows\smscfg.ini - (file path)
7. \windows\sms*.mif - (file path..if present)
8. HKLM\software\Microsoft\ccm - (registry key)
9. HKLM\software\Microsoft\CCMSETUP - (registry key)
10. HKLM\software\Microsoft\SMS - (registry key)

Ref: http://blogs.technet.com/b/michaelgriswold/archive/2013/01/02/manual-removal-of-the-sccm-client.aspx

Run Command to open SCCM client 'Configuration Manager Properties'

I had always checked online to find a Run command to open the 'Configuration Manager Properties' window from a SCCM client machine's Control Panel. Most of the time i had to create a shortcut of the Configuration Manager Properties window on the desktop for easy access.

Recently i found a post by Chris Nackers who has successfully achieved in getting the command line (which i hope is not available from Microsoft site itself). Thanks Chris for sharing the info.

Start - Run - “control smscfgrc”

Update to the above post:

• This command works for SCCM 2007 and SCCM 2012 clients. I haven't checked on SMS2003. 
• And it works pretty fine on Windows 7/8/2003/2008/2012 as well as Server Core operating systems.

Ref.: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/7b8b8e2a-0756-4be5-add0-a0a3f0808c7a/

Modifying CM 2007 service window cause unexpected delay in Updates deployment

A new Knowledge Base article (KB2850370) recently published for ConfigMgr 2007 talks about a rare issue that we may run into if we modify the properties of a maintenance window right after creating a new software update deployment.

Article Title: Modifying a Configuration Manager 2007 service window may cause an unexpected delay in a software update deployment
Article Link: http://support.microsoft.com/kb/2850370  
Article ID: 2850370

The article says that the software update will still get deployed on the clients but may happen a little later than we might expect. This is by design in System Center Configuration Manager 2007.

All about Branch Distribution Points on SCCM 2007

Recently I came across many issues related to "Branch Distribution Points" on SCCM 2007 and was on a search for more documentation on BDP. I hereby sharing my search results which might be beneficial for my future search as well for others.

• Carol Bailey on TechNet blog has documented some most valuable information about BDP: 

FAQs for Branch Distribution Points: 
http://blogs.technet.com/b/wemd_ua_-_sms_writing_team/archive/2008/07/27/faqs-for-branch-distribution-points.aspx

• TechNet Article by PaddyMaddy

DP VS Secondary Site VS BDP - In SCCM 2007 vs SCCM 2012
http://social.technet.microsoft.com/wiki/contents/articles/5292.dp-vs-secondary-site-vs-bdp-in-sccm-2007-vs-sccm-2012.aspx

• Carlos Santiago on TechNet blog has given additional information on Refreshing vs Updating a package on BDP: 

How do we refresh a package located on a Branch Distribution Point?

http://blogs.technet.com/b/carlossantiago/archive/2008/05/16/how-do-we-refresh-a-package-located-on-a-branch-distribution-point.aspx 

Other Useful TechNet articles about BDP:

Choose Between a Standard and Branch Distribution Point
http://technet.microsoft.com/en-us/library/bb932184.aspx 

About On-Demand Package Distribution
http://technet.microsoft.com/en-us/library/bb632582.aspx 

How to Prestage Packages on a Branch Distribution Point
http://technet.microsoft.com/en-us/library/bb681046.aspx 

SCCM Reporting - "SELECT permission was denied on the object"

Sharing you my experience on resolving the SELECT permission error while running a SCCM Web Report. 

Sometimes SCCM may throw an error while running a new report on Web Browser. The same report may work just fine on the SQL server reporting console, but not on web browser.

Detailed error on "Select permission" that appears on the Web browser:
The SELECT permission was denied on the object 'xxxxxxxxx', database 'SMS_ABC', schema 'dbo'.
Error Number: -2147217911
Source: Microsoft OLE DB Provider for SQL Server
Native Error: 229  

I then referred to some online articles for troubleshooting and solved the issue by adding the SELECT permissions for the SQL View on SQL server.

Added below the resolution snapshots for your reference:

Step 1 - SELECT permission error on SCCM Report

Step 2 - View properties - adding permission

Step 3 - Browse and add Database role "smsschm_user"

Step 4 - Choose Select permission for smsschm_user

Step 5 - Add "webreport_approle" and choose Select permission

Step 6 - SCCM Web Report works fine

Package/Task Sequence - Created, Modified or Deleted

Last week I had created 3 Task Sequences on our SCCM 2007 Primary server and had also taken snapshots of them for documentation. Today when i logged in the SCCM server, the Task Sequences were found missing. Guess me or someone has mistakenly deleted it.

Question:
How to find details about a created, modified or deleted Packages or Task Sequences.??

Answer:

In the SCCM'07 Primary Server, under System Status, choose the built-in "Status Message Queries" option.

On the right-side pane click choose and run the "Packages Created, Modified, or Deleted" query.

This report will be useful to monitor Changes to Task Sequences or Packages.

"Status Message Queries" is a good feature that i rarely used. No doubt I'll make use of this good option here-after..
 

Reference link to all find list of all default ConfigMgr 2007 Status Message Queries:

http://myitforum.com/cs2/blogs/dhite/archive/2008/05/18/default-configmgr-2007-status-message-queries.aspx

Skpswi.dat - Exclude Folders From SCCM Software Inventory

You can create a hidden file named Skpswi.dat and place it in the root of a client hard drive to exclude the drive from Software Inventory. You can also place this file in the root of any folder structure you want to exclude the folder from software inventory. This procedure can be used to disable software inventory on a single workstation or server client, such as a large file server.

The Skpswi.dat file only prevents software inventory for computer clients and does not affect mobile device client inventory.

To exclude folders from Software Inventory:

• Using Notepad.exe, create an empty file named SkpSwi.dat. (Run –> notepad –> Save as “SkpSwi.dat”)
• Right click the SkpSwi.dat file and click properties. In the file properties for the SkpSwi.dat file, select the Hidden attribute.
• Place the SkpSwi.dat file at the root of each client hard drive or folder structure that you wish to exclude from software inventory.

To Note: 

• Software inventory will not inventory the client drive again unless this file is deleted from the drive on the client computer. 
• Software inventory will only exclude the directory if Skpswi.dat is hidden.

Ref.: http://technet.microsoft.com/en-us/library/bb632671.aspx

http://eskonr.com/tag/skpswi-dat/

Task Sequence reports exit error code 183

Every (mostly even) task sequence reports exit error code 183 if you advertise several task sequences to a SMS/SCCM client machine in Configuration Manager 2007.

The error normally appears in SCCM when you perform the below tasks:

1. You create several task sequences in SCCM 2007.
2. You advertise these task sequences to a SMS/SCCM clients. All advertisements are mandatory.
3. All advertisements are scheduled to run at the same time.
4. User notification is disabled in the properties of the advertised programs client agent.

Note that this problem does not occur when user notification is enabled.

When this problem occurs, information that resembles the following is logged in the execmgr.log file as:
1600 (0x0640) 19.12.2007 13:31:34 Program exit code 183
1600 (0x0640) 19.12.2007 13:31:34 Script for Package:J1000014, Program: * failed with exit code 183
1600 (0x0640) 19.12.2007 13:31:34 Execution is complete for program *. The exit code is 183, the execution status is FailureNonRetry 

Microsoft has confirmed that this is a problem in SCCM 2007, and the Article ID 946519 explains the scenario with a Hotfix and Workaround steps.

Hotfix:

You can download the hotfix @ http://support.microsoft.com/kb/946519

Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described above. Apply this hotfix only to systems that are experiencing this specific problem.

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart the computer after you apply this hotfix.

WORKAROUND-1

Enable user notification in the properties of the advertised programs client agent. To do this, follow these steps:

1. Open the Configuration Manager console.
2. In the console tree, expand Site Management, expand the node that corresponds to the current site, expand Site Settings, and then click Client Agents.
3. In the details pane, right-click Advertised Programs Client Agent, and then click Properties.
4. On the Notification tab, click to select Provide a countdown, and then click OK.

 

WORKAROUND-2

Use only one task sequence at a time :)

Ref.: http://support.microsoft.com/kb/946519

Software Distribution is currently paused on this computer

   Today I came across a new issue while working on SCCM Task Sequence. The deployed softwares are not being received by the SCCM Client machine. My analysis on the issue and the solution with ref. links are given below for your reference.

The ConfigMgr Status Message Viewer showed the error stated below:

Message ID : 10038
System      : "MachineName"
Source       : SMS Client
Component : Software Distribution  Description: "The program for advertisement "ABCxxxxx" has not been run yet ("ABCyyyyy" - "App - Install"). Software Distribution is currently paused on this computer, and it has to be resumed before this program can begin."

Execmgr.log says "This program cannot run because a reboot is in progress or software distribution is paused."

RESOLUTION 1:
If Task Manager does not un-pause (resume) Software Distribution, then it will eventually get itself out of the paused state after 24 hours (probably it should).

RESOLUTION 2: 
Check the below snapshot and the registry keys:

For X86 machines: 

• HKEY_Local_Machine\Software\Microsoft\SMS\Mobile Client\Software Distribution\State\Pause

For X64 Machines:

• HKEY_Local_Machine\Software\Wow6432Node\Microsoft\SMS\Mobile Client\Software Distribution\State\Pause 

• HKLM\SOFTWARE\Microsoft\SMS\Task Sequence

On the right pane of the registry path, there might be some values that were not set to 0 again. Change the DWORD values for "Paused" and "Paused Cookie" from '1' to '0' and if possible restart the client.

You can try to stop/start the SMS Task Sequence Agent and then restart the SMS Agent Host, wait a couple of minutes and the Software Distribution will resume its process.

Please note that the task sequence resumed on the second snapshot but the detail states that it is failed which is due to a different error '183'. The discussion about the exit error code 183 is detailed here in my next post --> http://scorpits.blogspot.in/2013/01/task-sequence-reports-exit-error-code.html.

Ref.: http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/42114c0f-9de8-4a2c-9dac-1bac842b1d8a/

SCCM Client installation Troubleshooting steps Check list

We can find most of the SCCM value information on Eswar Koneti's blog.

A link to one such valuable post that helped me in maintaining a checklist for SCCM Client troubleshooting is given below. Please click the link to view the post.

SCCM Client installation Troubleshooting steps Check list
http://eskonr.com/2010/11/sccm-client-installation-troubleshooting-steps-check-list/

System Center Configuration Manager 2007 Toolkit V2

The Configuration Manager 2007 Toolkit V2 contains 11 downloadable tools to help you manage and troubleshoot Configuration Manager 2007. Click the below link to download the Toolkit.

ConfigMgrTool.msi - http://download.microsoft.com/download/5/5/0/55078AC4-3D15-407B-948E-CEB72A0A5A50/ConfigMgrTools.msi

1. Trace32 - A log viewer that provides a way to easily view and monitor log files created and updated by Configuration Manager 2007 clients and servers.
2. Client Spy -A tool that helps you troubleshoot issues related to software distribution, inventory, and software metering on Configuration Manager 2007 clients.
3. Delete Group Class Tool - A tool used to remove inventory group definitions along with history data, tables, views and stored procedures for the group.
4. Desired Configuration Management Migration Tool - A tool used to migrate from the DCM Solution for SMS 2003 to DCM in ConfigMgr 2007.
5. Desired Configuration Management Model Verification Tool - A tool used by desired configuration management content administrators for the validation and testing of configuration items and baselines authored externally from the Configuration Manager console.
6. Desired Configuration Management Substitution Variable Tool - A tool used by desired configuration management content administrators for authoring desired configuration management configuration items that use chained setting and object discovery.
7. Management Point Troubleshooter Tool - A tool that checks a computer system before and after a management point installation to ensure that the installation meets the requirements for management points.
8. Policy Spy - A policy viewer that helps you review and troubleshoot the policy system on Configuration Manager 2007 clients.
9. Preload Package Tool - A tool used to manually install compressed copies of package source files on Configuration Manager 2007 sites.
10. Security Configuration Wizard Template for Configuration Manager 2007 - The Security Configuration Wizard (SCW) is an attack-surface reduction tool for the Microsoft Windows Server 2008 R2 operating system. Security Configuration Wizard determines the minimum functionality required for a server's role or roles, and disables functionality that is not required. The Configuration Manager 2007 Service Pack 2 Security Configuration Wizard template supports new site system definitions and enables the required services and ports.
11. Send Schedule Tool - A tool used to trigger a schedule on a Client or trigger the evaluation of a specified DCM Baseline. You can trigger a schedule either locally or remotely.

 Ref: http://www.microsoft.com/en-us/download/details.aspx?id=9257