Checking an MD5 Checksum Of A Downloaded File in Linux

MD5 is a one-way algorithm as defined by the RFC1321 that can be used to verify the integrity of a file or filesystem by providing as 128bit digital signature.  This digital signature is like a fingerprint for a file or filesystem and will change dramatically even if a single byte changes.

This means they are excellent in checking the integrity of a file that you have downloaded of a mirror that provides the files equivalent MD5Checksum.  Continue reading

VBScript – Passing Named Arguments

I am always forgetting this so I have posted it so I can refer back to this when needed.  Sometimes via a command line you want to be able to pass command line parameters to a vbscript. e.g.

cscript.exe myscript.vbs /Parameter:value

The vbscript to handle this is as follow:

Option Explicit
Dim colNamedArguments

Set colNamedArguments = Wscript.Arguments.Named
If colNamedArguments.Exists("Parameter") Then
    Wscript.echo "Parameter Exists!"
    Wscript.echo "Parameter = " & _
End If

For more information see the following microsoft article :


Windows XP (x64) & Lenovo S30 Workstation SATA & SAS Drivers Via RIS

I have the challenge of trying to get Windows XP (x64) work on some of the most recent hardware.  SATA and the newer SAS Drivers are quite a challenge on these devices, as was proving the case when I was trying to get them to work on the Lenovo S30.  During Remote Installation Services (RIS) kept reporting “corrupted driver messages” when trying to put the two sets of drivers Continue reading

SCCM OSD ‘No Boot Action for Device (x) found

I was receiving the above message ‘No Boot Action for Device(32123) found.’  on the PXE service point server, in smspxe.log.

The number (32123) is the resource ID of the computer object found at that SCCM site.  The device was in a collection which had an advertisement pointing to a OSD Task sequence with a valid boot image.  I realised that the message is a little misleading.  I deal with a number of boot images and this particular boot image specified in this advertised Operating System Task Sequence was not on the SMSPXE$ share (i.e. not on the distribution point). 

So things to look out for :

  • Make sure that the OSD task sequence boot images are on the distribution point
  • That the task sequence you are using have a valid boot image, easy to decommision a boot image without updating your OSD task sequence