A while back I had a support case open with MS about some scripting in winPE. In order to debug the problem we wanted to see what variables were declared & what their values were. The support tech came up with the attachted script, I never got round to adding it to my scripts folder, so I ran it by opening a command shell in winPE (F8) then “net use Z: \\
Tag: SMS
Dell & HP Warranty Info in SCCM
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?
SCCM All Computers, their OU and last Hardware Scan
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)
SCCM Serial Numbers and Asset Tags
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.
Forefont Endpoint Protection Query Details
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.
OSD – Customising deployment depending on location
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.
SCCM restrict collection membership
The snippet allows one to create a collection containing objects that are in some OUs but NOT IN another collection
Rehome FCS
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
SCCM Dell Driver Links in report
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.
SCCM Warranty Reporting
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.