Sprint 3 Outline - brian-anderson01/Capstone GitHub Wiki
Overview
The main purpose of sprint 3 is to research and use Intune autopilot. Along with autopilot I would like to dive deeper into Intune and explore what else can be done with it. The main goal with using autopilot is to be able to deploy a new computer and have it join the domain, enroll into Intune and have access to the VPN and file shares all automatically. I would also like to look into how Azure VMs interact with a hybrid domain. I wan to see if joining my local domain from an Azure VM is possible. If it is, I will also look into testing autopilot on Azure VMs.
Objectives
- Research how to setup and use Intune Autopilot
- Research Azure VM implementation into a hybrid domain
- Configure autopilot and test that it works
- If applicable, test autopilot on Azure VMs
- Research what else Intune can do and add to this sprint
Tasks
- Research Intune Autopilot setup and deployment
- Research Azure VM compatibility with hybrid domain setups
- Research what else Intune can do and add to this sprint
- Setup and configure autopilot to join domain, Intune enroll etc.
- Test and confirm autopilot works on local computers
- If possible test and confirm autopilot works on Azure VMs
Sprint outcome
Now that this sprint has come to an end, I can share what was completed during the sprint. I got the Intune Connector for Active Directory installed on the DC. I also configured the necessary settings on the DC to make Autopilot domain join possible. After that, I configured Autopilot on Intune and had to configure quite a few settings for that. Once all of that was done I went to test Autopilot and it worked, except for the domain join. I spent the entirety of this last week troubleshooting the issue. As seen in my demo, I eventually got domain join with Autopilot working and all of the Intune profiles also worked. The only thing I was unable to get done this sprint was getting the Azure files PowerShell script setup, which I plan to do next sprint.