I'm starting to migrate our users and I have run into a few profiles that will not migrate, yet they have valid 2003 roaming profiles. I receive the following error...
The migration has failed. Log Message: No profiles found for migration
this error can occur, if the profile language could not be determined. Currently we determine the profile language by analysing the directory structure of the profile.
Is it possible, that you have redirected mostly all directories? In this case, the profile does not contain all standard directories so we cannot detemine the language.
The only work around for this case is to manually create the directories via a script.
For english profiles create:
%USERPROFILE%\Start Menu\Programs\Accessories\Accessibility
After the successfull migration, you can delete this folder.
OK, I don't understand something here. When I compare the profiles that did migrate with the ones that did not I don't see a difference in the Start Menu folder structure. None of our profiles have the Accessibility folder, yet 44 out of 50 successfully migrated. When I try to manually create the directory Start Menu\Programs\Accessories\Accessibility via Explorer and then try to re-run the migration I receive the same migration failure message. Perhaps I'm taking you too literally - do I only need to create the one directory? Does the directory need to be created using a script? Does the script need to run as part of the migration process or can the be created via Explorer?
could you please sent us a screenshot of the root directory of a profile that can be migrated and another screenshot of a profile that cannot be migrated?
By the way: The creation must be done via explorer or a script which runs outside Profile Migrator.
Here are the two root profile directories. The Anna.Startzell profile did not have a My Documents directory (and neither do the others that didn't migrate), but when I copied My Documents in from another profile it still would not migrate.
After a webinar with Ned, we found the error. Some profiles had wrong permissions, so Profile Migrator was unable to determine the correct owner.
After fixing the permissions on the profile directory, the migration was successfull.
Microsoft published a web page where it is described how to set up the permissions for roaming user profiles shared folders.