JosueNegron's Accepted Solutions

Yes, please ignore the terrible naming when selecting the staging options. For Windows 10, you will always want to use the Standard option. This option will do what you want since you are also using the auto re-assign parameter in the command-line.

You can check out the Troubleshooting Windows 10: VMware Workspace ONE Operational Tutorial | VMware guide for more details on what you can do to pinpoint the issue. My first step would be to check the MDM logs in event viewer for more details: App and Service Logs>Microsoft>Windows> DeviceManagement-Enterprise-Diagnostics-Provider>Admin

You are likely running into this known issue for the first question: VMware Knowledge Base Unapproving the update will not remove or rollback the update once it has installed. You can achieve this using a script or custom settings profile but there are some requirements when using the rollback API. API Reference: Update CSP - Windows Client Management | Microsoft Docs refer to Roll Back section. You can then leverage the VMwarePolicyBuilder.com site to make a custom settings profile. For more info regarding updates, please refer to Managing Updates for Windows 10: VMware Workspace ONE Operational Tutorial | VMware.

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. Checking if BIOS Password is Set (Get-WmiObject -namespace root\dcim\sysman -class DCIM_BIOSPassword)[0].IsSet Returns True if Admin BIOS Password (AdminPwd) is set. This needs to be reset or set to NULL value. Follow step #2 below. Resetting the BIOS Password You will need to enter your current password into the $adminPwd field. $value remains null to clear the BIOS password. $adminPwd = "" $attribute = "AdminPwd" $value = "" Get-CimInstance -Namespace root\dcim\sysman -ClassName DCIM_BIOSService | Invoke-CimMethod -MethodName SetBIOSAttributes -Arguments @{AttributeName=@($attribute);AttributeValue=@($value);AuthorizationToken=$adminPwd} SetResult is {0} (Success) - If the method is completed successfully. SetResult is {1} (Failure) the possible value is out of range. it is an unsupported BIOS operation. SetResult is {2} (Authentication Failure) - If the BIOS password is incorrect. e.g. providing a blank or incorrect "adminPwd" SetResult is {4294967295} (Invalid Possible Value) - if the possible value is invalid; or read-only. Once you obtain a Success, running the above command with null $adminPwd, try to create a new BIOS profile and push. If it still fails, then continue to next steps. Debug Logs We need to increase the logging level to Debug. Open Notepad in Admin mode. Open %ProgramFiles(x86)/AirWatch/AgentUI/AWProcessCommands.exe.config then set the loggingConfiguration level to Debug. Save the file, then close. See below. Checking the Log Create a new BIOS profile, and attempt to install it. To speed things up, go into device details -> Profiles, and manually re-push the BIOS profile in the Workspace ONE UEM console. Now on the device, right-click Workspace ONE icon -> click Sync in the hidden icon menu in the taskbar. Now we will look at the logs. Open the log located at %ProgramData%\AirWatch\UnifiedAgent\AWProcessCommands.logs and scroll to the bottom of the log file and start a search going up. If you are running into the BIOS Password error like below refer to the steps above on resetting your password. For all other issues, you will need to search for isSetResultOk = False and see which attribute is failing to be set on the device. In this example, everything fails, this is not typical, you should only see a few attributes fail, then remove those from the profile. Ensure the device supports those attributes or attribute values. 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

The best way to troubleshoot pending hub (basically Hub is not installed yet) is to navigate to Registry Editor -> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EnterpriseDesktopAppManagement\S-0-0-00-0000000000-0000000000-000000000-000\MSI\ then find the folder GUID for the Hub. There should be two; one is for the software deployment agent and one is for the hub, and check the status. 70 is successful. More details can be found in the Windows 10 Troubleshooting Tutorial. The most common issue is download failed and it's normally due to the network (e.g. proxy, mismatched time causing SSL failures, etc.).