@UWPVIOLATOR it would appear we have similar issues. Our Dell Precisions are doing something similar “Precision T3610 Invalid entry length (16). Fixed up to 11.” This is breaking our postdownload driver scripts as well. If you do a debug task on one of the machines and run dmidecode -t 1 you should see the invalid portion at the bottom. I can confirm on a T3610 that dmidecode 3.0-3 fixes the issue, it appears that fog is using version 3.0 (cannot confirm this though).
J
Best posts made by Jason Shoemake
-
RE: Invalid entry length (0). DMI table is broken! Stop.posted in FOG Problems
-
RE: Invalid entry length (0). DMI table is broken! Stop.posted in FOG Problems
@george1421 sorry if I had a typo somewhere, but 3.0-2 does not work. I have confirmed that anything newer than that does indeed work. Using 3.1-1 and your fix everything is working across the board now on our server. Thanks a lot, hopefully this will be helpful for @UWPVIOLATOR as well.
-
RE: LDAP Plugin - ID Must Be Set To Edit Errorposted in FOG Problems
@noelpd @george1421 not sure if this helps, but we had a similar issue with the location plugin and the fix was in this thread from Tom. This also solved an issue with the Wol Broadcast… Needed to remove and add the plugins back after running the fix…
https://forums.fogproject.org/topic/10364/issues-after-upgrading-from-1-4-3-to-1-4-4