MDT and Dell BIOS updates

-
I have read a lot on how to implement a BIOS update but was unable to get any of the previous postings to work.

So I incorporated some ideas into my own solution.

I used both WMI queries and MDT applications.  The structure is set up so only the correct BIOS is applied to the correct model and only if the device requires the BIOS update.

How I got BIOS updates to work...

  1. Download any BIOS updates you need and put them into separate applications
    1. Use the -noreboot -nopause as arguments
    2. Check the Hide this application in the Deployment Wizard
  2. Add a new group, called "BIOS Updates" to the relevant Task Sequences within the State Restore group and move it above the Install Applications action.
  3. Add a sub-group to "BIOS Updates" for the model of machine you are deploying
    1. example: Latitude E7240
  4. Open the group and click the options tab create a WMI query - change the value to match the model number you are working on, this limits the scope to only those models which are applicable
    1. Select * from Win32_ComputerSystem WHERE Model like 'modelname'
    2. example: Select * from Win32_ComputerSystem WHERE Model like '%7240%'
  5. Select Install a single application and select the relevant BIOS application made earlier
  6. Open the option tab and enter the WMI query, replace xxx with the new BIOS version - this limits the BIOS version to only replace where needed.
    1. select * from WIN32_BIOS where SMBIOSBIOSVersion < "xxx"
    2. example : select * from WIN32_BIOS where SMBIOSBIOSVersion < "A12"
  7. Click apply and add a reboot computer task
  8. Set up any other model as per steps 3 to 8.
  9. enjoy.



Comments

Post a Comment

Popular posts from this blog

PXE booting, MDT and 802.1x

-
Image
Oh dear. We implemented site wide 802.1x when we moved. This has caused numerous issues which we are still tracking down and killing with fire. Again "only-when-we-needed-it" struck as we had a new starter and need to build a machine. Ah.   No PXE.  However thankfully we were able to make a bootable USB using 802.1x and get our build working again from MDT in our 802.1 environment. Here's how we did it.   Caveats:  I'm assuming you know MDT and how PXE works. We use Computer certificates as the 8021x auth method. 802.1x is working in our environment GPO is used to start the wired 802.1x service on built machines. GPO is used to configure the network profile to use 802.1x What you need Get a USB stick to take your WinPE 4GB may be enough Make sure you are running an up to date working MDT installation! Create a machine certificate which has a long expiry date, you don't want to be making USB WinPE images every month!! Export the machine
Read more

Intune installation requires a wire...or does it?

-
If you are using Intune (great!) it assumes you have a wired connection (not great) - this is more of an issue as some machine now no longer have built in ethernet ports. It is possible to connect to your wireless - albeit in a slightly awkward way.....here's how During the OOBE hit SHIFT+F10 to get a command window and type either; start ms-settings: To get the settings window or start ms-availablenetworks: To see the network fly outs. Thanks to  Using a wireless network connection with Windows Autopilot white glove – Out of Office Hours (oofhours.com)
Read more

Security Policy 1001

-
We had an annoying warning showing every 5 minutes on our Read Only Domain Controllers.  This didn't affect service but meant we were losing our logs of important events (should the have occurred) "Security policy cannot be propagated. Security Configuration Server (in services.exe) is not ready. This is probably in system reboot. Policy will be tried again in the next propagation." Source: SceCli Event: ID 101 We tracked this down to a GPO which was populating the local Administrators group. Obviously a Domain Controller has no local users or groups so this was causing the issue. Ensuring that the GPO did not apply to the Domain Controllers - yes the GPO was linked at the root! fixed the issue. It is strange that we did not see the warnings on our main Domain Controllers only on the Read Only DC's as this would have affected all DCs the same (I would have thought)
Read more