Symptoms

Affected Products: Dell Command | Integration Suite Affected Platforms: LatitudePrecision Mobile Workstations Affected Operating Systems: Windows 10 1809 or later Are Windows 10 AMT client computers running DCIS having the vPro-AMT Discover Client and Unconfigure Client tasks fail? Dell's Intel Active Management Technology (AMT) client computers can encounter a failure with the error code of 0x00000020 (32). This happens when the DCIS 5.1.0 or earlier deploys the vPro-AMT Discover Client task sequence or the vPro-AMT Unconfigure Client task sequence. This is using the System Center Configuration Manager (SCCM), to your device collection that contains AMT clients that are running Windows 10. (With the build version 1809 or later.) Symptoms for this issue include: The task sequence fails on a client computer showing an error code of 0x00000020 (32). Where the task sequence is run on an AMT client computer running Windows 10 build version 1809 or newer. A window is displayed like the following example of the vPro-AMT Discover Client task sequence failing: When the task sequence fails, the last line of the discovery log recorded an exit code of 32. (The log file resides under the C:\Temp\amtlog folder on the client computer. For the vPro-AMT Discover Client task sequence, the discover log file is named discover.log. For the vPro-AMT Unconfigure Client task sequence, the log file is named unconfigure_discovery.log.)After the task sequence fails, the task sequence application that was run shows a Status of Failed. It displays a detailed code of 0x4005 (16389) in the Software Center application on the client computer. It looks like the following example of the vPro-AMT Discover Client task sequence in the Software Center application. After the task sequence fails, the administrator sees a Status Type of Error in the deployments folder in the SCCM console. Where this is an example of the vPro-AMT Discover Client task sequence:

Cause

Not Applicable

Resolution

Note: You need administrator privileges and access for the following instructions. You can resolve this issue by following the steps below: Launch System Center Configuration Manager (SCCM).Browse the vPro-AMT Discover Client task sequence: Click Software Library in the lower left pane.Under Overview, expand the Operating Systems folderExpand the Task Sequences folderSelect the Dell vPro-AMT Sequences folder. You should see a list of vPro-AMT task sequences in the main content window, like the following: Edit the vPro-AMT Discover Client task sequence: Right-click the vPro-AMT Discover Client task sequence and select Edit.An edit window appearsSelect the Run ACUConfig to perform a system discovery step in the left pane of the window.Select the Options tab in the right-hand pane.In the Success codes edit box, you should see 0 and 3010.Edit the Success codes list and add 32 at the end and select OK to save the change. Note: If you see multiple versions of the vPro-AMT Discover Client task sequence. Then select the vPro-AMT Discover Client task sequence with the highest version that you can see. (Versions 2 or higher has a v2 or higher indicator at the end of the name of the task sequence. Such as vPro-AMT Discover Client v2.) The window should look like the following, where 32 has now been added as a success code: Redeploy the updated vPro-AMT Discover Client task sequence to your device collection. The vPro-AMT Discover Client task sequence should now work successfully. The discover.log file on client computers may still show a warning exit code of 32. However, the warning is now acceptable, and the task sequence does not fail because of the warning.Repeat steps 2 through 4 to go to and edit the vPro-AMT Unconfigure Client task sequence as well. Note: You notice that the vPro-AMT Unconfigure Client task sequences have a different set of task sequence steps than the vPro-AMT Discover Client task sequence. However, it does still have its own version of Run ACUConfig to perform a system discovery, so the steps remain the same for both. Redeploy the updated vPro-AMT Unconfigure Client task sequence to your device collection. The vPro-AMT Unconfigure Client task sequence should now work successfully. The unconfigure_discover.log file on client computers may still show a warning exit code of 32. However, the warning is now acceptable, and the task sequence does not fail because of the warning.

Support Cases