http://blogs.technet.com/b/usmt/archive/2008/06/19/why-you-need-to-be-careful-with-c.aspxScanstate and Loadstate both allow the /c switch to be used to skip non-fatal errors.&#160; However, due to the impact that using it can have on a migration, great caution must be used when deploying Scanstate and Loadstate with /c.&#160; To get starteden-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/usmt/archive/2008/06/19/why-you-need-to-be-careful-with-c.aspx#3169317Tue, 16 Dec 2008 01:07:02 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3169317samohtrelhe<p>We DO use /C </p> <p>Mainly because there's non fatal errors on appr. 15% of all exports, but most of them are exactly that; Non Fatal.</p> <p>What we do instead, is scan the log afterwards, before the automatic reinstallation. The machines with errors are then NOT reinstalled until we have checked the logs.</p> <p>Doing it the other way would be an enourmes extra workload, since we would have to rescedule 15% of our exports, and maby even several times, just because of a tedious non significant error. We have 12.000 PC's</p> <p>At the end we redo under 2% of the exports.</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3169317" width="1" height="1">