We have a Linked Clone pool of 150 PCs. We noticed that the "Run Once" option on various configurations was not working as expected by reviewing the logs.
It seems that the "Run Once" adds a file to the USE\R's \Archives\FlexRepository\XYZ on a PER PC basis...and will not run again on that specific PC.
Am I missing something here?
Example:
you can set a condition for this kind of files, e.g.
Migrate Profiles - Desktop.xml.[*.1]
Hi John,
Can you explain a bit more what you are trying to do ?
Raymond
Sure. We setup a Logon Policy to run a RoboCopy script to migrate the old Persona data to the new UEM environment.
We'd like for it to only run once. eventually, we will delete these jobs, but need a few weeks for everyone to login to the new system.
The files shown above seems to be a marker for each desktop that it is run on...so that UEM knows it has Run Once.
Does that make more sense?
you can set a condition for this kind of files, e.g.
Migrate Profiles - Desktop.xml.[*.1]
Excellent Idea! I turned off the 'Run Once' function, and added a NOT condition on the files created in the folder. Worked like a charm.
Example: VDI_UEMProfiles$\%username%\Archives\FlexRepository\Logon\Migrate Profiles - Desktop.xml.[*.1]
Thanks for the workaround. I'm not sure why the "Run Once" is set to Per Machine", but this work around resolves my issue. Hope it helps others...
Now my data migration from the old Persona to new UEM is smooth. We went from local synced Desktop/Documents...to redirected UEM Desktop/Documents folders, and used robocopy script upon logon to copy the user data.
John
was not my idea, some other people worked on this too.
But one thing: If you turn off "run once", you will not get any of these flag files.
IMHO "Run Once" has to remain checked. The problem will show on new profiles.
Kind regards
Hartmut
Yes, that makes sense, as the "run once" generates the files that I am triggering from.
I realized that while testing, so I checked the box... and the solution is working well for us now.
This is known behavior of the RunOnce option, see appendix E in the UEM Admin Guide for more information on Run Once.
However, the behavior can be changed.
There is a hidden feature to let RunOnce behave differently in combination with a Local User Profie.
To enable this you have to manually add the "runOnceSpecial=1" attribute to the .XML file (for instance the "2nd floor printer.XML")
o Only in effect if run-once enabled, and profile type is local.
o If no 'run once' flag file exists matching '.[L-computername.1]', we check for '.[L-*.1]'.
If match is found, we consider the UEM action as having run before, but we also create '.[L-computername.1]' (in the standard way, so at logoff) to ensure that run-once logic remains working correctly in case the special attribute is cleared later on.
