8 Posts
0
2820
Dell Powershell DellBIOSPRovider not working in WinPE
Hello,
I'm a current user switching from HP management to Dell Management and I'm currently very unhappy with the result. While it's no unicorn and rainbow at HP, at least the tools work.
Now, my current struggle is with DellBIOSProvider. At first, this tool is lacking any documentation (pretty much like most of dell tools). But beside that, there's no real installation or requirement. So while looking at the sample script (which, the one coding these seems to have basic knowledge of Powershell), I manage to create my own script that call DellBIOSProvider. Everything work on the OEM image. Yay.
Let's do that in WinPE 10 now. Oh, nothing work, lots of error about missing smbios:. Let's ty the Load-DellBiosProvider cmdlet that's include with it. No error, great, I guess no message mean everythings good? Try again, no go, same errors.
While looking on the internet, I finally found that it require either HAPI or OMCI. 2 Things that again, I fail to find any up to date information about it. HAPI, I find older Dell Command Configure information that send me to installation path of DCC in the x86_64 folder looking for HAPIinstall.bat file. Well, file doesn't exist and nothing short of near that. Ah yeah, it's DCC 4.2.1.568, you know, the one that doesn't work out of the box because it failed to installed required dependencies while not listing these on the website or the "installation instruction"?
So, back to the root folder of DCC, there'S a installhapi.bat file. Launch that, file not found. Look at the script, it's trying to launch %0%\..\..\x86_64\hapiinstall.bat. Clearly, someone did copy paste, tried nothing.
Ok, go back to x86_64 folder. Bunch of bat file for WinPE offline install, 3 dll and cctk.exe. Ok, let's try the offline install. Check the little doc, it want to create it from pe scratch. Install ADK, launch, errors.... Ok, I'll do it myself. Looking at the script, the only thing it does is copy the content of x86_64 to mount\command configure\x86_64 and add wmi in the startup script. This won't fix my issue.
So, does anyone have a 2019 ways to get DellBIOSProvider to work so I can configure my bios password and bios configuration?
Thank you
parcstm
8 Posts
0
November 15th, 2019 04:00
Well, I found out this link where it says VC++ 2010 and 2015 is required
https://topics-cdn.dell.com/pdf/command-powershell-provider-v22_users-guide_en-us.pdf
But then, it's talking about msvcr140.dll which is not in the redist anymore because of new naming and module merging by microsoft.
This guy here tell us to put other files:
https://www.ladewig.com/dell-powershell-provider-2-0-requires-visual-c-2015/
I'm gonna try with that. Glad the only doc I could found on Dell Website, regarding latest version, isn'T up to date...
speedstep
9 Legend
9 Legend
•
47K Posts
0
November 17th, 2019 05:00
There is support and documentation for all of this.
The support however is not free.
You can even get a contract with onsite dell support engineer to help you.
https://topics-cdn.dell.com/pdf/command-powershell-provider-v22_users-guide_en-us.pdf
By default Windows PowerShell has its ExecutionPolicy set to Restricted. To run the Dell Command | PowerShell Provider cmdlets and functions, ExecutionPolicy must be changed to RemoteSigned at a minimum. To apply the ExecutionPolicy, run Windows PowerShell with Administrator privileges, and run the following command within the PowerShell console: Set-ExecutionPolicy RemoteSigned -force
DOT NET 2.0 3.5 and Visual C++ is going to be required
https://www.microsoft.com/en-us/download/details.aspx?id=8328
https://www.microsoft.com/en-US/download/details.aspx?id=13523
Microsoft Visual C++ redistributable 2010, 2015 Both 2010 and 2015 must be available
https://www.microsoft.com/en-us/download/details.aspx?id=22
The Visual C++ Redistributable Packages install run-time components of Visual C++ libraries. These components are required to run C++ applications that are developed using Visual Studio 2015 and link dynamically to Visual C++ libraries.
https://www.microsoft.com/en-us/download/details.aspx?id=48145
parcstm
8 Posts
0
November 20th, 2019 05:00
Hello,
Your installation package should contain all the requirements to use, not needing to install other package from somewhere else, that's the basis of software installation.
As for the C++, you can't install in WinPE, so you could simply include the required DLL, like I stated in my other reply, in the package, thus providing a working package out of the box.
My other problem is the fact that the DellBiosProvider doesn't allow access to all configuration. Some are read only, other return cannot be change with dellbiosprovider. I'm used to HP Bios where I change everything through WMI using powershell, it's a breeze and work perfectly. Here, there's some value that when queried, it says "hey, that's the value I accept" and when you pass this value, it reject it.