NINet.org

Recently I had an issue where ActiveSetup wasn’t installing some applications when deployed. It turned out that it was due to some of the packaged applications not having a program with the Windows installer information populated. As it was believed that this may not an isolated issues I was tasked with producing a report of all Packages where the information was missing. This is not actually possible via the default reports as none of the views exposed to SCCM actually contain this information. The only way to get this information is to query the SCCM database table “PkgPrograms”, and to do that and have a permenant report SSRS is needed as it can run with the credentials of the user generating it or with an execution account which may have more access.

(continue reading…)

There are 3 reports in this group;

The first returns a list of all packages in a Task Sequence and the DPs they are targeted at that are in a “not installed” state. Currently this only detects targeted and not installed, once I figure out the SQL i’ll update this so it includes DPs that it is not targeted at as well.

The second lists all Task Sequences that reference a specific package, the idea here is if you wish to replace a package with a newer version or decommission a package you can get a list of all of the TSes that include it.

The third and final report compares two Task Sequences and returns a list of packages that are in one but not the other along with the ID of the Task Sequence that it is in.

(continue reading…)

I have 85 or so DPs across more than 5 Primary sites and sometimes I see failures in newly created Task Sequences (or even old ones) during an OS deployment due to a package not being available.

• Distribution status of a specific package on a specific distribution point - This report shows the installation status of a package on the specified distribution point.
• Distribution points without a specific package - This report shows any Distribution Points a Package is not installed on. N.B. Package MUST be targeted to the site in order to be detected
• Distribution points without a specific package in a site – This report shows any Distribution Points a Package is not installed on in the specified site. N.B. Package MUST be targeted to the site in order to be detected
• Distribution status of a specific package in a site - This report shows the installation status of a package on each of its distribution points in the specified site

One of my users was complaining of “slow vm performance over the network”, so I requested a few simple diags including a traceroute from his machine to the vm instead I got a traceroute from the VM to the VM. So I decided that clearly I was asking too much from the user and threw the following batch file together (I may rewrite it in powershell for fun later).

(continue reading…)

After a mass of updates to the code a new version is out, this is still experimental so should only be used in a lab environment.

(continue reading…)

This little gem I wrote will listen to all interfaces on a computer for CDP packets. Once it has looped all the interfaces any packets it has captured are processed and added to WMI.

Using the attached SMS_DEF.mof we can extract that information and place it in SCCM. Anyone who knows what CDP is will see the benefit immediately. For the rest; CDP (Cisco Discovery Protocol), Cisco devices send out CDP packets every 60seconds each packet contains information about the port it was sent from and the sender. In a nutshell if my computer receives a packet then I can tell which switch I am connected to, what port on that switch and a few other bits and bobs about the switch. e.g. In a test environment I have a Cisco switch which connects to a Cisco IP phone which then connects to my computer, when exe runs I get two entries in WMI, one for the phone and one for the Switch.

The use case is that helpdesk  may not know where a user is physically or where they are connected to the network and the user may be experiencing network issues, this would allow a helpdesk tech to locate the switchport  the user is connected to and pass that info to the network team for troubleshooting saving both parties the hassle of tracing cables and also allowing reporting on where a user is plugging in over a period of time.

There is still a bit to be done for this but it does generally work.

(continue reading…)

I have tweaked my powershell script for the SCCM Dell/HP tags due to popular demand so that it can be run on a single machine using a list of service tags as the source and then will output to a CSV file. The source CSV can have any number of columns however it MUST have the following three for the script to work “Name,Vendor,Tag” in its default state. You also need to edit the $infile & $outfile variables as required.

(continue reading…)

Updated: 2011-08-18

This is the next evolution in the warranty info fight, Dell keep changing their site which is rather frustrating. I have re-written the Warranty Info Scripts in powershell as in my opinion the code is a lot cleaner and more manageable, I’ve tweaked the MOF edit required to read this.

One major change to the script is that I have added support for HP systems, now I must stress I only have one or two of these, both are out of warranty and only had base warranties so something may have been missed / may not work as expected. You can either fix it and let me know the changes you make or let me know, via the contact page, the tag of one of your systems and I will look at it when I get a chance.

If you use any other version of the script from my site you will need to update sms.mof as the reports have changed.

I am quite shameless so if you find this useful feel free to click on donate and well, donate. :D

What info do you get?

(continue reading…)

A quick Report to return all of the computers, the OU they are in and the last time they had  a Hardware scan.

First we create a temporary table to hold the 1st pass results, then we query that table looking for the longest OU for each computer ( this way we only get 1 record per computer returned, otherwise each level of the OU a computer is a member of will be returned)

(continue reading…)

This is just a quick one, if you have dell machines (not sure if other manufacturers do it) but one of the BIOS options is ASSET TAG. Now this does not, as you would expect, appear in Win32_BIOS, instead it appears under Win32_SystemEnclosure.

(continue reading…)