question

GrzegorzKostya-5353 avatar image
0 Votes"
GrzegorzKostya-5353 asked SimonRenMSFT-3639 commented

MDT doesn't process rules other than [DEFAULT] at first.

Im trying to set up MDT that will apply specific tasks for specific machines based on their MACs. The problem is it looks like MDT skips MACAddress rule totally and process only Default one. If I check box to process rules with Gather during task sequence I can see in BDD log that they are easily processed. Here is my customsettings.ini Any ideas what i'm doing wrong?

[Settings]

Priority=MACAddress,Default

Properties=MyCustomProperty







[00:00:00:00:00:00]

SkipWizard=YES

TaskSequenceID=TEST01



[11:11:11:11:11:11]

SkipWizard=YES

TaskSequenceID=TEST02



[Default]

OSInstall=Y

SkipCapture=YES

SkipAdminPassword=YES

SkipProductKey=YES

SkipComputerBackup=YES

SkipBitLocker=YES

SkipBDDWelcome=YES

SkipUserData=YES

SkipLocaleSelection=YES

KeyboardLocale=en-US

UserLocale=en-US

UILanguage=en-US

SkipTimeZone=YES

TimeZoneName=Central European Standard Time

SkipDomainMembership=YES

SkipComputerName=Yes

OSDComputerName=TestMDT

JoinWorkgroup=WORKGROUP

SkipSummary=Yes

EventService=http://WIN-TT6S3UDMUKI:9800

mem-mdt
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SimonRenMSFT-3639 avatar image
0 Votes"
SimonRenMSFT-3639 answered SimonRenMSFT-3639 edited

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

1,Per my experience, let me suggest using the MDT database to control your deployments firstly, not the customsettings.ini. We could add a computer to the database that will be identified by the MAC address and assign the TaskSequenceID/ComputerName etc. parameters. For more detailed steps, please refer to:
MDT: use with a database
Use the MDT database to stage Windows 10 deployment information

2,==>If I check box to process rules with Gather during task sequence I can see in BDD log that they are easily processed.
Do you mean if you set the option to "Gather local data and process rules" and left the rules file blank in Gather task sequence step, MDT will apply MACs-based tasks and work as expected? If yes, it may be the designed behavior per the official document.

When we are performing a zero touch installation (ZTI) with Configuration Manager, the steps would be similar to LTI but we would need to add a Gather step to read customsettings.ini at the beginning of the task sequence. Select Gather local data and process rules and on the Rules file field, type CustomSettings.ini or left blank. Please refer to:

Manage your Windows 7 deployment with MAC Addresses
Task Sequence Steps

187379-rules.png

Thanks for your time. Have a nice day!

Best regards,
Simon


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



rules.png (55.9 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GrzegorzKostya-5353 avatar image
0 Votes"
GrzegorzKostya-5353 answered SimonRenMSFT-3639 commented

Well I found what was the problem but I have different one now. It looks like that when winPE loads it doesn't recognize my PCI LAN card. Still gather scripts during task sequence have no problem with that. When i swapped to built-in lan winPE goes straight into task sequence based on mac address. The problem is I need it to work with external LAN cards.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @GrzegorzKostya-5353,

Thanks for your reply. Could we firstly complete the OS deployment and then add the external LAN card?

Thanks for your time. Have a nice day!

Best regards,
Simon

0 Votes 0 ·

Our mobos are engineering samples and we are flashing "blank" BIOS into them even few times a day. Everytime it's done MAC adress is changed to somehting like 88:88:88:88:88:88. Obviously we can change it with hex editor before flashing chip but that would add a lot of work for us. Then we are using them for automatic tests based on os deployment. For me it looks like Gather doesn't recognise network adapter at start.
First gather:
<![LOG[Getting network info]LOG]!><time="08:28:06.000+000" date="03-30-2022" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property definition is now = BDD_Welcome_ENU.xml]LOG]!><time="08:28:06.000+000" date="03-30-2022" component="Wizard" context="" type="1" thread="" file="Wizard">


And the one in task sequence looks like that:
<![LOG[Getting network info]LOG]!><time="08:29:21.000+000" date="03-30-2022" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Checking network adapter: [00000001] Intel(R) Gigabit CT Desktop Adapter]LOG]!><time="08:29:21.000+000" date="03-30-2022" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">

0 Votes 0 ·

Hi,

Thanks for your reply and information.

It's really a strange issue. I will do more research about it, if there is any update, I will let you know.

Thanks for your kindly understanding. Have a good day!

Best regards,
Simon

1 Vote 1 ·