Client Management: OS Deployment - WinPE cannot download or upload the wim to the share set in the image configuration in the console

Knowledge Article

Article Number

000367124

Old Article Number

000128484

Article Type

Solutions to a Product Problem

Title

Client Management: OS Deployment - WinPE cannot download or upload the wim to the share set in the image configuration in the console

Summary

One of the most common errors when running OS Deployment is "Error mounting log share". This means the OSD is not able to mount a network share to the OS Deployment Manager. If the OS Deployment gets this far then the device has network access as it was able to PXE boot. There can be multiple causes.

Alt+tab followed by an ipconfig /all should help identify if it is a driver issue.

Product

BMC Client Management

Component

Client Management

Applies to

Any version of BMC Client Management which has the OS Deployment module

Problem

When WinPe tries to access the share where the wim file is located it fails with the following errors:
When WinPe tries to access the share where the wim file to be captured should be stored it fails with the following errors:

User-added image

Cause

The project probably lacks of the right Deployment driver in the assigned drivers to the project.

Solution

This is one of the most common issue the new users of the OS Deployment (OSD) module will face.

The BCM OSD module is based on Windows ADK (AIK for the versions prior to 12.5 not included). When the device pxe boots at some point of the deployment or capture it will require to have NIC, SATA and maybe Chipset drivers set as deployment drivers in the project. Depending on the version of ADK that was in place on the OSD Manager WinPe may or may not include these drivers.

If they are not already included, then one will have to add them as OS Deployment drivers section:

User-added image

It the example above a vmware image is being deployed. The vmware NIC is a VMXNET3, its drivers are not included in the WinPe from ADK 1703 so it is mandatory to add it to the Deployment Drivers of this project. More information on ADK/WinPe in this Knowledge Article/KA: Client Management: OS Deployment - Is ADK 2004 supported?

What is very important in this type of situation is to go to the manufacturer site:

- check if there are NIC or SATA dedicated WinPe drivers - if not use the regular ones.
- download the very latest version of the driver from the computer manufacturer first, then from the network card/controller manufacturer if the first ones didn't work.

One method to import drivers in the console is mentioned this KA: Client Management - How to scan drivers from a directory and create drivers tags to use in OS Deployment projects

Attachment(s):