Delay in creation of Flag File

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   We tried to migrate users last night and had a mixed result.

Some of the issues are creations of our own making, but one of the issues we experienced is that in our deployment we were checking for the flag file to say that the machine had been migrated successfully.  The problem was that if the file was not found we stopped the deployment (migrating from Novell) and then had computers in a "semi migrated" state because the Novell DLU had not been disabled because the deployment had been stopped.

Our check for the file occurs when the "exe" is finished running but found that on some occassions the flag file is not created until about 20 - 30 seconds later therefore causing the misbelief that the migration had failed.  We assume this because of the time stamps on the files ont he local machines of the files.

Can someone please advise whether this is by design or should the file be created prior to the "exe" finishing? 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
tmruser Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 03 Feb 2013 Location: Australia Status: Offline Points: 3	Post Options Post Reply Quote tmruser Report Post Thanks(0) Quote Reply Topic: Delay in creation of Flag File Posted: 19 Feb 2013 at 11:14pm
	We tried to migrate users last night and had a mixed result. Some of the issues are creations of our own making, but one of the issues we experienced is that in our deployment we were checking for the flag file to say that the machine had been migrated successfully. The problem was that if the file was not found we stopped the deployment (migrating from Novell) and then had computers in a "semi migrated" state because the Novell DLU had not been disabled because the deployment had been stopped. Our check for the file occurs when the "exe" is finished running but found that on some occassions the flag file is not created until about 20 - 30 seconds later therefore causing the misbelief that the migration had failed. We assume this because of the time stamps on the files ont he local machines of the files. Can someone please advise whether this is by design or should the file be created prior to the "exe" finishing?

Support Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Status: Offline Points: 1860	Post Options Post Reply Quote Support Report Post Thanks(0) Quote Reply Posted: 20 Feb 2013 at 3:55am
	The flag file is written by the migration script, not by User Profile Wizard. Its only purpose is to prevent the migration script being run again on the same machine. Which “exe” file are you monitoring? If you want to coordinate disabling DLU with the end of the migration process, you could do that either by modifying the migration script (which checks the return value from Profwiz.exe) or from a follow-on file. The follow-on file only gets run if the migration is successful.