Issue: Capture Image or Deploy Image Action Fails

Problem

Deploying an Image or Capturing an Image fails during OS Provisioning.

Downloading prerequisites...
Connect to core:96-CORE3
Loading template...                                              
Action #1
Capture image
FAILED
error:[80001803H]The action failed.
Execute result:
return:-1
output:

Provisioning History Shows:

Internal Status: -2147477501

Cause

The Preferred Server listed in the template fails to resolve or authenticate. This is can be caused by a few things:

• The Preferred Server is not defined in the LDMS core.
  • If this is the case, the maptopreferredhandler.log on the client will show:

maptopreferredhandler.exe:******Mapping to: \\PreferredServer\share
maptopreferredhandler.exe:Drive letter = e
maptopreferredhandler.exe:Mode - Require Direct, no preferred server.
maptopreferredhandler.exe:Could not get credentials for preferred server.
maptopreferredhandler.exe:End of Map Drive.  Path used: - \\PreferredServer\share\.

• The Preferred Server credentials could not successfully authenticate.
  • This is often caused when the password for the Preferred Server is incorrect.
  • It may also occur if the Client cannot resolve the Preferred Server
  • The maptopreferredhandler.log on the client will show:

maptopreferredhandler.exe:******Mapping to: \\PreferredServer\share
maptopreferredhandler.exe:Drive letter = e
maptopreferredhandler.exe:Mode - Attempt preferred server.
maptopreferredhandler.exe:Could not map or unmap drive. Error code: 86

Solution / Workaround

Check the each cause to identify which one may be causing the current issue.

• Verify the Preferred Server that is used in the template is defined in the LDMS Core under Tools | Distribution | Content replication / Preferred Servers.

Note: Preferred Servers are mapped to as literal strings. This means that if a Preferred Server is added by FQDN, Maptopreferredhandler.exe (used in provisioning) will only recognize that it has credentials for that Preferred Server if it is listed in the template by FQDN. If you enter it by Short Name / Netbios, it requires that a Preferred Server be added to match. Because of this, there may be multiple Preferred Servers in the LDMS Core that point at the same machine.

• Verify the client can resolve the Preferred Server
  • From the MaptoPreferredHandler.log identify the Drive Letter and Share that is being mapped to. Use this information to manually map the share.
  • To test the credentials open a new Console window on the Client in WinPE and enter the following command:

  • Net Use e: \\PreferredServer\Share

• If it resolves the share, the window will prompt for credentials.

• If it fails to resolve the share it will give an error with information about the cause.

System error 53 has occurred.
The network path was not found.

• If the client cannot resolve the Preferred Server, it will be unable to map the drive necessary for provisioning.
  • Try using alternative names such as FQDN, Netbios, or IP in the template. If none work, correct the underlying issue preventing the machine from resolving the Preferred server.
• Verify the Credentials defined for the Preferred Server are current and have permission.
  • From the MaptoPreferredHandler.log identify the Drive Letter and Share that is being mapped to.
  • Use this information to manually map the share.
  • To test the credentials open a new Console window on the Client in WinPE.
  • Enter the following command:

  • Net Use e: \\PreferredServer\Share

Note: (use the information from maptopreferredhandler.log we gathered in your command i.e. Net Use e: \\96-Core\Images)

• Enter the same credentials that are defined for the Preferred Server within the LDMS Core when prompted
• The command window will indicate if successful.

• If it lists a failure, this is what is happening when Maptopreferredhandler.log tries to map to the share.

System error 86 has occurred.

• If manually mapping the drive fails, identify working credentials and update the Preferred Server in the LDMS Core accordingly.