Unsolved
10 Posts
0
470
Update at Next Reboot (Firmware)
I updated from the previous to the latest version of dell open manage and the update on next reboot seems to have vanished. i only get the option to schedule an update and update (risk of the server being force updated/ rebooted). Does anyone else have this issue with the old feature now gone?
Muese
16 Posts
0
May 15th, 2023 04:00
I still see it on Version 3.10.0 (Build 169)
A13xx
10 Posts
0
May 15th, 2023 05:00
jump to Version 3.10.1 (Build 51) and it vanishes
This is the same on update not needing reboot and also on an update needing a reboot. Option has vanished in chrome.
So if i roll back to previous version of OME the option comes back with a older version.
If i then go back to the latest version it still does not appear (latest chrome), if i switch from chrome to Opera it appears back. I have no idea why the latest version of chrome does not display this option on latest OME but does on the previous version.
A13xx
10 Posts
0
May 15th, 2023 06:00
this happens on any device type, chrome is
Version 113.0.5672.93 (Official Build) (64-bit)
It must be something up with my machine.
If i run chrome in incognito mode it works, and hte next reboot appears.
if i go back to non incognito with no extensions loaded it does not appear.
Previous version of OME and it appears with/ without extensions.
A very strange one but i do have a workaround.
DELL-Chris H
Moderator
Moderator
•
8.9K Posts
0
May 15th, 2023 06:00
A13xx,
From what I am seeing it's still there for me in 3.10.1, so I am not sure the cause. What we would need is more information on the device type and baseline, that way we can see if we can reproduce the issue on our side.
Let me know.
Muese
16 Posts
0
May 30th, 2023 05:00
Could be something with the browser cache?
Does it go away if you clean your browser cache or fully reload the web page with + ?
And it is also worth to check the Edge browser. The OME web site looks different in Edge.
Origin3k
4 Operator
4 Operator
•
1.9K Posts
0
May 30th, 2023 06:00
Maybe a "Layer8" Problem.....
with the current 3.10.1(Build 51) there is the following behaviour
Test it when selecting only one FW Package and not a bunch.
Regards,
Joerg