Install Automation Folder Fails with error "No appropriate BootWorks NIC found. Use Boot Disk Creator to create a BootWorks install package".
search cancel

Install Automation Folder Fails with error "No appropriate BootWorks NIC found. Use Boot Disk Creator to create a BootWorks install package".

book

Article ID: 226566

calendar_today

Updated On:

Products

Ghost Solution Suite

Issue/Introduction

Boot package is created but when installing the Automation Folder,  it shows the following error: "No appropriate BootWorks NIC found.  Use Boot Disk Creator to create a BootWorks install package".

 

 

 

Environment

Ghost Solution 

GSS 3.x

Cause

Mostly the reason is because either permissions on the temp folder or the temp folder is full.

Resolution

Option 1:

  • If the Symantec Standard tools is not installed, please  go into the DSSetup folder and run the msi installer.
  • Then import the ADK through Symantec > bootwiz on the Start menu.
    • Tools > Install Pre-Boot Operating System
  • Copy and replace the winpe10/11 folder to the GSS server under the bootwiz folder
    • From: C:\Program Files (x86)\Symantec\Ghost\bootwiz\Platforms\Winpe10 (or 11)
    • To: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\Bootwiz\platforms\Winpe10
  • Then build a brand new Preboot environment.

Option 2:

It's also possible to push the Automation Partition install using a Software Delivery task, instead of the default Automation Installer task.

To do create a Software Delivery Task, use the correct file under C:\Program Files (x86)\Altiris\eXpress\Deployment Server\BWPkgs\<WinPEVersion>\x64

 

Option 3:

If it doesn't help, you can check the network adapter driver:

  • Go onto that machine you are trying to deploy an image to, type in msinfo32 and check the Network Adapter
  • Use the following link to find the required Driver:
    • https://knowledge.broadcom.com/external/article?articleId=178788
  • After finding the driver you can add it to the WinPE
    • https://knowledge.broadcom.com/external/article?articleId=178832
  • Then recreate the Automation Environment Preboot Environment, and roll it to computers.

Attachments