Month: December 2011

New Look!

Posted on Updated on

I’ve updated my blog with a newer theme – one that better supports blocks for my shorter code, maintains the previous functionality, and allows me to use a rotating custom header from my own photography.  I’m really happy with it and enjoy the new look.  Pop on over for a peek!  https://t3chn1ck.wordpress.com

Reblog: ConfigMgr OSD Always including certain files in your Boot Images

Posted on

Cool way to automagically include support-related files in your boot images for troubleshooting during task sequences.  I’m re-blogging it so I would always remember it ;-)

http://www.1e.com/blogs/2010/07/17/ConfigMgr-OSD-Always-including-certain-files-in-your-Boot-Images-think-Trace32/

Custom Client Health Monitoring, Part 3

Posted on Updated on

This is part 3 of 3 on my custom client health monitoring reports, which I created way back in SMS 2003 and I still use today.  Part 1 outlines a custom report that I call “Computers that belong to X number of monitored collections“, which shows how many collections in which a computer resides.  Part 2, a drill down of the first report, will then show exactly which collections that computer is a member of, called Collection memberships for a specific computer.  Drilling down into that report then shows a report that will show all computer records that are in the collection.  This report can be particularly helpful when trying to identify a set of computers (such as all at a particular location) that are being impacted.

The code:

select Count(FCM.Name) as 'Total number of computers in collection', 
   COL.Name, COL.Comment, COL.CollectionID
 from v_FullCollectionMembership FCM, v_Collection COL
 where  ((COL.CollectionID='CollectionID1' and FCM.CollectionID='CollectionID1') or
   (COL.CollectionID='CollectionID2' and FCM.CollectionID='CollectionID2') or
   (COL.CollectionID='CollectionID3' and FCM.CollectionID='CollectionID3') or
   (COL.CollectionID='CollectionIDetc' and FCM.CollectionID='CollectionIDetc') )
 group by COL.Name, COL.CollectionID, COL.Comment
 order by 'Total number of computers in collection' DESC

Now, link this report for further drill down into the default SCCM report for computer information by

  1. Edit the report and select the “Links” tab
  2. Change the “Link type” to “Link to another report”
  3. Select report “Members of a selected collection”
  4. Create a new Target Report Prompt where Name=variable, Prompt text=Collection ID, and Column=4
  5. Click OK and enjoy drill down ;-)

This now completes a trio of custom client health monitoring/reporting collections!

SUP Search Folder: All non-superseded updates for workstations

Posted on Updated on

This is the search folder that I use to identify any and all security updates possibly available to Windows workstation OS computers.  It includes other products too, not just Windows.

  • Products
    • CAPICOM
    • Expression Media\Web
    • MS Lync 2010
    • MS StreamInsight
    • MS Works
    • Network Monitor
    • Office 2003/2007/2010
    • Report Viewer
    • Silverlight
    • SQL Server
    • Visual Studio
    • Windows 7 Client
    • Windows Defender
    • Windows Vista
    • Windows XP
    • Works 6-9 Converter
    • Writer Installation and Upgrades
  • Update Classification:
    • Critical Updates
    • Security Updates
    • Update Rollups
    • Updates
    • Applications
  • Expired: No
  • Superseded: No
  • Title:
    • Update
    • Malicious software removal tool
    • Visual C++

Finally, select the option “Search all folders under this feature”

Custom Client Health Monitoring, Part 2

Posted on Updated on

This is part 2 of 3 on my custom client health monitoring reports, which I created way back in SMS 2003 and I still use today.  Part 1 outlines a custom report that I call “Computers that belong to X number of monitored collections“, which shows how many collections in which a computer resides.  Drilling down into that report will then show exactly which collections that computer is a member of.  This report I call “Collection memberships for a specific computer“.  The code for this report is as follows:

select distinct SYS.Name0 as 'Computer',
  SYS.User_Name0 as 'User Name',
  col.Name, col.CollectionID
from v_R_System SYS
LEFT join v_FullCollectionMembership fcm on fcm.ResourceID=sys.ResourceID
LEFT join v_Collection col on col.CollectionID=fcm.CollectionID
where SYS.Name0=@var1 AND (
  FCM.CollectionID='CollectionID1' or
  FCM.CollectionID='CollectionID2' or
  FCM.CollectionID='CollectionID3' or
  FCM.CollectionID='CollectionIDetc' )
GROUP BY SYS.Name0, SYS.User_Name0, col.name, col.collectionID
ORDER BY SYS.Name0 

Now, link this report for further drill down into the default SCCM report for computer information by

  1. Edit the report and select the “Links” tab
  2. Change the “Link type” to “Link to another report”
  3. Select report “Hardware – General – Computer information for a specific computer”
  4. Create a new Target Report Prompt where Name=variable, Prompt text=Computer Name, and Column=1
  5. Click OK and enjoy drill down ;-)

Next up: Part 3 of 3 – Monitored Collections Summary

Custom Client Health Monitoring, Part 1

Posted on Updated on

Something that I created way back with SMS 2003 is created a set of reports as my own homegrown monitoring for client health (note: I still use these reports today with SCCM 2007) .  This is part 1 of 3.

BACKGROUND: In a typical environment, a computer can reside in many collections with many different advertisements assigned to it.  Often these collections are designed with queries that will return a subselect set of systems that “do not have something installed”.  For example, the query may be designed to list a set of systems that do not have Adobe Reader, so as the software installs and the PCs submit the updated inventory, those computers will then get removed from the collection upon the next scheduled update cycle.

The following report, Computers that belong to X number of monitored collections, will list PCs in the most collections.  However, not all collections are subselect collections that contain computers missing software.  For example, I have recurring scripts assigned to various PCs to perform various tasks that I do not want as part of the results.  This code only reports on the collections that I care about.  To use this, simply change the “CollectionID” with the collection that you want to report upon.

select distinct
   SYS.Name0 as 'Computer',
   SYS.User_Name0 as 'User Name',
   Count (*) as 'Number of missing installs',
   HWSCAN.LastHWScan,
   SWSCAN.LastScanDate
 from v_R_System SYS
 LEFT join v_FullCollectionMembership fcm on fcm.ResourceID=sys.ResourceID
 LEFT JOIN v_GS_LastSoftwareScan SWSCAN on SYS.ResourceID = SWSCAN.ResourceID
 LEFT JOIN v_GS_WORKSTATION_STATUS HWSCAN on SYS.ResourceID = HWSCAN.ResourceID
 LEFT JOIN v_UpdateScanStatus UPSCAN on SYS.ResourceID=UPSCAN.ResourceID
 where SYS.Name0=FCM.Name AND (
   FCM.CollectionID='CollectionID1' or
   FCM.CollectionID='CollectionID2' or
   FCM.CollectionID='CollectionID3' or  
   FCM.CollectionID='CollectionIDetc' )
 GROUP BY SYS.Name0,
   SYS.User_Name0,
   HWSCAN.LastHWScan,
   SWSCAN.LastScanDate
 ORDER BY 'Number of missing installs' desc, SYS.Name0

Results can look like this:

Next up: drilling down into this report to reveal Collection memberships for a specific computer

Fix for SMS Trace missing columns

Posted on

I had a problem with SMS Trace recently when review SCCM log files; it suddenly only displayed the “Log Text” column.  When reviewing the logs, it’s equally as useful to see the Date/Time column so that you can just glance at entries to see when they occurred without having to select every single line item.  Anyhow, trying to add the columns back through File > Preferences just didn’t get the job done.  In the end, the fix was to simply delete regkey HKCU\Software\Microsoft\Trace32.  After launching SMS Trace, the registry key was recreated and the columns returned…