Haven't figured out how to implement sites yet. To create a user attribute, most of the documentation speaks giving the  Device Attribute a name that agrees with the device attribute name in the registry of the operating system that is installed on the device, ET1 has no registry so not sure how to implement this on Android. We'll be staging devices in a Central facility then sending devices out in the field where the ET1 will be expected to check in with a new relay server.  Once the device hits the store we'll need to have the store scan a new RD profile to set the new Relay Server, during this I can add a setting to the Profile to set the TZ, each site will have a unique staging profile.

Create a site for each store. Having sites is always a good idea. Assign store relay server to the site, set site type "both". Create a number of Control.DateAndTime (if you're using this control module) or Timezone settings objects with proper timezones. Assign them to sites as Additional Attributes as required. Specify store site as Production Site in your staging profile. Stage. Enjoy. Recommend attending AAL1700 and AAL2700 trainings on MSP Core functionality, available at learning.motorolasolutions.com - this scenario is covered there (well, not exactly this, but very similar :) ).

John; There is no way to automatically and dynamically define the time zone because it is something you cannot know without know where a device will be used.  If a device is on WWAN, it may get time zone from the carrier.  But if the device is on WLAN, there may be no easy way to determine the time zone.  The most common way I have seen this done is to base the time zone on the Site.  In many cases, you will be able to define that each Site resides within a specific time zone and hence the devices assigned to that Site can be inferred to be at that same time zone.  If you are using MSP 4.0, you can use a Site Attribute to assign a time zone value to each Site and then make the time zone in the DateAndTime Settings Object depend on that Site Attribute.  Then, as long as you set the values properly (see the table which provides the values for each time zone), it ought to work.  Another way it is commonly done is to use a separate TimeZone Setting that is defined as an Additional Setting for each Site and which is inhereted from the Site during Staging. Allan