Based on discussions with the FileExts technical team, the Sysprep copy profile in unattend.xml is indeed not fully supported in this situation. If the copyprofile option is to be used silently, the Wind user or deployment manager must ensure that the target profile is copied as the default profile before running the user’s copy profile.
The copy settings profile runs after the computer was probably removed from the domain during system preparation and the settings configured in the Internet site account were lost. If someone makes changes to a user’s fallback profile and then joins the computer system to a domain, the customizations that your organization made to the default user summary will appear in the new domain data files.
When using CopyProfile, the setup often requires you to use a separate answer to generalize the machine by suggesting sysprep. Note the usage considerations when using CopyProfile: Use only the built-in administrator account on the reference computer.
Here’s how it’s done:
Windows 7: Fatal error when trying to start the machine with Sysprep. During Windows 7, sysprep stops the process with the response “A fatal error occurred while a person was preparing the machine.” The problem occurs when using a response file or reading the Sysprep GUI. From an elevated command prompt, run the sysprep command. The process stops with a large error message.
How do I actually get a sysprep error?
I’m Ahmir, a freelance writer and editor who specializes in technology and business. My work has been featured on many of the most popular tech blogs and websites for more than 10 years. Efficient-soft.com is where I regularly contribute to my writings about the latest tech trends. Apart from my writing, I am also a certified project manager professional (PMP).