This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
How can I deploy a default Normal.dotm (custom default colours) to users so that it is not overwritten the first time Word (2013 or 2016) is run?
I've tried setting the MigrateNormalOnFirstBoot registry key but it doesn't seem to make any difference and Word still overwrites the Normal.dotm file on first-run. If I overwrite the file after first-run, it works fine, but I need the file to be available from the first time users open Word as doing it after the fact requires Word to be closed.
Any assistance would be appreciated.
Thanks,
Steve.
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
You may be more likely to get assistance with this issue if you post to
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=word
To the best of my knowledge, this is not possible with any Microsoft deployment tools (MDT\SCCM), and certainly not without being certain of both the user for whom every given machine will be imaged for and their password, which is not practical when deploying significant numbers of systems.
Won't work, as per my post, the file gets overwritten the first time Word is run. I can add it to the Default User profile and the file is copied to the user profile when created, when Word is first run however it recreates the file. The file is perfectly valid as I can overwrite it _after_ first-run and it stays there and works fine so it's not a corruption issue.