Device ID - Revision history

KGR at 09:01, 11 March 2026

2026-03-11T09:01:39Z

CWI: /* Android */

2025-09-25T13:44:28Z

‎Android

CWI: /* Mobile {{Version/XamarinSince|1.1}} */

2025-09-25T13:39:54Z

‎Mobile {{Version/XamarinSince|1.1}}

CWI: /* Mobile {{Version/XamarinSince|1.1}}{{Version/MobileSince|5.0}} */

2025-09-23T13:21:08Z

‎Mobile {{Version/XamarinSince|1.1}}{{Version/MobileSince|5.0}}

CWI: /* Windows */

2025-09-23T07:58:55Z

‎Windows

CWI: /* Mobile {{Version/XamarinSince|1.1}} */

2025-09-22T13:34:18Z

‎Mobile {{Version/XamarinSince|1.1}}

CWI at 13:25, 18 September 2025

2025-09-18T13:25:08Z

CWI at 10:10, 18 September 2025

2025-09-18T10:10:13Z

TSI at 17:12, 21 January 2021

2021-01-21T17:12:10Z

MKR: Added 3.8 flag and fixed small spelling and formatting things

2021-01-21T11:16:27Z

Added 3.8 flag and fixed small spelling and formatting things

@@ Line 1: / Line 1: @@
-[[File:deviceid_uwp.png|thumb|350px| Device ID on UWP Client]]
+[[File:DeviceID_WinX.png|thumb|350px| Device ID on UWP Client]]
 The Device ID is a unique identifier of the device, which is fetched from the OS and used to uniquely identify devices to [[HowTo:Restrict_Access_to_known_Devices_(Satellites) |restrict access]] to them. The type of ID and its origin vary by platform. The Device ID is also sent to the Ubik Web Service.
@@ Line 12: / Line 12: @@
 <gallery widths="220" heights="360">
-File:deviceid_xamarin.png| Device ID on Mobile Client
+File:DeviceID_MAUI.jpeg| Device ID on Mobile Client
 </gallery>
-[[Category:Android|Device ID]]
-[[Category:Device management|Device ID]]
-[[Category:Hardware|Device ID]]
-[[Category:Mobile|Device ID]]
-[[Category:WinX|Device ID]]
 == Technical Information ==
@@ Line 34: / Line 34: @@
 If a system does not have a TPM or UEFI support, and thus an ID was obtained from the registry, a clean install of Windows will result in a new, different ID being returned. If no ID could be generated, the old ASHWID identifier is used.
-[[Category:Android|Device ID]]
-[[Category:Device management|Device ID]]
-[[Category:Hardware|Device ID]]
-[[Category:Mobile|Device ID]]
-[[Category:WinX|Device ID]]
 === Android ===
