Please note that this guide only applies to Dell systems. I tested these steps on a Dell OptiPlex 780 SFF (Small Form Factor), Dell OptiPlex 790 SFF, and Dell OptiPlex 3040 MT (Mini-Tower). All systems were running Windows 7 Professional x64 and Windows 10 Pro x64.
I cannot guarantee this guide will work with Windows Vista or Windows XP. Before we get started, you are going to need the following tools installed on your workstation:.
Oct 21, 2010 Installing Dell OMSA on CentOS. Dell OpenManage Systems Administrator is an INVALUABLE resource when managing dell systems. Specifically from the perspective of viewing any hardware problems and getting more information about your disks and any RAID controllers you have installed. Yum install srvadmin-hapi.
System Center Configuration Manager 2012 R2 Admin Console. Dell Command Configure Toolkit First, download the latest BIOS revisions for each of the models deployed throughout your organization from. Create a new folder in which you will place the downloaded revisions. For this guide, I will be saving all necessary files to the following location.
BIOS repository I have created separate folders for each model. If you download multiple revisions for one model, I suggest you come up with a naming convention so you don't have multiple separate directories to hold one revision. For this guide, I will be using the following naming convention: O780-A15 O = OptiPlex (Family), 780 = (Model), - A15 = (BIOS Revision) Next, launch the Dell Command Configure Toolkit Wizard.
Although you can configure separate packages for each model in your organization, I recommend creating a multiplatform package that will work with all models. I have never had any issues creating a multiplatform package that works with different Dell models, even those manufactured as late as 2010. With that in mind, select the Create Multiplatform Package tab and configure the package options. My configuration When you are satisfied with your configuration, export your package as a.CCTK (Client Configuration Toolkit) file using the EXPORT CONFIG button and save it to a location SCCM can access. For this guide, I will be saving my configuration to the following location: SCS-CFGMGR-MP SWSTORE BIOS Dell CCTK Configs Once you save your configuration, navigate to 'C: Program Files (x86) Dell Command Configure' and copy the contents of the folder 'X8664' to a location SCCM can access. You will be importing the directory to which you copy these files as a package in SCCM. For this guide, I will be copying these files to the following location: SCS-CFGMGR-MP SWSTORE BIOS Dell CCTK Note your configuration file and the contents from the 'X8664' folder must be accessible through the same package in SCCM.
This is because you need Dell's CCTK executable to apply your configuration. CCTK folder structure Now we are ready to create the task sequence that will push the BIOS configuration.
The toolkit will deploy this task sequence as a required advertisement and will also flash any BIOS updates needed using the revisions you downloaded earlier. Open the Configuration Manager Admin Console and navigate to the Software Library applet. Expand the Application Management node and click on the Packages applet. Create a new package using the Dell CCTK folder you just created, but do not create a program or add any requirements. Flash BIOS Dell OptiPlex 780 options Make sure to point the step to the package that contains the executable you wish to run. Repeat this process for every model to which you wish to deploy BIOS updates.
If you add a new revision, you will need to update the executable name and WMI queries as needed. It seems that newer Dell models such as the OptiPlex 3040 do not use A01, A02, etc. As their BIOS revisions but just numbers instead (1, 1.4.2, etc.). Pay close attention when entering your WMI query for the 'SMBIOSBIOSVersion' property. When you are done, add a new group called 'Apply BIOS Configuration' and add another step to Run Command Line.
Configure the step as shown below. Set BIOS password options Close the task sequence when you've finished configuring the last step.
Finally, we are going to deploy the task sequence to a device collection. Right-click on the task sequence and click Deploy.
Choose a collection to deploy the task sequence to and click Next. Choose Required as the purpose and make the advertisement available only to Configuration Manager clients. When specifying the deployment schedule, keep in mind the task sequence will force a reboot on the machine. For this reason, I have chosen to deploy the task sequence at 11:00 PM. If you run the task sequence on a new computer that has an outdated BIOS revision and does not have a BIOS password set, and you specify the /p switch for the BIOS update the update will fail because an incorrect password was specified. If you choose the option to continue on error, the BIOS will not update which defeats the purpose of the step. As for the password being stored in clear text in log files, this is not true.
Dell was smart enough to configure their utility to omit the specified password when writing log files (see the CCTK log file image). Even though the password will be stored in clear text in the task sequence step, only users with access to SCCM will be able to see the password. Hi Joe- That was actually one of my concerns when I tested the deployment process for this article. The oldest model I tested this on was a Dell OptiPlex 780 which was released in 2009.
I managed to upgrade from A02 to A16 without having to do a step-ladder upgrade process. This may be an issue with models previous to 2009, and if that is the case than those workstations will most likely be upgraded if they haven't been already- thus eliminating the problem. I cannot say if this problem affects laptops or not, but if that is the case then I would create a model-specific device collection for all the workstations with an outdated BIOS revision. I would then deploy a custom task sequence that goes through and updates the BIOS one revision after the other until the workstation has the most current revision. This can be accomplished by having each task sequence step run depending on the result of a WMI query to detect the BIOS revision. If you can think of a cleaner / more efficient way to accomplish this I encourage you to comment it below! Alex, I've followed your guide, and it works pretty well, however, I am hitting one minor issue.
I'm able to clear the bios password (if it is there, if not it skips as it should) however, the next step is to flash the bios, once that happens, the computer reboots, the bios is flashed successfully, however the task sequence doesn't actually finish because the bios update is prompting a reboot before it gets to the last step in the task sequence, which is to set the BIOS password back. Basically, SCCM thinks the task sequence has 'failed' so I go back into the catalog and just rerun it a second time, this time since the bios has already been flashed, it doesn't actually flash the BIOS, and it goes all the way through and sets the password. Is there a way around this? I initially thought that the task sequence would resume after the BIOS flash, but that has not been the case, at least not for me. I just wanted to see if anyone else has reported this issue, or if there is a way to solve it without having to run the task sequence twice. Alex, Not sure what may have changed overnight, but moments after posting my problem to this forum this morning, things seem to be working fine. The task sequence does not re-launch after the BIOS update, but it does process the 'Set Bios Password' command, and it is working properly.
I will note that I had to add a success code of 6 to each of my Flash BIOS run command line steps in order for it to succeed, I am running SCCM 1702, installed on a Windows Server 2016 box, supporting a Windows 10 Enterprise Environment, where Bitlocker is enabled. Thank you for your reply! Hi Similar to Alex I have followed the blog and clears BIOS password, Flashes the BIOS for an Optx 7020 reboots but does not continue the TS after reboot and get a failed status. When I rerun the TS manually it will complete the TS & reset the BIOS password. I have it set to run as domain admin in TS TS Is- Install HAPIx64 Driver - Clear BIOS Pwd - Flash BIOS (/r restarts device) The following does not run after reboot unless I manually run the TS again Lockdown BIOS All Systems - Set BIOS Pwd-Restart Any ideas. Hi my Purpose is to apply Password for all dell computers and disable any boot options Except hdd.
SCCM1602 Windows 10 ENT 1607 Dell OptiPlex 9020 I've followed your guide, and it not working for me, i need help SAP!! I will upload the smsts.log and photos of the TS and program i created. The only thing that is not slimier to the post is the folder 'Configs' i didn't see it at all, so i created empty one. Sorry for the poor language.
I will very appreciate all the help i can get! All the files uploaded to my google drive Thnks Elad. From what I gathered from the screen grabs you provided, it seems the TS is failing not on the actual BIOS lockdown phase of the task sequence, but the Flash BIOS step. Make sure that the package referenced in that step points to the Dell OptiPlex-9020-All Revisions package. The 80070002 error means that ConfigMgr can't find one or more of the referenced files. Also, ensure that the folder C: Temp exists on the HD of the machine you are running the task sequence on, so the application actually has a folder to write to. Great work on this!
I did need to make some tweaks though. I also was having issues with the task sequence resuming after the BIOS update restart.
I believe this was due to the PC not being able to save the TS state fast enough before the machine restarted (I have pretty new Dell's here with SSD drives). Once it restarted there were errors in the logs re: not being able to find content. My solution was to remove the /r (force restart) on the BIOS steps and add a TS 'restart computer' step at the end of all the BIOS steps. You will need to add success code '2' to all the BIOS steps as well. I also added the Task Sequence variable condition 'SMSTSLastActionRetCode' equals '2' to the restart computer step so that the PC would only restart if one of the BIOS steps actually ran.
Last note is to also make sure your PC's have a C: temp folder (or just pick a different folder, i used C: Windows CCM Logs ' as I have a few which didn't for some reason which will error out when CCTK tries to write a log file. Hope that helps some people. Hi Jim, Yes, I do realise the reason the check is failing. What I am looking for a is a way to get SCCM to compare the 'numbers' correctly. I can change the check to do a greater than check instead of a less than check, but then it will not work for 1.16.5 I was just hoping that someone may have figured out a method of doing these checks vs the new Dell revision numbers. I'm getting increasingly more frustrated, as Dell tell me I need to talk to Microsoft for a solution, while Microsoft tell me I need to talk to Dell. Sorry for delay in replying.
It has been several months, and still no proper resolution to this. I've worked with both MS and Dell, and they both say the other needs to help. The only solution that will work is to create a lengthy script file and deploy that, rather than to use a Task Sequence. As I am not a programmer or scripter, I was unable to write anything that would work. We are still using Task Sequences, and are using the (not equals) operator. This will work, unless a newer revision is installed (which we have run into a few times when we purchase new computers with updated BIOS revisions.) As mentioned previously, the BiosMinor and BiosMajor versions cannot be used, as they are sometimes identical for different BIOS versions (e.g.
1.16.4 and 1.17.5 are both major 3 minor 0) So, the only two options I can see are: Use the comparison, and make sure you keep it up to date with latest BIOS versions Create a script to do the comparison and installation and deploy it via Package instead. Hi, I have been trying to deploy Win10 on E7450 machines.
![Dell openmanage could not install the hapi driver download full Dell openmanage could not install the hapi driver download full](http://www.techbeatly.com/wp-content/uploads/2018/10/how-to-install-racadm-for-idrac-on-rhel-linux-cover.png)
In order to achieve this, I have created a sequence which involves updating the BIOS to A17. However, it errors when completing the task: 0X800700D8 '0x800700D8 = This version of%1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.'
After reading and following the steps proposed in this blog, I also have attempted to install a different BIOS version to see if that is a prerequisite of the latest BIOS version - I have tried to install A06 and A12 without any luck - same error. Hi Dario, Which point of the Task Sequence does the error occur? Does it get past the HAPI install? You can check the SMSTS.log file to see if it has any more detailed error message.
If it happens during the BIOS update, then there is also the log file that was generated as part of the installation command in the instructions above: /l=C: Temp O780A15.log – Switch to generate a log file from the executable. Lastly, there could also be some more information in the Windows Event logs (System or Application). CMTrace is great for looking through logs. This site has a few other tools that might be useful in other areas too: I'm sorry I can't be much more help than that, as I'm in the same boat as you when things go wrong with SCCM. Sifting through so many different logs, and trying to find the right ones, is frustrating ?. Yes I am checking every single log at the moment.
This is one of them. Rtm sms framework core ccmcore commandline.cpp,1019) clCommandLine.Execute( uOptions, pszWorkingDir, lpDesktop ), HRESULT=800700d8 (e: ntssccmrelease sms client osdeployment installsoftware runcommandline.cpp,565) ReleaseSource for C: SMSTaskSequence Packages MPC0011F. Reference count 1 for the source C: SMSTaskSequence Packages MPC0011F before releasing Released the resolved source C: SMSTaskSequence Packages MPC0011F cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=800700d8 (e: ntssccmrelease sms client osdeployment installsoftware main.cpp,372) CreateProcess failed.
Code(0x800700D8) Command line execution failed (800700D8) Failed to execute command line 'C: SMSTaskSequence Packages MPC0011F E7450A17.exe' /s /r'. His version of is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher. (Error: 800700D8; Source: Windows) Install Software failed to run command line, hr=0x800700d8.
![Dell openmanage could not install the hapi driver download Dell openmanage could not install the hapi driver download](http://docplayer.net/docs-images/40/14734834/images/page_13.jpg)
Hi Dario, Sorry for delay, but I've been busy with some other stuff. Not sure if I can help much with this one. Might need to hit the TechNet forums, though my experience there is they will send you to Dell, and Dell will send you back. I have run into a similar error when trying to upgrade on a BIOS that was too old, and needed another version installed first. Though, you mentioned that you already tried that.
I noticed in your command above that it does not include creating the log file. If you add /l=C: Temp E7450A17.log to the end of the command, the BIOS file itself will create a log file, which may include more information than the SCCM log file. If this doesn't help, then I'll have to leave it for others to comment, as I'm out of ideas.
I will try it again the next time I there. Is the reference to /var/log/vmware to a path within the zip file itself?
MetadataDownloadError Could not download from depot at zip: /var/log/vmware/OM-SrvAdmin-Dell-Web-8.5.0 -2372.VIB- ESX60iA00.zip?index.xml, skipping (('zip: /var/log/vmware/OM-SrvAdmin-Dell-Web-8.5.0 -2372.VIB- ESX60iA00.zip?index.xml', ', 'Error extracting index.xml from /var/log/vmware/OM-SrvAdmin-Dell-Web-8.5.0 -2372.VIB- ESX60iA00.zip: Errno 2 No such file or directory: '/var/log/vmware/OM-SrvAdmin-Dell-Web-8.5. 0-2372.VIB -ESX60iA0 0.zip') url = zip: /var/log/vmware/OM-SrvAdmin-Dell-Web-8.5. 0-2372.VIB -ESX60iA0 0.zip?inde x.xml Also, aside from being in Maintenance Mode, the DELL instructions indicate the host will need to be rebooted. Is this true?
What is the relative risk for installing this software on production server? Please look at the following example.tested to confirm, and demonstrate! The Host has internet access, confirmed by the use of wget to full down the file you are trying to install!
I executed the command you chose to use, which also fails, although I have changed to the directory the ZIP file exists! Command you used esxcli software vib install -d OM-SrvAdmin-Dell-Web-8.5.0-2372.VIB-ESX65iA00.zip Select all WRONG Correct usage.
Esxcli software vib install -d /vmfs/volumes/nfs-VMwareBackup/OM-SrvAdmin-Dell-Web-8.5.0-2372.VIB-ESX60iA00.zip Select all CORRECT Select all.