Free Disk Space Collection SCCM 2012

We have been having several users with older PC's complaining of low disk space errors.  These are normally shared Dell PC's with 80GB HDD's.  We have lots of surgerys where tens of nurses will log on and subsequently create a local profile.  As we have cached mode enabled for Outlook (don't ask) this creates massive .OST files in every profile.

I wanted SCCM to keep track of these machines and subsequently run a batch file that clears all the .OST files off the machine.

I wanted a collection that would list all machines with less than 1GB free disk space.  I created the collection courtesy of http://myitforum.com/myitforumwp/2013/12/09/sccm-2012-r2-free-disk-space-report/ but found it was empty no matter what.

I then eventually came across this post http://e-enfra.blogspot.co.uk/2012/02/sccm-2012-free-disk-space-is-not.html instructing that by default the disk space isn't automatically collected by the hardware inventory cycle.

Enable this and just wait for the Harware Inventory Cycle to kick in and the disk space info will become available.

ifM63x64.sys file missing or corrupt - SCCM OSD (X1 Carbon)

Building a new Lenovo X1 Carbon with the new integrated LAN adapter (no more guessing which USB port to use!) via SCCM 2007 and I came across this little blinder.

After the first reboot to OS I was presented with this error screen:

I spotted that is was driver in my driver pack (taken from Lenovo's SCCM pack) for the  Intel Ethernet FCoE Virtual Storport Miniport Driver.

I located the driver in my driver pack and removed it - left he check box UNTICKED to update the distribution point and then manually when and updated it after myself. 

Once I was happy that the source had incremented by one version I kicked off the build again.

Sure enough it sailed through and we are all happy....

 

Microsoft Error Codes seen during SCCM software deployments

I may have posted this before - I can't remember.

Error code               Value  Description
---------------------------------------------------------------------------
ERROR_SUCCESS               0   Action completed successfully.
ERROR_INVALID_DATA         13   The data is invalid.
ERROR_INVALID_PARAMETER    87   One of the parameters was invalid.
ERROR_INSTALL_SERVICE_
 FAILURE                 1601   The Windows Installer service could not be 
                                accessed. Contact your support personnel 
                                to verify that the Windows Installer 
                                service is properly registered.
ERROR_INSTALL_USEREXIT   1602   User cancel installation.
ERROR_INSTALL_FAILURE    1603   Fatal error during installation.
ERROR_INSTALL_SUSPEND    1604   Installation suspended, incomplete.
ERROR_UNKNOWN_PRODUCT    1605   This action is only valid for products that
                                are currently installed.
ERROR_UNKNOWN_FEATURE    1606   Feature ID not registered.
ERROR_UNKNOWN_COMPONENT  1607   Component ID not registered.
ERROR_UNKNOWN_PROPERTY   1608   Unknown property.
ERROR_INVALID_HANDLE_
 STATE                   1609   Handle is in an invalid state.
ERROR_BAD_CONFIGURATION  1610   The configuration data for this product is 
                                corrupt. Contact your support personnel.
ERROR_INDEX_ABSENT       1611   Component qualifier not present.
ERROR_INSTALL_SOURCE_
 ABSENT                  1612   The installation source for this product 
                                is not available. Verify that the source 
                                exists and that you can access it.
ERROR_INSTALL_PACKAGE_
 VERSION                 1613   This installation package cannot be 
                                installed by the Windows Installer 
                                service. You must install a Windows 
                                service pack that contains a newer version 
                                of the Windows Installer service.
ERROR_PRODUCT_
 UNINSTALLED             1614   Product is uninstalled.
ERROR_BAD_QUERY_SYNTAX   1615   SQL query syntax invalid or unsupported.
ERROR_INVALID_FIELD      1616   Record field does not exist.

ERROR_INSTALL_ALREADY_
 RUNNING                 1618   Another installation is already in 
                                progress. Complete that installation 
                                before proceeding with this install.
ERROR_INSTALL_PACKAGE_
 OPEN_FAILED             1619   This installation package could not be 
                                opened. Verify that the package exists and 
                                that you can access it, or contact the 
                                application vendor to verify that this is 
                                a valid Windows Installer package.
ERROR_INSTALL_PACKAGE_
 INVALID                 1620   This installation package could not be 
                                opened. Contact the application vendor to 
                                verify that this is a valid Windows 
                                Installer package.
ERROR_INSTALL_UI_
 FAILURE                 1621   There was an error starting the Windows 
                                Installer service user interface. Contact 
                                your support personnel.
ERROR_INSTALL_LOG_
 FAILURE                 1622   Error opening installation log file. 
                                Verify that the specified log file 
                                location exists and is writable.
ERROR_INSTALL_LANGUAGE_
 UNSUPPORTED             1623   This language of this installation package 
                                is not supported by your system.
ERROR_INSTALL_TRANSFORM_
  FAILURE                1624   Error applying transforms. Verify that
                                the specified transform paths are valid.
ERROR_INSTALL_PACKAGE_
 REJECTED                1625   This installation is forbidden by system 
                                policy. Contact your system administrator.
ERROR_FUNCTION_NOT_
 CALLED                  1626   Function could not be executed.
ERROR_FUNCTION_FAILED    1627   Function failed during execution.
ERROR_INVALID_TABLE      1628   Invalid or unknown table specified.
ERROR_DATATYPE_MISMATCH  1629   Data supplied is of wrong type.
ERROR_UNSUPPORTED_TYPE   1630   Data of this type is not supported.
ERROR_CREATE_FAILED      1631   The Windows Installer service failed to 
                                start. Contact your support personnel.
ERROR_INSTALL_TEMP_
 UNWRITABLE              1632   The temp folder is either full or 
                                inaccessible. Verify that the temp folder 
                                exists and that you can write to it.
ERROR_INSTALL_PLATFORM_
 UNSUPPORTED             1633   This installation package is not supported 
                                on this platform. Contact your application 
                                vendor.
ERROR_INSTALL_NOTUSED    1634   Component not used on this machine.
ERROR_PATCH_PACKAGE_
 OPEN_FAILED             1635   This patch package could not be opened. 
                                Verify that the patch package exists and 
                                that you can access it, or contact the 
                                application vendor to verify that this is 
                                a valid Windows Installer patch package.
ERROR_PATCH_PACKAGE_
 INVALID                 1636   This patch package could not be opened. 
                                Contact the application vendor to verify 
                                that this is a valid Windows Installer 
                                patch package.
ERROR_PATCH_PACKAGE_
 UNSUPPORTED             1637   This patch package cannot be processed by 
                                the Windows Installer service. You must 
                                install a Windows service pack that 
                                contains a newer version of the Windows 
                                Installer service.
ERROR_PRODUCT_VERSION    1638   Another version of this product is already 
                                installed. Installation of this version 
                                cannot continue. To configure or remove 
                                the existing version of this product, use 
                                Add/Remove Programs on the Control Panel.
ERROR_INVALID_COMMAND_
 LINE                    1639   Invalid command line argument. Consult the 
                                Windows Installer SDK for detailed command 
                                line help.
ERROR_INSTALL_REMOTE_
  DISALLOWED             1640   Installation from a Terminal Server
                                client session not permitted for 
                                current user.
ERROR_SUCCESS_REBOOT_
  INITIATED              1641   The installer has started a reboot.
                                This error code not available 
                                on Windows Installer version 1.0.
ERROR_PATCH_TARGET_
  NOT_FOUND              1642   The installer cannot install the
                                upgrade patch because the program
                                being upgraded may be missing, or the
                                upgrade patch updates a different
                                version of the program. Verify that 
                                the program to be upgraded exists on
                                your computer and that you have the 
                                correct upgrade patch.
 
                                This error code is not available on
                                Windows Installer version 1.0.
ERROR_SUCCESS_REBOOT_
 REQUIRED                3010   A restart is required to complete the 
                                install. This does not include installs 
                                where the ForceReboot action is run. Note 
                                that this error will not be available until 
                                future version of the installer. 
    

Trend OfficeScan 10 causing Hash Mismatch Errors in SCCM 2007

For the last 2 years of my SCCM Career I've been blighted with issues concerning the above.  I've added exceptions to our Trend server, calls have been logged but I can never seem to get this sorted.

I find that if Trend is running the execmgr.log will sometimes show Hash Mismatch errors.  If I manually disable Trend (or better still remove it!!) - it works fine.

I've started adding a quick command to my Task Sequences and package deployments to temporarily disable OfficeScan while the deployment takes place and it works a charm!!

Simply add the following command lines before and after via Task Sequence or simply create a package with a batch file containing the following.

Before:

net stop tmlisten
net stop ntrtscan

After:

net start tmlisten
net start ntrtscan

Obviously this works manually too if you should ever need to disable Trend remotely...  Even if it has a password!!!!!!!! ;)

