Path > 256 FixIf your help file contains very long folder and file names, and your "Output staging folder" is also a long path, then you may see problems. This is because Windows prefers paths <= 256 chars. Previously mshcMigrate stopped Migration with a "file not found" error popup. In build 61 we now work-around most of these 256 path issues. No more batch stopping popups. However our 3rd party ZIP code does required paths < 256 chars. So if you see "File name too long" errors in the log file, please choose a shorter "output staging folder" path. 2 New Batch Command - CopyTo=, DeleteAfterCopy=Some issues have come to our attention:
Build 61 now has two new batch commands. CopyTo=c:\Path\
Batch Mode - Best PracticeThe original idea with mshcMigrate was that you could specify the "Output staging folder" once, and use that folder for all your migrate jobs. Each time you perform a Migrate, the job output is stored in a single folder under the Staging folder. If you run several Migration jobs we recommend the following.
Note: DeleteAfterCopy= command successfully removes all files but can leave a few stubborn folders. This is why we recommend you run DEL in recursive mode to clean up any remaining temp folders. Once mshcMigrate.exe shuts-down, the stubborn folders will delete without a problem. |
Blog >