Custom Token Replacement in a custom unattend file fails to process
Last Updated February 11, 2019
When you have a custom token for your name or OU placement setup in your custom unattend file you will see that sometime those tokens do not populate, or come out blank and cause the machine to not be setup correctly. You can find this issue by looking at the unattend copied into automation located at \Windows\Panther\unattend.xml.
An issue where it sometimes wouldn't process that section of code when running a deploy.