That is a completely custom task configured in either your boot image or your task sequence and is thus not being generated by ConfigMgr. You need to find the source of this custom task and examine it's rule set and then determine why this rule set doesn't like the model. As noted and to reiterate, this is not in any way ConfigMgr functionality.
To start, you should edit the task sequence being executed and look for any custom tasks near the beginning of it -- this is probably a run command-line task. From there you can examine what this task is running but without knowing anything about it, nothing more can be said.
Alternatively, this could be initiated by a pre-start command which in turn can be configured on the boot image itself or boot media depending on which is used. Same story though that without knowing anything about the custom task being run, nothing more can be said.
If you need further details on editing a task sequence or finding the pre-start command, you can search the official documentation by each the phrase "mem docs" in your favorite search engine along with only key words and phrases like edit task sequence or pre-start command.