For a project we did update & configure the BIOS on Dell systems within WinPE (boot image) just before applying the OS. This was choosing during the migrating of XP to Win7. In this way we were sure every system has the same harddisk setting configured SATA/AHCI ect. Before applying the OS. We did used the Dell CCTK tool for this…
Think we had one or two failures, but there where luckily successfully by using a manual upgrade. Regards, David van Beek KPN Consulting From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, August 19, 2014 7:58 PM To: [email protected] Subject: Re: [MDT-OSD] Is BIOS updating through SCCM or MDT a fairly safe process now ? I've had success in applying BIOS updates on HP and Dell systems with SCCM. It can be a fairly straight forward process and found I didn't need to worry about bricking a bunch of systems. I can count on one hand the amount of systems that encountered issues in my environment from a BIOS update. For HP I've used System Software Manager (SSM) which is available for free from HP. It helped for updating HP devices in my environment and can also be used to update device drivers as well. For Dell I've used their Client Configuration Utility to create the payload and update the BIOS. For Dell systems, the payload file gets deleted after execution so you need to download the payload to the local cache. Thanks, Chris From: Bain.John <[email protected] <mailto:[email protected]> > To: "[email protected] <mailto:[email protected]> " <[email protected] <mailto:[email protected]> > Date: 19/08/2014 02:28 PM Subject: [MDT-OSD] Is BIOS updating through SCCM or MDT a fairly safe process now ? Sent by: [email protected] <mailto:[email protected]> _____ I remember back in the day applying BIOS updates was some sort of dark art. Where you would only think of doing it if you absolutely had too. So what I am really asking is, are people deploying BIOS updates through task sequences in MDT and SCCM and is it a safe process now ? Anyone brick a bunch of computers through a bad package ? John ----------------------------------------------------------------------- This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you. La présente communication, y compris toute pièce qui y a été jointe, est destinée uniquement à la personne ou à l’entité à laquelle elle a été adressée, et contient des renseignements à caractère confidentiel et personnel. Toute diffusion ou reproduction non autorisée ou toute intervention entreprise relativement à son contenu est strictement interdite. Si vous avez reçu ce message par erreur, veuillez nous le signaler immédiatement afin que nous puissions effectuer la correction à nos dossiers. Veuillez par la suite supprimer ou détruire le contenu de la transmission originale ainsi que toute réponse ultérieure. Merci. -----------------------------------------------------------------------
