Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
The Windows Software Distribution Agent (SFD Agent) might fail to install on some systems which are re-enrolled into Workspace ONE UEM. In cases where this occurs, applications distributed from the console will show as queued for devices on the Troubleshooting tab of device details but never be deployed to the systems. To identify a machine which is impacted by this issue, check the value of the Status attribute for the registry keys depending on the version of the SFD agent deployed: SFD Agent Version Registry Path21.01HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EnterpriseDesktopAppManagement\S-0-0-00-0000000000-0000000000-000000000-000\MSI\{1C11A920-7CE4-471F-A3A9-5CD9DB60783C}21.02HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EnterpriseDesktopAppManagement\S-0-0-00-0000000000-0000000000-000000000-000\MSI\{12E6A912-F946-445C-94FC-068BC8FB820A}21.05HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EnterpriseDesktopAppManagement\S-0-0-00-0000000000-0000000000-000000000-000\MSI\{3DEFFDF1-BB2C-4616-A9FF-920E986458D4} A status of 60 indicates a failed install and a status of 70 indicates a successful install.When SFD Agent fails to install, under the Event Viewer > Windows Logs > Application, you will see the following Error message:“VMware SfdAgent – Error 1904. Module C:\WINDOWS\system32\AirWatchMDM.dll failed to register. HRESULT -2147024894. Contact your support personnel."
This error can occur when a system which was previously enrolled into Workspace ONE UEM is re-enrolled after Intelligent Hub was uninstalled, the Work/School Account on Windows 10 removed, the device was deleted from the console or an Enterprise wipe command was issued for the device. It could also occur if 3rd party products such as older versions of Microsoft SCCM prior to SCCM 1710 are on an effected device and trigger un-enrollment. The error can also occur in situations where a Windows PC with many applications on it is in process of an Enterprise Wipe. Enterprise Wipe can take a long time to completely execute if many Windows applications have been distributed from the console. The SFD agent must remove all applications which were installed by UEM, and then remove itself from the system. The error will appear during a re-enrollment prior to completion of the wipe. The error will occur if registry or other residual entries remain on the system after the un-enrollment occurs and the device is re-enrolled.
The SFD agent will not be installed, preventing the ability to deliver applications from the UEM console to a newly enrolled device.
A script is available to address situations where this problem occurs. This script will be necessary until an in-product solution to address the failure to install is developed. Please open a support request referring to this KB and include the below information from an impacted device. Event Viewer > Windows Logs > Application logs Airwatch MDM registry export from Computer\HKEY_LOCAL_MACHINE\SOFTWARE\AirWatchMDM The above information is required for VMware Support and Engineering to validate if this is the same issue as mentioned in the KB and provide the script. To contact Workspace ONE Support, please view the following resource: How to access VMware Workspace ONE support