Monthly Archives: June 2013

You are browsing the site archives by month.

Show all Relevant Collection Memberships (SQL)

Purpose: Query all the relevant Collection Memberships, defined by you.

After a while, your workstations might be members of many different Device Collections. If you need to point out which collections are actually relevant in some scenarios, you need to use prefixes in your Collection Names. With these prefixes, you can filter out unrelevant collections and create a report, which only shows the relevant Device Collections.

Continue Reading

Extend SCCM client Hardware Inventory with a Custom Attribute value

Purpose: Gather a new registry value that is not included in the built-in values.

SCCM has a long list of Hardware Inventory objects that you can set the system to gather for you from each workstation. As you continue to use SCCM more intensively, you will notice that the built-in list is not comprehensive for all your great ideas. Thats when you need to extend the SCCM 2012 Hardware Inventory and gather the registry values that you have noticed to be important for you. This will take a moment, so dont rush it.

Continue Reading

Remove a known file from Current User desktop (VBS)

Purpose: Remove a predefined file from every actual user profile folder in a workstation.

In a scenario where you have delivered files to every or some user profiles of a workstation, you need to iterate through the C:\Users\Public\ -subfolders to reach your files. Of course this can be used as well against something that you have not delivered at all. These scenarios can be faulty application shortcuts directly in user desktop, user based configuration files in AppData -folders or similar.

Usage: cscript.exe IT_OSD_VBS_RemoveAFileFromEveryUserProfile.vbs (no parameters exist)
Configuration: You need to insert the file that you want to remove to strFolderPathLocal

Continue Reading

Replace a Setting in a text file (VBS)

Purpose: Replace a setting in a text file without sending the whole file (for example: INI-file).

You might have an application that includes a configuration file. This configuration file is deployed along with the application. As time passes, your users will have made their own changes through the application to this configuration file. When you need to update all of the configuration files yourself, you simply cannot replace the file. This would remove all the changes that your users have done. You will need to replace the single line in the file and leave everything else as it was.

Usage: cscript.exe IT_APP_VBS_ReplaceLineInATextFile.vbs (no parameters exist)
Configuration: You need to insert your own customization line.

Continue Reading

Compare Registry Values (VBS)

Purpose: You have two registry values, which you need to compare

This solution is not compatible as a SCCM application custom script detection method. It is meant to generally demonstrate how to compare registry values with VBS.

Usage: cscript.exe IT_OSD_VBS_CompareTwoRegistryValues.vbs (no parameters exist)
Configuration: You need to insert your own registry paths.

Continue Reading

Show an application in the Programs list of Windows 7

Purpose: List your custom application or configuration in Windows 7 (x64) Programs list

If you need to list your custom application or a setting in the Windows 7 operating system Programs list (Control Panel -> Programs), you need to add a registry key to the local machine registry. However, there is a catch. You need to add two registry values inside the key for it to appear in the Programs list. There are many more available for additional information, but two is required. This could be used if you are gathering the Programs list for a SCCM report and want that something you are deploying will be shown in this report as well.

Continue Reading

Use a Custom Script to detect the presence of an Application Deployment Type in SCCM 2012

Purpose: a fundamental thing to know when creating a Custom Detection script in SCCM 2012

Creating a custom application detection script will require one thing to be understood before you begin scripting: How the SCCM understands that the application is installed or is not installed. You might think that if your script is returning true or false, or if it is returning zero or one – you would have found the syntax, but you are wrong.

Continue Reading

Report with a Selectable Collection Parameter (SQL)

Purpose: Create a Report that allows a user to select the limiting Collection from a drop down list

When you are creating more complex reports with the Report Builder, you will begin to use different kind of parameters with queried values. One of the most common SCCM parameter is the Collection parameter. This guide is valid when you need create your report and let a user to limit it to a single collection.

Continue Reading