Custom Token Replacement in a custom unattend file fails to process

book

Article ID: 173502

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

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.

Cause

An issue where it sometimes wouldn't process that section of code when running a deploy.

Resolution

For 8.5 apply TECH251651
For 8.5 RU1 apply INFO5299

Fix will be included in 8.5 RU2 code.