Author Archives: Jyri Lehtonen

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

Using the SQL Server Report Builder on an External Workstation (Export/Import Certificate)

Purpose: Requirements to correctly use SQL Server Report Builder on an external workstation

Should you need to use the SQL Server Report Builder from an external workstation (not directly from the SQL Server where the Report Service Point is installed), you will need to add the SQL server certificate to the external workstation. This will allow the external workstation to function properly with all of the Report Builder actions.

Continue Reading

Create a new Data Source in SQL Reporting Services

Purpose: Create a Central SQL Report Data Source (else you need one in every custom report)

Once you take upon the quest of creating reports using SQL Reporting Services, you will soon notice that you are doing the same task in every report that you create. Therefore you should create a centralized data source that your reports will be using. This will save you time and nerves (so you can create even more reports, yey!)

Continue Reading

Allow limited users to install fonts in Windows 7 with UAC turned on (BAT)

Purpose: Allow non-administrator / limited user to install fonts in W7 with UAC turned on

Since the Windows 7 operating system has been published, the Web has been full of questions about how to allow limited users to install fonts in a corporate environment. There are not many ways available, unless you really want to lower the security of your OS and change the way the OS is supposed to work. However there is at least one way to allow this: first you need to change the way you have tried to approach this problem. You can install the fonts to a user session instead of the local machine. You will need to create a system that will make sure that the fonts are kept in the user session even after a system reboot or for another user.

Usage: IT_APP_BAT_UserBasedFontInstallation.bat
Configuration: You can change the location of the Public Fonts -directory, if it pleases you.

Continue Reading

Show all Application Packages Sorted by Date (SQL)

Purpose: Query SCCM 2012 database for all created Applications and sort them by Date

If you need to query details about Applications in SCCM 2012, you cannot do that in WQL. The Admin Console currently supports only to query the old Package-format applications. Should you require information about the new Applications that were introduced in SCCM 2012, you need to use SQL and play with the SQL Server Report Builder to get the report into SCCM.

Continue Reading

Show All Categories and Post Topics only (PHP)

Purpose: Show All WordPress Blog Categories and the Post topic names only

A WordPress PHP script. An example of the action can be seen in the Archives page of this blog. It is a tidy view with no other fusshuss to easly navigate through the stuff written in here. More old fashioned hierarchical way.

Continue Reading

Update SCCM 2012 Admin Console to SP1 CU1

Purpose: You have installed SCCM SP1, and now you need to update your Admin Consoles!

Updating the SCCM 2012 system with any major update that includes fixes to the Admin Console – generally means that you need to update all the Admin Consoles that you have in your environment to meet the version of your servers. In SP1 CU1, you can still use the old Admin Console after the update, so there is no rush to update all of the Admin Consoles.

Continue Reading

Update SCCM 2012 Admin Console to SP1

Purpose: You have installed SCCM SP1, and now you need to update your Admin Consoles!

Updating the SCCM 2012 system with any major update that includes fixes to the Admin Console – generally means that you need to update all the Admin Consoles that you have in your environment to meet the version of your servers. In SP1, you cannot use the old console after the server update anymore at all, so you will be forced to update the Admin Consoles immediately. Neat to know at this point, right?

Continue Reading

Update the SCCM 2012 Clients to SP1 CU1

Purpose: You have installed SCCM SP1 CU1, and now you need to update your agents!

Updating the SCCM 2012 system with any major update that includes fixes to the client-side – automatically means that you need to update all the clients that you have in your environment to meet the version of your servers. This can be done using different methods. The following methods are at least supported by Microsoft as a weapon of choice. In this post, I will only cover the method that I selected.

Methods of updating the SCCM 2012 clients:

  1. Install new client as an application / package.
  2. Use built-in tool of Client pushing (unsupported for CU-updates).
  3. Setup Client Update as part of Software Updates.
  4. Enable Site-Wide client automatic installation (only major updates).
  5. Install the client manually to desired workstations.

Continue Reading

Update the SCCM 2012 Clients to SP1

Purpose: You have installed SCCM SP1, and now you need to update your agents!

Updating the SCCM 2012 system with any major update that includes fixes to the client-side – generally means that you need to update all the clients that you have in your environment to meet the version of your servers. This can be done using different methods. The following methods are at least supported by Microsoft as a weapon of choice. In this post, I will only cover the method that I selected.

Methods of updating the SCCM 2012 clients:

  1. Install new client as an application / package.
  2. Use built-in tool of Client pushing.
  3. Setup Client Update as part of Software Updates.
  4. Enable Site-Wide client automatic installation.
  5. Install the client manually to desired workstations.

Continue Reading