 Chuck has a question. Hi, I've been switching new computers over to Microsoft 365 accounts. Instead of setting up a local admin account on the machine, what is the best way to set up a handful of computers without using my login credentials? I know in a domain environment, I would have a domain admin account I could use, but would this work the same if I set up an unlicensed admin user just to set up the computer? I don't necessarily know who will be using the computer right away, but want to get a jump start on setup so I can hand the device over and they can just log in. I'm confused what they mean by unlicensed user because in the setup of a machine, there's no license involved. Azure Backup Recovery isn't limited. You're limited by a number of objects to what? I think it's like 900,000 now or something like that. I don't know. That should not be an issue. If he wants to go ahead and he wants to set these things up clean, oh, I'm sorry. The name on this was Chris, maybe it's a she, I don't know. Chuck. Oh, Chuck. Well, that's probably definitely a guy. It could be a girl, I don't know. But if they want to set it up so it looks like nobody's even touched the thing and they treat it like shrinkwrapped where basically you just ship them a machine. They can do Azure Active Directory domain join, right? So you set up a domain in Azure Active Directory and then anybody who opens up a machine can join that domain without any admin ever logging into it. Now, if they want to preconfigure the machine and then ship it to the user and not have that admin on there, there's something called autopilot. So you use autopilot to preconfigure the machine. There has to be an administrator. I say this for two reasons. Number one, there has to be an administrator of user because you don't want a machine. I apologize for the talk. You don't want a machine not having an admin user. You have to have a backdoor. And especially if you're managing these machines, if you're going to manage them through Intune, Intune requires it, all right? There's no doubt about it. You have to have it. So but what Autotune can do is autopilot can do is autopilot can actually hide that other user. So the regular user won't see it, right? It won't show up as an extra icon. It won't show up as an extra login, anything like that. The user will just be able to once they get the machine, they turn it on. It's preconfigured by the IT folks with all the apps and everything else. And they basically, they get what they call, is for many known as an out-of-box experience and an OBE experience. And it goes through the whole, you know, little setups and things like that, like, you know, setting up your language and your keyboard and your things like that, you know? And then they just, it comes up and asks you to log into Azure AD and to your Microsoft account. And the user doesn't know anything about a pre-configuration except when they finally get to the desktop and they see, oh, there's my, you know, work app. There's my other work app. There's all the stuff is preconfigured and pre-installed. I'm doing this exact process at the moment where the end user had to do all that pre-build that autopilot process themselves. It's not the, you know, it's literally from that out-of-the-box. And I created a guide, quite a long sort of extensive guide of what it goes through in the tick, tick, tick, tick, you know, of building the device. And they're a little overwhelmed with it because they feel like they're building a laptop and they have this guide that was sort of seven pages long just with screenshots showing them what it looked like. And, you know, some of the pushback that's going on is like, no, and then there's, if it takes just that little bit too long, there's this failure that was sort of happening. So what was supposed to take a really short period of time, you know, 15, max 20 minutes could be taken two hours because they were having to restart. And then it was taking them three and four and sometimes all day because it was having these fails. So therefore it looked like the end user was having a dreadful experience. It was just that one little component take too long. So it had a class as a fail. So, so from the end user perspective, they didn't know what they were doing freaking out. So it's like, right, no, the organization needs to do that pre-build exactly what you were talking, Mike, with the, that incident back end and building. And then all they had to do was the end experience where they, all they do is walk up, type in their email and then just go through and put in your PN, your facial recognition straight in. It does the initial, you know, like you would at home, the high we're getting your device, you know, your device ready for a window, blah, blah, blah. And it was a really simple process. And we saw such a shift from the behavior from one to the other of the panic from an end user perspective. So it comes down to, well, who are you trying to do it with as well? You know, because you could really overwhelm the user and we've got, I had to can all of that last minute, literally two weeks prior to roll out where everything was all sorted and all the guides to redo all the guides, still finalizing the guide right at this moment. And we go live in a week's time. So desperately, and we've got to get them printed. But we had to, we had to change it because it was just too overwhelming for an end user. So did I take them into, take whoever you're working with into account when you go to do this process? I think that, I mean, the question here for Chuck is, I mean, my assumption that this is a small organization, so they're not to the point where they're creating like a, you know, a series of pre-built laptops that are ready to go out to, it's like a regular onboarding process. This is a, you know, smaller organization, but there's got to be a better way to do that. Even it's like five machines for five people versus, hey, I do five a week. This is part of my job to do this. Yeah. Yeah, and I would say that, I mean, if some folks don't want to go with the autopilot route because the autopilot is, to me, there was a simpler solution back in the day, which was in Teflon Go, something called the MDT, which was a Microsoft deployment toolkit. And that actually you could do that locally or you could have a user's computer halfway across the world connect to an MDT server on the internet and then download the entire hard drive image to that computer. And the MDT allows for that. So good example is a user, you know, the hard drive dies or, you know, something happens where their hard drive gets corrupted and won't boot. MDT, if you're gonna get them back up with a actual bootable USB or a live DVD, CD, DVD. MDT, then they can connect to that server and then basically it just streams the entire image across the internet. It takes a while, obviously, but it's a full repair process. I mean, it's a full self-service type of process that can be done through that. Autopilot is actually much more advanced in terms of works with Azure and things like that, but MDT is, Autopilot is actually kind of outlined around MDT, so. So MDT is not available anymore then? Oh, there it is. So there's no, or there it is? Yeah, yeah, MDT is still available. It's part of the ADK, the development kit for Windows 10 and Windows 11. So MDT is still available.