The latest 1.9.0 Bios still has the issue. I started to investigate how to edit the DMI/SMBIOS table. I found a tool from American Megatrends (Bios on T30 is American Megatrends, or AMI for short), it is called DMIEDIT. When I open DMIEdit I can see the family name is set to HEX 90 1C. Assuming these are hex for ascii characters, this means 90 does not exist and 1C is for a file separator, probably the reason for the issue. Running DMIEDIT in the GUI you can edit the field, deleting the 2 characters and replacing it with a space (HEX 20) and pressing "update all" fixes the issue. This only works until you reboot. I created a startup task in windows to run the command line version on DMIEDIT to edit the field on every boot. Something like DMIEDIT.exe /SF " " works.
Kind of a hack but Dell has not fixed the issue in some time, not sure they ever will.
Apologies for missing out your post. I'll probably work with you here, so we can have the public chip in with their experience if they have the same issue as you do. I'll try my best to help out.
Mentioning about the previous BIOS version that worked out for you, could you recall which version was it? I'm not good in WSUS, but could you let me know if there is any error messages that pops out in the logs? What OS are you running on the T30?
The output of System Information below your post, where did you obtain that?
I have the same issue, Dell support has not been helpful. The output I use is from dmidecode for Windows, also in the OS registry the family is blank. I am running Windows Server 2019. On other model servers, not T30's, the family name is set to PowerEdge. I have tried to update it in the registry and it doesn't work and is cleared on each reboot. From my research it has to be fixed in the bios file. Some google research points to the dmi info needing to be complete and readable by the OS.
Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: PowerEdge T30 Version: Not Specified Serial Number: xxxxx UUID: xxxxxx Wake-up Type: Power Switch SKU Number: 07C5 Family: ..
There are no errors it just never sends the info over to wsus because Microsoft requires the family field to have info in it. The devs that wrote the bios at Dell have left the field blank I assume
Bios 1.7.0 released and still the same issue. Any chance this will get fixed? Can it be escalated someway? Dell support in chat and phone doesn't seem to care or open tickets about it since the system in functional.
But DMIEDIT doesn't work for us. I can see the value, but DMI update fails or utility crashes, depends on version. We've tried DMITEDIT v 5.13 and 5.20.0042 (and plenty other tools) from Windows, WinPE and DOS with no success.
Does anyone have working version of DMIEDIT with BIOS 1.10.1 or any other solution?
I don't understant how DELL has not solved it for so long and every new BIOS has the same issue.
We looked at this one when it was released with msutton, and if memory serves everyone we open past 1.9.0 it was all encrypted now. So adding unencrypted strings in with dmiedit just no longer works
We noticed because it didn't look the same as before. We couldn't figure out a way around it
msutton51
1 Rookie
•
10 Posts
0
May 27th, 2022 21:00
The latest 1.9.0 Bios still has the issue. I started to investigate how to edit the DMI/SMBIOS table. I found a tool from American Megatrends (Bios on T30 is American Megatrends, or AMI for short), it is called DMIEDIT. When I open DMIEdit I can see the family name is set to HEX 90 1C. Assuming these are hex for ascii characters, this means 90 does not exist and 1C is for a file separator, probably the reason for the issue. Running DMIEDIT in the GUI you can edit the field, deleting the 2 characters and replacing it with a space (HEX 20) and pressing "update all" fixes the issue. This only works until you reboot. I created a startup task in windows to run the command line version on DMIEDIT to edit the field on every boot. Something like DMIEDIT.exe /SF " " works.
Kind of a hack but Dell has not fixed the issue in some time, not sure they ever will.
jturnergstop
1 Rookie
•
7 Posts
0
July 19th, 2021 10:00
Anyone have idea on this?
DELL-Joey C
Moderator
•
4.1K Posts
0
July 21st, 2021 20:00
Hi,
Apologies for missing out your post. I'll probably work with you here, so we can have the public chip in with their experience if they have the same issue as you do. I'll try my best to help out.
Mentioning about the previous BIOS version that worked out for you, could you recall which version was it? I'm not good in WSUS, but could you let me know if there is any error messages that pops out in the logs? What OS are you running on the T30?
The output of System Information below your post, where did you obtain that?
msutton51
1 Rookie
•
10 Posts
0
July 29th, 2021 09:00
I forget which bios version last worked 1.2? or 1.3.1?
msutton51
1 Rookie
•
10 Posts
0
July 29th, 2021 09:00
I have the same issue, Dell support has not been helpful. The output I use is from dmidecode for Windows, also in the OS registry the family is blank. I am running Windows Server 2019. On other model servers, not T30's, the family name is set to PowerEdge. I have tried to update it in the registry and it doesn't work and is cleared on each reboot. From my research it has to be fixed in the bios file. Some google research points to the dmi info needing to be complete and readable by the OS.
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: PowerEdge T30
Version: Not Specified
Serial Number: xxxxx
UUID: xxxxxx
Wake-up Type: Power Switch
SKU Number: 07C5
Family: ..
msutton51
1 Rookie
•
10 Posts
0
July 29th, 2021 09:00
Using Powershell to get system family.
Get-WmiObject Win32_ComputerSystem | Select-Object -ExpandProperty SystemFamily
Returns:
jturnergstop
1 Rookie
•
7 Posts
0
July 29th, 2021 10:00
I think the last good working was 1.3. I got it the same As the other poster on the thread
jturnergstop
1 Rookie
•
7 Posts
0
July 29th, 2021 10:00
There are no errors it just never sends the info over to wsus because Microsoft requires the family field to have info in it. The devs that wrote the bios at Dell have left the field blank I assume
msutton51
1 Rookie
•
10 Posts
0
November 19th, 2021 08:00
Bios 1.7.0 released and still the same issue. Any chance this will get fixed? Can it be escalated someway? Dell support in chat and phone doesn't seem to care or open tickets about it since the system in functional.
DELL-Charles R
Moderator
•
4.7K Posts
0
November 19th, 2021 10:00
Hello msutton51,
I have put in a request to my systems management engineer to propagate up to development team.
msutton51
1 Rookie
•
10 Posts
0
March 7th, 2022 23:00
Latest 1.8.1 has same issue
DELL-Joey C
Moderator
•
4.1K Posts
0
March 8th, 2022 00:00
Hi @msutton51,
I tried looking back at the old case that you had with me, the engineering mentioned about feature request to be investigated.
Please send me a PM of your server service tag, I'll try to check with engineering what can be assisted.
Jiri P
1 Rookie
•
3 Posts
0
March 19th, 2023 23:00
Hello, we have the same issue with BIOS 1.10.1.
But DMIEDIT doesn't work for us. I can see the value, but DMI update fails or utility crashes, depends on version. We've tried DMITEDIT v 5.13 and 5.20.0042 (and plenty other tools) from Windows, WinPE and DOS with no success.
Does anyone have working version of DMIEDIT with BIOS 1.10.1 or any other solution?
I don't understant how DELL has not solved it for so long and every new BIOS has the same issue.
jturnergstop
1 Rookie
•
7 Posts
0
March 21st, 2023 03:00
Jiri,
We looked at this one when it was released with msutton, and if memory serves everyone we open past 1.9.0 it was all encrypted now. So adding unencrypted strings in with dmiedit just no longer works
We noticed because it didn't look the same as before. We couldn't figure out a way around it
Jiri P
1 Rookie
•
3 Posts
0
May 14th, 2023 23:00
The same problem with recently released BIOS 1.11.0.
DELL is ignoring this problem for so long, windows update still broken with no workaround. DELL support is terrible, no more DELL servers in future...