Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Changing the source of the serial number to the Type1 BIOS information causing issues within an OEM #111

Closed
1 task done
Flickdm opened this issue Jun 2, 2023 · 1 comment
Assignees
Labels
state:needs-triage Needs to triaged to determine next steps type:bug Something isn't working urgency:medium Important with a moderate impact

Comments

@Flickdm
Copy link
Member

Flickdm commented Jun 2, 2023

Is there an existing issue for this?

  • I have searched existing issues

Current Behavior

Description

The DfciPkg\UnitTests\DfciTest testcases all run a command on the device under test to obtain the device manufacturer, product name, and serial number and build packets with this identifying information. It was not clear at the time the tests were made which serial number to use, as all of the devices being tested had the same serial number for the Type1 and Type3 SMBIOS Serial number. That is, until a recent OEM had a laptop with different serial numbers for the Type1 and Type3 tables.

A (recent change was made to test that OEMS are using Type 01 instead of Type 3.

Expected Behavior

The test cases should use the Type3 serial number.

Steps To Reproduce

Run the Dfci_IntuneEnroll testcase with a system that has

Different serial numbers for the Type1 and Type3 BIOS tables
Has a properly fixed DfciDeviceIdSupportLib platform library that sets the DeviceId to the Type3 serial number
Fixes the Robot script to obtain the Type3 serial number for building the packets

Build Environment

- OS(s):
- Tool Chain(s):
- Targets Impacted:

Version Information

3.0.0

Urgency

Medium

Are you going to fix this?

I will fix it

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

@Flickdm Flickdm added state:needs-triage Needs to triaged to determine next steps type:bug Something isn't working labels Jun 2, 2023
@github-actions github-actions bot added the urgency:medium Important with a moderate impact label Jun 2, 2023
@Flickdm Flickdm self-assigned this Jun 2, 2023
@Flickdm
Copy link
Member Author

Flickdm commented Jun 6, 2023

Type 01 is by design. This is what Intune expects - not Type 03. Type 01 is the correct form.

@Flickdm Flickdm closed this as not planned Won't fix, can't repro, duplicate, stale Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:needs-triage Needs to triaged to determine next steps type:bug Something isn't working urgency:medium Important with a moderate impact
Projects
None yet
Development

No branches or pull requests

1 participant