@@ Line 47: / Line 47: @@
 Version 1.0.80 of the Mobile Android app based the device ID onto the [https://developer.android.com/reference/android/provider/Settings.Secure#ANDROID_ID ANDROID_ID (SSAID)], in the same way to how the native Android client does it. This also removed the need for the <code>READ_PHONE_STATE</code> permission. This method now also works for Android 10+, even for unenrolled devices.
-[[Category:Android|Device ID]]
-[[Category:Device management|Device ID]]
-[[Category:Hardware|Device ID]]
-[[Category:Mobile|Device ID]]
-[[Category:WinX|Device ID]]
 === iOS ===

@@ Line 41: / Line 41: @@
 === Android ===
-On the native Android client, the [https://developer.android.com/reference/android/provider/Settings.Secure#ANDROID_ID ANDROID_ID (SSAID)] is accessed. Before Android 8, this ID was bound to a device for its lifetime. Since Android 8, the ID is different for every user (if the device has the multi-user feature enabled) and when the device is reset.
+On the legacy native Android client, the [https://developer.android.com/reference/android/provider/Settings.Secure#ANDROID_ID ANDROID_ID (SSAID)] is accessed. Before Android 8, this ID was bound to a device for its lifetime. Since Android 8, the ID is different for every user (if the device has the multi-user feature enabled) and when the device is reset.
 On the Mobile Android app, before version 1.0.80, depending on the version of the OS, the [https://developer.android.com/reference/android/os/Build#SERIAL Build.SERIAL] is accessed (below Android 8), and [https://developer.android.com/reference/android/os/Build#getSerial() Build.getSerial] starting with Android 8, also requiring the <code>READ_PHONE_STATE</code> permission. With Android 10, the function only works for devices enrolled in an organization.
 Version 1.0.80 of the Mobile Android app based the device ID onto the [https://developer.android.com/reference/android/provider/Settings.Secure#ANDROID_ID ANDROID_ID (SSAID)], in the same way to how the native Android client does it. This also removed the need for the <code>READ_PHONE_STATE</code> permission. This method now also works for Android 10+, even for unenrolled devices.
 === iOS ===
 On iOS, the application makes use of the [https://developer.apple.com/documentation/uikit/uidevice/1620059-identifierforvendor identifierForVendor]. This is a GUID uniquely identifying a device to an app vendor.

@@ Line 12: / Line 12: @@
 <gallery widths="220" heights="360">
-File:deviceid_android.png| Device ID on legacy Android Client
+File:deviceid_xamarin.png| Device ID on Mobile Client
-File:deviceid_xamarin.png| Device ID on Mobile (Xamarin Android) Client
 </gallery>

@@ Line 8: / Line 8: @@
 === UWP ===
 On the Windows client, the Device ID can be accessed on the Connection Settings page.
-=== Mobile {{Version/XamarinSince|1.1}}{{Version/MobileSince|5.0}} ===
+=== Mobile {{Version/XamarinSince|1.1}} ===
 On the newer Mobile clients (iOS and Android), the Device ID can be inspected on the General Settings page.

@@ Line 25: / Line 25: @@
 The Device ID should be unique enough to exclusively identify a device/client and shouldn't get lost if the app updates.
 === Windows ===
-This information applies both to the UWP/WinX client as well as the unreleased Mobile UWP client:
+This information applies both to the UWP/WinX client as well as the unreleased Mobile Widows client:
 In the UWP/WinX client until version 3.7.17, the Device ID is created using the [https://docs.microsoft.com/en-us/uwp/api/windows.system.profile.hardwareidentification.getpackagespecifictoken ASHWID identifier] encoded to a Base64 string. This ID is relatively consistent but can change when e.g. a docking station with a network card is attached.
@@ Line 34: / Line 34: @@
 If neither of these sources is available, this method will return an ID that is backed by the Windows registry.
 If a system does not have a TPM or UEFI support, and thus an ID was obtained from the registry, a clean install of Windows will result in a new, different ID being returned. If no ID could be generated, the old ASHWID identifier is used.
 === Android ===

@@ Line 21: / Line 21: @@
 This information applies both to the UWP/WinX client as well as the unreleased Xamarin.UWP client:
-In the UWP/WinX client until version 3.7.x, the Device ID is created using the [https://docs.microsoft.com/en-us/uwp/api/windows.system.profile.hardwareidentification.getpackagespecifictoken ASHWID identifier] encoded to a Base64 string. This ID is relatively consistent but can change when e.g. a docking station with a network card is attached.
+In the UWP/WinX client until version 3.7.17, the Device ID is created using the [https://docs.microsoft.com/en-us/uwp/api/windows.system.profile.hardwareidentification.getpackagespecifictoken ASHWID identifier] encoded to a Base64 string. This ID is relatively consistent but can change when e.g. a docking station with a network card is attached.
-{{Version/WinXSince|3.8}}
+{{Version/WinXSince|3.7.18}}
-Starting with UWP 3.8, the [https://docs.microsoft.com/en-us/uwp/api/windows.system.profile.systemidentification.getsystemidforpublisher SystemIdentification.GetSystemIdForPublisher()] method is used to return a unique system identifier based on the app publisher ID.
+Starting with UWP 3.7.18, the [https://docs.microsoft.com/en-us/uwp/api/windows.system.profile.systemidentification.getsystemidforpublisher SystemIdentification.GetSystemIdForPublisher()] method is used to return a unique system identifier based on the app publisher ID.
 The ID is generated either using a Trusted Platform Module (TPM) if present or a Unified Extensible Firmware Interface (UEFI) if present.
 If neither of these sources is available, this method will return an ID that is backed by the Windows registry.