Unsolved

2 Intern

 • 

143 Posts

1058

November 29th, 2021 09:00

Driver updates fail

I'm finding that any time a driver update involves the network (e.g. NIC, Chipset, etc.), the update fails. Technically, they always hang at 50% and never proceed.

I assume that the issue is once the ethernet driver update occurs, connectivity is lost and OMEnt can't and/or doesn't know how to recover.

Are there any workarounds or options to get NIC driver updates to complete successfully?

2 Intern

 • 

143 Posts

November 29th, 2021 12:00

Just some additional info. Chipset update task is still at 50% after 1.5 hours. I can see in the device's page in OMEnt that one of the NIC ports went down, then came back up.

Task details are stuck with the following display:

Task initiated for updates via OS
===========================
Getting update status from the target machine...
DSU response: Getting System Inventory
DSU response: Getting System Inventory
 
This hasn't changed since a few minutes after the update started.

4 Operator

 • 

2.9K Posts

November 29th, 2021 14:00

Heya Justin,

 

I'm working on redeploying an OMEnt environment, so I can't test this myself immediately, but it is something I'm working on. If I were to hazard a guess, it may be something inventory related. In the meantime, you might reach out to phone support, if this is pressing for you.

 

EDIT: I just completed some testing and was not able to replicate this behavior. I would have to recommend contacting phone support. Once the progress bar hits 50%, the drivers have been downloaded to OMEnt and are trying to be pushed to the host. So my assumption based on what we're seeing in behavior is that the problem would be with the appliance's ability to push them to the target.

2 Intern

 • 

143 Posts

December 2nd, 2021 11:00

Thanks for testing. The driver(s) actually get installed successfully. The problem seems to be that in the process of updating the NIC driver, connectivity is lost (as expected), but OMEnt can pick up the process again once connectivity is restored.

I've replicated this on every system I have the requires NIC driver updates. Process starts, hangs indefinitely at 50%. Cancel the task after several hours, refresh the inventory on the system and it shows the updated driver. So the operation is completing successfully, it's just that OMEnt task apparently can't determine that fact once connectivity is lost during the task.

 

2 Intern

 • 

143 Posts

December 6th, 2021 08:00

I might also add that in all instances these servers have teamed NIC's, all using Microsoft's native Teaming function.

2 Intern

 • 

143 Posts

March 24th, 2022 09:00

I'm still experiencing this issue whenever trying to deploy NIC drivers.

Wondering if anyone else has encountered this and/or has a fix?

Moderator

 • 

4K Posts

March 25th, 2022 03:00

Hello,

did you tried to contact phone support as Dylan suggested? We cannot replicate this behavior Otherwise let's see if other customer already had this issue.

Thanks

Marco

No Events found!

Top