NINet.org

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…)

Those of us that installed FEP 2010 are no doubt annoyed that we cannot see the details of the queries used by SCCM to populate the FEP created collections.

The following will require acess to the SQL instance that SCCM uses as the querys are to be executed driectly on that instance.

(continue reading…)

It’s been a while since I posted anything, but I’ve been really busy at home and in work.

Although I have beening using OSD for a while it hasn’t been completely automated, things like timezone, keyboard locale etc still need to be changed by an administrator after a rebuild. Now we have sites in America, UK, Europe and Japan, so I need to account for them in my task sequence. I will admit here that I had a bit of trouble with getting the script to work so I did get some help from MS (they added 2 lines of code to the script and 1 task sequence event).

There are 2 parts to this, 1st is the vbscript to detect and set the location and then some task sequence events to act on the variables we set.

(continue reading…)

The snippet allows one to create a collection containing objects that are in some OUs but NOT IN another collection

(continue reading…)

When I was building our SCCM environment I decided it would be a good time to clean up WSUS & FCS and bring them under the new system.

The problem I ran into was “How do I repoint FCS?” without having to uninstall and reinstall it on every machine.

The solution, a bit of VB script based on the information here: http://blogs.technet.com/fcsnerds/archive/2008/11/12/changing-the-management-group-to-which-an-fcs-client-reports.aspx

(continue reading…)

LAST UPDATED: 2010-04-12

These 2 reports will determine the link to the dell driver page for the systems based on their OS and Architecture.

(continue reading…)

IIRC I got these on “myitforum” but I can’t remember where abouts.

I have modified them a bit to restrict to just the machines I have (mainly a Dell shop) and to exclude VMs.

(continue reading…)

2011-07-11: This method is now deprecated please go here: http://ninet.org/2011/07/dell-hp-warranty-info-in-sccm

LAST UPDATED: 2010-09-22

UPDATE 2010-09-14: Dell have changed the layout to add an extra field in the contracts section so the scripts are broken

UPDATE 2010-07-09: I’ve noticed this page is getting a lot of hits, I haven’t had a chance to get this working yet so if anyone does please post a comment or drop me a mail using the contact page. I’ll try and get some time next week to look at it again.

These scripts are a work in progress and you should check back regularly for updates until I mark them as final.

This is an updated version of the “SCCM Get Dell warranty info”

Basically the problem with the other script is that a user with admin privs must run it or the computer account must have access to the internet.

I have split the script in 2 and rejigged it slightly so that now 1 (user) script is run “When user is logged on with the users privliges” and the other (system) script is run 2nd “When user is logged on with administrative privliges”. You can use the “Run another program 1st” option in the program definition which should make it practically act like a single script.

(continue reading…)

2011-07-11: This method is now deprecated please go here: http://ninet.org/2011/07/dell-hp-warranty-info-in-sccm

LAST UPDATED: 2010-09-22

UPDATE 2010-09014: Dell have changed the layout to add an extra field in the contracts section so the scripts are broken

Version 2: work around for computer account that can’t access the internet http://ninet.org/2010/03/sccm-get-dell-warranty-info-v2/

I found a script and mof edit here: Sherry Kissinger’s Blog at myitforums.com

However when I tried it, it was completely broken all the data being returned in the wrong place. So I have rewritten it so that it is more modular and hopefully easier to maintain.

Now a bit of a disclaimer, my vbs skills are very rusty so the script works though it probably isn’t very efficient. So if you can suggest improvements please do and I’ll update the script as needed.

Although the code is long most of it is comments and “wscript.echo” statements for debugging, feel free to strip them out if you want something more compact.

I have also added the ability to dump the results to a csv file that you can collect with SCCM if you don’t want to capture from WMI.

(continue reading…)