Windows Portable Devices List

[Leroy Turcios]

Thisis a list of all devices coming natively with Microsoft's Windows 10 Mobile operating system. The list also includes devices running two additional flavours of Windows 10 for mobile devices, Windows 10 Mobile Enterprise and Windows 10 IoT Mobile Enterprise. All devices below come with SD card support.

The Microsoft Teams Devices Certification Program ensures certified devices meet a high standard, with higher performance targets and quality metrics across the entire Teams experience (audio, video, user interface). Microsoft and OEM partners are actively working together to ensure devices meet all certification requirements, including security, audio and video quality, Teams experience, and accessibility.

The Microsoft Teams Devices Certification Program ensures certified devices meet specific requirements for hardware design and performance only. The certification program doesn't evaluate feature-level or cloud environment support.

Certified Microsoft Teams Rooms systems are available on both Windows and Android operating systems. Whether you should choose a Teams Rooms system on Windows or Android depends on your specific needs and budget. Select the Teams Rooms for Windows and Teams Rooms for Android tabs for a complete list of certified systems and links to their respective product sites. For additional certification information specific to Teams Rooms for Android see details below.

Numerous certified peripherals, from speakers to microphones and cameras, are available for use with Teams Rooms systems. Select the Peripherals tab for a complete list of peripherals and links to their respective product sites.

The following information pertains to Teams Rooms for Android only.For additional Android based devices that are Microsoft certified, please visit Microsoft Teams certified Android devices.

Certification programs are designed to ensure all certified devices run an Android version with the required feature set for Teams and Teams Admin Center. Certification end dates are based on the Android version running on the device when it enters into the certification program. Our OEM partners are working to extend the lifetime of the certification by upgrading the Android version and recertifying, or by releasing new models that are state-of-the-art.

Microsoft is committed to certifying devices on latest Android versions available for Teams devices as long as OEM partners and SoC manufacturers are able to meet all certification requirements in effect at the time device enters certification.

After certification end date, Microsoft is committed to making efforts to support the most recent version of the Teams client on such devices for two years following the end of the certification period.

Certification end dates are based on the Android version release date plus five years. Once the device passes the certification requirements and OEM partners provide the firmware that enables the upgrade to a newer Android version, the certification end date will be extended to match the new Android OS version release date plus five years.

A consumer TV used as a front of room display needs to support/enable the Consumer Electronics Control (CEC) feature of HDMI so that it can switch automatically to an active video source from standby mode. This feature is not supported on all TVs.

Our network gave an error that there was an IP address conflict and I'd like to find what all the device IP addresses are. (I've also had need of that before). (update/clarification:I'm looking for a Windows-based too.)

You mentioned that a duplicate IP address was identified. Both machines should have generated a warning screen, which should allow you to identify the machines. If DHCP is used, then another request should have been generated and the problem may have self resolved.

What device logged the IP address conflict? Was it a server, router, etc.? Some platforms (Solaris and BSD) will log the MAC address of the offending host along with the error message. If the IP address in question is within one of your DHCP pools, it's also worth checking your DHCP server's logs for the MAC address it's attempting to assign that IP address to.

Failing that, I would recommend logging on to the default router of the subnet that this problem is occurring on, and monitoring the ARP table. There should be one IP address that flips between multiple MAC addresses; again, those two MAC addresses represent the devices you are interested in.

Once you have the MAC addresses of the two devices, you should be able to tie them to specific switch ports. This question provides more information on how to do that. You can also use an OUI lookup tool to help identify the manufacturer of each device.

If you have access to the router that's acting as the default gateway for the subnet in question, then listing the ARP cache on the router (I believe it's just "show arp" on a Cisco IOS device) is the best way to go.

The router arp cache may still not be 100%. It won't show any hosts that haven't communicated within the arp timeout period, or at least that haven't communicated off subnet within the arp timeout period. But in most cases it's much more likely to get you more complete results than any other method.

I suggest using Fing. It's a simple network scanner that is available for Windows, Mac, Linux, and even for mobile devices for wireless networks (Android and iOS devices). And it can easily be used in scripting.

I have a serial to USB device and more than one of those can be connected to the computer. I need to query and retrieve a list of COM ports that the devices are connected to. In Windows Device Manager you can get the COM port + friendly name of devices that are connected at the present time. This list is dynamic.

I had to solve a similar issue just some weeks ago. I came accross the Jawin-Project that provided everything you need to use WMI-Queries. It is already quite old but works like a charm if you follow the documentation. A nice German walkthrough can be found codegods blog.

For me, it did not solve all problems (I had some very specific things to find out about the target device), I finally created an own JNI (Java Native Interface) Class and DLL in C incorporating the windows API.

I am looking at Java Native Access as it provides access to the windows API from pure Java code - no JNI to deal with. I was concerned about the LGPL license; whether it can be included in a commercial product but from what a few posts in the newsgroup say, it can be. After I try it out in the next few weeks, I shall post back here.

Next to "Report Type", select All devices and systemsummary. The printout will contain all the IRQ (interruptrequest) settings, the system resource reports, a list of all devicesand their drivers, and each driver's location on the computer. (If youplan to format your hard drive and reinstall Windows, it is a goodidea to print this first, especially if you have off-brand hardware.)

The Resources tab tells which IRQ the installed device isusing. Another device using the same IRQ can create a conflict, whichmay be why the device is not working. In this case, you can eitherreinstall it with a different IRQ, or change its IRQ. Onlyadvanced users should attempt to change IRQ settings. If thedevice is Plug and Play (PnP), it should not be affected by changingthe IRQ. If the device is not PnP, changing the IRQ may cause it tostop working. Use the instructions above for checking all IRQs in useon your computer, and find an IRQ that is not in use. To change theIRQ, select the Resources tab and uncheck Use AutomaticSettings. In the "Resource settings:" box, double-clickInterrupt Request to bring up a new window with the option tochange the selected IRQ.

Note: If the selected device is a modem ora mouse, the Resources tab will not appear. To check theresources of a modem or mouse, select the Ports option in thelist of devices in the Device Manager. Select the port where themodem or mouse is installed, and then click Properties. Thiswill bring up a Port Properties window with aResources tab, where you can check the resources for themodem or mouse.

Removing a device causes Windows to lose all recognition of it, andthe device will stop working properly. Windows should automaticallyrecognize a new device when it restarts, but this does not alwayshappen. If Windows does not recognize the device, you will need to usethe Add New Hardware icon in the Control Panel for Windows toproperly recognize the hardware. Before removing the device, be sureyou have all the necessary drivers required for the device; this willhelp if you need to reinstall it.

You can manage all your devices from the Workspace ONE UEM console. The Dashboard is a searchable, customizable view that you can use to filter and find specific devices. This feature makes it easier to perform administrative functions on a particular set of devices. The Device List View displays all the devices currently enrolled in your Workspace ONE UEM environment and their status. The Device Details page provides device-specific information such as profiles, apps, Workspace ONE Intelligent Hub version and which version of any applicable OEM service currently installed on the device. You can also perform remote actions on the device from the Device Details page that are platform-specific.

You can view graphical representations of relevant device information for your fleet, such as device ownership type, compliance statistics, and platform and OS breakdowns. You can access each set of devices in the presented categories by selecting any of the available data views from the Device Dashboard.

Select a device-friendly name in the General Info column at any time to open the details page for that device. A Friendly Name is the label you assign to a device to help you differentiate devices of the same make and model.

3a8082e126