My guess is that when moving the file back to the Server Folder, you are picking up some inherited permissions. In any case, the way you are doing it sounds complicated and potentially problematic. How about doing the migration this way.
1. Add the new distribution folder as a mounted folder on the server.
2. To migrate a qvw, move it from the old server folder to the new Publisher Source folder. Then create a reload and distribute task for it.
What a good idea : making the distribute to a shared folder. I was so silly I had not thought about that and created a batch to copy files from a distribution folder to the remote server.
there are still problems of security .. when data reducing, the document fails to load on the Server.
Copying the version from Source Documents perfectly works ..
There is really a difference between the Distributed Version of the file and the reloaded version. But I dont' see which one..
I'm using DMS security
but I don't want to change the .meta file.
I cannot do a Server distribution because I'm still using QV Server built-in Distribution for some tasks.
So the tasks already migrated to Publisher must be moved manually, not through Server distribution.
The fact that it works when copying the reloaded source documents instead of the same document distributed confuses me ..