Per-User Data

When using the local install option outlined in the Client Considerations topic, all downloaded information is saved in each user’s local appdata folder (e.g., C:\Users\<username>\AppData\Roaming\ArcFMMobile).

On the staging machine with packages downloaded for the target group, access the ArcFMMobile folder for a user representing the target group. In this example we’re using Karen for the username, i.e., C:\Users\karen1234\AppData\Roaming\ArcFMMobile.
Copy all files from this folder to the distribution folder for the target group.
On all devices for the target group, copy the files from the distribution folder to the AppData folder for all users.
IMPORTANT: After sideloading to a Windows device for using this scenario, the ArcFM Mobile user is likely to receive a notification very similar to "The key is not valid for use in the specified state." The reason for the notification is based on the data.dat file, which contains all the replica information each user needs, in addition to a refresh token that is unique to each user. You do not need to take any action based on this notification.