Sideload Data to Windows Devices
The methods to sideload data are dependent upon the installation method you chose after reviewing the Client Considerations topic. There are two things you should know before reading further:
-
If you are not using the shared data approach, all downloaded information is saved in one location, per user, on the device. Only the user who downloaded the data has access to it; additional users need to perform a download of the same data to have access to it.
-
If you are using shared data, all downloaded information is saved in a location (different from the location above) that all users of the device can access.
Per-User Data
- 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.
Shared Data
- On the staging machine with packages downloaded for the target group, access C:\ProgramData\Schneider_Electric\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 ArcFMMobile folder.