Knowledge Base: Resolving OSDeploy Network Driver Installation Failures in ManageEngine Endpoint Central

Overview

This article provides a systematic approach to diagnosing and resolving network driver installation failures during OS deployment for new computer models using ManageEngine Endpoint Central's OSDeploy feature. A common symptom is new notebooks staging without functional network connectivity, even when drivers have been added to the repository.

Understanding the Problem

When introducing a new notebook model to your environment, OS deployment may complete without installing critical drivers, such as network or touchpad drivers. This occurs even if the correct drivers have been uploaded to the Endpoint Central Driver Repository. The root cause is often an incomplete driver database within the deployment media, stemming from an insufficient repository scan.

Primary Symptoms:

• Newly staged PCs lack network connectivity.

• Additional hardware (e.g., touchpad) may not function.

• Deployment logs indicate missing driver errors.

• Remote troubleshooting is hindered due to the lack of network access.

Diagnosis: Gathering Log Files

The first step in diagnosis is to collect and review the relevant log files.

1. Distribution Server Logs

Location on the Endpoint Central Distribution Server:

• C:\Program Files (x86)\ZohoCorp\OSDDSComponent\logs

• C:\Program Files (x86)\ZohoCorp\OSDPXEComponent\PXEService\logs

2. Client-Side Patcher Logs

Location on the affected, newly deployed client machine:

• C:\Windows\PatcherLogs

Action: Compress all logs from the above paths into a single folder. Upload the archive for analysis by support if needed.

Resolution: Performing a Full Driver Repository Scan

The most common resolution for this issue is to force a Full Scan of the driver repository, followed by regenerating the deployment media. This ensures the PXE boot image contains the complete and updated driver set.

Steps to Resolve:

1. Initiate a Full Repository Scan:

   • In the Endpoint Central console, navigate to the Driver Repository.

   • Perform a Full Scan on the repository path (e.g., \\10.12.51.31\ec-driver). Do not rely on a differential or incremental scan for this step.

2. Regenerate Deployment Media:

   • After the full scan completes, create a new PXE Bootable Media.

   • Best Practice: It is recommended to delete the old/previous bootable media to avoid selection errors during future deployments.

3. Retest Deployment:

   • Use the newly created media to stage the problematic notebook model again.

   • Verify that network drivers and other hardware drivers install correctly during the OS deployment process.

Conclusion and Best Practices

Persistent network driver installation failures during OS deployment are frequently resolved by ensuring the driver repository is comprehensively scanned. A Full Scan rebuilds the internal driver database, correcting omissions that can occur with differential scans.

Proactive Maintenance:

• Conduct a Full Scan of the Driver Repository whenever adding drivers for a new hardware model.

• Always generate new deployment media after a Full Scan and before deploying to new models.

• Maintain a clean repository by removing outdated driver packs.

Further Assistance

If the issue persists after following these steps, please contact ManageEngine Support. For efficient troubleshooting, provide the following:

• The compressed log files collected as described above.

• The specific notebook model and hardware details.

• The version of Endpoint Central in use.