Oh, my mouse froze there. Anyways, I just got off the phone with the OCA not too long ago. Completely forgot what was on my mind. Got off the phone with the OCA, Max asked me to order some supervisor logbooks, Chris suggested that I call the OCA because they might have access to that, they did in fact have access to that. So I ordered, Max needed for himself, for Evan, Ryan and Chris, he needed four, I ordered five just to have one as a backup in the office in case we need it for somebody else or for whatever reason. While I was on the phone with them, I asked them about the login and tried to familiarize myself really quick with what is there. I ended up removing Amber, Cole and Jake from the account who were on there and we changed Troy from being the admin to Master Account Holder being the admin, I confirmed the email and created a password and added the login information to Hoodoo so that we can manage it. I also created a portal access for it and I added Troy for documentation purposes over there and had to figure out how to add users which is through a link that the person supplied, I bookmarked that as well in Hoodoo in the password page over there.

I'm at a bit of a crossroads with what I'm going to do right now. I do know what I should do, so I'm going to do that. I'm going to go back to the Entune setup for the computers, and I have to reach out to this guy about the phones, because this is getting pretty stupid.

Just finishing now. Spent most of the day working on a script to automate the autopilot setup. I got most of the downloader done today. There's some permission issues that I'm having with the directories. So once I've done that, tomorrow I'm going to make the script to rename the computer. Well, to do a lot of things, I'm going to have to generate a hardware hash off of that that we're going to have to store. So I'm going to have to create a whole separate system for that as well. I'm going to have to create a database with hardware hash computer information. I could see if this integrates with Hoodoo, but it's very, I mean, it is maybe possible that I could make it integrate with Hoodoo, but the computer wouldn't be added in before. So no, we would have to be a separate database that would store the hardware hash and any kind of assets that we assign to like license keys for Windows, et cetera, would be connected to that.

once I... so part of that script is that it'll have to detect the hardware hash it'll have to send it to an API endpoint which I have ready but I have to do the whole hardware hash script then it has to send it there I have to make a receiver at a database and pretty much make the script check if it's already been added in there I will have to actually create another script in Hoodoo to see to get the device hardware ID so I'll have to make a separate PowerShell script for that and execute that to get the hardware device IDs and then I'll have to add the existing ones into the database and their corresponding computer names and if they have computer any kind of licenses or anything and yeah

And then after that, what I'll be able to do is get that information back in a JSON and automatically apply the name if it's been there so we could have permanent computer naming convention. And then if the Windows edition is Windows Home, then it will check if there is automatically a key associated with it and do the upgrade. If there isn't a key, then you know we'll have to enter a key. And after those two things have been done, I think it's going to be ready for enrollment. And then I'm gonna have to create an API connector. I have to figure that out to connect our service with Azure. And then using the graph API or something, I'm gonna have to enroll the computer into Autopilot and trigger it. I feel like this is probably two more days that I'm gonna have to work on this. But once that's done, Autopilot will be ready to go for new systems, for formatted or new systems.

For old systems, I'm going to have to do an adoption script, but I think I could run that script from PowerShell. Pretty much that script will just run the same thing that we have, that I'm going to be building right now, except it's just going to report to, just do the registration with the Azure. So it's only going to do the last step, the last portion of it.

after that the new computers anyways will be enrolled in autopilot and old computers will be enrolled but not using I will have to do I don't have to do an adaption script actually for non-domain joined computers I could do all that manually and to be honest it will be better just to probably get people to back up their data clear the computer well enroll it in autopilot clear the computer restart it and have it fresh but I'll have to see anyways Caroline is it wants a different computer anyways so half the battle is kind of down but anyways I'll have to figure that out on a different day but yeah looking pretty good and then the scripts that I've done they're one-liners so they're actually gonna be really good for for using and automating different things that we have to do on the computer

Once the autopilot is done, computers will automatically enroll into a domain joined environment and that's pretty much it. And then it's just going to be bit by bit adding software into Intune. The issue that I'm going to have with Intune is that I think we're going to do the version management outside of it in Action 1 because it just seems to do a little bit better at managing it. Intune actually kind of sucks for packet management. It's nice to install default apps, but it's not nice to install one-off apps. So if we have a group of people that are going to use the software, and specifically because we do have Company Portal as well, which is going to be available, then that's going to be a nice feature where people will not be searching around on the internet to download things. They'll just go to Company Portal and that will allow them to download and install.

There it is, I'm done for today.