Tag Archives: Sccm

Extend SCCM client Hardware Inventory with a Custom Attribute value: Client Cache Size

Purpose: Gather SCCM client cache sizes from your environment

I used to have a situation where many people did many things with great enthusiasm. Sounds familiar? This resulted in a non standard environment. To make sure that all SCCM Clients have the same CACHE SIZE, we need to first gather that CACHE SIZE with SCCM before we can create any Device Collections to hunt down wrong SCCM client cache sizes. Wrong CACHE SIZES can occur when SCCM clients are installed with different parameters or altered manually.

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

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

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

Update SCCM 2012 to SP1 CU1

Purpose: You have installed SCCM SP1, but its not up to date anymore, Aieee! Do something again!

So you thought you are safe now that the SP1 is installed and all your worries will go away? Wrong! SP1 created some new issues and did not fix all the original issues you might have had with the system. So I urge you to update SCCM 2012 SP1 to the following Comulative Update 1, which will help you to grow less grey hair. With all these different issues, there will most likely be updates more in the future, but do not wait for SP2 to appear, it could take a while.

Bug fixes in Configuration Manager 2012 SP1 CU1 (Includes download link)

Update SCCM 2012 to SP1

Purpose: You installed RTM version, and its now not up to date anymore, Aieee! Do something!

Let me begin by pointing out the obvious here: you do not need this update because of all the new features it gives, you need this update because of all the bug fixes it does! My god, that almost rhymed, I could start writing poetry. The post is divided into two parts: the first part containing the requirements that you need to do before you can move to the second part, which is the actual installation of the update. Do not step over the first part, you really do need to do all of these.

Bug fixes in Configuration Manager 2012 SP1

New features in Configuration Manager 2012 SP1 (Referenced)

Show Workstation Name in Computer Icon and Start Menu (BAT)

Purpose: Show the Workstation name on Desktop and Start Menu (natively)

The case everyone is familiar with (more or less) is the case of getting a customer to tell the support personnel their computer name. This can be done with multiple different ways (tag the computer with stickers, link username and computer name in your management tool, or create something that helps the user to tell it). The way I’m going to demonstrate is suited for some cases: create something that helps the user to tell it. In this case it is going to be by renaming the “Computer” icon on the public desktop and forcing it to be shown there. This will also then rename the Start Menu “Computer”.

Requirements: SetACL.exe (http://helgeklein.com/setacl/) / included in the download
Usage: start “Configure” /wait IT_OSD_BAT_ShowWorkstationNameInMyComputer.bat
Debugging: The script must be ran as NT AUTHORITY/SYSTEM (ie. the installing force of SCCM).
Configuration: No need.
Continue Reading