I have followed the Dell Command Suite Integration tutorial at Integrating with Dell Client Command Suite: VMware Workspace ONE Operational Tutorial | VMware for Dell Command | Monitor, since I'm interested pushing BIOS Profile to a Dell system.
I have succesfuly deployed Dell Command | Monitor as a Native app, both Auto and on demand. DCM installs well on the systems. I have configured a BIOS profile and assigned it to a group. But whenever UEM tried to install the BIOS profile, it fails.
I have checked, logs, event viewer, tried differente versions of Dell Command Monitor, to no avail. It looks liked somehow it gets to integrate as it shows the BIOS option in the device details, but still fails to install the profile.
Any advice will be appreciated.
Mario_Juarez and rwamps,
After doing some testing and validation with Mario_Juarez and our R&D team, it turned out that the device in question (Latitude E5401) did not support the Wake-on-LAN "BIOS Attribute" setting of "LAN or WLAN" was not supported by the device, therefore the profile failed to install. Feedback on seeding the latest version of the Dell Command | Monitor client and improving the return of why the profile failed to install back to the console has been passed along to R&D.
rwamps - let me provide a few tips to get this working for you as well. Ensure that you currently do not have a BIOS password set, if so, clear the password/set it to blank. Ensure the device supports all attempted configurations that are set in the BIOS profile. If you are unsure, I will tell you how to verbose the logs to see what is failing.
$adminPwd = ""
$attribute = "AdminPwd"
$value = ""
Get-CimInstance -Namespace root\dcim\sysman -ClassName DCIM_BIOSService | Invoke-CimMethod -MethodName SetBIOSAttributes -Arguments @{AttributeName=@($attribute);AttributeValue=@($value);AuthorizationToken=$adminPwd}
I will be updating the Integrating with Dell Client Command Suite: VMware Workspace ONE Operational Tutorial | VMware on Tech Zone soon with some of this information and added warnings to ensure System and BIOS attributes are supported on the managed Dell devices.
Respectfully,
Josue
Mario_Juarez,
I authored the integration tutorial you referenced. I will be implementing a few updates. One update is that Dell Command | Monitor is now seeded in the console, so basically once the profile is pushed Dell Command | Monitor will be installed, so it's not necessary to publish that app. I believe you are running into a newly discovered issue which occurs when Dell Command | Monitor is removed after the profile comes down, then re-installed. Can you un-enroll your device (make sure to uninstall DCM), unassign the DCM app, then re-enroll the device and push the BIOS profile to see if it successfully deploys. Let me know what happens. I also send you a private message.
Thanks,
Josue
I am having the same/similar issue. Dell Command | Monitor installs, but the profile doesn't install successfully. In the client logs I get this error:
Error AW.Win32.AWCommandBusiness.CommandHandlers.BiosPasswordResetCommandHandler.ProcessCommand_$_ UnSupported Command. Command Type : ResetBiosPassword Method: AW.Win32.AWCommandBusiness.CommandHandlers.BiosPasswordResetCommandHandler.ProcessCommand_$_;
Also, in the console, under the troubleshooting tab, it is showing a "reset bios password" command that fails, which doesn't make sense to me.
Hi rwamps, i reviewed this issue with Josue and it seems to be a bug within Dell Command | Monitor integration with WS ONE. We tried some of Jouse's recommendations to no avail.
He sent the issue to the Dev team and I'm waiting for feedback.
In the meantine, you don't need to upload Dell Command | Monitor anymore, as it is seeded in the console and deployed automatically when a Dell BIOS Profile is assigned.
Yeah, I saw his comment about Monitor installing automatically now, which is great, although I did notice that it's still installing a previous version (10.0) instead of the new version 10.2. Not sure if that will make any difference. Thanks for the additional info!
Yes, that is another To-do, upgrade the seeded version to 10.2. Also they are considering seeding Dell BIOS Verification to the console, probably will see it in a future console version.
Mario_Juarez and rwamps,
After doing some testing and validation with Mario_Juarez and our R&D team, it turned out that the device in question (Latitude E5401) did not support the Wake-on-LAN "BIOS Attribute" setting of "LAN or WLAN" was not supported by the device, therefore the profile failed to install. Feedback on seeding the latest version of the Dell Command | Monitor client and improving the return of why the profile failed to install back to the console has been passed along to R&D.
rwamps - let me provide a few tips to get this working for you as well. Ensure that you currently do not have a BIOS password set, if so, clear the password/set it to blank. Ensure the device supports all attempted configurations that are set in the BIOS profile. If you are unsure, I will tell you how to verbose the logs to see what is failing.
$adminPwd = ""
$attribute = "AdminPwd"
$value = ""
Get-CimInstance -Namespace root\dcim\sysman -ClassName DCIM_BIOSService | Invoke-CimMethod -MethodName SetBIOSAttributes -Arguments @{AttributeName=@($attribute);AttributeValue=@($value);AuthorizationToken=$adminPwd}
I will be updating the Integrating with Dell Client Command Suite: VMware Workspace ONE Operational Tutorial | VMware on Tech Zone soon with some of this information and added warnings to ensure System and BIOS attributes are supported on the managed Dell devices.
Respectfully,
Josue
I just wanted to say thanks for the feedback, I just released a blog regarding tips on using Dell Command | Update 3.1 and Dell Command | Monitor here: Dell Command | Update 3.1 Tips and Tricks for Workspace ONE UEM Integration | VMware