Microsoft
Ok, joining to the domain with all other policies blocked is an option, this may resolve the "slow" issue. But honestly, not every customer of us who is using Teams Rooms, has a software deployment solution like SCCM. And especially for a central meeting room system i don't want to have additional work with feature upgrades. The customers buy such a system to have a stable and user friendly system which is just managing himself as far as possible. Re-imaging with every build of windows is not the solution i think, especially if the have no SCCM.
I found the following article. This looks like it could work even for the 1903 oobe problems.
https://winaero.com/blog/disable-privacy-experience-windows-10/
And the article from MS for the GPO setting is this one, but there is nothing about disabling OOBE.
https://docs.microsoft.com/de-de/microsoftteams/room-systems/room-systems-v2-operations#configuring-group-policy-for-microsoft-teams-rooms
I will try now to set the local GPO on my non-domain joined systems (of course if you have many devices joining the domain and setting gpos is more effective).
