MicrosoftDaniel Jelinek, Harald Rau I would advise you NOT use the OS pre-installed on the units. Who knows what is going on, for instance we received one unit that was pre-configured for another organizations domain! You should re-image, and if you do not have an imaging solution you can use the Installation Media Script to create a flash drive for installation found here: https://docs.microsoft.com/en-us/microsoftteams/room-systems/console#Reimage
The script includes a sysprep answer file that disables OOBE user mode, which bypasses all those questions you are being asked about pen, location etc. Sysprep is the only way I know of to get rid of those messages. You can see this by looking at the answer file included on the Flash Drive Imaging solution. Although Feature updates are supported, I have been re-imaging them, the beauty of SCCM, a few clicks and 80 minutes later the units are re-imaged, then all I have to do is sign into all of them.
IoT is only support if it is Enterprise, we just use Enterprise (not IoT Enterprise) which has been solid for us, so make sure that is the case. IoT LTSB for instance is not supported as noted here: https://docs.microsoft.com/en-us/MicrosoftTeams/room-systems/srs2-lifecycle-support
If the units are slow after joining your domain it is most likely because other group policy settings are hitting the unit that should not, or you have other issues with your domain. These units should be placed in an inheritance disabled OU, so they do not get any GPO's that they should not. Also your Default Domain policy should be minimal, as these settings will still hit the units. We additionally set up QoS settings to ensure the units have network priority over other devices on the network.
I searched, but cannot find the GPO settings recommended for the units, Maybe Sohail_Tariq or Ilya Bukshteyn could point you to the correct article regarding GPO's? But I got them from a MS article. They include auto admin sign in, and power settings etc.
I hope this helps guys! Good luck!