iPhone Activation Error

So if you, like me have woken up on 6th October 2013 to find a nice little error on your crApple device asking you to "Activate" then you may want to find out how to fix it.

 

As the calendar rolls over to 6th Oct; Reports are coming in from all over the World of people with iOS7 beta6 being locked out of their phones due to the expiry of the test version of the nice shiney iOS7 being retired.

Blah blah blah I'm going to cut the crap and just get on with it as it's Sunday morning and I'm trying to enjoy my kids, a bacon butty & a cup of tea...

Get the stuff you need & back it up baby...

• Download the latest crapTunes or update from within crapTunes.
• Backup your crapPhone with crapTunes if you can (I couldn't).
• You can still access photos so if you need to, back them up too.
• Download the latest version of iOS 7.0.2 from one of these sources (not responsible for external content etc etc) then hold down on the option key (Mac) or the shift key (Windows) and click the “Check for Update” button in the Summary pane of crapTunes. Browse to the file you downloaded. (it will take an age!)
  

iPad2(Wi-Fi) (iPad2,1)	7.0.2 (11A501)
iPad2(AT&T) (iPad2,2)	7.0.2 (11A501)
iPad2(Verizon) (iPad2,3)	7.0.2 (11A501)
iPad2,4 (iPad2,4)	7.0.2 (11A501)
iPad2,5 (iPad2,5)	7.0.2 (11A501)
iPad2,6 (iPad2,6)	7.0.2 (11A501)
iPad2,7 (iPad2,7)	7.0.2 (11A501)
iPad3,1 (iPad3,1)	7.0.2 (11A501)
iPad3,2 (iPad3,2)	7.0.2 (11A501)
iPad3,3 (iPad3,3)	7.0.2 (11A501)
iPad3,4 (iPad3,4)	7.0.2 (11A501)
iPad3,5 (iPad3,5)	7.0.2 (11A501)
iPad3,6 (iPad3,6)	7.0.2 (11A501)
iPhone4 (iPhone3,1)	7.0.2 (11A501)
iPhone3,2 (iPhone3,2)	7.0.2 (11A501)
iPhone4(Verizon) (iPhone3,3)	7.0.2 (11A501)
iPhone4S (iPhone4,1)	7.0.2 (11A501)
iPhone5,1 (iPhone5,1)	7.0.2 (11A501)
iPhone5,2 (iPhone5,2)	7.0.2 (11A501)
iPhone5,3 (iPhone5,3)	7.0.2 (11A501)
iPhone5,4 (iPhone5,4)	7.0.2 (11A501)
iPhone6,1 (iPhone6,1)	7.0.2 (11A501)
iPhone6,2 (iPhone6,2)	7.0.2 (11A501)
iPodTouch(5G) (iPod5,1)	7.0.2 (11A501)

•  Choose the file and let it do it's thing.  Don't worry - you won't loose any data either!!!

BLOODY CRAPPLE!!!


DocN

X1 Carbon Incorrect Hash Errors during OSD

I was fighting with this one for a couple of days.  Lenovo X1 Carbon - deploying Windows 7 x64.  All drivers were fine and dandy but I was getting randon "Incorrect hash value" errors when the OSD was failing.

This was determined by looking in the SMSTS.log once the OSD had failed.

It transpires that if the USB to Ethernet adapter was plugged in to the right hand USB socket it was dropping loads of packets.  Plugging it into the left hand side worked a treat.

As simple a solution as it sounds this may be far too obvious for some tecchy to even try.  I managed to replicate this on 3 different units so it wasn't just faulty parts.

Felt like a complete numpty once I discovered the fix!

Turn on logging for MSI installs

If you ever install from MSI's (which I'm sure you do) it can be handy to turn on logging so you can see the outcome - particularly handy if the install is failing.

