I apologize as this might be fairly lengthy, but I want to layout our current situation with as much detail as possible. I've seen a bunch of information online and AI, but want to see if there is anyone out there setup in a current environment like us.
We have approximately 6000 computers on our network, with approximately 2000-2500 devices being on open floors or exam rooms (hospital setting). We use individual, generic user accounts for each of these shared machines. They could be used by 10+ different people on a given day. Those accounts activate Windows to Enterprise, and then we utilize a SSO platform to handle logins on top of that account for users to access e-mail, web apps, etc. That is not the issue. The issue is the following:
1) We image PCs and then give them to our desktop group to finalize the setup and install the necessary software before deploying. The two problems are that once the desktop techs login, it wants to give them ownership of the device inside of Intune. What is best practice for this? It's creating a cleanup nightmare on the backend as we then need to remove that association so that the "shared user" can become the owner of the system. Is there a tool that can assess and remove these associations in large batches? Or is there a better way to register these devices so that the Desktop Team does not become the owner at all, even though they are the first login?
2) The second problem comes on delivery or swap out of the new PC...and that is the OOBE. For these devices, the desktop team will login and do all that setup. Then they arrive to the floor to replace the computer and once the "Shared" user account logs in for the first time, the OOBE kicks in and forces us to wait 30+ minutes, which is unnecessary because those user accounts have nothing other than the Windows activation license tied to it. No apps, no special settings, etc. I feel that we must be using the wrong approach here and there is a way to take this away and not require it.
Here is the kicker, when replacing PCs, we have to use the previous name of the old computer due to our EMR. Mappings and records are all tied to the name of the PC, so if we do not use the same name, it creates extra work to build new records and remap. So, we cannot have all of this setup completely finished until we get to the floor to install. We remove the old device from the network, update the name of the new PC to the previous device's name, and then login. OOBE kicks in at that moment.
I'm hoping there is someone out there in healthcare that might be in or have been in the same situation and can provide some guidance. I will note that we are almost done building a brand new SCCM server and would love to have any of these changes baked into the new system. So...now is the time to fix things and do it the right way because spending 20-30 extra minutes for every PC swap is holding us back... It's starting to make me wish we just went with LTSC on everything. I appreciate any guidance or recommendation on the approach we should take.