Hi Eric,
Sorry for the late respond,
Answer to 1)
We go thru the very normal printer adding process.
Go into Settings -> Bluetooth & devices -> Printers & Scanners -> Add device
then printers with correct names pops up for picking.
then click on Add device for the printer that the user wanted to add.
Printer name still showing correctly until seconds before installation done, then the printer name changed to Model number.
We also tried adding the printer manually (which will require Local Admin credential to continue, that add work load to our IT Admins)
Selecting "Add a printer using an IP address or hostname"
When
Device type: was set to "IPP Device"
Hostname or IP address: entered the Printer's IP address.
Then click on Next
Printer added successfully, and the Printer Name showing correctly.
When
Device type: was set to "Web Service Device" (which is the same type as Adding the printer automatically.)
Hostname or IP address: entered the printer's IP address.
Then click on Next
Then it shows printer added successfully, and asking for Printer name: the pre-filled name is the Printer's Model number.
Then printer sharing option page shows up.
This seems like showing the automatic printer add has some name mapping issue.
I believe the the printer driver used in both method here, adding Automatically and manually with IPP or WSD type, are the same from Microsoft generic driver.
Answer to 2)
I haven't tried install the driver before adding the printer automatically, will try and update in later reply.
Answer to 3)
It happens to all Printers (all our printers are Brother brand), and it happens to all our Windows OS machines (most of them are running Windows 11 pro, only a few running Windows 10 Pro.) Mac users doesn't have this problem.
Answer to 4)
I checked with Brother support as well,
We did updated the Printer name in the printer Web Portal, which doesn't help.
They recommend us to change printer name after adding it, which also will add load to our IT Admin and users.
As from the test we did in Answer to 1), it looks more like a Printer name mapping issue when address Automatically or under WSD type, which Microsoft might be able to fix?
Thanks,