Use the following code after your package.MSI and then a log file will be generated at the location you choose:

msiexec /i Packagename.msi /l*v c:\logname.log

PXE & OSD Builds Failing - conflicting records

If you have ever had issues with your PXE boot failing when you try to rebuild a machine that already exists within SCCM then this may help you out.

I'd been spilling over this one on and off for a while when I discovered that these machines were appearing in "Conflicting Records". 

Conflicting Records within SCCM console

You have a few options here.  We can get SCCM to manage conflicting records by chaging the setting site wide:

1. Navigate to System Center Configuration Manager / Site Database / Site Management / <site code> - <site name>
2.  Right-click <site code> - <site name> and then click Properties. 
3. Under the "Advanced" tab, you can choose Manually resolve conflicting records or Automatically create new client records for duplicate hardware IDs.
4. OK

Another option is to manually resolve conflicting records:

From conflicting records as above select the conflicting record and look in the actions pain and you will see  few options:

1.  Merge - combines the new record with the existing one merging together
2. New - creates a brand new record for the conflict
3. Block - creates a new record but blocks it

Then there is another really cool way of doing it!!

•  Save this into a file called "Merge.vbs" to somewhere of your choice - we will be using it in  a few steps time - don't forget to check your formatting if you copy and paste - the "quotes" can sometimes 'mess up' etc

