Ghost Solution Suite

Hi, 

I'm having an issues trying to install an automation folder on a Windows 10 system.

I get the message "No appropriate bootworks NIC found.  Use boot Disk Creator to Create a Bootworks install package."

The same system with windows 7 works fine.  It detects the NIC properly.

Server: GSS Ver 3.2 (Build 1325)  R1.

Anyone run into the same problem?

Ed

Ed,

Please see the automation install kb below, this should help you get automation folders installed correctly.

https://support.symantec.com/en_US/article.HOWTO124186.html

Hi Brycen,

Perhaps I'm missing something from that article. 

I have a working automation folder for my Windows 7 systems.  Everything is fine.

The same hardware except the OS is windows 10, it fails to install the automation folder and I get that message instantly.

For the Windows 7 system the under Network adapter it lists the NIC and proper inforamtion.

For the Windows 10 system under Network adapter it just lists "1)  "

I've attached the screen shots for you.

Ed

Just discovered that it is also occuring with new Windows 7 systems. 

Same hardware they were not in the console before the R1 service patch.

Ed

Ed,

Looks like the inventory is not present. Right click on the non-working machine in the console and do an advanced->Get inventory. After a few minutes you should see the values populate so that i.p. address, etc.. is shown similar to the other working client.

I have already tried this before posting to the form.  I wish it was that simple!

It does not populate the NIC information.

When requesting an inventory update from the console, the status on the client indicates that the update is sent back to the console.

Ed

Ed,

Try removing the machine from the console (right click delete) and then see if it comes back in and pulls the inventory correctly.

There is no reason specific to Windows 10 that ghost would be having issues pulling inventory. I have seen similar behavior when Ghost was corrupted and also when hardware is malfunctioning on the client machine.

Hi Brycen,

From what I can tell from my testing it appears that the issues happens when starting from a system that has legacy disabled.

NOTE: The widnows 10 I'm dealing with is in Audit mode.

I can and have duplicated the results.

1) Started with a system and disabled Legacy so could only boot with UEFI.

2) Installed Windows 10, in Audit mode.

3) Installed GSS client, the client is able to communicate with the console however the NIC is never correctly identified.

4) If you try to install the automation partition or run a script the first thing the client does is "Sending a wakeup packet".  Then the system will restart, once it's back to the desktop it get the command from the server and then restarts again... until the job is manually deleted.

If Legacy is Enabled and UEFI boot is not, I can install windows 10 and the GSS client and it reacts normally can install the automation folder and run scripts.

Someone must have run across this before, or perhaps I'm missing something simple.

Ed

Hi Brycen,
 

Deleteing the records of the systems from the console did nothing.

I am able to repeat the procedure and perhaps provide a little more info. 

1) Legecy mode is disabled. (only allowing UEFI boot)

2) Windows 10 installed and put into Audit mode.

3) GSS3.1 client is installed.

The client can communicate to the server however does not give full information concerning the NIC. ie type.

When tring to install the automation folder the message .  "No appropriate Bootworks NIC found..."

1) If Legacy is enabled and UEFI boot is disabled.

2) Windows 10 installed in Audit mode.

3) GSS3.1 client is installed.

The client can communicate and all inforamtion is displayed in the console.

No issues installing the automation folder or running any scripts.

Someone must have hit this issue before or I'm missing something simple.

Ed

Ed,

I have tested your scenarios and did not run into any issues installing the automation folders to new windows 7 or 10 machines. I suspect this may be hardware related / environmental.

I suggest you call in and create a case for this issue, so that the support team can help you resolve the issue experienced.