I'm just on a call with Michael right now discussing the video and getting him to work.

Alright, I haven't heard from TCC. I followed up with TCC. Nobody's getting back to me about the Wi-Fi. It's going to cause a bit of an issue. But, anyways, I have a solution because we have a spare router now from Kenville Farm. I'm going to try to set up one of those routers using a unique Wi-Fi name. And then I'm going to have to create a deployment so that we can deploy our own profile before logon. This is necessary so that I can have remote access into the system before somebody logs in. And so the user can log in because Microsoft has recently deemed that WPA2 Enterprise is insecure if it's not using a certificate-based authentication. And so they have blocked it in system-wide deployment and installation unless we turn off credential guard, which is a whole different problem on its own. But we don't want to do that, so we're not going to do that and risk more security, which Microsoft is stupid. Anyways, long story short, I'm going to set up that router. And we're going to just leave it in magenta, and it'll use that for pre-logon. Because, again, it is needed for people to be able to authenticate. A computer needs an internet connection. And I need to write a script after that. We'll check if TCC client is available and if we are connected to whatever I named that new Wi-Fi. Probably magenta pre-logon or something. I don't know. And I'll have to deploy an app that will check if we're connected to magenta pre-logon and TCC client is available. And if that's the case, then we will switch. We're going to prompt the user in an annoying fashion every five minutes with a pop-up that, hey, you got to switch to TCC client. Because that's going to be the instructions that we need to do. So that's the only workaround that I have right now. And we'll make it work with TCC's help.