Dim swbemLocator
Dim swbemServices

Main()

Sub Main()
Dim oProviderLocation
Dim oLocation
Dim oReg
Dim oPendingRegs
    Set swbemLocator = CreateObject("WbemScripting.SWbemLocator")
    swbemLocator.Security_.AuthenticationLevel = 6 'Packet Privacy.
    Set swbemServices = swbemLocator.ConnectServer(".", "root\SMS")
    Set oProviderLocation = swbemServices.InstancesOf("SMS_ProviderLocation")
    For Each oLocation In oProviderLocation
        If oLocation.ProviderForLocalSite = True Then
            Set swbemServices = swbemLocator.ConnectServer(oLocation.Machine, "root\sms\site_" + oLocation.SiteCode)
        End If       
    Next

    Set oPendingRegs = swbemServices.ExecQuery("SELECT * FROM SMS_PendingRegistrationRecord")
    For Each oReg In oPendingRegs
        Resolve 1, oReg.SMSID
    Next

End Sub

Sub Resolve(action, SMSID)
Dim InParams
    Set InParams = swbemServices.Get("SMS_PendingRegistrationRecord").Methods_("ResolvePendingRegistrationRecord").InParameters.SpawnInstance_
    InParams.Action = action
    InParams.SMSID = SMSID

    swbemServices.ExecMethod "SMS_PendingRegistrationRecord","ResolvePendingRegistrationRecord", InParams
End Sub

• Ensure that conflicting records on the advanced tab of site properties is still set to "Manually Resolve Conflicting Records"
• Create a new status filter rule with the following properties: 

Component : SMS_DISCOVERY_DATA_MANAGER
Message ID: 2642

• On the actions tab select "run a program" and specify the above script we created.  If on a x64 server you may need to specify the full path to "cscript.exe" i.e. “C:\Windows\SysWOW64\cscript.exe C:\SCCMTools\Merge.vbs”

Relying on the status filter rule will mean that the script will only run when it detects the 2642 event however you can run the script manually if you want to tidy up what is already there.

I have to thank a great SCCM consultant; Dean Lockwood at BDS services for this - although he will tell you it was my inspiration that prompted the outcome ;)

Task Sequence Fails Error 0x80040104

More fun and games with OSD Task Sequences - this time in the form of error 0x80040104.

The error as it was displayed on the clients screen was:

This task sequence cannot be run because a package referenced by the task sequence could not be found. For more information, please contact your system administrator or helpdesk operator.

This happened immediately after selecting the task sequence and processing the dependencies.

Upon viewing the SMSTS.log we spotted the error

Failed to resolve selected task sequence dependencies. Code(0x80040104)


The only change made to the TS since yesterday was a new driver package for the Lenovo X220T tablets.  The reference to a missing package reminded me of a post I made once in reference to drivers and driver packages - that if you leave the distribution point on Source version 1 it will just bomb out.  Refreshing the DP didn't help so went via "Manage" and created a new source version.


As if by magic..... It worked!

SMSTS.log

verifying content availability for package optional program *

I have a task sequence setup for quick deployment of corporate apps to machines that haven't yet got complete driver packages and get a vanilla install of Windows 7 x64 deployed.

This TS was recently failing when run from "Run Advertised Programs" with the error:

verifying content availability for package optional program *

It turned out my Java Package didn't have program selected due to the it being disabled from the actual packages program its self.  I've highlighted it below.  If you do get the error it's worth checking your TS programs - unfortunately SCCM doesn't always give the most comprehensive of error messages - I hope this helps someone else.