Thank you. Those are very good points, Raymond.

I tested the profile and package version but became impatient waiting for the profile at "pending install". This took so long that the profile was still "pending install" when its window closed. By comparison, file sync starts essentially instantly on my test device.

Edit: this is the test "window" in time that I am referring to:

Thank you Matt and Raymond,

Matt, I hope you don’t mind if I break down your reply and address some of the sentences in turn…

“Relocation rules can be setup to activate during a certain time.”

They can but they need a trigger condition in addition to the activation time (which isn't a schedule like "daily at 1am" but is a one-off instead). That trigger condition can be either a change of IP address (no use to me) or a change of custom data – i.e. something that my Javascript could change. Please see the attached screenshot.

The thing that concerns me about the dialogue shown in the screenshot (ignore my "group" and "custom data" details for a moment, contextually they’re nonsense I used solely to create the screenshot) is the statement at the bottom “Note: These mappings are only evaluated while the device is connecting. If the device is already online when its address changes, the device must disconnect and re-connect for the relocation to take place.” Does this note - which is clearly written in the context of IP addresses- also mean that the mappings of custom data are also only evaluated while the device is connecting?

 “What you could do in theory is have two Virtual Groups set up with no filter criteria, one for updating the devices and one for staging where the devices don't update. Point your File Sync rule just at the updating Virtual group. Move all the pending devices to update into the staging virtual group and then have a relocation rule that is set up to move them into the update group during your update window at night. Then have an alternate relocation rule that activates at the end of the update window to move them out of the updating group into the staging group automatically.”

Yes, this could work thank you. But wouldn’t filters on the virtual folders themselves, evaluating my “in upgrade window” or “outside of upgrade window” variable be assessed on every collection of the custom data? (Which, in my experience is normally updated on every check-in, although in another thread I believe that Raymond once warned that that per-checkin custom data collection isn’t guaranteed).

“In my experience a File Sync rule that has started on a device will continue on a device to completion even after it is unassigned so any devices in the middle of their download at the end of the window would continue to download the file even after being moved out of the folder. You can interrupt this download however with a restartagent script.”

Useful to know, thanks again. I've already got the following script saved as part of my toolbox of scripts as it's so useful to have to hand: "restartagent --immediately"

==============================

Next question please. Can MobiControl cope with -or at least manage- several hundred simultaneous downloads each of 200MB? I don’t want to overwhelm the cloud servers. I’d also prefer to avoid the syncing excercise going on for several nights in a row, but could live with that if necessary. I am hoping that one of you is a "vetran" of syncing a similarly sized file to a similar number of devices - theoretically simultaneously!